New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 813176 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Leases directory creating dirty tree, failing push

Project Member Reported by pho...@chromium.org, Feb 16 2018

Issue description

======== cros-full-0011.mtv.corp.google.com ========
Running '/usr/local/autotest/site_utils/deploy_server_local.py ' on cros-full-0011.mtv.corp.google.com
Will skip service check for pushing servers in prod.
Checking tree status:
Traceback (most recent call last):
  File "/usr/local/autotest/site_utils/deploy_server_local.py", line 538, in <module>
    sys.exit(main(sys.argv[1:]))
  File "/usr/local/autotest/site_utils/deploy_server_local.py", line 504, in main
    verify_repo_clean()
  File "/usr/local/autotest/site_utils/deploy_server_local.py", line 101, in verify_repo_clean
    raise DirtyTreeException(out)
__main__.DirtyTreeException: project autotest/                               (*** NO BRANCH ***)
 --     leases/177206678


 

Comment 1 by pho...@chromium.org, Feb 16 2018

======== cros-full-0010.mtv.corp.google.com ========
Running '/usr/local/autotest/site_utils/deploy_server_local.py ' on cros-full-0010.mtv.corp.google.com
Will skip service check for pushing servers in prod.
Checking tree status:
Traceback (most recent call last):
  File "/usr/local/autotest/site_utils/deploy_server_local.py", line 538, in <module>
    sys.exit(main(sys.argv[1:]))
  File "/usr/local/autotest/site_utils/deploy_server_local.py", line 504, in main
    verify_repo_clean()
  File "/usr/local/autotest/site_utils/deploy_server_local.py", line 101, in verify_repo_clean
    raise DirtyTreeException(out)
__main__.DirtyTreeException: project autotest/                               (*** NO BRANCH ***)
 --     leases/177209944
 --     leases/177209962

Comment 2 by pho...@chromium.org, Feb 16 2018

Cc: pprabhu@chromium.org
Is this just a question of adding leases/ to .gitignore?

Comment 3 by pho...@chromium.org, Feb 16 2018

Manually ran repo sync to bring cros-full 10 and 11 up to date.
Why do we have a dirty tree check?  I thought we agreed on always nuking (reset --hard or similar).

That said, we should add leases/ to .gitignore.
Project Member

Comment 5 by bugdroid1@chromium.org, Feb 21 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/624ab95d4b427786997bc7cd9832099730402de4

commit 624ab95d4b427786997bc7cd9832099730402de4
Author: Allen Li <ayatane@chromium.org>
Date: Wed Feb 21 04:32:06 2018

[autotest] Ignore leases files

BUG= chromium:813176 
TEST=None

Change-Id: I4e96f1ce8da5b116740c0ed1c8ed55ed6789332f
Reviewed-on: https://chromium-review.googlesource.com/923739
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Allen Li <ayatane@chromium.org>
Reviewed-by: Paul Hobbs <phobbs@google.com>

[add] https://crrev.com/624ab95d4b427786997bc7cd9832099730402de4/leases/.gitignore

Comment 6 by nxia@chromium.org, Feb 22 2018

I still saw this error yesterday 

======== chromeos-server126.hot.corp.google.com ========
Running '/usr/local/autotest/site_utils/deploy_server_local.py ' on chromeos-server126.hot.corp.google.com
Will skip service check for pushing servers in prod.
Checking tree status:
Traceback (most recent call last):
  File "/usr/local/autotest/site_utils/deploy_server_local.py", line 538, in <module>
    sys.exit(main(sys.argv[1:]))
  File "/usr/local/autotest/site_utils/deploy_server_local.py", line 504, in main
    verify_repo_clean()
  File "/usr/local/autotest/site_utils/deploy_server_local.py", line 101, in verify_repo_clean
    raise DirtyTreeException(out)
__main__.DirtyTreeException: project autotest/                               (*** NO BRANCH ***)
 --	leases/178323311


Comment 7 by nxia@chromium.org, Feb 22 2018

probably it's because I didn't use the up-to-date master branch, will leave this bug open and verify it tomorrow.
Status: Fixed (was: Untriaged)
Fixed, I think

Sign in to add a comment