Closed
Bug 1276389
Opened 8 years ago
Closed 8 years ago
Remove esr38 from the buildbot configs
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: RyanVM, Assigned: RyanVM)
References
Details
Attachments
(2 files)
78.52 KB,
patch
|
rail
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
20.19 KB,
patch
|
rail
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Comment 1•8 years ago
|
||
Attachment #8757529 -
Flags: review?(catlee)
Assignee | ||
Comment 2•8 years ago
|
||
grep says I've gotten all esr38 references, but I'm getting errors when I run list_builder_differences.sh for reasons I can't fathom. 2016-05-27 19:30:34,455 - Couldn't load test-output/bm81-build_scheduler/master.cfg Traceback (most recent call last): File "/home/ryanvm/.mozilla/releng/repos/braindump/buildbot-related/dump_master_json.py", line 111, in dump_master c = loadMaster(path) File "/home/ryanvm/.mozilla/releng/repos/braindump/buildbot-related/dump_master_json.py", line 26, in loadMaster execfile(path, g, g) File "/home/ryanvm/.mozilla/releng/repos/buildbot-configs/test-output/bm81-build_scheduler/master.cfg", line 110, in <module> execfile(releaseConfigFile, releaseBranchConfig, releaseBranchConfig) IOError: [Errno 2] No such file or directory: 'release-thunderbird-comm-esr38.py'
Flags: needinfo?(catlee)
Attachment #8757530 -
Flags: review?(catlee)
Updated•8 years ago
|
Attachment #8757529 -
Flags: review?(catlee) → review?(rail)
Updated•8 years ago
|
Attachment #8757530 -
Flags: review?(catlee) → review?(rail)
Comment 3•8 years ago
|
||
(In reply to Ryan VanderMeulen [:RyanVM] from comment #2) > Created attachment 8757530 [details] [diff] [review] > remove esr38 from tools > > grep says I've gotten all esr38 references, but I'm getting errors when I > run list_builder_differences.sh for reasons I can't fathom. > > 2016-05-27 19:30:34,455 - Couldn't load > test-output/bm81-build_scheduler/master.cfg > Traceback (most recent call last): > File > "/home/ryanvm/.mozilla/releng/repos/braindump/buildbot-related/ > dump_master_json.py", line 111, in dump_master > c = loadMaster(path) > File > "/home/ryanvm/.mozilla/releng/repos/braindump/buildbot-related/ > dump_master_json.py", line 26, in loadMaster > execfile(path, g, g) > File > "/home/ryanvm/.mozilla/releng/repos/buildbot-configs/test-output/bm81- > build_scheduler/master.cfg", line 110, in <module> > execfile(releaseConfigFile, releaseBranchConfig, releaseBranchConfig) > IOError: [Errno 2] No such file or directory: > 'release-thunderbird-comm-esr38.py' I think this is because it uses unmodified tools repo, where esr38 is enabled on some masters. If we land the tools patch it should just work
Flags: needinfo?(catlee)
Updated•8 years ago
|
Attachment #8757530 -
Flags: review?(rail) → review+
Updated•8 years ago
|
Attachment #8757529 -
Flags: review?(rail) → review+
Comment 4•8 years ago
|
||
Comment on attachment 8757530 [details] [diff] [review] remove esr38 from tools https://hg.mozilla.org/build/tools/rev/5ebdd8b4cab5
Attachment #8757530 -
Flags: checked-in+
Comment 5•8 years ago
|
||
Comment on attachment 8757529 [details] [diff] [review] remove esr38 from buildbot-configs https://hg.mozilla.org/build/buildbot-configs/rev/1831040dc4bf
Attachment #8757529 -
Flags: checked-in+
Comment 6•8 years ago
|
||
In production: https://hg.mozilla.org/build/buildbot-configs/rev/1831040dc4bf
Comment 7•8 years ago
|
||
Thank you for the patches Ryan!
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Comment 8•8 years ago
|
||
I used Fabric to run 'make update' on the build masters, and also scheduler (manually), since they were failing checkconfig after the landings here. The automated reconfig script doesn't update the master_config.json --> bug 1277116.
Comment 9•8 years ago
|
||
fix up: https://hg.mozilla.org/build/tools/rev/9b0658fa7382
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
•