On Sun, 5 Apr 2009, Laurent GUERBY wrote: > I'm thinking of changing my auto tester to report a broken bootstrap > (the first time a bootstrap fails), is there a normalized way to > report such failures to gcc-testresults@ or g...@?
The "regression" component in Bugzilla exists for automatic reports from regression testers (mainly for testsuite regressions rather than bootstrap failures, I think), but using it without enough people who are going to follow up actively with updates on the reports, closing them once fixed, moving to appropriate components after further investigation, marking duplicates, etc., would be a bad idea. I also don't know if there's a better way of using it automatically than interacting with the web interface to Bugzilla via screen scraping. The existing "bootstrap" component needs people going through past reports and establishing if the issues reported are still present; bugs tend just to languish there. -- Joseph S. Myers jos...@codesourcery.com
