I'm having issues with my patch from bug 1170522 in that it seems to trigger builds to just time out, with little information on what is failing. I'd like to be able to poke at a loaner machine in order to reproduce the issue and figure out how to fix it.

Email sent to :Gijs for further instructions. Loaning machines: - b-2008-ix-0074 Hi Gijs, I am going to assign this to you to keep track of the loan. When you are finished with the loan forever, please comment stating so here in the bug, and mark the bug as RESOLVED.

I'm having serious issues trying to get a mozharness build to run on this machine. So far I: - created my own subdir under c:/builds/moz2_slave/ - checked out mozharness into scripts/ underneath that dir - checked out fx-team into src/ underneath that dir - copied the default desktop config and set "is_automation" to False in it - run the mozilla-build bash login shell (there's a cmd prompt open on the machine that is stuck at "Error sending notice to nagios (ignored)" - I don't know if this is relevant) - from the mozilla-build, try to run the same run_script line as in http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/gijskruitbosch@gmail.com-e8e59f36fafe/try-win32-debug/try-win32-debug-bm83-try1-build6045.txt.gz : 'c:/mozilla-build/python27/python' '-u' 'scripts/scripts/fx_desktop_build.py' '--config' 'builds/releng_base_windows_32_builds.py' '--custom-build-variant-cfg' 'debug' '--config' 'balrog/production.py' '--branch' 'try' '--build-pool' 'production' that produced errors relating to buildprops.json not being there. That's why I changed the first config path to my copy that had is_automation set to False. That still dies for pretty similar reasons: 16:56:56 INFO - Traceback (most recent call last): 16:56:56 INFO - File "c:\builds\moz2_slave\gijs-test\build\tools\buildfar m\utils\hgtool.py", line 76, in <module> 16:56:56 INFO - js = json.load(open(options.propsfile)) 16:56:56 INFO - IOError: [Errno 2] No such file or directory: 'c:\\builds\\ moz2_slave\\gijs-test\\buildprops.json' 16:56:56 ERROR - Return code: 1 16:56:56 INFO - rmtree: c:\builds\moz2_slave\gijs-test\build\src 16:56:56 INFO - Using _rmtree_windows ... 16:56:56 INFO - retry: Calling _rmtree_windows with args: ('c:\\builds\\moz2 _slave\\gijs-test\\build\\src',), kwargs: {}, attempt #1 16:56:56 INFO - retry: attempt #1 caught exception: Unable to checkout 16:56:56 INFO - retry: Failed, sleeping 60 seconds before retrying I don't know how to fix this. I don't want it to be using buildprops at all, and I don't understand how to tell it not to, and to just run the build with the src I already checked out.

Gijs: I re-triggered your try run and grabbed the buildprops.json from it. That should help you get going here. This isn't the first time this has come up. I'll file a bug to get the buildprops.json file added to the list of artifacts we upload with each build.

(In reply to Chris Cooper [:coop] from comment #3) > This isn't the first time this has come up. I'll file a bug to get the > buildprops.json file added to the list of artifacts we upload with each > build. Bug 1177095 filed.

You can also do --no-read-buildbot-config and point to the builds --installer-url/--tests-url: https://wiki.mozilla.org/ReleaseEngineering/Mozharness/How_to_run_tests_as_a_developer#...on_a_loaner_machine It is likely that we should add instructions directly into mozharness on how to reproduce locally and on a loaner. I added this for the Firefox UI mozharness script and it is very useful.

(In reply to Armen Zambrano G. (:armenzg - Toronto) from comment #5) > You can also do --no-read-buildbot-config and point to the builds > --installer-url/--tests-url: but I'm trying to run a *build*, not a test, so I don't want installer/test URL, do I? --no-read-buildbot-config isn't a recognized option (or so it tells me).

My apologies. I should have read more closely. It seems that --no-read-buildbot-config was not added to that mozharness script/

Alright, I'm done with the slave. Thank you very much for providing it, and for all of your feedback and help in getting the build to work.