| Message ID | CAKdteOY71ZUYRMR=ENWdSu-MB6EwQasY4xsoF_DHvpCwkSi6yw@mail.gmail.com |
|---|---|
| State | New |
| Headers | show |
ping? On 13 April 2016 at 10:21, Christophe Lyon <christophe.lyon@linaro.org> wrote: > Hi, > > While investigating stability problems when running GCC validations, > I fixed DejaGnu to properly handle cases where it cannot parse the > testcase output: > http://lists.gnu.org/archive/html/dejagnu/2016-04/msg00008.html > > This means that such cases now return "unresolved" which confuses > ${tool}_load in gcc-dg.exp, as it currently only handles "pass" and "fail". > > The attached small patch fixes this. > > This is probably for stage 1 only I guess. > > OK? > > Christophe.
diff --git a/gcc/testsuite/lib/gcc-dg.exp b/gcc/testsuite/lib/gcc-dg.exp index 9e4ecce..6cdce0d 100644 --- a/gcc/testsuite/lib/gcc-dg.exp +++ b/gcc/testsuite/lib/gcc-dg.exp @@ -380,6 +380,7 @@ if { [info procs ${tool}_load] != [list] \ switch [lindex $result 0] { "pass" { set status "fail" } "fail" { set status "pass" } + default { set status [lindex $result 0] } } set result [list $status [lindex $result 1]] }
Hi, While investigating stability problems when running GCC validations, I fixed DejaGnu to properly handle cases where it cannot parse the testcase output: http://lists.gnu.org/archive/html/dejagnu/2016-04/msg00008.html This means that such cases now return "unresolved" which confuses ${tool}_load in gcc-dg.exp, as it currently only handles "pass" and "fail". The attached small patch fixes this. This is probably for stage 1 only I guess. OK? Christophe. 2016-04-13 Christophe Lyon <christophe.lyon@linaro.org> * lib/gcc-dg.exp (${tool}_load): Add default return value handler.