On 05/17/2017 01:39 PM, Bernd Edlinger wrote:
On 05/15/17 03:39, Daniel Santos wrote:
I should add that if you want to run faster tests just on the ms to sysv
abi code, you can use make RUNTESTFLAGS="ms-sysv.exp" check and then if
that succeeds run the full testsuite.
Daniel
Hmm, that's funny...
If I use "make check-c RUNTESTFLAGS="ms-sysv.exp" -j8" it seems to work,
but if I omit the -j8 it fails:
make check-c RUNTESTFLAGS="ms-sysv.exp"
...Test Run By ed on Wed May 17 20:38:24 2017
Native configuration is x86_64-pc-linux-gnu
=== gcc tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file
for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for
target.
Using /home/ed/gnu/gcc-trunk/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running
/home/ed/gnu/gcc-trunk/gcc/testsuite/gcc.target/x86_64/abi/ms-sysv/ms-sysv.exp
...
ERROR: tcl error sourcing
/home/ed/gnu/gcc-trunk/gcc/testsuite/gcc.target/x86_64/abi/ms-sysv/ms-sysv.exp.
ERROR: no such variable
(read trace on "env(GCC_RUNTEST_PARALLELIZE_DIR)")
invoked from within
"set parallel_dir "$env(GCC_RUNTEST_PARALLELIZE_DIR)/abi-ms-sysv""
(file
"/home/ed/gnu/gcc-trunk/gcc/testsuite/gcc.target/x86_64/abi/ms-sysv/ms-sysv.exp"
line 154)
invoked from within
"source
/home/ed/gnu/gcc-trunk/gcc/testsuite/gcc.target/x86_64/abi/ms-sysv/ms-sysv.exp"
("uplevel" body line 1)
invoked from within
"uplevel #0 source
/home/ed/gnu/gcc-trunk/gcc/testsuite/gcc.target/x86_64/abi/ms-sysv/ms-sysv.exp"
invoked from within
"catch "uplevel #0 source $test_file_name""
=== gcc Summary ===
/home/ed/gnu/gcc-build/gcc/xgcc version 8.0.0 20170514 (experimental)
(GCC)
make[2]: Leaving directory `/home/ed/gnu/gcc-build/gcc'
make[1]: Leaving directory `/home/ed/gnu/gcc-build/gcc'
Hmm, that might be something I hadn't actually tried. And if I run it
in a directory where I had previously run a multi-job check it doesn't
blow up (maybe because the directory is already there?) Due to the
nature of my test program, I had to break with tradition and implement
something akin to the test that generates random structs (I forgot what
that one is called). It ended up breaking the bastardized
parallelization scheme, so I had to implement my own re-bastardized
scheme. Looks like I can just skip parallelization if
GCC_RUNTEST_PARALLELIZE_DIR isn't defined.
I have another Solaris test issue on PR 80759 so I'll fix that along
with it.
Thanks,
Daniel
PS: Oh! it might be due to the difference between -j1 and no -j argument.
