As was said in the other posting, you need to create a log file
of the testing, and then you can analyse it (locate the failed test files etc.).
Here's how I do it on Linux.
After it finishes, see the file /tmp/my_tests.log for the details.
my_build_script.sh:
-------------------
nCores=$(getconf _NPROCESSORS_ONLN)
nJobs=$(( $nCores * 2 ))
#...
function do_tests()
{
echo ""
echo "do_tests: start"
make -j $nJobs -k check
#...
echo "do_tests: end"
echo ""
}
do_tests 2>&1 | tee /tmp/my_tests.log
U.Mutlu wrote on 07/04/2018 11:21 PM:
You can get a more detailed output, like in the following posting:
https://gcc.gnu.org/ml/gcc-testresults/2018-07/msg00453.html
陈龙 wrote on 07/04/2018 03:32 AM:
Hi,
I have run the testsuite of GCC and compared with results from a similar
configuration in the gcc-testresults mailing list, the results just have a
little difference,and my test summary is in chapter Summary as below,. Both
of the results have many unexpected fails, I want to know why they failed
but the g++.log couldn’t affort enough fail case information,they were all
almost described like this:'FAIL: g++.dg/pr80481.C -std=gnu++14
scan-assembler-not vmovaps'.So was it right with so many fails? And could
you tell me how could I debug the fail case please?Thanks.
Test Environment
- x86_64-pc-mingw64 and msys2
- gcc8.1.0
Summary
=== g++ Summary ===
# of expected passes 115078
# of unexpected failures 628
# of unexpected successes 3
# of expected failures 493
# of unresolved testcases 5
# of unsupported tests 5122
/mingw64/bin/c++ version 8.1.0 (x86_64-posix-seh-rev0, Built by MinGW-W64
project)
Best regards
CL
