This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients David.Edelsohn, db3l, gvanrossum, koobs, larry, ncoghlan, neologix, pitrou, python-dev, sbt, skrah, vstinner
Date 2013-11-20.03:06:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1384916770.99.0.99798019162.issue19652@psf.upfronthosting.co.za>
In-reply-to
Content
Oh, sorry, I didn't realize the name of the failing test was in the issue title. But even that's no excuse, because it's also in the log. :-(

Fortunately the line where we're hanging is also in the log: line 291 in selectors.py is in PollSelector. So that's settled. But we don't know if that's the first of the three tests that runs or not.

What's also strange is that several other tests (test_subprocess_kill() and test_subprocess_terminate()) also send signals, so they should work exactly the same way. But again we don't know if any of them are being run before the signal test.

Do you have any other traces from the same bot? Do they all fail in the same test? Is the test order randomized?
History
Date User Action Args
2013-11-20 03:06:11gvanrossumsetrecipients: + gvanrossum, db3l, ncoghlan, pitrou, vstinner, larry, skrah, neologix, python-dev, sbt, koobs, David.Edelsohn
2013-11-20 03:06:10gvanrossumsetmessageid: <1384916770.99.0.99798019162.issue19652@psf.upfronthosting.co.za>
2013-11-20 03:06:10gvanrossumlinkissue19652 messages
2013-11-20 03:06:10gvanrossumcreate