From 68da9b418c5d7508a58c7c46461e4097de2858e1 Mon Sep 17 00:00:00 2001 From: Ben Elliston Date: Sat, 23 Aug 2003 05:41:08 +0000 Subject: [PATCH] * contrib/README: Bring up to date. --- ChangeLog | 4 ++++ contrib/README | 20 +++++++------------- 2 files changed, 11 insertions(+), 13 deletions(-) diff --git a/ChangeLog b/ChangeLog index 229847d..24020d1 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,7 @@ +2003-08-23 Ben Elliston + + * contrib/README: Bring up to date. + 2003-08-23 Corinna Vinschen * config/sid.exp: Add gdb settings to use no hardware watchpoints. diff --git a/contrib/README b/contrib/README index d776f6e..33b32ba 100644 --- a/contrib/README +++ b/contrib/README @@ -1,16 +1,10 @@ -These are "user" contributed scripts that automate testing. These all +These are user contributed scripts that automate testing. These all depend on using "make check", so they are included here as an aid to -helping others automate their own testing. All of these script do -report filtering on the output from DejaGnu. test-tool and test-g++ -are basically the same script. test-target is the script I use for our -quarterly release and it is the most sophisticated. It still uses -"make check" (a make target that start runtest) to produce the -results, but tests our entire tool chain for native and crosses. It -also produces a short summary report that gets emailed, as well as -summary reports. It does regression analysis using the previous test -run. testit is a very crude and simple Tk GUI for accessing all the -testing results. Hope these are helpful to anyone, I'd like to collect -more from the net as they get developed. +helping others automate their own testing. All of these scripts do +report filtering on the output from DejaGnu. - - rob - +test-tool and test-g++ are basically the same script. +testit is a very crude and simple Tk GUI for accessing all the testing +results. Hope these are helpful to anyone, I'd like to collect more +from the net as they get developed. -- 2.7.4