meson test failed about su2@master on canetos8_aarch64
Tom-python0121 opened this issue · 7 comments
Hello, I meet a problem:meson test failed about su2@master on canetos8_aarch64.
[root@bigdata spack-build]# ls
Common SU2_CFD SU2_DEF SU2_DOT SU2_GEO SU2_PY SU2_SOL UnitTests build.ninja compile_commands.json externals meson-info meson-logs meson-private
[root@bigdata spack-build]# meson test
ninja: Entering directory `/home/stage/root/spack-stage-su2-master-6pqdoqje4yuyseje7lkxnucdij7l5njz/spack-src/spack-build'
ninja: no work to do.
1/1 Catch2 test driver FAIL 0.01s exit status 1
>>> MALLOC_PERTURB_=206 /home/stage/root/spack-stage-su2-master-6pqdoqje4yuyseje7lkxnucdij7l5njz/spack-src/spack-build/UnitTests/test_driver
Ok: 0
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 0
Timeout: 0
Full log written to /home/stage/root/spack-stage-su2-master-6pqdoqje4yuyseje7lkxnucdij7l5njz/spack-src/spack-build/meson-logs/testlog.txt
testlog details:
testlog.txt
Does the code run?
What happens if you use ./meson.py instead of just meson?
What happens if you call the unit test executables directly (they will be in the meson build folder)?
@pcarruscag This is compiled using the spack management and has been run. The previous version can run successfully, but it fails after version 7.5.0
previously when?
@pcarruscag su2@7.3.1 can passed.
I'm not sure that is running the SU2 unit tests.
Can you run the test_driver executable directly and check the output?
It will be in the "build" directory / UnitTests/test_driver
@pcarruscag There is no indication that there is a problem with the test_driver execution.
[root@bigdata spack-build]# cd UnitTests/
[root@bigdata UnitTests]# ls
test_driver test_driver.p
[root@bigdata UnitTests]# ./test_driver
[root@bigdata UnitTests]#
Thanks for checking, in that case I do not think it is a bug on our side.