New submission from Chris Jerdonek <chris.jerdo...@gmail.com>: Running tests using the -j/--multiprocess option doubly-nests the test working directory:
$ ./python.exe -m test -j3 -->cpython/build/test_python_63955/build/test_python_63956 $ ./python.exe -m test -->cpython/build/test_python_63957 It seems like the test directories for different processes should be siblings when running in multiprocessing mode as opposed to doubly-nesting under a new build directory. ---------- components: Tests messages: 165052 nosy: cjerdonek priority: normal severity: normal status: open title: test directory doubly-nested running tests with -j/--multiprocess versions: Python 3.3 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15300> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
