[Numpy-discussion] Mysterious test_pareto failure on Travis
Tue Sep 4 13:02:22 CDT 2012
On Tue, Sep 4, 2012 at 2:18 PM, Nathaniel Smith <email@example.com> wrote:
> On Tue, Sep 4, 2012 at 1:47 PM, Scott Sinclair
> <firstname.lastname@example.org> wrote:
>> On 4 September 2012 12:23, Matthew Brett <email@example.com> wrote:
>>> On Tue, Sep 4, 2012 at 11:15 AM, Nathaniel Smith <firstname.lastname@example.org> 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 believe Travis just (a couple of days ago?) switched to Ubuntu 12.04
>>> images - could that be the problem?
>> For whatever it's worth, tox reports:
>> py24: commands succeeded
>> py25: commands succeeded
>> py26: commands succeeded
>> py27: commands succeeded
>> ERROR: py31: InterpreterNotFound: python3.1
>> py32: commands succeeded
>> py27-separate: commands succeeded
>> py32-separate: commands succeeded
>> with git revision a72ce7e on my Ubuntu 12.04 machine (64-bit).
> It works for me on 64-bit 12.04 too. However, the Travis machines are
> using *32*-bit 12.04, which might be the problem... anyone got one of
> those lying around to test?
I do - send me your ssh public key somehow?
More information about the NumPy-Discussion