Brett Cannon added the comment: So the reason we don't have the coverage run complain loudly is it takes at least 40 minutes to complete, so having to wait for that could potentially be annoying if you're e.g. trying to merge a cherry-pick and you just want to verify you didn't break anything.
And yes, there might be some connection to issue #29048. To keep things simple we can close this in favour of the other issue and track the work there. ---------- superseder: -> Coverage influence tests, make some of them fail _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29691> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
