public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "howarth.at.gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/64983] Incomplete summary when regtesting with dejagnu 1.5.2. Date: Sun, 29 Mar 2015 15:10:00 -0000 [thread overview] Message-ID: <bug-64983-4-OD2mdFnbfj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64983-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64983 --- Comment #9 from Jack Howarth <howarth.at.gcc at gmail dot com> --- Note that this issue seems to only be fixable from within dejagnu and that the commit of 6d2e2d3791bcea70131a6cf64a0a5223333a7b8e effectively broke the log_summary proc in dejagnu's lib/framework.exp by reseting the testcnt global which is used as follows... # If the tool set `testcnt', it wants us to do a sanity check on the # total count, so compare the reported number of testcases with the # expected number. Maintaining an accurate count in `testcnt' isn't easy # so it's not clear how often this will be used. if {[info exists testcnt]} { if { $testcnt > 0 } { set totlcnt 0 # total all the testcases reported foreach x { FAIL PASS XFAIL KFAIL XPASS KPASS UNTESTED UNRESOLVED UNSUPPORTED } { incr totlcnt test_counts($x,$which) } set testcnt test_counts(total,$which) if { $testcnt>$totlcnt || $testcnt<$totlcnt } { if { $testcnt > $totlcnt } { set mismatch "unreported [expr {$testcnt - $totlcnt}]" } if { $testcnt < $totlcnt } { set mismatch "misreported [expr {$totlcnt - $testcnt}]" } } else { verbose "# of testcases run $testcnt" } if {[info exists mismatch]} { clone_output "### ERROR: totals do not equal number of testcases run" clone_output "### ERROR: # of testcases expected $testcnt" clone_output "### ERROR: # of testcases reported $totlcnt" clone_output "### ERROR: # of testcases $mismatch\n" } } } foreach x { PASS FAIL XPASS XFAIL KPASS KFAIL UNRESOLVED UNTESTED UNSUPPORTED } { set val $test_counts($x,$which) if { $val > 0 } { set mess "# of $test_counts($x,name)" if { $xml } { xml_output " <summary>" xml_output " <result>$x</result>" xml_output " <description>$mess</description>" xml_output " <total>$val</total>" xml_output " </summary>" } if { [string length $mess] < 24 } { append mess "\t" } clone_output "$mess\t$val" }
next prev parent reply other threads:[~2015-03-29 13:41 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-09 14:24 [Bug testsuite/64983] New: " dominiq at lps dot ens.fr 2015-02-09 14:36 ` [Bug testsuite/64983] " dominiq at lps dot ens.fr 2015-02-18 17:55 ` howarth at bromo dot med.uc.edu 2015-02-18 19:37 ` iains at gcc dot gnu.org 2015-02-18 20:15 ` howarth at bromo dot med.uc.edu 2015-02-18 20:21 ` iains at gcc dot gnu.org 2015-03-28 18:07 ` howarth at bromo dot med.uc.edu 2015-03-28 20:56 ` howarth at bromo dot med.uc.edu 2015-03-29 7:17 ` howarthjw at gmail dot com 2015-03-29 15:10 ` howarth.at.gcc at gmail dot com [this message] 2015-03-29 15:39 ` dominiq at lps dot ens.fr 2015-03-31 5:09 ` howarth.at.gcc at gmail dot com 2015-03-31 9:34 ` dominiq at lps dot ens.fr
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=bug-64983-4-OD2mdFnbfj@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).