Re: Re: [farm-report] Daily Snake Farm report

On Fri, Sep 13, 2002 at 10:11:05AM -0400, Guido van Rossum wrote:
> > I'm not ignoring this issue, but the files do get both stdout and
> > stderr redirected to them.
> 
> Aha.  The OOM kill must've thrown away the pending stdout buffer;
> makes sense.  Try running the tests with "python -u".

The kill in itself doesn't do this. Have a look at some of the failed
ia64 tests (eg
http://www.lysator.liu.se/xenofarm/python/files/97_13/testlog.txt; The
failed test is test_grp, so we're missing a lot of output). 

> > Rather, I think this may be a issue with how regrtest.py handles
> > stdout.
> 
> Doubt it.  While regrtest.py indeed redirects stdout of the test it
> runs, it prints the test name to the real stdout.

But how come it disappears when I do "make test > file.log 2>&1"? If I
run the test in my terminal, I see all the text. If I redirect both
stdout and -err to file, I get what you see in the results. python -u
solves this problem, but seem to favour stderr, so lines can change
order.

> Mmm, do you want me to add a flush() call to regrtest.py?  That would
> be easy and effective and not require you to use python -u.

That might be a good idea. Since switching to xenofarm, I can no
longer make local modificaitons to the local CVS copy of Python. This
is because the modification results in an 'M' entry from CVS, which
makes the dist builder wait for the CVS to stabilize. But the 'M'
won't go away, so the builder will wait indefinitely.

This must be solved by adding a mechanism to patch the dist source
just before it is packaged, but it will be some days before that
functionality is implemented. Meanwhile, a flush might help (and is a
good idea anyway).
-- 
Anders "Quest" Qvist

"We've all heard that a million monkeys banging on a million typewriters
will eventually reproduce the entire works of Shakespeare. Now, thanks 
to the Internet, we know this is not true." -- Robert Wilensky