it appears the windows01-64-ux laptops are running jobs on trunk when it should on be mozilla-central
Categories
(Testing :: Performance, enhancement)
Tracking
(firefox67 fixed, firefox68 fixed)
People
(Reporter: jmaher, Assigned: Callek)
References
Details
Attachments
(2 files)
our load has increased on the windows ux laptops and the queue will take a couple days to clear out.
we need to figure out why these are running on inbound/autoland and turn those tests off.
Reporter | ||
Comment 1•5 years ago
|
||
this is a side effect of shippable builds - these were designed to run on nightlies only, now that shippable is the same, we need to pin these tests to be m-c only.
Reporter | ||
Comment 2•5 years ago
|
||
and it looks to be setup properly to be try/m-c:
https://searchfox.org/mozilla-central/source/taskcluster/ci/test/raptor.yml#14
not sure why this is on inbound/autoland
Assignee | ||
Comment 3•5 years ago
|
||
Pushed by jwood@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/3d678990e647 Properly avoid running on -ux hardware oustide of try/mozilla-central. r=jmaher
Comment 5•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Comment 6•5 years ago
•
|
||
It appears we have talos/raptor jobs running on mozilla-beta for windows10-64-ux. I didn't think these configuration changes needed to be uplifted, or am I wrong?
https://treeherder.mozilla.org/perf.html#/graphs?series=mozilla-beta,1829086,1,10
Reporter | ||
Comment 7•5 years ago
|
||
these should only be running on mozilla-central and try, not mozilla-beta. Is there a need to run these elsewhere- if so we would need to consider more devices.
Comment 8•5 years ago
|
||
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #7)
these should only be running on mozilla-central and try, not mozilla-beta. Is there a need to run these elsewhere- if so we would need to consider more devices.
Right, Im saying that they are currently running on mozilla-beta. I'm not suggesting this is something we want, I'm querying why this fix doesn't appear to have addressed mozilla-beta. We noticed it in Perfherder alerts. https://treeherder.mozilla.org/perf.html#/graphs?series=mozilla-beta,1829086,1,10
Reporter | ||
Comment 9•5 years ago
|
||
I believe the answer is this was not uplifted to mozilla-beta.
:ryanvm, how do we request a beta uplift?
Comment 10•5 years ago
|
||
It's a test-only change, so it just needs to be on the sheriffs' radar to do so :)
Comment 11•5 years ago
|
||
bugherder uplift |
Updated•5 years ago
|
Comment 12•5 years ago
•
|
||
The test are not running on beta anymore but they are running on mozilla inbound and autoland with a large queue. Also the test on central are queued for a long time.
Joel is there something that can be done?
Reporter | ||
Comment 13•5 years ago
|
||
disable tp6-3 on windows ux laptops from running on autoland
Reporter | ||
Comment 14•5 years ago
|
||
this was a regression when we turned off tp6-3 for windows aarch64
Reporter | ||
Updated•5 years ago
|
Comment 16•5 years ago
|
||
Pushed by jmaher@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/def8a63f9038 disable tp6-3 on windows ux laptops from running on autoland. r=davehunt
Comment 17•5 years ago
|
||
bugherder |
Description
•