On Fri, Feb 6, 2009 at 1:34 PM, Eric Smith 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
On Fri, Feb 6, 2009 at 1:14 PM, Eric Smith 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 a
Guilherme Polo wrote:
On Fri, Feb 6, 2009 at 1:14 PM, Eric Smith 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,
On Fri, Feb 6, 2009 at 1:14 PM, Eric Smith 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 ?
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
