From: George France <france@handhelds.org>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com, clp@iol.unh.edu
Subject: Re: exit status of 'make check'
Date: Tue, 13 Nov 2001 09:53:00 -0000 [thread overview]
Message-ID: <01112513400901.05740@shadowfax.middleearth> (raw)
In-Reply-To: <20011125124718.A25769@nevyn.them.org>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
We are not discussing, the results of 'runtest'. We are discussing the
results of 'make check'. Here is another simple example, On 2001-11-22, I
built the gcc_3.0.2 HEAD branch. 'make check' returned a zero for an exit
code, but many of the testsuites FAILed.
--George
I have attached a copy of the results.
>
> From runtest's man page:
>
> EXIT CODES
> runtest sets the exit code to 1 if any of the tests failed, or
> sets it to 0 if all the
> tests passed.
>
> DejaGNU seems to agree with me on this one.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: X-check.log --]
[-- Type: text/english; name="X-check.log", Size: 7427 bytes --]
make[1]: Entering directory `/home/buildsys/build/intel1/bootstrap-gcc_3.0.2/native/gcc-head/gcc'
Making a new config file...
echo "set tmpdir /home/buildsys/build/intel1/bootstrap-gcc_3.0.2/native/gcc-head/gcc/testsuite" >> ./tmp0
test -d testsuite || mkdir testsuite
rm -f testsuite/site.exp
sed '/set tmpdir/ s|testsuite|testsuite|' < site.exp > testsuite/site.exp
(rootme=`pwd`; export rootme; \
srcdir=`cd /home/buildsys/source/gcc-head/gcc; pwd` ; export srcdir ; \
cd testsuite; \
EXPECT=expect ; export EXPECT ; \
if [ -f ${rootme}/../expect/expect ] ; then \
TCL_LIBRARY=`cd .. ; cd /home/buildsys/source/gcc-head/gcc/../tcl/library ; pwd` ; \
export TCL_LIBRARY ; fi ; \
runtest --tool gcc )
WARNING: global config file /home/buildsys/site.exp not found.
Test Run By france on Thu Nov 22 13:51:44 2001
Native configuration is i686-pc-linux-gnu
=== gcc tests ===
Schedule of variations:
unix
Running target unix
Using /mnt/u2/toolchain/baseline/install/intel1/bootstrap-gcc_3.0.2/native/dejagnu-1.4.2/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /mnt/u2/toolchain/baseline/install/intel1/bootstrap-gcc_3.0.2/native/dejagnu-1.4.2/share/dejagnu/config/unix.exp as generic interface file for target.
Using /home/buildsys/source/gcc-head/gcc/testsuite/config/default.exp as tool-and-target-specific interface file.
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.c-torture/compile/compile.exp ...
FAIL: gcc.c-torture/compile/20011114-1.c, -O0
FAIL: gcc.c-torture/compile/20011114-1.c, -O1
FAIL: gcc.c-torture/compile/20011114-1.c, -O2
FAIL: gcc.c-torture/compile/20011114-1.c, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/compile/20011114-1.c, -O3 -g
FAIL: gcc.c-torture/compile/20011114-1.c, -Os
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.c-torture/execute/execute.exp ...
FAIL: gcc.c-torture/execute/20011114-1.c execution, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/20011114-1.c execution, -O3 -g
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.c-torture/execute/ieee/ieee.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.c-torture/execute/memcheck/memcheck.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.c-torture/unsorted/unsorted.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.dg/cpp/cpp.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.dg/dg.exp ...
FAIL: gcc.dg/c99-intconst-1.c (test for excess errors)
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.dg/format/format.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.dg/noncompile/noncompile.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.dg/special/ecos.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.dg/special/special.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.misc-tests/acker1.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.misc-tests/bprob.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.misc-tests/dg-test.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.misc-tests/dhry.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.misc-tests/gcov.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.misc-tests/linkage.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.misc-tests/matrix1.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.misc-tests/mg.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.misc-tests/sieve.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/gcc.misc-tests/sort2.exp ...
=== gcc Summary ===
# of expected passes 16336
# of unexpected failures 9
# of expected failures 61
# of unsupported tests 25
/home/buildsys/build/intel1/bootstrap-gcc_3.0.2/native/gcc-head/gcc/xgcc version 3.1 20011122 (experimental)
make[1]: [check-gcc] Error 1 (ignored)
(rootme=`pwd`; export rootme; \
srcdir=`cd /home/buildsys/source/gcc-head/gcc; pwd` ; export srcdir ; \
cd testsuite; \
EXPECT=expect ; export EXPECT ; \
if [ -f ${rootme}/../expect/expect ] ; then \
TCL_LIBRARY=`cd .. ; cd /home/buildsys/source/gcc-head/gcc/../tcl/library ; pwd` ; \
export TCL_LIBRARY ; fi ; \
runtest --tool g++ )
WARNING: global config file /home/buildsys/site.exp not found.
Test Run By france on Thu Nov 22 14:10:15 2001
Native configuration is i686-pc-linux-gnu
=== g++ tests ===
Schedule of variations:
unix
Running target unix
Using /mnt/u2/toolchain/baseline/install/intel1/bootstrap-gcc_3.0.2/native/dejagnu-1.4.2/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /mnt/u2/toolchain/baseline/install/intel1/bootstrap-gcc_3.0.2/native/dejagnu-1.4.2/share/dejagnu/config/unix.exp as generic interface file for target.
Using /home/buildsys/source/gcc-head/gcc/testsuite/config/default.exp as tool-and-target-specific interface file.
Running /home/buildsys/source/gcc-head/gcc/testsuite/g++.dg/dg.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/g++.dg/special/ecos.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/g++.old-deja/old-deja.exp ...
FAIL: g++.other/enum5.C (test for excess errors)
XPASS: g++.pt/decl2.C ICE - (test for errors, line 8)
XPASS: g++.robertl/eb17.C Execution test
=== g++ Summary ===
# of expected passes 6726
# of unexpected failures 1
# of unexpected successes 2
# of expected failures 94
# of untested testcases 9
/home/buildsys/build/intel1/bootstrap-gcc_3.0.2/native/gcc-head/gcc/testsuite/../g++ version 3.1 20011122 (experimental)
make[1]: [check-g++] Error 1 (ignored)
(rootme=`pwd`; export rootme; \
srcdir=`cd /home/buildsys/source/gcc-head/gcc; pwd` ; export srcdir ; \
cd testsuite; \
EXPECT=expect ; export EXPECT ; \
if [ -f ${rootme}/../expect/expect ] ; then \
TCL_LIBRARY=`cd .. ; cd /home/buildsys/source/gcc-head/gcc/../tcl/library ; pwd` ; \
export TCL_LIBRARY ; fi ; \
runtest --tool g77 )
WARNING: global config file /home/buildsys/site.exp not found.
Test Run By france on Thu Nov 22 14:22:04 2001
Native configuration is i686-pc-linux-gnu
=== g77 tests ===
Schedule of variations:
unix
Running target unix
Using /mnt/u2/toolchain/baseline/install/intel1/bootstrap-gcc_3.0.2/native/dejagnu-1.4.2/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /mnt/u2/toolchain/baseline/install/intel1/bootstrap-gcc_3.0.2/native/dejagnu-1.4.2/share/dejagnu/config/unix.exp as generic interface file for target.
Using /home/buildsys/source/gcc-head/gcc/testsuite/config/default.exp as tool-and-target-specific interface file.
Running /home/buildsys/source/gcc-head/gcc/testsuite/g77.dg/bprob/bprob.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/g77.dg/dg.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/g77.dg/gcov/gcov.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/g77.f-torture/compile/compile.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/g77.f-torture/execute/execute.exp ...
Running /home/buildsys/source/gcc-head/gcc/testsuite/g77.f-torture/noncompile/noncompile.exp ...
=== g77 Summary ===
# of expected passes 1360
/home/buildsys/build/intel1/bootstrap-gcc_3.0.2/native/gcc-head/gcc/testsuite/../g77 version 3.1 20011122 (experimental)
make[1]: Leaving directory `/home/buildsys/build/intel1/bootstrap-gcc_3.0.2/native/gcc-head/gcc'
next prev parent reply other threads:[~2001-11-25 18:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-11 10:33 Michael Elizabeth Chastain
2001-11-11 11:30 ` George France
2001-11-11 22:14 ` Daniel Jacobowitz
2001-11-12 15:02 ` George France
2001-11-13 8:47 ` Daniel Jacobowitz
2001-11-13 9:53 ` George France [this message]
2001-11-13 10:05 ` Daniel Jacobowitz
2001-11-13 10:26 ` George France
2001-11-25 20:59 ` George France
-- strict thread matches above, loose matches on Subject: below --
2001-11-13 10:34 Michael Elizabeth Chastain
2001-11-13 12:38 ` George France
2001-11-25 22:21 ` George France
2001-11-25 21:11 ` Michael Elizabeth Chastain
2001-11-10 10:17 George France
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01112513400901.05740@shadowfax.middleearth \
--to=france@handhelds.org \
--cc=clp@iol.unh.edu \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox