search for: rc_1_34_0

...'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: <begin crappy ASCII art> ----------------------------------------------------...

> Tanya M. Lattner wrote: > >> How large of a change have you made? With 3 days before the branch >> creation, I strongly advise people not to be checking in major changes. > > Depends how you look at it. Structurally, it separates two files into > four and moves some functionality from one class to a new class, so in a > sense that's a big change.

...#39;s a lot of messages to wade through and > read to get this information. Right. > 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 think that this is a great idea. However, instead of picking u...