This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author zach.ware
Recipients ZackerySpytz, berker.peksag, doko, miss-islington, pablogsal, serhiy.storchaka, zach.ware
Date 2018-08-26.17:15:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1535303758.33.0.56676864532.issue34171@psf.upfronthosting.co.za>
In-reply-to
Content
> 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).

> It may be easier to remove "trace.cover" before testing every time than clean up all buildbots once.

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.
History
Date User Action Args
2018-08-26 17:15:58zach.waresetrecipients: + zach.ware, doko, berker.peksag, serhiy.storchaka, ZackerySpytz, pablogsal, miss-islington
2018-08-26 17:15:58zach.waresetmessageid: <1535303758.33.0.56676864532.issue34171@psf.upfronthosting.co.za>
2018-08-26 17:15:58zach.warelinkissue34171 messages
2018-08-26 17:15:58zach.warecreate