After backporting a patch from Neal (to make test_timeout less likely
to fail on the Mac buildbot slave living at python.org), all 14
are green. Yippee! Let's keep 'em that way. You can all take the
weekend off ;-)
I believe it's possible to fiddle the buildbot master to send email
when a test run fails, and maybe it's time to start doing that.
BTW, there's still one compiler warning on Windows, on the trunk:
warning C4267: 'initializing' : conversion from 'size_t' to
'int', possible loss of data
Has anyone else noticed this? For a long time (possibly years), I see
an infrequent error in test_socket_ssl, like so (this is on WinXP
test test_socket_ssl crashed -- exceptions.TypeError: 'NoneType'
object is not callable
I haven't been able to provoke it by running test_socket_ssl in a
loop, and I don't have a guess about what's going wrong by eyeballing
test_rude_shutdown() is dicey, relying on a sleep() instead of proper
synchronization to make it probable that the `listener` thread goes
away before the main thread tries to connect, but while that race may
account for bogus TestFailed deaths, it doesn't seem possible that it
could account for the kind of failure above.
I'd like to freeze the release24-maint branch for 2.4.3c1 this
Thursday 23rd March from 0000 UTC. I'll post a note once that's done,
but as usual, please please only check in critical fixes in the week
between 2.4.3c1 and 2.4.3 (which will follow next week).
Please let me know if you have any issues with this. Should I also put
this sort of information somewhere on the web? Maybe a slot at the
top of the buildbot page?
Anthony Baxter <anthony(a)interlink.com.au>
It's never too late to have a happy childhood.