Closed Bug 1548614 Opened 7 months ago Closed 5 months ago

Rename UX machines to ref-hw for clarity

Categories

(Testing :: General, defect, P3)

defect

Tracking

(firefox69 fixed, firefox70 fixed)

RESOLVED FIXED
mozilla69
Tracking Status
firefox69 --- fixed
firefox70 --- fixed

People

(Reporter: sphilp, Assigned: egao)

References

Details

Attachments

(3 files)

Currently the Windows 10 reference hardware machines are referred to as "UX" machines on treeherder/taskcluster/try. This is confusing as it appears they could be for "user experience".

Lets rename them from windows10-64-ux to windows10-64-ref-hw-2017

windows10-64-ref-hw-2017 would be most descriptive.

:fubar, what would be involved in changing the machine on your end? Just a taskcluster worker change? a machine name change?

Flags: needinfo?(klibby)

I was discussing this with Mark on Friday, and I think it makes sense to change the names when we move them all to Bitbar, which we can now work on. There's a bit of work involved, with DNS and TC and soon puppet, so let's do it as a package.

Flags: needinfo?(klibby)

I think this is asking for 2 separate changes.

One would be a change to the node name. Which is currently like t-w1064-ux-xxx. My preference there is to change the ux to something that references the hardware and not the function. Similar to the ms in the moonshoot names. I will figure out where to make this change as we hash out the deployment process with Bitbar.

The other is changing the workerType from gecko-t-win10-64-ux to something more representative of the specific tasks that are performed by the worker. This is consistent with our other Windows tester workerType(s). We may want to go with something more like gecko-t-win10-64-ref-hw. This is a small change in the configuration file for the node. There maybe some additional changes in Taskcluster if we decide to a new clientID for the laptops when they get moved to Bitbar.

The priority flag is not set for this bug.
:gbrown, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(gbrown)
Flags: needinfo?(gbrown)
Priority: -- → P3
Depends on: 1555023

Jmaher: I am planning on enacting these changes when these are moved to Bitbar. The one part I am not sure how to address in the changes in tree that will point the tests to the new workerType. Also Bitbar is expecting to take a day to get the laptops up and running after the hand off. I think we should do the hand off in 2 groups, so that we don't completely lose the pool. Once Bitbar has the laptops up we then switch the workerType in tree. Thoughts? Do you think there is a better way to go about it? Who should I talk to about making the changes in tree?

I will ask :egao to do the in-tree changes, it should be as simple as:
https://searchfox.org/mozilla-central/search?q=windows10-64-ux&path=

One thing is we should support both the old and new as soon as possible- then we can move a few devices over and get them online, etc. Once everything is moved over, we can clean up the stuff remaining in-tree.

:egao, can you work with :markco to find the right taskcluster worker types and names to use for these renamed machines?

Flags: needinfo?(egao)

:markco - let's sync up in the Bitbar slack channel about this process. The in-tree changes should be fairly simple, but having to support both for a short period of time might prove troublesome.

Flags: needinfo?(egao)

(In reply to Edwin Gao (:egao) from comment #8)

:markco - let's sync up in the Bitbar slack channel about this process. The in-tree changes should be fairly simple, but having to support both for a short period of time might prove troublesome.

Sorry I never saw this comment. The current status is BItbar has a laptop, and I have provided them with a bootstrap script. They are going to run through it tomorrow. It should come up with the ref-hw workerType.

Attachment #9072694 - Attachment description: Bug 1548614 - change from windows10-64-ux to windows10-64-ref-hw-2017 → Bug 1548614 - change worker and task name from windows10-64-ux to windows10-64-ref-hw-2017
Pushed by egao@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/7bc777500d40
change worker and task name from windows10-64-ux to windows10-64-ref-hw-2017 r=jmaher
Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
See Also: → 1560926
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Reopened as the windows10-64-ux machines are ready to migrate to the win10-64-ref-hw-2017 machines over at Bitbar.

Pushed by egao@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1d8cfc4b67da
migrate over win10-64-ux machines to 2017 reference hardware hosted at Bitbar r=jmaher
Status: REOPENED → RESOLVED
Closed: 6 months ago5 months ago
Resolution: --- → FIXED

Git PR to give a pretty name to Reference HW is as follows:

https://github.com/mozilla/treeherder/pull/5078

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