[Python-3000] buildbots

[Neal Norwitz]

We got 'em.  Let the spam begin! :-)

This page is not linked from the web anywhere:
  http://python.org/dev/buildbot/3.0/

I'm not expecting a lot of signal out of them at the beginning.  All
but one has successfully compiled py3k though.  I noticed there were
many warnings on windows.  I wonder if they are important:

pythoncore - 0 error(s), 6 warning(s)
_ctypes - 0 error(s), 1 warning(s)
bz2 - 0 error(s), 9 warning(s)
_ssl - 0 error(s), 23 warning(s)
_socket - 0 error(s), 1 warning(s)

On trunk, the same machine only has:
bz2 - 0 error(s), 2 warning(s)

There are several other known warnings on various platforms:
Objects/stringobject.c:4104: warning: comparison is always false due
to limited range of data type
Python/import.c:886: warning: comparison is always true due to limited
range of data type
Python/../Objects/stringlib/unicodedefs.h:26: warning: 'STRINGLIB_CMP'
defined but not used

I find it interesting that the gentoo buildbot can run the tests to
completion even though I can't run the tests from the command line.
There was one error:

Traceback (most recent call last):
  File "/home/buildslave/python-trunk/3.0.norwitz-x86/build/Lib/test/test_normalization.py",
line 36, in test_main
    for line in open_urlresource(TESTDATAURL):
  File "/home/buildslave/python-trunk/3.0.norwitz-x86/build/Lib/io.py",
line 1240, in __next__
    line = self.readline()
  File "/home/buildslave/python-trunk/3.0.norwitz-x86/build/Lib/io.py",
line 1319, in readline
    readahead, pending = self._read_chunk()
  File "/home/buildslave/python-trunk/3.0.norwitz-x86/build/Lib/io.py",
line 1123, in _read_chunk
    pending = self._decoder.decode(readahead, not readahead)
  File "/home/buildslave/python-trunk/3.0.norwitz-x86/build/Lib/encodings/ascii.py",
line 26, in decode
    return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe1 in position
105: ordinal not in range(128)

The alpha has this problem:

test_socket
sem_init: Too many open files
Unhandled exception in thread started by <bound method
BasicSocketPairTest.clientRun of <test.test_socket.BasicSocketPairTest
testMethod=testRecv>>
Traceback (most recent call last):
  File "/net/taipan/scratch1/nnorwitz/python/3.0.norwitz-tru64/build/Lib/test/test_socket.py",
line 124, in clientRun
    self.server_ready.wait()
  File "/net/taipan/scratch1/nnorwitz/python/3.0.norwitz-tru64/build/Lib/threading.py",
line 367, in wait
    self._cond.wait(timeout)
  File "/net/taipan/scratch1/nnorwitz/python/3.0.norwitz-tru64/build/Lib/threading.py",
line 209, in wait
    waiter = _allocate_lock()
thread.error: can't allocate lock
Fatal Python error: UNREF invalid object
*** IOT/Abort trap

Also test_long failed on the Alpha.

ia64 had this problem:

test test_builtin failed -- Traceback (most recent call last):
  File "/home/pybot/buildarea/3.0.klose-debian-ia64/build/Lib/test/test_builtin.py",
line 1474, in test_round
    self.assertEqual(round(1e20), 1e20)
AssertionError: 0 != 1e+20

Then:

test_tarfile
python: Objects/exceptions.c:1392: PyUnicodeDecodeError_Create:
Assertion `start < 2147483647' failed.
make: *** [buildbottest] Aborted

On the amd64 (ubuntu) test_unicode_file fails all 3 tests.

The windows buildbot seems to be failing due to line ending issues?

Another windows buildbot failed to compile:
_tkinter - 3 error(s), 1 warning(s)

See the link for more details.  Lots of little errors.  It doesn't
look like any buildbot will pass on the first run.  However, it looks
like many are pretty close.

n
PS Sorry about the spam on python-checkins.  It looks like there can
be only a single mailing list and that it's all or nothing for getting
mail.  At least I didn't see an obvious way to configure by branch.
You'll just have to filter out the stuff to py3k.

Since I always seem to recreate the steps necessary for adding a new
branch, here are some notes (mostly for me).  If anyone else wants to
help out with the buildbot, etc, that would be great.  To add a new
branch for a buildbot:
 * Add the branch in the buildbot master.cfg file.  2 places need to be updated.
 * Add new rules in the apache default configuration file (2 lines).
Make sure to use the same port number in both the changes.
 * Check in the buildbot master config.  apache config too?

Remember it takes a while (30-60 seconds) to restart both apache and
the buildbot master.  Both need to be restarted for the change to take
effect.