[Bug testsuite/61606] New: About GCC install, testing step (mostly check...)
fernando at info dot unlp.edu.ar
gcc-bugzilla@gcc.gnu.org
Wed Jun 25 11:40:00 GMT 2014
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61606
Bug ID: 61606
Summary: About GCC install, testing step (mostly check...)
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: fernando at info dot unlp.edu.ar
Hi,
I'm making my own todo list for GCC install from sources, given that at some
point I would like to contribute to gfortran, if possible (I'm rather far from
it right now). Just to be clear, my todo list to install from sources is at
http://fernando.usr.me/GCC-gfortran-install.html
(maybe it would be useful some day for enhancing the online documentation...
maybe not...).
Anyway, I'm trying now the testing phase, I've installed the dependencies (AKA
prerequisites in GCC documentation) and I'm lost about testing results...
According to
https://gcc.gnu.org/install/test.html
"It is normal for some tests to report unexpected failures"
thus, I was particularly focused on "ERROR" and "WARNING", but the information
on where to look for is rather insufficient for me:
"The result of running the testsuite are various *.sum and *.log files in the
testsuite subdirectories."
Where are those subdirectories?
Also, now nearer a bug report: I've tried the testing step with
$ make -k check >> TSTFILE.OUT 2>&1
and
$ tail -30 TSTFILE.OUT
exit $exit_status
Test Run By fernando on Mon Jun 23 07:27:47 2014
Native configuration is i686-pc-linux-gnu
=== libatomic tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using
/nethome/fernando/gnu-compilers/gcc-4.9.0/libatomic/testsuite/config/default.exp
as tool-and-target-specific interface file.
Running
/nethome/fernando/gnu-compilers/gcc-4.9.0/libatomic/testsuite/libatomic.c/c.exp
...
=== libatomic Summary ===
# of expected passes 44
# of unsupported tests 5
make[4]: se sale del directorio
`/nethome/fernando/gnu-compilers/4.9.0-objdir/i686-pc-linux-gnu/libatomic/testsuite'
make[3]: se sale del directorio
`/nethome/fernando/gnu-compilers/4.9.0-objdir/i686-pc-linux-gnu/libatomic/testsuite'
make[3]: se ingresa al directorio
`/nethome/fernando/gnu-compilers/4.9.0-objdir/i686-pc-linux-gnu/libatomic'
true DO=all multi-do # make
make[3]: se sale del directorio
`/nethome/fernando/gnu-compilers/4.9.0-objdir/i686-pc-linux-gnu/libatomic'
make[2]: se sale del directorio
`/nethome/fernando/gnu-compilers/4.9.0-objdir/i686-pc-linux-gnu/libatomic'
make[1]: Debido a los errores, el objetivo `check-target' no se reconstruyó.
make[1]: se sale del directorio `/nethome/fernando/gnu-compilers/4.9.0-objdir'
make: *** [do-check] Error 2
make: Debido a los errores, el objetivo `check' no se reconstruyó.
lun jun 23 07:27:54 ART 2014
(fernando is the account name and /nethome/fernando is $HOME)
i.e. the testing failed (or at least I think so...). However, using
$ ../gcc-4.9.0/contrib/test_summary
cat <<'EOF' |
LAST_UPDATED: Obtained from SVN: tags/gcc_4_9_0_release revision 209612
Native configuration is i686-pc-linux-gnu
=== gcc tests ===
Running target unix
=== gcc tests ===
Running target unix
=== gcc tests ===
Running target unix
=== gcc tests ===
Running target unix
=== gcc tests ===
Running target unix
=== libatomic tests ===
Running target unix
=== libatomic Summary ===
# of expected passes 44
# of unsupported tests 5
=== libgomp tests ===
Running target unix
WARNING: program timed out.
FAIL: libgomp.c/depend-3.c execution test
=== libgomp Summary ===
# of expected passes 2411
# of unexpected failures 1
=== libitm tests ===
Running target unix
=== libitm Summary ===
# of expected passes 26
# of expected failures 3
# of unsupported tests 1
=== libstdc++ tests ===
Running target unix
=== libstdc++ Summary ===
# of expected passes 9232
# of expected failures 41
# of unsupported tests 555
=== libstdc++ tests ===
Running target unix
=== libstdc++ Summary ===
# of expected passes 448
Compiler version: gcc
Platform: i686-pc-linux-gnu
configure flags: --prefix=/nethome/fernando/gnu-compilers/4.9.0-instdir
--enable-languages=c,c++,fortran --disable-multilib
EOF
Mail -s "Results for gcc testsuite on i686-pc-linux-gnu"
gcc-testresults@gcc.gnu.org &&
mv /nethome/fernando/gnu-compilers/4.9.0-objdir/./gcc/testsuite/gcc1/gcc.sum
/nethome/fernando/gnu-compilers/4.9.0-objdir/./gcc/testsuite/gcc1/gcc.sum.sent
&&
mv /nethome/fernando/gnu-compilers/4.9.0-objdir/./gcc/testsuite/gcc2/gcc.sum
/nethome/fernando/gnu-compilers/4.9.0-objdir/./gcc/testsuite/gcc2/gcc.sum.sent
&&
mv /nethome/fernando/gnu-compilers/4.9.0-objdir/./gcc/testsuite/gcc3/gcc.sum
/nethome/fernando/gnu-compilers/4.9.0-objdir/./gcc/testsuite/gcc3/gcc.sum.sent
&&
mv /nethome/fernando/gnu-compilers/4.9.0-objdir/./gcc/testsuite/gcc4/gcc.sum
/nethome/fernando/gnu-compilers/4.9.0-objdir/./gcc/testsuite/gcc4/gcc.sum.sent
&&
mv /nethome/fernando/gnu-compilers/4.9.0-objdir/./gcc/testsuite/gcc5/gcc.sum
/nethome/fernando/gnu-compilers/4.9.0-objdir/./gcc/testsuite/gcc5/gcc.sum.sent
&&
mv
/nethome/fernando/gnu-compilers/4.9.0-objdir/./i686-pc-linux-gnu/libatomic/testsuite/libatomic.sum
/nethome/fernando/gnu-compilers/4.9.0-objdir/./i686-pc-linux-gnu/libatomic/testsuite/libatomic.sum.sent
&&
mv
/nethome/fernando/gnu-compilers/4.9.0-objdir/./i686-pc-linux-gnu/libgomp/testsuite/libgomp.sum
/nethome/fernando/gnu-compilers/4.9.0-objdir/./i686-pc-linux-gnu/libgomp/testsuite/libgomp.sum.sent
&&
mv
/nethome/fernando/gnu-compilers/4.9.0-objdir/./i686-pc-linux-gnu/libitm/testsuite/libitm.sum
/nethome/fernando/gnu-compilers/4.9.0-objdir/./i686-pc-linux-gnu/libitm/testsuite/libitm.sum.sent
&&
mv
/nethome/fernando/gnu-compilers/4.9.0-objdir/./i686-pc-linux-gnu/libstdc++-v3/testsuite/libstdc++.sum
/nethome/fernando/gnu-compilers/4.9.0-objdir/./i686-pc-linux-gnu/libstdc++-v3/testsuite/libstdc++.sum.sent
&&
mv
/nethome/fernando/gnu-compilers/4.9.0-objdir/./i686-pc-linux-gnu/libstdc++-v3/testsuite/normal0/libstdc++.sum
/nethome/fernando/gnu-compilers/4.9.0-objdir/./i686-pc-linux-gnu/libstdc++-v3/testsuite/normal0/libstdc++.sum.sent
&&
mv /nethome/fernando/gnu-compilers/4.9.0-objdir/./gcc/testsuite/gcc1/gcc.log
/nethome/fernando/gnu-compilers/4.9.0-objdir/./gcc/testsuite/gcc1/gcc.log.sent
&&
mv /nethome/fernando/gnu-compilers/4.9.0-objdir/./gcc/testsuite/gcc2/gcc.log
/nethome/fernando/gnu-compilers/4.9.0-objdir/./gcc/testsuite/gcc2/gcc.log.sent
&&
mv /nethome/fernando/gnu-compilers/4.9.0-objdir/./gcc/testsuite/gcc3/gcc.log
/nethome/fernando/gnu-compilers/4.9.0-objdir/./gcc/testsuite/gcc3/gcc.log.sent
&&
mv /nethome/fernando/gnu-compilers/4.9.0-objdir/./gcc/testsuite/gcc4/gcc.log
/nethome/fernando/gnu-compilers/4.9.0-objdir/./gcc/testsuite/gcc4/gcc.log.sent
&&
mv /nethome/fernando/gnu-compilers/4.9.0-objdir/./gcc/testsuite/gcc5/gcc.log
/nethome/fernando/gnu-compilers/4.9.0-objdir/./gcc/testsuite/gcc5/gcc.log.sent
&&
mv
/nethome/fernando/gnu-compilers/4.9.0-objdir/./i686-pc-linux-gnu/libatomic/testsuite/libatomic.log
/nethome/fernando/gnu-compilers/4.9.0-objdir/./i686-pc-linux-gnu/libatomic/testsuite/libatomic.log.sent
&&
mv
/nethome/fernando/gnu-compilers/4.9.0-objdir/./i686-pc-linux-gnu/libgomp/testsuite/libgomp.log
/nethome/fernando/gnu-compilers/4.9.0-objdir/./i686-pc-linux-gnu/libgomp/testsuite/libgomp.log.sent
&&
mv
/nethome/fernando/gnu-compilers/4.9.0-objdir/./i686-pc-linux-gnu/libitm/testsuite/libitm.log
/nethome/fernando/gnu-compilers/4.9.0-objdir/./i686-pc-linux-gnu/libitm/testsuite/libitm.log.sent
&&
mv
/nethome/fernando/gnu-compilers/4.9.0-objdir/./i686-pc-linux-gnu/libstdc++-v3/testsuite/libstdc++.log
/nethome/fernando/gnu-compilers/4.9.0-objdir/./i686-pc-linux-gnu/libstdc++-v3/testsuite/libstdc++.log.sent
&&
mv
/nethome/fernando/gnu-compilers/4.9.0-objdir/./i686-pc-linux-gnu/libstdc++-v3/testsuite/normal0/libstdc++.log
/nethome/fernando/gnu-compilers/4.9.0-objdir/./i686-pc-linux-gnu/libstdc++-v3/testsuite/normal0/libstdc++.log.sent
&&
true
and I do not see any thing failed... Other attempts to see problems:
$ grep "ERROR:" TSTFILE.OUT
$
i.e. no "ERROR:"
$ grep "WARNING:" TST-CHCK-4.OUT
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
WARNING: program timed out.
else echo "WARNING: could not find \`runtest'" 1>&2; :;\
else echo "WARNING: could not find \`runtest'" 1>&2; :;\
else echo "WARNING: could not find \`runtest'" 1>&2; :;\
WARNING: program timed out.
else echo "WARNING: could not find \`runtest'" 1>&2; :;\
else echo "WARNING: could not find \`runtest'" 1>&2; :;\
i.e. several timeouts... which seem to be the "only" problem, but the testing
did not end...
Is there a single way to look for PASS/FAIL answer to the GCC check step? I
mean: nothing went out of normal would mean PASS, otherwise FAIL.
Are the *.sum and *.log in the directories shown/used by
../gcc-4.9.0/contrib/test_summary?
In my specific case, what would be producing the
make: *** [do-check] Error 2
and how to "solve" it?
TIA,
Fernando.
More information about the Gcc-bugs
mailing list