This is the mail archive of the frysk@sources.redhat.com mailing list for the frysk project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Automated build and test system (overview)

GCC's regression tester is a well cited example of how to not report test results ;-) It e-mails everyone that made a change, no matter how irrelevant, having the effect of crying wolf :-(

Testing such as being discussed here gives us access to higher level trend data. Examining that data allows us to identify emerging problems, for instance constant breakage with a specific compiler, kernel breakages. When applicable we can then adjust our processes do address persistent problems.

Andrew

Stan Cox wrote:
On Mon, 2007-03-12 at 13:23 +0100, Mark Wielaard wrote:
Having something that can pinpoint when
which test result flipped from PASS/FAIL would be great. 

Perhaps something like the gcc regression tester which posts regressions
along with ChangeLog entries since the last run:
 http://gcc.gnu.org/ml/gcc-regression
?



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]