Closed
Bug 807115
Opened 12 years ago
Closed 11 years ago
Inherit project slaves from their platform
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sfink, Assigned: sfink)
Details
Attachments
(1 file)
2.43 KB,
patch
|
catlee
:
review+
sfink
:
checked-in+
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Comment 1•12 years ago
|
||
Assignee | ||
Comment 2•12 years ago
|
||
Comment on attachment 676788 [details] [diff] [review] Inherit project slaves from their platform Oops, I think I may have broken bzexport so it permits an empty comment 0. The problem is that spidermonkey builds are now getting their configuration from the underlying platform, which for linux64 is now set up to run under mock. But they were still using the "native" (non-mock) slaves. So they run on a non-mock slave and look for hg in a directory that only the mock slaves have, which fails. Or at least, that's my current theory.
Attachment #676788 -
Flags: review?(catlee)
Updated•12 years ago
|
Attachment #676788 -
Flags: review?(catlee) → review+
Assignee | ||
Updated•12 years ago
|
Attachment #676788 -
Flags: checked-in+
Assignee | ||
Comment 3•12 years ago
|
||
http://hg.mozilla.org/build/buildbotcustom/rev/7919d8e0e982
Comment 4•12 years ago
|
||
In production
Assignee | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
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
•