Message4515

Author kfitch42
Recipients billiejoex, kfitch42, pjenvey
Date 2009-04-15.14:40:37
SpamBayes Score 2.5598462e-07
Marked as misclassified No
Message-id <1239806438.24.0.599756881215.issue1312@psf.upfronthosting.co.za>
In-reply-to
Content
So I checked out the latest code, and the 'buffer' issue is gone, but I
still had to tweak SUPPORTS_IPV6 to get it to run. Also, the test suite
does not pass under CPython. The first thing that jumped out at me is
that it is checking for equality of floating point numbers, generally a
BIG no-no. In particular since, at a glance, those numbers are related
to something called 'CallLater'. Usually when scheduling something in
the future you can only so it will happen no-sooner-than, not exactly at.

That being said, I see nothing like what was described in the original
bug report. To be honest, my best guess is that this is actually a
hardware issue (bad ram?) or perhaps a currupted disk ... since the JVM
"shouldn't" crash.
History
Date User Action Args
2009-04-15 14:40:38kfitch42setmessageid: <1239806438.24.0.599756881215.issue1312@psf.upfronthosting.co.za>
2009-04-15 14:40:38kfitch42setrecipients: + kfitch42, pjenvey, billiejoex
2009-04-15 14:40:38kfitch42linkissue1312 messages
2009-04-15 14:40:37kfitch42create