[Python-Dev] test_itertools fails for trunk on x86 OS X machine (original) (raw)

Grig Gheorghiu grig.gheorghiu at gmail.com
Fri Sep 22 04:16:33 CEST 2006

On 9/21/06, Jack Diederich <jackdied at jackdied.com> wrote:

On Thu, Sep 21, 2006 at 03:28:04PM -0700, Grig Gheorghiu wrote: > On 9/21/06, Jack Diederich <jackdied at jackdied.com> wrote: > > The python binary is out of step with the testitertools.py version. > > You can generate this same error on your own box by reverting the > > change to itertoolsmodule.c but leaving the new test in testitertools.py > > > > I don't know why this only happened on that OSX buildslave > > Not sure what you mean by out of step. The binary was built out of the > very latest itertoolsmodule.c, and testitertools.py was also updated > from svn. So they're both in sync IMO. That tests passes successfully > on all the other buildslaves in the Pybots farm (x86 Ubuntu, Debian, > Gentoo, RH9, AMD-64 Ubuntu) >

When I saw the failure, first I cursed (a lot). Then I followed the repr all the way down into stringobject.c, no dice. Then I noticed that the failure is exactly what you get if the test was updated but the old module wasn't. Faced with the choice of believing in a really strange platform specific bug in a commonly used routine that resulted in exactly the failure caused by one of the two files being updated or believing a failure occurred in the long chain of networks, disks, file systems, build tools, and operating systems that would result in only one of the files being updated - I went with the latter. I'll continue in my belief until my dying day or until someone with OSX confirms it is a bug, whichever comes first. not-gonna-sweat-it-ly, -Jack

OK, sorry for having caused you so much grief....I'll investigate some more on the Pybots side and I'll let you know what I find.

Grig

More information about the Python-Dev mailing list