This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
Sunday Project gdb test results, 2001-03-24
- To: gdb-testers at sources dot redhat dot com
- Subject: Sunday Project gdb test results, 2001-03-24
- From: Michael Elizabeth Chastain <chastain at cygnus dot com>
- Date: Sat, 24 Mar 2001 22:19:00 -0800
Here are my Sunday Project results for 2001-03-24.
Red Hat Linux 6.2 native:
=== gdb Summary ===
# of ERRORs 4
# of WARNINGs 2
# of expected passes 6573
# of unexpected failures 111
# of unexpected successes 11
# of expected failures 156
# of unresolved testcases 2
# of untested testcases 19
Red Hat Linux 7.0 native:
=== gdb Summary ===
# of ERRORs 4
# of WARNINGs 2
# of expected passes 6623
# of unexpected failures 106
# of unexpected successes 11
# of expected failures 155
# of unresolved testcases 2
# of untested testcases 18
Solaris 2.5.1 native:
=== gdb Summary ===
# of ERRORs 4
# of WARNINGs 2
# of expected passes 6614
# of unexpected failures 97
# of unexpected successes 11
# of expected failures 155
# of unresolved testcases 34
# of untested testcases 19
I ran the tests with fsf gcc cvs gcc-3_0-branch 2001-03-24 and FSF gdb
cvs 2001-03-24. I counted the ERROR and WARNING lines by hand inspection
of the summary files.
All results are in Terf, http://sources.redhat.com/cgi-bin/gdb.cgi .
Note that Terf still has problems with duplicate test names.
The merged results for all platforms contain 4 ERRORs, 2 WARNINGs,
and 120 FAILs.
Here are the merged ERRORs categorized by test script:
4 TOTAL
= =====
4 gdb.c++/userdef.exp
Here are the merged WARNINGs categorized by test script:
2 TOTAL
= =====
2 gdb.c++/userdef.exp
Here are the merged FAILs categorized by test script:
120 TOTAL
=== =====
30 gdb.c++/virtfunc.exp
18 gdb.c++/classes.exp
11 gdb.base/callfwmall.exp
8 gdb.c++/cplusfuncs.exp
7 gdb.c++/templates.exp
6 gdb.c++/overload.exp
6 gdb.c++/inherit.exp
5 gdb.c++/namespace.exp
4 gdb.c++/method.exp
4 gdb.c++/derivation.exp
3 gdb.threads/pthreads.exp
3 gdb.c++/local.exp
2 gdb.c++/annota2.exp
2 gdb.base/structs2.exp
2 gdb.base/selftest.exp
2 gdb.base/return2.exp
2 gdb.base/ending-run.exp
1 gdb.trace/packetlen.exp
1 gdb.stabs/weird.exp
1 gdb.java/jmisc.exp
1 gdb.c++/demangle.exp
1 gdb.base/exprs.exp
Changes from 2001-03-17:
2001-03-17 total 0 ERRORs
gdb.c++/userdef.exp +4 ERRORs needs investigation
2001-03-24 total 4 ERRORs
2001-03-17 total 0 WARNINGs
gdb.c++/userdef.exp +2 WARNINGs needs investigation
2001-03-24 total 2 WARNINGs
2001-03-17 total 122 FAILs
gdb.c++/virtfunc.exp -1 FAILs probably a harness glitch
gdb.c++/userdef.exp -1 FAILs test script has ERRORs instead
2001-03-24 total 120 FAILs
The first test in virtfunc.exp changed its result from FAIL to UNRESOLVED.
virtfunc.cc has not changed; virtfunc.exp has not changed; and the output
in gdb.log has not changed. This looks some kind of test harness problem
(virtfunc.exp comes right after userdef.exp, which is giving ERRORs
and WARNINGs). I'm not going to investigate this.
The test program gdb.c++/userdef.cc failed to compile this week.
I don't know yet whether this is a problem in g++ or a problem in the
test program. (g++ has been tightening up on illegal C++ constructs).
Next, I am looking into userdef.cc.