[LLVMdev] 1 Week Before 2.0 Branch Creation

Tanya M. Lattner tonic at nondot.org
Sat May 5 15:50:48 PDT 2007

>> It would be good to have a mailing list for test results where 'make check'
>> results could be posted so that there is some reference and people could
>> avoid repeating builds.
> There's the llvm-testresults list, but I find it less than fully useful
> because it's not immediately obvious from scanning message subjects if
> there's been a test failure.  It's a lot of messages to wade through and
> read to get this information.
> What about a Tinderbox-like setup where we could consult a web page to
> see the current status of the repository?  Boost has a nice setup:
> http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/index_release.html
> It's probably more complex than what we need.  Maybe we just need a
> page grouping each test under it's suite and marking the result on
> each architecture.  Something like this:

I agree the test results are not displayed well. Its not well known, but I 
have been redesigning our databases and scripts to enable better display 
of the data. Right now its not very easy to do what you describe.


More information about the llvm-dev mailing list