Hello,
With the tnaur PPC OSX buildbot slave back in business, I have finally spent
the effort to figure out in detail what these reports actually tell me. As I
understand the buildbot-collator code, an element in the lists of unexpected
passes and failures gives the test name, the number of builders that report
the unexpected result, and the name of the "smallest" of these builders. And
"smallest" is defined in Data.hs as the most preferred builder for debugging
the problem according to suitable criteria. So, for example, the line
GMapAssoc 3 x86-64 Linux head
among the "Old unexpected test failures" tells me that 3 builders got this
unexpected failure and the smallest of these were "x86-64 Linux head".
I would suggest extending this scheme by listing, for each test, all the
builders, sorted, rather than just the smallest. Perhaps simply on a single
line, although more elaborate formatting could be imagined. But in such a way
that it was easy to see, for a particular test, which builders actually
reported the unexpected result.
This would help me decide which tests to investigate. In addition, as far as I
can tell, the builder ordering is not complete, so it is unclear which
builder is actually listed, in case several are smallest. This unclarity
would also be eliminated.
Best regards
Thorkil
On Sunday 10 June 2007 09:30, BuildBot Collator wrote:
> Build results:
> x86-64 Linux head: lost
> ...
> Old unexpected test passes:
>
> arith008 1 x86 Windows head
>
> Fixed unexpected test failures:
>
> arith011
>
> Old unexpected test failures:
>
> CPUTime001 1 tnaur PPC OSX head
> GMapAssoc 3 x86-64 Linux head
> ...
> user001 2 x86-64 Linux head
>
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
