thanks, I find the tinderbox runs and these reports very useful.
I just recently reported derby issues for the outstanding suites
failures, I think some by hand updates have to happen to get the
"automatic failure analysis" to pick these up. If there is anything
I can do to help with this let me know.
Ole Solberg wrote:
Mike Matrigali wrote:
When you go to the full history page
(http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/Limited/index_all.html)
It only lists derbyall failures, making it sort of hard to track down
suite failures, I had to click on 0 failure cases. It is too bad
but I don't think there have actually been any 0 failure runs in
quite awhile. I would like to see at least the tinderbox runs reporting
0 failures before we consider doing a release (even better if all the
regression runs reported 0 failures - it is fine by me to remove known
bug test runs if they are reported in JIRA with appropriate priority).
I'll fix these reports to also include the ...suites.All failures.
Thanks for reminding me!
