[Python-3000] test_profile failing

[Brett Cannon]

On Fri, Feb 29, 2008 at 11:22 AM, Barry Warsaw <barry at python.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
>  Hash: SHA1
>
>
> On Feb 29, 2008, at 12:49 PM, Guido van Rossum wrote:
>
>  > On Fri, Feb 29, 2008 at 9:41 AM, Guido van Rossum <guido at python.org>
>  > wrote:
>  >> It looks like the failures are shallow -- there's a "golden" expected
>  >> output which includes some silliness like the exact number of CPU
>  >> seconds used.
>  >
>  > Actually I take it back. The same approach works fine in the trunk, so
>  > I suspect it's a merge problem. It may be quite subtle, alas. :-(
>  >
>  > Still, we shouldn't release with this failing. It would reduce
>  > confidence in the releases and generate tons of spurious customer
>  > support calls ^W^W^W bug reports.
>
>  Of course, the /real/ bug is that a commit was allowed that broke the
>  test suite.  This failure goes back to the first rev on the buildbot
>  page 61103 so it'll take a little more investigation to see what broke
>  it.
>
>  I'll see what can be done to fix this particular problem, and try to
>  be more attentive to buildbot failure notices when they happen so we
>  can nip it closer to the bud.  Ultimately, it would be nice if we had
>  a process that prevented any breaking patch from landing, but we're
>  not there yet.

A quick tweak to test_profile to print out what it got for output
shows that some changes to io.py led to a different tracing.

-Brett