WARNING: A test appears to be hung. There has been no output for 600 seconds.
Forcibly shutting down the test suite
I think this is a bit bogus to say "won't fix." make check is a very well established convention for something people ought to be able to run to check their work.
Is there something that makes 'make check' reliable when run by automated test runs but not for interactive use?
I just hit this too:
lp.archiveuplo ader.tests. test_ppauploadp rocessor. TestPPAUploadPr ocessor. testPPAUploadRe sultingInNoBuil ds
WARNING: A test appears to be hung. There has been no output for 600 seconds.
Forcibly shutting down the test suite
I think this is a bit bogus to say "won't fix." make check is a very well established convention for something people ought to be able to run to check their work.
Is there something that makes 'make check' reliable when run by automated test runs but not for interactive use?