[issue34171] Lib/trace.cover not removed by the clean target

Change by Cheryl Sabella : -- stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list

[issue34171] Lib/trace.cover not removed by the clean target

Serhiy Storchaka added the comment: New changeset e3f20828f6b7f59baa2d25437176ee32ae7700b0 by Serhiy Storchaka (Miss Islington (bot)) in branch '3.7': bpo-34171: Fix test_trace. (GH-8940) (GH-8951) https://github.com/python/cpython/commit/e3f20828f6b7f59baa2d25437176ee32ae7700b0 --

[issue34171] Lib/trace.cover not removed by the clean target

Change by miss-islington : -- pull_requests: +8427 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34171] Lib/trace.cover not removed by the clean target

Serhiy Storchaka added the comment: New changeset b44a1d4f71daf4edb948b9878f82a60891e4a2e1 by Serhiy Storchaka in branch 'master': bpo-34171: Fix test_trace. (GH-8940) https://github.com/python/cpython/commit/b44a1d4f71daf4edb948b9878f82a60891e4a2e1 --

[issue34171] Lib/trace.cover not removed by the clean target

Zachary Ware added the comment: > Can we manually ssh into the buildbots from the buildbot master and delete > the file? 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).

[issue34171] Lib/trace.cover not removed by the clean target

Serhiy Storchaka added the comment: It may be easier to remove "trace.cover" before testing every time than clean up all buildbots once. -- ___ Python tracker ___

[issue34171] Lib/trace.cover not removed by the clean target

Change by Serhiy Storchaka : -- pull_requests: +8413 stage: resolved -> patch review ___ Python tracker ___ ___ Python-bugs-list

[issue34171] Lib/trace.cover not removed by the clean target

Pablo Galindo Salgado added the comment: Can we manually ssh into the buildbots from the buildbot master and delete the file? -- ___ Python tracker ___

[issue34171] Lib/trace.cover not removed by the clean target

Zachary Ware added the comment: It looks like https://github.com/python/buildmaster-config/pull/43 won't actually help; I changed it to use `method='clean'` because we don't want to blow away the `externals` directory on Windows buildbots, and `*.cover` is in `.gitignore` so

[issue34171] Lib/trace.cover not removed by the clean target

Zachary Ware added the comment: No, there isn't. However, https://github.com/python/buildmaster-config/pull/43 should help; I'll try to get that deployed later today. -- ___ Python tracker

[issue34171] Lib/trace.cover not removed by the clean target

Pablo Galindo Salgado added the comment: @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. -- nosy: +zach.ware ___ Python tracker

[issue34171] Lib/trace.cover not removed by the clean target

Serhiy Storchaka added the comment: 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. --

[issue34171] Lib/trace.cover not removed by the clean target

Pablo Galindo Salgado added the comment: Several buildbots are failing due to commit c406d5cd74002964a64c3eb7d9e2445a7fd3a03f: https://buildbot.python.org/all/#/builders/40/builds/709 https://buildbot.python.org/all/#/builders/21/builds/1459

[issue34171] Lib/trace.cover not removed by the clean target

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue34171] Lib/trace.cover not removed by the clean target

miss-islington added the comment: New changeset 80e9fedcf579537c5bc51ff3c9c18d14d9598564 by Miss Islington (bot) in branch '3.7': bpo-34171: Prevent creating Lib/trace.cover when run the trace module. (GH-8841) https://github.com/python/cpython/commit/80e9fedcf579537c5bc51ff3c9c18d14d9598564

[issue34171] Lib/trace.cover not removed by the clean target

Change by miss-islington : -- pull_requests: +8392 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34171] Lib/trace.cover not removed by the clean target

Serhiy Storchaka added the comment: New changeset c406d5cd74002964a64c3eb7d9e2445a7fd3a03f by Serhiy Storchaka in branch 'master': bpo-34171: Prevent creating Lib/trace.cover when run the trace module. (GH-8841)

[issue34171] Lib/trace.cover not removed by the clean target

Change by Serhiy Storchaka : -- nosy: +berker.peksag ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34171] Lib/trace.cover not removed by the clean target

Serhiy Storchaka added the comment: PR 8841 prevents creating Lib/trace.cover when run the trace module. -- nosy: +serhiy.storchaka ___ Python tracker ___

[issue34171] Lib/trace.cover not removed by the clean target

Change by Serhiy Storchaka : -- pull_requests: +8315 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34171] Lib/trace.cover not removed by the clean target

Change by Berker Peksag : -- keywords: +patch pull_requests: +8161 stage: -> patch review ___ Python tracker ___ ___

[issue34171] Lib/trace.cover not removed by the clean target

Zackery Spytz added the comment: It seems that this file is left by test_trace after commit 47ab15470d72367694d7758004067313ae022f0e. -- nosy: +ZackerySpytz ___ Python tracker

[issue34171] Lib/trace.cover not removed by the clean target

New submission from Matthias Klose : 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. --