You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After clean build all but One ExaGO tests fail. It seems there is a path issue somewhere. The error message is:
3% tests passed, 37 tests failed out of 38
Label Time Summary:
incline-skip = 1.28 sec*proc (1 test)
Total Test time (real) = 48.13 sec
The following tests FAILED:
2 - UNIT_TESTS_OBJECTIVE_SIZE_OF_unittestx3.m_IPOPT_POWER_BALANCE_POLAR (Failed)
3 - UNIT_TESTS_OBJECTIVE_SIZE_OF_unittestx600.m_IPOPT_POWER_BALANCE_POLAR (Failed)
4 - UNIT_TESTS_OBJECTIVE_SIZE_OF_unittestx3.m_HIOPSPARSE_POWER_BALANCE_POLAR (Failed)
( ... )
38 - SOPFLOW_SOLUTION_OUTPUT_MINIMAL (Failed)
can't opendir /ccs/home/peles/src/exago/exago-github/build/tests/functionality: No such file or directory at /ccs/home/peles/src/exago/exago-github/tests/functionality/scripts/post_test.pl line 9.
Problem running command: perl /ccs/home/peles/src/exago/exago-github/tests/functionality/scripts/post_test.pl /ccs/home/peles/src/exago/exago-github/build/tests/functionality
Problem executing post-test command(s).
Errors while running CTest
Exact commands to reproduce, if applicable
git clone [email protected]:pnnl/ExaGO.git exago
mkdir build
cd build
CC=gcc CXX=g++ FC=gfortran cmake -DEXAGO_ENABLE_PYTHON=Off ../exago
make
ctest
I am using GCC 10.2, PETSc and other dependencies are built using ExaGO Spack package. Let me know what other debugging information you need me to provide.
The text was updated successfully, but these errors were encountered:
Issue type
Relates to
Summary
After clean build all but One ExaGO tests fail. It seems there is a path issue somewhere. The error message is:
Exact commands to reproduce, if applicable
I am using GCC 10.2, PETSc and other dependencies are built using ExaGO Spack package. Let me know what other debugging information you need me to provide.
The text was updated successfully, but these errors were encountered: