-
-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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
Lib/trace.cover not removed by the clean target #78352
Comments
Lib/trace.cover is not removed by the clean target, and apparently this file is always created in the source tree, not in the build tree. It should be created in the build tree, if that's not possible, it should be cleaned in any case. |
It seems that this file is left by test_trace after commit 47ab154. |
PR 8841 prevents creating Lib/trace.cover when run the trace module. |
New changeset c406d5c by Serhiy Storchaka in branch 'master': |
New changeset 80e9fed by Miss Islington (bot) in branch '3.7': |
Seems this is a temporary issue. Tests are failed due to trace.cover files left from previous runs. Recreating the working space from zero should fix the issue, but I don't know how to do this on all buildbots. |
@zach.ware Is there a way to clean the workspace of these buildbots programmatically/from the UI? I can do it myself if you tell me how it must be done. |
No, there isn't. However, python/buildmaster-config#43 should help; I'll try to get that deployed later today. |
It looks like python/buildmaster-config#43 won't actually help; I changed it to use |
Can we manually ssh into the buildbots from the buildbot master and delete the file? |
It may be easier to remove "trace.cover" before testing every time than clean up all buildbots once. |
No, there is no access to the workers except for the connection created by each worker for the purpose of buildbot communication (and individually by each worker owner).
I agree. Alternately, the test could be changed to avoid that assertion; it's strange that the test could fail just because a file could happen to exist outside of the test's control. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: