Hg updating to public failed

So tackling the job of getting these machines up again, things are not off to a good start ..... Just tried to run runner (after checking it wasn't running, and nor was buildbot): [[email protected]~]# /etc/init.d/runner start Starting runner failed [[email protected]~]# cat /var/log/2014-08-14 ,290 - INFO - iteration 1 Reporting hg version in use command: START command: hg -q version command: cwd: .

When I investigated, the first host I saw (b-linux64-hp-0004releng.scl3.mozilla.com) had no buildbot running, due to a Runner failure. As you see, when it fails to update the tools checkout, it deletes it, in the hope of doing a fresh clone.command: output: command: END (0.00s elapsed) Traceback (most recent call last): File "/usr/local/bin/hgtool.py", line 104, in ", line 47, in run_cmd File "/usr/lib64/python2.6/subprocess.py", line 497, in check_call retcode = call(*popenargs, **kwargs) File "/usr/lib64/python2.6/subprocess.py", line 478, in call p = Popen(*popenargs, **kwargs) File "/usr/lib64/python2.6/subprocess.py", line 639, in __init__ errread, errwrite) File "/usr/lib64/python2.6/subprocess.py", line 1228, in _execute_child raise child_exception OSError: [Errno 13] Permission denied: '.' Reporting hg version in use command: START command: hg -q version command: cwd: . It works using the collapse capability of the rebase extension, and keeping track of the last squashed revision using a bookmark (in the working repository). We started with a single version of the file; then we made some changes; while someone else made different changes to the same text.Our task in resolving the conflicting changes is to decide what the file should look like.