This was meant to be a "Yup, she's all good" exercise before 2.4 final goes out the door. Not quite so simple, unfortunately. . . (FWIW, I doubt this is a Python problem, but I'd like some of the other folks here who use Cygwin to have a look at the failure symptoms) My Python build (built & running under Cygwin) seems to be having trouble with any tests involving threads (test_asynchat, test_thread, test_threaded_import, test_socket_ssl for starters). When run using "./python -E Lib/test/regrtest.py -unetwork,decimal -r", several tests execute normally, then the test execution hangs. From what I can tell, the hang generally occurs on the first test that makes use of threading. When run on their own, the affected tests run for a short while, then terminate abruptly (i.e. regrtest.py doesn't print its result summary, and the output from the tests themselves shows they haven't run to completion). I suspect (hope?) that the problem is actually in my Cygwin setup rather than in Python, but I'm trying to figure out how to go about proving that. I did a 'make clean' and rebuild to see if stale files were the problem, then a 'make install' to see if the problem was accidentally picking the old python2.3 DLL's instead of the python2.4 DLL's, but neither of those appeared to make any difference. I only got the regression tests working *at all* today, after doing 'find . -name "\.dll" | rebaseall -T -' from my python/dist/src directory to get rid of the Cygwin remap errors when loading DLL's. I figured I'd ask the folks here for ideas (is Jason still around?), before trying to ask the question from the Cygwin end. Cheers, Nick. -- Nick Coghlan | Brisbane, Australia Email: ncoghlan@email.com | Mobile: +61 409 573 268
Nick, On Sat, Nov 20, 2004 at 01:03:42AM +1000, Nick Coghlan wrote:
I only got the regression tests working *at all* today, after doing 'find . -name "\.dll" | rebaseall -T -' from my python/dist/src directory to get rid of the Cygwin remap errors when loading DLL's.
The above is expected behavior, but see below...
I figured I'd ask the folks here for ideas (is Jason still around?), before trying to ask the question from the Cygwin end.
Yes, I'm still around. :,) What Cygwin version are you using? 1.5.12? FWIW, I got the following results when running Python-2.4b1's normal (i.e., no extras) regression test: $ ./python.exe -E -tt ./Lib/test/regrtest.py -l ... 252 tests OK. 2 tests failed: test_subprocess test_tcl ... The above results was under a pre-1.5.12 Cygwin CVS on XP Pro SP1: $ uname -a CYGWIN_NT-5.1 gelpdevjt022 1.5.12(0.116/4/2) 2004-10-28 07:28 ... Amazingly, I did *not* need to run rebase like I normal do! Please let me know if you need help tracking down Cygwin related problems. Thanks, Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
Jason Tishler wrote:
Nick,
On Sat, Nov 20, 2004 at 01:03:42AM +1000, Nick Coghlan wrote:
I only got the regression tests working *at all* today, after doing 'find . -name "\.dll" | rebaseall -T -' from my python/dist/src directory to get rid of the Cygwin remap errors when loading DLL's.
The above is expected behavior, but see below...
I thought so - it was your advice that Google turned up to tell me how to fix it :)
I figured I'd ask the folks here for ideas (is Jason still around?), before trying to ask the question from the Cygwin end.
Yes, I'm still around. :,)
What Cygwin version are you using? 1.5.12?
1.5.11 (also on XP Pro SP1)
$ uname -a
CYGWIN_NT-5.1 pseudopolis 1.5.11(0.116/4/2) 2004-09-04 23:17 ...
I'll try updating all the Cygwin packages and see where that gets me.
Nick, On Sat, Nov 20, 2004 at 12:28:50PM +1000, Nick Coghlan wrote:
Jason Tishler wrote:
What Cygwin version are you using? 1.5.12?
1.5.11 (also on XP Pro SP1)
Cygwin 1.5.11 has some issues (e.g., pthreads), which is why I skipped that version... :,)
I'll try updating all the Cygwin packages and see where that gets me.
Did you upgrade Cygwin to 1.5.12?
Now it's hanging in configure (and the m4 interpreter was one of the things that got updated). *sigh* I need to wake up more before I dig into this.
The above is strange, but the m4 package was just taken over by another maintainer.
If you (or anyone else) could check that the unit tests work on Cygwin for you, that would make me more certain that this is just a problem with my own Cygwin setup, and not related to anything in 2.4c1 that wasn't in 2.4b1.
I just upgraded one of my machines to Cygwin 1.5.12, but I did not upgrade the other packages. I get the following results: failures: test_shutil (passed under older Cygwin and/or Python versions) test_subprocess (new test) test_tcl (new test) hangs: test_threaded_import (passed under older Cygwin and/or Python versions) I will investigate the above and report back. Thanks, Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
Jason Tishler wrote:
Did you upgrade Cygwin to 1.5.12?
I did. However, the bash shell was just behaving strangely after that, as was the Cygwin installer itself. I tried to do a clean install, and the install program is now hanging. So I don't think we can take any error reports from my system seriously at this point. Something isn't happy :( Anyway, I won't be posting any more about this on py-dev, since I've established that *my* problems probably aren't Python related. Cheers, Nick. -- Nick Coghlan | Brisbane, Australia Email: ncoghlan@email.com | Mobile: +61 409 573 268
Nick Coghlan wrote:
Anyway, I won't be posting any more about this on py-dev, since I've established that *my* problems probably aren't Python related.
I lied. The *real* final word - some digging with Google shows that there are still some issues with Cygwin and hyperthreaded processors. Sure enough, my desktop is a hyper-threaded P4. Just a minor detail the "Known Problems" section in the Cygwin FAQ neglects to mention. . . Cheers, Nick. -- Nick Coghlan | Brisbane, Australia Email: ncoghlan@email.com | Mobile: +61 409 573 268
Nick, On Mon, Nov 22, 2004 at 09:52:24PM +1000, Nick Coghlan wrote:
Nick Coghlan wrote:
Anyway, I won't be posting any more about this on py-dev, since I've established that *my* problems probably aren't Python related.
I lied. The *real* final word - some digging with Google shows that there are still some issues with Cygwin and hyperthreaded processors. Sure enough, my desktop is a hyper-threaded P4.
Mine too. I guess the above may explain why I can't get test_threaded_import to hang again... Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
On Sat, Nov 20, 2004 at 10:06:37AM -0500, Jason Tishler wrote:
If you (or anyone else) could check that the unit tests work on Cygwin for you, that would make me more certain that this is just a problem with my own Cygwin setup, and not related to anything in 2.4c1 that wasn't in 2.4b1.
I just upgraded one of my machines to Cygwin 1.5.12, but I did not upgrade the other packages. I get the following results:
failures:
test_shutil (passed under older Cygwin and/or Python versions) test_subprocess (new test) test_tcl (new test)
hangs:
test_threaded_import (passed under older Cygwin and/or ...
I will investigate the above and report back.
AFAICT, the above (with possibly one exception) are due to Cygwin bugs. I can provide more details if anyone is interested. On Sat, Nov 20, 2004 at 01:03:42AM +1000, Nick Coghlan wrote:
This was meant to be a "Yup, she's all good" exercise before 2.4 final goes out the door.
IMO, "Yup, she's all good!" :,) The test_tcl test case is failing under Cygwin because it expects loadtk() to fail if the DISPLAY environment variable is not set. However, under Cygwin we have the following: >>> import os, Tkinter >>> del os.environ['DISPLAY'] >>> Tkinter.Tcl().loadtk() >>> The above works because Cygwin's Tcl/Tk renders directly on the Windows GDI instead of going through an X Server. Can I submit a patch to test_tcl to skip this test as is done for win and darwin? Thanks, Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
Jason Tishler wrote:
The test_tcl test case is failing under Cygwin because it expects loadtk() to fail if the DISPLAY environment variable is not set. However, under Cygwin we have the following:
>>> import os, Tkinter >>> del os.environ['DISPLAY'] >>> Tkinter.Tcl().loadtk() >>>
The above works because Cygwin's Tcl/Tk renders directly on the Windows GDI instead of going through an X Server. Can I submit a patch to test_tcl to skip this test as is done for win and darwin?
You could, but I just fixed it anyway. =) In revision 1.6 . -Brett
Brett, On Tue, Nov 23, 2004 at 07:02:18PM -0800, Brett C. wrote:
Jason Tishler wrote:
The above works because Cygwin's Tcl/Tk renders directly on the Windows GDI instead of going through an X Server. Can I submit a patch to test_tcl to skip this test as is done for win and darwin?
You could, but I just fixed it anyway. =) In revision 1.6 .
Thanks! Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
participants (3)
-
Brett C. -
Jason Tishler -
Nick Coghlan