the 3 builders for the new FreeBSD 9.2 x86-64 slave are up and running:
Nov 20 09:42 601a9d1cb6eb... failure freebsd-9.2-amd64-python2.7 #12 Failed 1 test (select) 1 test (poll) 3 tests (kqueue) Nov 20 09:42 601a9d1cb6eb... failure freebsd-9.2-amd64-pypy2.2 #8 Failed 28 tests (select) 28 tests (poll) 93 tests (kqueue) Nov 20 09:42 601a9d1cb6eb... failure freebsd-9.2-amd64-pypy-nightly #6 Failed 28 tests (select) 28 tests (poll) 31 tests (kqueue)
CPy 2.7: this is a vanilla build from Python 2.7.6 sources PyPy 2.2: this is a vanilla build from PyPy 2.2 sources PyPy Nightly: this is build by the PyPy buildslave (running on the same host) from PyPy head
All binaries are compiled using Clang 3.3 (which will be the default toolchain beginning with FreeBSD 10, kernel to userland).
The biggest issue that was causing a bunch of IPv6 tests to fail is already solved and merged:
Thanks Jean-Paul (exarkun) and Laurens (lvh)!
Regarding the remaining failing tests:
1) CPy 2.7 / select & poll reactors
There is 1 identified issue left: https://twistedmatrix.com/trac/ticket/6846
2) CPy 2.7 / kqueue reactor
Apart from #6846, in above run, there are 2 failing tests.
My problem is: I think I have seen the _same revision_ yield between 0 - 4 failing tests for kqueue. I'll watch that, and then see.
3) PyPy 2.2 & nightly / select & poll reactors
I would focus on these 28 failing tests first, since they are "stable" both across PyPy 2.2 / Nightly and select/poll reactors.
From a first quick lock, there might be some low hanging fruit - tests that probably test CPy specific behavior like.
I guess analyzing and fixing the PyPy related issues won't happen tomorrow. It'll take some time.