[Python-Dev] 3.0 buildbots all red

[Mark Dickinson]

On Sun, Mar 16, 2008 at 1:32 PM, Neal Norwitz <nnorwitz at gmail.com> wrote:
>
> I think this is possible, though considerable work.  Probably the
> biggest win will be creating a mock for socket and using mock sockets
> in the tests for asyn{core,chat}, smtplib, xmlrpc, etc. That will fix
> about 75% of the problems on 2.6.  The remaining problems are:
>
>  * test_asyn{chat,core} might not be meaningful with mock sockets and are flaky
>  * the alpha fails test_signal/socket for weird alarm conditions.
> this might be hard to debug/fix (I have access to this box though)
>  * test_sqlite is broken on x86 with an old sqlite (I have access to this box)
>  * test_bsddb may be flaky, I'm not sure
>  * probably a few platform specific problems
>

test_tokenize is also currently (sometimes) failing on many of the bots.
I've been looking into it, but I'm struggling to find the problem.  The
traceback e.g. for the amd64 gentoo buildbot ends with

 File "/home/buildbot/slave/py-build/3.0.norwitz-amd64/build/Lib/io.py",
line 1081, in decode
 output = self.decoder.decode(input, final=final)
 File "/home/buildbot/slave/py-build/3.0.norwitz-amd64/build/Lib/codecs.py",
line 291, in decode
 (result, consumed) = self._buffer_decode(data, self.errors, final)
 UnicodeDecodeError: 'utf8' codec can't decode bytes in position
12-15: invalid data

On my own machine (SuSE 9.3/i686) I'm seeing this test pass about 80%
of the time and fail the other 20% with something like the above,
the position of the reported invalid data changing from run to run.  It
looks like data are getting corrupted somewhere along the line.

Anyone have any ideas?

Mark