-
Notifications
You must be signed in to change notification settings - Fork 3
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
Issue with coverage==5.0 #24
Comments
It looks like coverage=5.0 changed how the path to the coverage data is dictated -- instead of determining the file name at write, it must be determined when the coverage object is created. We need to move some of the logic in exit of coverage.py to enter. Probably shall always modify cov.config.data_file to a temporary location regardless of number of ranks, then in exit depending on the number of ranks combine or rename the coverage result. @nickhand, any comments on this approach? |
I think the issue has creepped into nbodykit main test suite. https://travis-ci.org/bccp/nbodykit/jobs/631984492 We need to sort this out. |
@rainwoodman I can take a look this weekend and offer some comments |
Great! |
It looks like |
I think the rest of the logic still works. They changed the underlying data format from a JSON file to a SQLite database file, but the current logic doesn't depend on the storage format |
It does depend on how the storage logic is executed -- the storage containers are created before write occurs, thus we had to lift the file names to before cov.start(). |
MPI tests with coverage end with a failure like the following:
Issue goes away if I revert to coverage==4.5.4
The text was updated successfully, but these errors were encountered: