[Numpy-discussion] Testsuite fails with Python 2.7.3rc1 and 3.2.3rc1 (Debian)

[Ralf Gommers]

On Sun, Apr 1, 2012 at 12:08 PM, Sandro Tosi <matrixhasu at gmail.com> wrote:

> On Sun, Apr 1, 2012 at 11:32, Ralf Gommers <ralf.gommers at googlemail.com>
> wrote:
> > Thanks. Can you explain what happens when running the tests? I don't
> > understand why the log says "Fatal Python error...Aborted" and then it
> > happily continues (or restarts) and returns "OK (KNOWNFAIL=3, SKIP=4)"
> even
> > for the 2.7.3rc1 and 3.2.3rc2 release candidates.
>
> I think it's some sort of stdout/stderr mixup, where
>
> .....
> -----
> Ran 3541 tests in 26.049s
>
> OK (KNOWNFAIL=3, SKIP=4)
>
> is printed before the information about the tests, such as:
>
> Running unit tests for numpy
> NumPy version 1.6.1
> NumPy is installed in
>
> /build/buildd-python-numpy_1.6.1-6-i386-lYkcLV/python-numpy-1.6.1/debian/tmp/usr/lib/python2.7/dist-packages/numpy
> Python version 2.7.3rc1 (default, Mar 10 2012, 00:01:06) [GCC 4.6.3]
> nose version 1.1.2
>
> so it might be that only the debug flavors are affected by this problem.
>

OK, that makes sense. So there are six test runs; for normal and debug
builds of 2.6.7, 2.7.3rc1 and 3.2.3rc2. Only the debug builds of the RCs
have a problem, debug build of 2.6.7 is fine.

So I'd think that most likely there is a problem with how the debug
versions of the RCs were built.

Ralf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20120401/06b728f2/attachment.html>