Open GoogleCodeExporter opened 9 years ago
Looks like this is still a problem in version 1.3.1. If you run this without
the versbose flag (e.g. nosetests --processes=4 --with-id), the tests do not
fail, but the .noseids file is populated with only a few lines of data, such
that the --failed flag is useless (all tests get rerun, regardless of whether
they passed or failed.
Any chance someone is working on a fix for this?
Original comment by nguilf...@gmail.com
on 29 Apr 2014 at 1:01
I don't have a patch for this issue, but I built a plugin to help get around it:
https://github.com/dustinkeitel/goober
This plugin prints out 'nosetests -v' plus the paths to those failing tests
upon the completion of a test run. The idea is to make it as easy as possible
to just run the troublesome tests from a multiprocess test run.
You run: nosetests --goober --processes=-1 path/to/tests
The output looks like:
YOU SHOULD RE-RUN:
nosetests -v --goober path/to/failed.py:test_1 path/to/errored.py:test_2
Original comment by dustin.k...@gmail.com
on 28 Aug 2014 at 5:39
Hi Dustin. I finally got around to integrating goober and in combination with
sed to automate retries, it works great. Many thanks!
Original comment by nguilf...@gmail.com
on 6 Jan 2015 at 1:08
Original issue reported on code.google.com by
anh.hai....@gmail.com
on 16 Aug 2011 at 7:30