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 ned.deily
Recipients amaajemyfren, docs@python, hroncok, mdk, ned.deily, petdance, vstinner
Date 2020-05-28.22:25:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content
I think our CI checks already take too long to run and use possibly more than our fair share of global open source resources (provided by GitHub, Travis, MS Azure) especially considering how infrequently you would expect to find a problem and the low severity of missing one immediately.  I think a more appropriate choice would be to set up a buildbot to do such a check, perhaps weekly is often enough, not more than daily.

Julien, what do you think?
History
Date User Action Args
2020-05-28 22:25:23ned.deilysetrecipients: + ned.deily, vstinner, docs@python, mdk, hroncok, amaajemyfren, petdance
2020-05-28 22:25:23ned.deilysetmessageid: <[email protected]>
2020-05-28 22:25:23ned.deilylinkissue40770 messages
2020-05-28 22:25:23ned.deilycreate