[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

Stefan Krah added the comment: Thanks for looking at the patch! Committed in r81676. -- resolution: -> accepted status: open -> closed ___ Python tracker ___ ___

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

R. David Murray added the comment: I can't believe I messed that up. Yes, the patch looks fine, please apply. -- ___ Python tracker ___ _

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

Stefan Krah added the comment: On 2.6, the tests aren't skipped if test_support.verbose is 0. David, if the fix looks good to you I can apply it. test_itimer_virtual: timeout: likely cause: machine too slow or load too high. test test_signal failed -- Traceback (most recent call last): File

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

R. David Murray added the comment: Skips ported to 2.6 in r80295, py3k in r80296, and 3.1 in r80297. -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker _

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

R. David Murray added the comment: The FreeBSD bot in question is now running 6.4, and test_signal is still failing. I have access to a 6.3 box, which shows exactly the same failures as I see in the buildbot log. On that box, doing t = threading.Thread(target=lambda: None) t.start()

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

Mark Dickinson added the comment: I'm hoping (though it's only a faint hope) that the change in r75986 might allow the test suite to run to completion on the FreeBSD buildslave. -- nosy: +mark.dickinson ___ Python tracker

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

R. David Murray added the comment: Since this is apparently a known FreeBSD bug, we should put a conditional skip into test_signal. -- components: +Tests stage: -> needs patch type: -> behavior ___ Python tracker

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

Eric Smith added the comment: http://www.python.org/dev/buildbot/all/builders/x86%20FreeBSD%20trunk reports: FreeBSD 6.2-RELEASE (VMWare Image, 256MB, 10GB on P4/1.8GHz Host) -- nosy: +eric.smith ___ Python tracker

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

R. David Murray added the comment: Does anyone know what version of FreeBSD the FreeBSD buildslave is running? This problem is affecting most of its runs. -- keywords: +buildbot nosy: +r.david.murray versions: +Python 2.7, Python 3.1, Python 3.2 ___

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment: The tests are passing on FreeBSD 7.0 (only checked amd64 at this point). I came across a reference to an errata notice for FreeBSD 6.x which appears pertinent: http://security.freebsd.org/advisories/FreeBSD-EN-08:01.libpthread.asc As I r

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

Guilherme Polo <[EMAIL PROTECTED]> added the comment: Last time I checked many more would cause ItimerTest to not run properly, these were: test_asynchat, test_asyncore, test_decimal, text_docxmlrpc, test_ftplib, test_logging, test_poplib, test_queue, test_smtplib, test_socket and all these tests

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment: I should be more specific: itimer_test_prof (test.test_signal.ItimerTest) appears to go into an infinite loop when run after test_fork1 or test_wait4 have been run. ___ Python tracker <[EMAIL PROTECTED]

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment: >From the problematic test run log: ... test_main (test.test_signal.InterProcessSignalTests) ... FAIL ... I should be using the full name, sorry. This failure seems unrelated to the itimer problem though (which is in itimer_test_prof).

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

Guilherme Polo <[EMAIL PROTECTED]> added the comment: When you say "interprocess signal test" do you actually mean ItimerTest ? Because I don't see the former failing, and the later hangs because signals are not being delivered to it (SIGVTALRM neither SIGPROF). _

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment: Spelunking with test_fork1, it seems that the interprocess signal test failure is due to the HUP signal not being delivered from the subprocess to the parent (line 99 of test_signal.py: self.assertTrue(self.a_called).

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment: I compiled the C test case from issue 2240: $ gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -o test_2240 test_2240.c {lifted as many gcc options off the standard Python compile as possible} $ ldd test_2240 test_2240:

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment: After perusing test_wait4, I tried substituting test_fork1 for test_wait4 and got the same behaviour from test_signal. ___ Python tracker <[EMAIL PROTECTED]> _

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment: Oops - the itimer tests are in test_signal, not test_wait4. test_wait4 just triggers the problems in test_signal (both the itimer problems and the interprocess signal test failure). ___ Python tracker

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment: I've had a chance to do some testing and it _is_ related to the itimer tests (in test_wait4). This is with r66550: $ ./python -E -tt ./Lib/test/regrtest.py -l -v test_wait4 test_signal test_wait4 test_wait (test.test_wait4.Wait4Test) ...

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment: It doesn't appear to me to be related to issue 2240, as my build linked against libpthread: $ ldd ./python ./python: libutil.so.5 => /lib/libutil.so.5 (0x28187000) libm.so.4 => /lib/libm.so.4 (0x28193000) libpthrea

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

Guilherme Polo <[EMAIL PROTECTED]> added the comment: Can you check if it is not the itimer tests that are causing that ? I'm interested in gathering some more info about the problem and hopefully fixing it now. Take a look into issue2240 and verify if it is related to your problem, please.

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

Changes by Andrew I MacIntyre <[EMAIL PROTECTED]>: -- versions: +Python 2.6 ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-l