On Sun, Feb 13, 2005 at 12:09:21PM -0500, Christopher Faylor wrote: > On Mon, Feb 14, 2005 at 01:17:03AM +1000, Nick Coghlan wrote: > >Nick Coghlan wrote: > >Command lines looked like (with thread and file counts filled in): $ > >python /lib/python2.4/test/test_threadedtempfile.py -t <threads> -f > ><files> > > > >The results weren't particularly deterministic, beyond a general > >'more threads, more files' -> 'more likely to hang'. 10 & 10 seemed > >to do it fairly effectively although even that would occasionally > >succeed (the default is 20 & 20). > > > >When it *did* hang, it was with a number of threads successfully > >opening their files on an iteration, with the remainder of the > >threads locking up attempting to open a new temporary file. The next > >time around, the remaining threads would hang while attempting to > >open the temporary file. > > > >The main script hangs because it is waiting for the threads to > >terminate. > > Is this a regression?
I don't know. > Was this also problem with 1.5.12? AFAICT, no. However, another threaded regression test hung in 1.5.12 as indicated in the README: Under XP Pro SP1, Cygwin 1.5.12-1, ntsec, and NTFS, Cygwin Python passes all tests except for following: ... test_threaded_import (occasionally hangs) So, maybe I was just "lucky" test_threadedtempfile did not hang when I ran the regression test especially since it hung under 1.5.10-3. 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 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/