Closed
Bug 1278611
Opened 8 years ago
Closed 8 years ago
move valgrind tc builds to tier1 and stop building buildbot binaries
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kmoir, Assigned: h.franciskang)
References
Details
Attachments
(3 files, 3 obsolete files)
7.63 KB,
patch
|
rail
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
327 bytes,
text/plain
|
Details | |
13.85 KB,
patch
|
rail
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
Now that valgrind builds are running via taskcluster, we can probably move them to tier1 and stop building the buildbot binaries.
Reporter | ||
Updated•8 years ago
|
Assignee: nobody → fkang
Reporter | ||
Comment 1•8 years ago
|
||
Francis if you are still having problems with your buildbot patches let me know and I can run the patches against my buildbot dev masters and help you debug the errors.
Flags: needinfo?(fkang)
Assignee | ||
Comment 2•8 years ago
|
||
Flags: needinfo?(fkang)
Assignee | ||
Comment 3•8 years ago
|
||
Comment on attachment 8763613 [details] [diff] [review] Remove valgrind script invocation from bbcustom I think this should be sufficient to disable valgrind builds, but I'm not sure how to test it. Is there a way to get try to use my modified buildbotcustom?
Attachment #8763613 -
Attachment description: I think this should be sufficient to disable valgrind builds, but I'm not sure how to test it. Is there a way to get a try run to work with my modified buildbotcustom? → Remove valgrind script invocation from bbcustom
Assignee | ||
Comment 4•8 years ago
|
||
Also, attachment 8763613 [details] [diff] [review] only prevents the valgrind bash script from being run (if it works). The script and any other remnants would have to be deleted as well.
Reporter | ||
Comment 5•8 years ago
|
||
Aren't there still references to valgrind in buildbot-configs/mozilla/config.py that need to be deleted as well? Usually I test them on a dev-master https://wiki.mozilla.org/ReleaseEngineering/How_To/Setup_Personal_Development_Master and compare the builders before and after https://wiki.mozilla.org/ReleaseEngineering:TestingTechniques#builder_list.py_.2F_dump_master.py
Assignee | ||
Comment 6•8 years ago
|
||
Disable the use of valgrind builders
Assignee | ||
Comment 7•8 years ago
|
||
https://travis-ci.org/hfkang/build-buildbot-configs/builds/142468014 I've disabled valgrind builds in buildbotcustom, and removed references to it in both buildbotcustom and buildbot-configs. It is no longer installed as a mock package, nor is it enabled in try as a test option. I've tested out the two patches on my devmaster, http://dev-master2.bb.releng.use1.mozilla.com:8066/builders and all the valgrind builders have been removed. The travis run with both patches is also above. I also removed references to valgrind from buildbot-configs/mozilla/thunderbird_config.py as it didn't seem to be used there either. Remaining steps would be to delete the old valgrind directory from moz-central and the valgrind test from trychooser?
Assignee | ||
Comment 8•8 years ago
|
||
Removes valgrind builders on buildbot masters
Attachment #8763613 -
Attachment is obsolete: true
Attachment #8766463 -
Attachment is obsolete: true
Attachment #8767997 -
Flags: review?(rail)
Assignee | ||
Comment 9•8 years ago
|
||
Remove references to valgrind from buildbot-configs
Attachment #8767998 -
Flags: review?(rail)
Assignee | ||
Comment 10•8 years ago
|
||
braindump/buildbot-related/builder_list.py master/master.cfg was executed on the master before and after the patches. this diff shows the valgrind builders were removed.
Updated•8 years ago
|
Attachment #8767997 -
Flags: review?(rail) → review+
Comment 11•8 years ago
|
||
Comment on attachment 8767998 [details] [diff] [review] rm valgrind from buildbot-configs Review of attachment 8767998 [details] [diff] [review]: ----------------------------------------------------------------- ::: tox_env.sh @@ +20,5 @@ > hgme braindump > > +repo="buildbotcustom" > +if [ ! -d "${TOX_WORK_DIR}/${repo}" ]; then > + git clone https://github.com/hfkang/build-buildbotcustom ${TOX_WORK_DIR}/buildbotcustom I don't think you want this landed. ;)
Attachment #8767998 -
Flags: review?(rail)
Comment 12•8 years ago
|
||
BTW, feel free to kill moar stuff in https://dxr.mozilla.org/build-central/search?q=valgrind&redirect=false
Assignee | ||
Comment 13•8 years ago
|
||
Attachment #8767998 -
Attachment is obsolete: true
Assignee | ||
Updated•8 years ago
|
Attachment #8768036 -
Flags: review?(rail)
Comment 14•8 years ago
|
||
Comment on attachment 8768036 [details] [diff] [review] Remove valgrind from buildbot-configs Review of attachment 8768036 [details] [diff] [review]: ----------------------------------------------------------------- _~ _~ )_)_~ )_))_))_) _!__!__!_ \______t/ ~~~~~~~~~~~~~ it!
Attachment #8768036 -
Flags: review?(rail) → review+
Assignee | ||
Comment 15•8 years ago
|
||
I forgot autoland wouldn't work here. What's the procedure for pushing changes to buildbot?
Flags: needinfo?(rail)
Comment 17•8 years ago
|
||
Comment on attachment 8767997 [details] [diff] [review] rm valgrind from buildbotcustom https://hg.mozilla.org/build/buildbotcustom/rev/ee757cc22d46
Attachment #8767997 -
Flags: checked-in+
Comment 18•8 years ago
|
||
Comment on attachment 8768036 [details] [diff] [review] Remove valgrind from buildbot-configs https://hg.mozilla.org/build/buildbot-configs/rev/e582005ba6bd
Attachment #8768036 -
Flags: checked-in+
Comment 19•8 years ago
|
||
In production: https://hg.mozilla.org/build/buildbot-configs/rev/e582005ba6bd
Comment 20•8 years ago
|
||
In production: https://hg.mozilla.org/build/buildbotcustom/rev/ee757cc22d46
Assignee | ||
Comment 22•8 years ago
|
||
(In reply to Kim Moir [:kmoir] from comment #21) > :fkang can this be closed? Ah yes. I believe so. Thanks for reminding me :)
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(fkang)
Resolution: --- → FIXED
Reporter | ||
Comment 23•8 years ago
|
||
great, good work!
Comment 24•8 years ago
|
||
Yay!
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
•