Message194656
| Author | sbt |
|---|---|
| Recipients | Stan.Seibert, asksol, brandon-rhodes, catalin.iacob, christian.heimes, dholth, gregory.p.smith, jnoller, mrmekon, ned.deily, neologix, numbernine, pitrou, rcoyner, sbt, vsekhar |
| Date | 2013-08-08.09:44:19 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <5203686C.30708@gmail.com> |
| In-reply-to | <1375948722.86.0.204906917562.issue8713@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> Richard, can you say what failed on the OS X 10.4 (Tiger) buildbot?
There seems to be a problem which depends on the order in which you run
the test, and it happens on Linux also. For example if I do
./python -m test -v \
test_multiprocessing_fork \
test_multiprocessing_forkserver
Then I get lots of failures when forkserver runs. I have tracked down
the changeset which caused the problem, but I have not had time to look
in to it.
> The only vaguely suspicious message when running with -v was:
> [...]
> [semaphore_tracker] '/mp18203-0': [Errno 22] Invalid argument
> [semaphore_tracker] '/mp18203-1': successfully unlinked
> [...]
That is expected and it shows the semaphore tracker is working as
expected. Maybe I should print a note to stderr to expect this. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-08-08 09:44:19 | sbt | set | recipients: + sbt, gregory.p.smith, pitrou, christian.heimes, ned.deily, jnoller, rcoyner, asksol, dholth, brandon-rhodes, neologix, catalin.iacob, numbernine, vsekhar, mrmekon, Stan.Seibert |
| 2013-08-08 09:44:19 | sbt | link | issue8713 messages |
| 2013-08-08 09:44:19 | sbt | create | |