U.Mutlu wrote on 07/17/2018 07:00 PM:
U.Mutlu wrote on 07/17/2018 05:34 PM:
Jonathan Wakely wrote on 07/17/2018 05:08 PM:
On Tue, 17 Jul 2018 at 15:40, U.Mutlu wrote:
It seems "make check" appends new results to existing results, right?
No.
Is there a make target for cleaning the results of the previous "make check"
run(s)?
They should be replaced by a new run.
Hmm. will try again.
As suspected: in the report it lists also the results of old test runs.
Ie. my last test run was this:
make -j5 -k check-gcc-c RUNTESTFLAGS="--target_board=mips-sim-idt64/-O3"
But the report has also entries about "g++", but which shouldn't occur
with this test ("check-gcc-c").
The screen output contains only "=== gcc Summary ==="
But the report starts so:
########
LAST_UPDATED: Mon Jul 16 19:30:10 UTC 2018 (revision 262747)
Target is mipsisa64-unknown-elf
Host is x86_64-pc-linux-gnu
=== g++ tests ===
Running target mips-sim-idt64/-O3
FAIL: g++.dg/compat/abi/bitfield1 cp_compat_x_tst.o-cp_compat_y_tst.o execute
...
#######
Ie. even the "LAST UPDATED" is that of yesterday, as it rather should show
current datetime.
But: I used the string "mips-sim-idt64/-O3" only in this last test.
So, something's fishy here; it IMHO indeed seems to merge the old results with
the new results.
I'll take a deeper look...
SOLVED:
If one wants to delete the results of old/prev test runs,
then one has to delete all the *.sum files under the build dir before starting
the new test(s):
cd build
# delete old *.sum files of prev test runs:
touch dummy.sum
rm -f $(find . -name "*.sum*" -print)
make -j5 -k check-gcc-c RUNTESTFLAGS="--target_board=mips-sim-idt64/-O3"
...
