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 vstinner
Recipients ned.deily, vstinner, zach.ware
Date 2017-09-05.23:50:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1504655434.83.0.185912126913.issue31355@psf.upfronthosting.co.za>
In-reply-to
Content
Failures of the two Allowed Failure jobs, coverage and macOS, are not reported to GitHub PR. For example, the coverage job is failing on Python 3.6 since May 2016 at least, and nobody noticed.

I don't think that it's worth it to waste Travis CI resources if nobody notices failures.

See https://github.com/python/core-workflow/issues/101 for the discussion on Allowed Failures on Travis CI.
History
Date User Action Args
2017-09-05 23:50:34vstinnersetrecipients: + vstinner, ned.deily, zach.ware
2017-09-05 23:50:34vstinnersetmessageid: <1504655434.83.0.185912126913.issue31355@psf.upfronthosting.co.za>
2017-09-05 23:50:34vstinnerlinkissue31355 messages
2017-09-05 23:50:34vstinnercreate