regrtest hangs on test_tk_guionly
In the trunk, test_tk_guionly hangs if I run it through regrtest. This is on a Fedora Core 6 box, without X installed. If I run test_tk_guionly directly, it exits saying there's no DISPLAY set, which is what I'd expect: ------8<------------------ [trunk]$ ./python Lib/test/test_ttk_guionly.py Traceback (most recent call last): File "Lib/test/test_ttk_guionly.py", line 11, in <module> raise test_support.TestSkipped("ttk not available: %s" % msg) test.test_support.TestSkipped: ttk not available: no display name and no $DISPLAY environment variable [29788 refs] ------8<------------------ If I run regrtest with (or without) -v, it hangs without any output from test_tk_guionly: ------8<------------------ ... OK test_transformer Test multiple targets on the left hand side. ... ok ---------------------------------------------------------------------- Ran 1 test in 0.020s OK test_ttk_guionly <hangs here> ------8<------------------ I'm not seeing a problem in the py3k branch. There, test_tk_guionly is skipped: ------8<------------------ test_ttk_guionly test_ttk_guionly skipped -- ttk not available: no display name and no $DISPLAY environment variable ------8<------------------ I'm not sure how to further isolate this, since I can't duplicate it when running the test by itself. I'm mostly curious if anyone else is seeing this problem. If it's just me, I'll just switch to a Mac, where the problem doesn't occur (if for no other reason, because ttk is not available). If others are seeing a problem, I'll spend some time isolating it. Is anyone else seeing this problem? Eric.
On Fri, Feb 6, 2009 at 1:14 PM, Eric Smith <eric@trueblade.com> wrote:
In the trunk, test_tk_guionly
test_ttk_guionly, right ?
hangs if I run it through regrtest. This is on a Fedora Core 6 box, without X installed.
Does it hang if you run it alone through regrtest, or, together with all the other tests ?
If I run test_tk_guionly directly, it exits saying there's no DISPLAY set, which is what I'd expect:
------8<------------------ [trunk]$ ./python Lib/test/test_ttk_guionly.py Traceback (most recent call last): File "Lib/test/test_ttk_guionly.py", line 11, in <module> raise test_support.TestSkipped("ttk not available: %s" % msg) test.test_support.TestSkipped: ttk not available: no display name and no $DISPLAY environment variable [29788 refs] ------8<------------------
If I run regrtest with (or without) -v, it hangs without any output from test_tk_guionly:
------8<------------------ ... OK test_transformer Test multiple targets on the left hand side. ... ok
---------------------------------------------------------------------- Ran 1 test in 0.020s
OK test_ttk_guionly <hangs here> ------8<------------------
I'm not seeing a problem in the py3k branch. There, test_tk_guionly is skipped:
------8<------------------ test_ttk_guionly test_ttk_guionly skipped -- ttk not available: no display name and no $DISPLAY environment variable ------8<------------------
I'm not sure how to further isolate this, since I can't duplicate it when running the test by itself. I'm mostly curious if anyone else is seeing this problem. If it's just me, I'll just switch to a Mac, where the problem doesn't occur (if for no other reason, because ttk is not available). If others are seeing a problem, I'll spend some time isolating it.
Is anyone else seeing this problem?
I've noticed it, it is on http://bugs.python.org/issue5122 The second part of the issue description is actually unrelated to the problem (or at least I'm almost sure it is), so you may discard it. I wasn't able to duplicate it here, but I could try installing fedora here to try reproducing and see if I can solve it.
Eric.
-- -- Guilherme H. Polo Goncalves
Guilherme Polo wrote:
On Fri, Feb 6, 2009 at 1:14 PM, Eric Smith <eric@trueblade.com> wrote:
In the trunk, test_tk_guionly
test_ttk_guionly, right ?
Right, sorry.
hangs if I run it through regrtest. This is on a Fedora Core 6 box, without X installed.
Does it hang if you run it alone through regrtest, or, together with all the other tests ?
It does not hang: [trunk]$ ./python Lib/test/regrtest.py test_ttk_guionly test_ttk_guionly test_ttk_guionly skipped -- ttk not available: no display name and no $DISPLAY environment variable 1 test skipped: test_ttk_guionly 1 skip unexpected on linux2: test_ttk_guionly
I've noticed it, it is on http://bugs.python.org/issue5122
The second part of the issue description is actually unrelated to the problem (or at least I'm almost sure it is), so you may discard it. I wasn't able to duplicate it here, but I could try installing fedora here to try reproducing and see if I can solve it.
Unfortunately I can't give you access to this machine. Maybe http://www.snakebite.org/ will be able to help. If you think my issue is related to 5122, I'll reply to that issue and move the discussion there. I can test on a Fedora 10 box, too. Eric.
On Fri, Feb 6, 2009 at 1:34 PM, Eric Smith <eric@trueblade.com> wrote:
If you think my issue is related to 5122, I'll reply to that issue and move the discussion there. I can test on a Fedora 10 box, too.
Eric, I've followed the "amd64 gentoo trunk" buildslave and noticed it took a very long time on test_tcl (or test_ttk_guionly) and then ended up getting the error described in the issue. As I see, the test hanged and buildslave decided to quit. -- -- Guilherme H. Polo Goncalves
On Fri, Feb 6, 2009 at 1:14 PM, Eric Smith <eric@trueblade.com> wrote:
If it's just me, I'll just switch to a Mac, where the problem doesn't occur (if for no other reason, because ttk is not available). If others are seeing a problem, I'll spend some time isolating it.
If you move to Mac then you may end with an abort :) See http://www.python.org/dev/buildbot/all/OS%20X%20x86%20trunk/builds/99/step-t... I tried asking emailing noller to ask what tcl is installed on that mac but I got no answer, so in this case the buildslave serves me no purpose. Apparently it doesn't happen all the time (after a change on how the tcl interpreter was being created in the tests) but it still happens sometimes. I also opened an issue for this, see: http://bugs.python.org/issue5120, I ended up closing it after checking that this noller buildslave stopped aborting but it still happens from time to time. -- -- Guilherme H. Polo Goncalves
participants (2)
-
Eric Smith -
Guilherme Polo