Notes: 2016/05/09 - 2016/05/13

Slave loan bugs:

• https://bugzil.la/1271780 - Please loan fkang a linux64 aws build machine
• https://bugzil.la/1271170 - Slave loan request for a t-w732-ix machine to ashiue
• https://bugzil.la/1270764 - Slave loan request for a t-w864-ix machine to ihsiao
• https://bugzil.la/1272002 - lave loan request for a talos-linux64-ix slave to acomminos
• https://bugzil.la/989543 - (t-xp32-ix-113) t-xp32-ix-113 problem tracking

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

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

[Alin] [***will need to see why screen sharing on Vidyo does not work, sorry for inconveniences***]

Example on how to test a patch:

On local computer:

1. clone the repo where the file(s) that you want to modify are stored
   • e.g: hg http://hg.mozilla.org/build/buildbot-configs/
   • if the repo is already cloned, make sure it's up-to-date: hg pull; hg update -C
2. make the changes to the files from the repo
3. compute the patch: e.g. hg diff > test.patch

On dev-master2:

1. go to /builds/buildbot/<your_name>, clone 'braindump' repo: http://hg.mozilla.org/build/braindump/
   • if it's already cloned, make sure it's up-to-date
2. cd to your master's home folder, activate the virtual environment: source bin/activate
3. you can do some optimizations on /master/master_config.json in order to limit the number of tests/builders to certain platforms/branches.
   • see https://wiki.mozilla.org/ReleaseEngineering/How_To/Setup_Personal_Development_Master#Optimizations
4. compute the list of builders/tests using 'builder_list.py' script:
   • e.g. ../braindump/buildbot-related/builder_list.py master/master.cfg > old
5. copy the patch from your local computer and apply it on your master
   • e.g. cd buildbot-configs; patch -p1 < ../test.patch
6. run 'cd buildbot-configs; ./test-masters.sh' - all the tests should pass
7. run 'make checkconfig' --> should say 'Config file is good!'
8. compute the new list of builders/tests
9. compute the difference file: e.g. diff -U 8 -p old new > diff.txt