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
Christopher Faylor wrote:
To help preserve my tenuous grasp on sanity, please reply to *this
thread* when reporting problems. Please don't start a new thread. Just
reply here so that mailing list threading is preserved and I can easily
check for all success or error reports. As before, any kind
Nick Coghlan wrote:
Christopher Faylor wrote:
Of course, I don't actually know if this is a related problem or not.
I'm hoping Chris can check it easily, since it happens with the standard
Cygwin Python, not just with the version I built from Python's current CVS.
I took the obvious step of
On Mon, Feb 14, 2005 at 01:17:03AM +1000, Nick Coghlan wrote:
Nick Coghlan wrote:
Christopher Faylor wrote:
Of course, I don't actually know if this is a related problem or not.
I'm hoping Chris can check it easily, since it happens with the standard
Cygwin Python, not just with the version I
Christopher Faylor wrote:
On Mon, Feb 14, 2005 at 01:17:03AM +1000, 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
Is this a regression? Was this also problem with 1.5.12?
Unless
On Mon, Feb 14, 2005 at 01:12:53PM +1000, Nick Coghlan wrote:
Christopher Faylor wrote:
On Mon, Feb 14, 2005 at 01:17:03AM +1000, 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
Is
Christopher Faylor wrote:
On Mon, Feb 14, 2005 at 01:12:53PM +1000, Nick Coghlan wrote:
I can't say for sure if it's a regression, since I never got 1.5.12 to work
properly at all (and hence didn't back up the bin directory before dropping
the snapshot binaries into it). At the moment, I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On my machine my own test case, and the make -j2 test case, have been
running now for more than an hour, no problem so far.
You seem to be on the right track :)
Thanks for your efforts
Christopher Faylor wrote:
I'm not claiming that it is right now. I haven't tried a make -j test
yet. I just thought it was time to release another try on the world
again:
http://cygwin.com/snapshots/
To help preserve my tenuous grasp on sanity, please reply to *this
thread* when reporting
The latest snapshot has my latest try at fixing the dreaded
hyperthreading problem. My previous fix was flawed in that once Corinna
corrected a typo in my change, the problem showed up again.
So, I've reworked the synchronization logic again and even ran cygwin
through that test suite thing that
10 matches
Mail list logo
