Re: The anatomy of a build result

> Right now, the daily report doesn't say which step failed, but it will
> soon.
> 
> Hope this explains things. I will update the web page with an
> introduction as soon as I get the time.

Can't you add an index.html that shows the log files on order of
execution, with a fail/succeed indicator?  That would be usable.  I
think you're not going to get anybody interested in looking at
problems using the current setup, and then there's no point in running
the thing at all.  A one-line summary of the first thing that failed
in the email summary would also be helpful.

Now, onto the failure at hand.  Look at
http://www.lysator.liu.se/xenofarm/python/files/67_6/testlog.txt

It ends with two occurrences of

make[1]: *** [test] Killed

with no clues about why.  That's very strange.  Maybe something is
enforcing a strict time limit?

(The normal test output is not included,
which seems to point to another bug in xenofarm.)

--Guido van Rossum (home page: http://www.python.org/~guido/)