commit | 342f156c3594e34a47d0bab9a99fd0f7add9cb67 | [log] [tgz] |
---|---|---|
author | David James <davidjames@chromium.org> | Fri Jul 15 15:21:18 2011 -0700 |
committer | David James <davidjames@chromium.org> | Fri Jul 15 15:31:45 2011 -0700 |
tree | 88cb760327bca2ba21754a2c4d12beebcb257c64 | |
parent | d6ae1ec95ef1532828bbf82f1b642d0966f08ca5 [diff] |
enter_chroot should only modify things within a lock. enter_chroot is often called from multiple processes and we expect that it doesn't modify anything unless it's within a lock. This CL moves chroot modifications up to occur during the lock so that we don't have multiple modifications to .gitconfig occurring at the same time. This prevents the following warning: error: could not lock config file /b/cbuild/chroot/home/chrome-bot/.gitconfig: File exists See http://chromeos-botmaster.mtv.corp.google.com:8026/builders/TOT%20Pre-Flight%20Queue/builds/3771/steps/Test/logs/stdio BUG=chromium-os:17661 TEST=Run enter_chroot.sh and verify gitconfig is still setup. Change-Id: I73a7755d62cce895c76b8e0f35838b3874e5db33 Reviewed-on: http://gerrit.chromium.org/gerrit/4208 Reviewed-by: Chris Sosa <sosa@chromium.org> Tested-by: David James <davidjames@chromium.org>