Closed
Bug 1385074
Opened 7 years ago
Closed 7 years ago
regression from taskcluster migration of windows - lost the q1s job for win7/10
Categories
(Testing :: Talos, enhancement)
Testing
Talos
Tracking
(firefox56 fixed)
RESOLVED
FIXED
mozilla56
Tracking | Status | |
---|---|---|
firefox56 | --- | fixed |
People
(Reporter: jmaher, Assigned: jmaher)
References
Details
(Whiteboard: [PI:July])
Attachments
(1 file)
1.61 KB,
patch
|
rwood
:
review+
|
Details | Diff | Splinter Review |
we seemed to have lost the new quantum-pageload-stylo-e10s job. this is a new job we added late last week and appears to have been lost when we did the migration.
Assignee | ||
Comment 1•7 years ago
|
||
:callek, it looks like we are doing the jobs correctly in the decision task: https://public-artifacts.taskcluster.net/UHCkB2ILS-y_8vMoZ1tfwA/0/public/logs/live_backing.log but the job never runs, can you help us debug via BBB?
Flags: needinfo?(bugspam.Callek)
Assignee | ||
Updated•7 years ago
|
Whiteboard: [PI:July]
Updated•7 years ago
|
Assignee: nobody → catlee
Flags: needinfo?(bugspam.Callek)
Assignee | ||
Comment 2•7 years ago
|
||
16:13 < catlee> BB has "Windows 10 64-bit mozilla-central pgo talos quantum-pageload-e10s" 16:13 < catlee> and TC is looking for "Windows 10 64-bit mozilla-central pgo talos q1s-e10s"
Assignee | ||
Comment 3•7 years ago
|
||
this also does the shift from q -> tp6 for our ultimate goal- I might as well do this while I am making changes.
Attachment #8891053 -
Flags: review?(rwood)
Updated•7 years ago
|
Attachment #8891053 -
Flags: review?(rwood) → review+
Pushed by jmaher@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/132d97901319 regression from taskcluster migration of windows - lost the q1s job for win7/10. r=rwood
Updated•7 years ago
|
Assignee: catlee → jmaher
Comment 6•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/132d97901319
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox56:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla56
You need to log in
before you can comment on or make changes to this bug.
Description
•