Closed Bug 1554314 Opened 5 years ago Closed 3 years ago

Deploy desktop startup recorder (fxrecord) to Toronto Office

Categories

(Infrastructure & Operations :: RelOps: General, task, P1)

Product:
Infrastructure & Operations
Component:
RelOps: General
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: plawless, Assigned: barret)

References

Details

This is to track the set up we discussed a couple of weeks ago (sphilp, sdonner, dhunt, rwood).

Hardware:

Further details about the set up can be found in this doc: https://docs.google.com/document/d/1TFwg1-vxeRcKNiJq-tL8RTx9EQHd4gurdB3k663hj1g/edit#heading=h.j48ksahnrl0m

Let me know what else you need from me.

Thanks for filing this Patricia- in the document describing the setup, there is a server for referencing content/test controller- is this any machine that we need? Are there requirements for that machine?

Flags: needinfo?(plawless)

:tarek, is this a similar setup to what you are experimenting with for video playback?

Flags: needinfo?(tarek)

Yes, except that I am trying with this capture device : https://www.amazon.fr/gp/product/B07DHDHLYQ (I received it today!)
it can do 4k30fps and 1080/60fps.

I will start to play with it this week and can report back

Flags: needinfo?(tarek)

Hi Joel,
I believe the server (test runner) can be any Windows machine capable of running the video capture software.

Mike - is that right?

Flags: needinfo?(plawless) → needinfo?(mconley)

(In reply to Patricia Lawless from comment #0)

Is this particular device a hard requirement or do we have some flexibility? 4gb of memory and Celeron means it's going to be a bit slow, both in terms of running tests but also for general management of the system which in turn leads to longer downtime between testing, etc.

Just one of them?

(In reply to Patricia Lawless from comment #4)

Hi Joel,
I believe the server (test runner) can be any Windows machine capable of running the video capture software.

The test runner can really be anything that can run the capture device's software. Preferably, the capture device drivers can be invoked using script to get the recordings. The test runner just needs to be powerful enough to record the frames without dropping any.

There's the analysis step as well, which might use a tool I wrote called croptop1, unless PI comes up with something better (which is maybe preferable). That runs in a web browser.

(In reply to Kendall Libby [:fubar] (he/him) from comment #5)

(In reply to Patricia Lawless from comment #0)

Is this particular device a hard requirement or do we have some flexibility? 4gb of memory and Celeron means it's going to be a bit slow, both in terms of running tests but also for general management of the system which in turn leads to longer downtime between testing, etc.

This is the reference device that we're supposed to be measuring against, so unless we can somehow simulate its low power in a reliable way, it's probably what we should be using.

Flags: needinfo?(mconley)

(In reply to Kendall Libby [:fubar] (he/him) from comment #5)

(In reply to Patricia Lawless from comment #0)

Is this particular device a hard requirement or do we have some flexibility? 4gb of memory and Celeron means it's going to be a bit slow, both in terms of running tests but also for general management of the system which in turn leads to longer downtime between testing, etc.

Just one of them?

+1 to what mconley said in comment#6. As for how many... one should be sufficient for now but we'll take more if we can get it (2 would be good).

(In reply to Mike Conley (:mconley) (:⚙️) from comment #6)

This is the reference device that we're supposed to be measuring against, so unless we can somehow simulate its low power in a reliable way, it's probably what we should be using.

Ok; we'll get one or two and see how it goes. Who determines what the reference hardware is for random projects like this? I'd like to get plugged into the process much earlier if at all possible.

Patricia, would you be meet up with Mark Cornmesser in MTV2 to talk about the hardware and testing? He's been managing the other hardware in the lab and will be down there to hand over some hardware to Bitbar.

The reference hardware is the standard "2018 reference hardware" that was chosen Firefox-wide (we didn't choose it ourselves).

Sure, I can meet Mark. When will he be in MTV?

There hasn't been any activity in a year on this bug (and 1575379). :plawless, is this still relevant?

Flags: needinfo?(plawless)
Priority: -- → P5

Hey :sparky,
:barret was working on these bugs in Q3-Q4 2019. I'll assign him to them so he can decide what to do with them when the work picks up again.

Flags: needinfo?(plawless)
Assignee: relops → brennie

Thanks :plawless! Setting to P1 based on our new triage guidelines: https://wiki.mozilla.org/TestEngineering/Performance/Triage_Process

Priority: P5 → P1
Status: NEW → ASSIGNED
Summary: Frame recording cold startup testing set up → Deploy desktop startup recorder (fxrecord) to Toronto Office
Depends on: 1715622
Depends on: 1715643
Depends on: 1715669

The associated Jira ticket (https://mozilla-hub.atlassian.net/browse/FXP-1419) was marked as done on September 2nd after recieving an update from Barret. Bug 1738369 also suggests this was complete, and has recently started to fail.

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED

(In reply to Dave Hunt [:davehunt] [he/him] ⌚GMT from comment #14)

The associated Jira ticket (https://mozilla-hub.atlassian.net/browse/FXP-1419) was marked as done on September 2nd after recieving an update from Barret. Bug 1738369 also suggests this was complete, and has recently started to fail.

There are also details in https://mozilla-hub.atlassian.net/browse/FXP-1416.

You need to log in before you can comment on or make changes to this bug.