Test push is failing because of repo on pprabhu-skylab-drone-2
Reported by
jrbarnette@chromium.org,
May 23 2018
|
||
Issue descriptionThe test push to prod is failing. Here's the relevant part from the test_push log: [chromeos-staging-master2.hot.corp.google.com] out: Updating server: pprabhu-skylab-drone-2.cbf.corp.google.com [chromeos-staging-master2.hot.corp.google.com] out: Checking tree status: [chromeos-staging-master2.hot.corp.google.com] out: stderr: [chromeos-staging-master2.hot.corp.google.com] out: Traceback (most recent call last): [chromeos-staging-master2.hot.corp.google.com] out: File "/usr/local/autotest/site_utils/deploy_server_local.py", line 544, in <module> [chromeos-staging-master2.hot.corp.google.com] out: sys.exit(main(sys.argv[1:])) [chromeos-staging-master2.hot.corp.google.com] out: File "/usr/local/autotest/site_utils/deploy_server_local.py", line 510, in main [chromeos-staging-master2.hot.corp.google.com] out: verify_repo_clean() [chromeos-staging-master2.hot.corp.google.com] out: File "/usr/local/autotest/site_utils/deploy_server_local.py", line 102, in verify_repo_clean [chromeos-staging-master2.hot.corp.google.com] out: raise DirtyTreeException('%s repo not clean: %s' % (HOSTNAME, out)) [chromeos-staging-master2.hot.corp.google.com] out: __main__.DirtyTreeException: pprabhu-skylab-drone-2.cbf.corp.google.com repo not clean: project autotest/site_utils/autotest_private/ [chromeos-staging-master2.hot.corp.google.com] out: missing (run "repo sync") If you log in to the cited server, you find this: chromeos-test@pprabhu-skylab-drone-2:/usr/local/autotest$ repo status project autotest/site_utils/autotest_private/ missing (run "repo sync") Which is a bit hard to read, but basically, "autotest/site_utils/autotest_private" hasn't been installed.
,
May 23 2018
This was me rsync()ing stuff over to /usr/local/autotest/site_utils/ which ended up deleting the .gitignore'ed site_utils/autotest_private I've fixed the immediate problem by simply running 'repo sync' in /usr/local/autotest. (1) There is a conflict here with me wanting to keep the skylab-drone's in staging lab for monitoring purposes -- we want dashboards and pushes to make sure that these drones are stable enough to enter prod -- and wanting to muck around on the drones because skylab is under active development. (2) If 'repo sync' solved this problem, deploy_server_local.py needs to be hardened to recover from this problem on its own. I have a wip for (2) https://chromium-review.googlesource.com/#/c/chromiumos/third_party/autotest/+/1068160 Don't have time for it right now though.
,
Aug 17
No more rsyncing stuff over. |
||
►
Sign in to add a comment |
||
Comment 1 by pprabhu@chromium.org
, May 23 2018