ReleaseEngineering/Buildduty/TaipeiMeetings/May16-May20
From MozillaWiki
Notes: 2016/05/16 - 2016/05/20
Slave loan bugs:
- https://bugzil.la/1273200 - loan jmaher 5 linux64 ix machines, please allow wlach/garndt network access as well
- https://bugzil.la/1273598 - Slave loan request for a t-w864-ix machine
- https://bugzil.la/1273666 - please loan kmoir a dev-linux64-ec2 aws build machine
Things to pursue if there are no loans:
- Setup development masters to enable you to test buildbot patches - https://wiki.mozilla.org/ReleaseEngineering/How_To/Setup_Personal_Development_Master
- We created build master and test master on dev-master2
- [Fixed][ihsiao] practicing how to test a patch, 3 tests failed in step 6 (run 'cd buildbot-configs; ./test-masters.sh' - all the tests should pass), trying to figure out the issue.
- make sure your code checkouts for buildbot-configs, buildbotcustom, and tools are up-to-date, i.e. hg pull && hg update -r default. There were some code issues with buildbotcustom last Friday, so if you happened to pull at the wrong time, you might have ended up with the broken code.
- [Fixed][ashiue] Encounter ImportError: No module named buildbotcustom.misc when executed ./braindump/buildbot-related/builder_list.py master/master.cfg, trying to figure out this problem => It works now, thx!
- Probably need to set a PYTHONPATH to point to your buildbotcustom dir
- Alternately, you should make sure you are running inside the virtualenv for your master before running other commands, i.e. cd build-master; source bin/activate (I just tried this in the venv for my build master without doing anything else, and was able to run the builder_list.py script)
- [Fixed][ihsiao] practicing how to test a patch, 3 tests failed in step 6 (run 'cd buildbot-configs; ./test-masters.sh' - all the tests should pass), trying to figure out the issue.
- Write a tool to update bugzilla bugs for outstanding machine loans and ask if the loaner is still needed on say, a weekly basis: https://bugzil.la/1171165