Oh, maybe I saw them. Are you talking about: "test_multiprocessing_forkserver: TestIgnoreEINTR.test_ignore() fails on Travis CI" https://bugs.python.org/issue33531
"test_asyncio: test_subprocess test_stdin_broken_pipe() failure on Travis CI" https://bugs.python.org/issue33532 (I just created these two issues.) Victor 2018-05-16 2:22 GMT-04:00 Victor Stinner <vstin...@redhat.com>: > It seems like the job has been rescheduled. I cannot see the failure > ("394 tests OK"). Would you mind to open a bug report? > > Do you only see these failures in the 3.6 branch? > > Victor > > 2018-05-15 16:36 GMT-04:00 Terry Reedy <tjre...@udel.edu>: >> I am getting repeated bogus failures, completely unrelated to a trivial >> patch, more often than not, on Travis-CI >> For instance, >> https://travis-ci.org/python/cpython/jobs/379349709 >> 2 tests failed: >> test_asyncio test_multiprocessing_forkserver >> 1 test altered the execution environment: >> test_importlib >> >> The failures repeated on retest. Can someone turn off the bad test methods? >> >> tjr >> >> _______________________________________________ >> python-committers mailing list >> python-committers@python.org >> https://mail.python.org/mailman/listinfo/python-committers >> Code of Conduct: https://www.python.org/psf/codeofconduct/ _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
