Closed
Bug 1217534
Opened 9 years ago
Closed 9 years ago
linux64 talos is not running on mozilla-aurora or mozilla-beta
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jmaher, Assigned: kmoir)
Details
Attachments
(2 files, 2 obsolete files)
1.65 KB,
patch
|
armenzg
:
review+
kmoir
:
checked-in+
|
Details | Diff | Splinter Review |
1.76 KB,
text/plain
|
Details |
wlach pointed out that we don't run linux64 talos on aurora or beta. This stopped on Oct 13th.
Reporter | ||
Comment 1•9 years ago
|
||
:Callek, can you help us figure out what went wrong here. I looked at a few things and couldn't determine the root cause.
Flags: needinfo?(bugspam.Callek)
Comment 2•9 years ago
|
||
Last push with L64 talos: https://treeherder.mozilla.org/#/jobs?repo=mozilla-beta&revision=8974b3c15604 The next one does not have them anymore: https://treeherder.mozilla.org/#/jobs?repo=mozilla-beta&revision=7c95e499110e The builders don't show up in here: http://people.mozilla.org/~armenzg/permanent/all_builders.txt
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → kmoir
Assignee | ||
Comment 3•9 years ago
|
||
The problem is that 6b1e88013eba added gtests after the get_talos part due to an ordering issue which changed the talos platform to ubuntu64_vm instead of ubuntu64_hw and there weren't any builders associated with it. In any case, I don't really to wrestle that ordering issue again so I'll just explicitly set the talos platform for m-a and m-b. I didn't see that when I was testing the other bug because I was testing on a master configured for linux64 vms, not linux64 hw to match our production systems.
Assignee | ||
Comment 4•9 years ago
|
||
Assignee | ||
Updated•9 years ago
|
Attachment #8677679 -
Flags: review?(jmaher)
Assignee | ||
Updated•9 years ago
|
Flags: needinfo?(bugspam.Callek)
Reporter | ||
Updated•9 years ago
|
Attachment #8677679 -
Flags: review?(jmaher) → review+
Assignee | ||
Updated•9 years ago
|
Attachment #8677679 -
Flags: checked-in+
Assignee | ||
Comment 5•9 years ago
|
||
Comment on attachment 8677679 [details] [diff] [review] bug1217534.patch That didn't work. Trying something different
Attachment #8677679 -
Flags: checked-in+ → checked-in-
Comment 6•9 years ago
|
||
Would backing out the gtests patch be an option? (and try re-landing it after using list_builder_differences.sh)
Comment 7•9 years ago
|
||
I'm surprised your patch didn't work from looking at the builder.diff! Good luck!
Assignee | ||
Comment 8•9 years ago
|
||
The problem with the previous patch is that it added m-a and m-b talos builders to masters with only vms attached, not talos machines and thus it failed due to the lack of matching slaves. Testing new patches to address this but no luck yet.
Comment 9•9 years ago
|
||
In production: https://hg.mozilla.org/build/buildbot-configs/rev/2a071c368c01
Comment 10•9 years ago
|
||
In production: https://hg.mozilla.org/build/buildbot-configs/rev/ecac0ce8742a
Assignee | ||
Comment 11•9 years ago
|
||
Attachment #8677679 -
Attachment is obsolete: true
Attachment #8677680 -
Attachment is obsolete: true
Assignee | ||
Comment 12•9 years ago
|
||
builder diff for a master with ubuntu64_hw slaves diff for a master w ubuntu64_vm slaves is a noop ./test-masters.sh runs green
Assignee | ||
Updated•9 years ago
|
Attachment #8678304 -
Attachment is patch: false
Assignee | ||
Updated•9 years ago
|
Attachment #8678303 -
Flags: review?(armenzg)
Updated•9 years ago
|
Attachment #8678303 -
Flags: review?(armenzg) → review+
Assignee | ||
Comment 13•9 years ago
|
||
Comment on attachment 8678303 [details] [diff] [review] bug1217534-2.patch and tests pass
Attachment #8678303 -
Flags: checked-in+
Assignee | ||
Comment 14•9 years ago
|
||
I seen builder jobs on the appropriate masters after the reconfig.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•