nose + processes + xunit

N

Noon Silk

Has anyone had any trouble with this setup?

I am in a situation where, the tests run fine when I don't include
"--processes=N", however, when I *do* do that, they exit early?

The reason I think they exit, is that I'm actually running a different
executable, and I load it like so:

retcode = subprocess.call(["start /wait myprog.exe"], shell=True)

Now, note that this is on Windows 7; the "start /wait" does basically
exactly what you think. *And indeed it operates correctly in a single
process*, but when nose tries to run multi-process, it fails to block,
and the test executes far sooner than it should.

Indeed, Nose claims that it ran 0 tests, when it actually at least ran
1! So, I think the myprog.exe is sending some signal to kill it.

It so happens that start has a "/B"  parameter that may also help
here, but actually it doesn't. The result is that I don't get any
further output from the test (that is, the xunit xml isn't generated,
and even the console doesn't report anything as having happened).

Interested in thoughts ...

--
Noon Silk

Fancy a quantum lunch? http://groups.google.com/group/quantum-lunch?hl=en

"Every morning when I wake up, I experience an exquisite joy — the joy
of being this signature."
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,954
Messages
2,570,116
Members
46,704
Latest member
BernadineF

Latest Threads

Top