-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
experiments: test_new_simple is flaky #4401
Comments
Another failure on a different test:
Could be a one-time failure though, but maybe this assumption about time should not even be here? |
Happened again, but with a different message: https://travis-ci.com/github/iterative/dvc/jobs/375383416
|
It is for short period of time till it gets resolved See: iterative#4401
It is for short period of time till it gets resolved See: #4401
I've narrowed down the issue to gitpython Inserting this code into if not self.scm.is_dirty():
tree = self.exp_dvc.tree
logger.debug("--- workspace params.yaml:")
with tree.open("params.yaml") as fobj:
data = fobj.read()
logger.debug(f"{data}")
rev = self.scm.get_rev()
tree = self.scm.get_tree(rev)
logger.debug("--- baseline params.yaml:")
with tree.open(os.path.join(self.exp_dvc.root_dir, "params.yaml")) as fobj:
data = fobj.read()
logger.debug(f"{data}")
logger.debug(f"non-dirty exp workspace @ '{rev}'")
raise UnchangedExperimentError(self.scm.get_rev()) gives
so edit: the issue here was that |
So the underlying issue is related to input collection when we populate the executor tmp dir. The gitpython index/tree doesn't always behave consistently for merge commits, so sometimes the uploaded tree did not contain the correct changes. Abstracting the tmp dir input collection to use |
Need to investigate flaky test, probably hitting some gitpython related race condition again
context:
https://travis-ci.com/github/iterative/dvc/jobs/372602915
https://travis-ci.com/github/iterative/dvc/jobs/372071149
The text was updated successfully, but these errors were encountered: