Re: The anatomy of a build result

Guido van Rossum <[email protected]> writes:

> I should mentione one more thing that Anders failed to mention.  There
> actually *is* an indicator of which test failed in the Xenofarm
> directory listings.  For each phase, there's an empty file named
> "foo.pass" or "foo.fail" indicating success or failure for that phase.
> 
> For example, in 
> http://www.lysator.liu.se/xenofarm/python/files/68_9/?1031574402
> there's a "test.fail" file, pointing out that the clues to the
> failures are in "testlog.txt".
> 
> Now all we need is something that takes these directory listings and
> produces usable HTML.

Something like http://www.lysator.liu.se/~ceder/xeno/latest.html
maybe?  

This output is for another project that uses the Xenofarm, but all you
should have to do to produce similar output for the Python builds is
to copy xenofarm/projects/lyskom-server/latest.sh, change a few paths
at the top of the script, change the string
"/home/ceder/.xeno-mysql-pwd" to a file where the MySQL password is
stored, change the string "lyskom-server" to "Python" in a couple of
places, and make sure that latest.sh is run every few minutes.  (It
should be run by result_parser.pike when a new result has arrived.  I
might get around to adding support for that sometime in the future.)

I don't know the MySQL password for the Python database, so I cannot
set this up.

The "latest.sh" script is a /bin/sh-script that has grown too large.
I need to rewrite it in a better language (read: Python).

There are two things I plan to do with the layout once I have
converted the script to Python:

 - Replace the "Machine" column with two columns: a "OS" column to the
   left, and a "Computer" column to the right.  This will use the
   vertical screen estate more efficiently.

 - Sort the lines within each build on the "OS" column.

These changes will probably not be made for several weeks.  I suggest
you use "latest.sh" as it is, for the time being.

    /ceder