[issue33531] test_asyncio: test_subprocess test_stdin_broken_pipe() failure on Travis CI
STINNER Victor
report at bugs.python.org
Fri May 18 20:42:04 EDT 2018
STINNER Victor <vstinner at redhat.com> added the comment:
Terry: " The Travis retest (for 3.7 backport) just failed with the same errors. Why can't we disable this tests. It now takes hours to do a merge with two backports."
Usually, I prefer to try to understand a bug before disabling, even temporarely, a test. Most of the time, a test failure means a regression. If we disable a test, we reduce the code coverage and more generally reduces the quality of the code.
I would prefer to only disable the test if nobody understand the issue and the issue blocks the workflow longer than a few days. This week, there was a CPython sprint during Pycon US, so yeah, it was annoying.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33531>
_______________________________________
More information about the Python-bugs-list
mailing list