[Numpy-discussion] Mysterious test_pareto failure on Travis
Tue Sep 4 14:41:57 CDT 2012
On Tue, Sep 4, 2012 at 12:31 PM, Ondřej Čertík <firstname.lastname@example.org> wrote:
> On Tue, Sep 4, 2012 at 3:15 AM, Nathaniel Smith <email@example.com> wrote:
>> The last two Travis builds of master have failed consistently with the
>> same error:
>> It looks like a real failure -- we're getting the same error on every
>> build variant, some sort of problem in test_pareto. Example:
>> The obvious culprit would be the previous commit, which regenerated
>> mtrand.c with Cython 0.17:
>> What's weird, though, is that that commit passed just fine on Travis:
>> It's just the two commits since then that failed. But these commits
>> have been 1-line docstring changes, so I don't see how they could have
>> possibly created the problem.
>> Also, the test passes fine with python 2.7 on my laptop with current master.
>> Can anyone reproduce this failure? Any ideas what might be going on?
> I made this:
> It was me who updated the Cython file. It seemed to be working. I've
> added the issue
> to the release TODO.
Ok, here is how to reproduce the problem:
1) install my numpy-vendor vagrant image (32 bit Ubuntu), as directed
in the README:
2) run tests, you'll get:
More information about the NumPy-Discussion