One test fails on Mac with static libraries #5
Comments
|
A few of the tests check the error | x - x_k | as well as the residual and fail when it's too large. This is one of those tests. I'll fix it tomorrow. |
Several of the linear solver tests were checking the error | x - x_k | as well as the residual | b - A x_k |. If the residual is more than the tolerance, that's bad and the test SHOULD fail. The failing test reported by Barry Smith et al at ANL was checking whether the error was less than some constant value, which was never a good idea. We could theoretically check whether |x - x_k| / |x_k| <= cond(A) |r| / (|A| |x_k|) but I'm just going to disable the error check altogether; I don't want to introduce any messiness involving the condition number of A to a straightforward example. Many thanks to the ANL folks for reporting this bug as issue #5 on github!
|
@BarrySmith Is this test still failing? |
|
It should unless you made some changes? xSDK installer is currently pulling your commit 9fc43b7 Should that be updated? Barry
|
|
Bummer. I thought that commit would fix this problem. I'm working on a clang build right now; I'll let you know if I have trouble reproducing the problems you guys have been seeing. |
|
I think its fixed in 9fc43b7 [which we are currently using] The nightlybuilds have been working fine since then [and they use --with-shared-libraries=0 with clang on Mac] |
This same error occurs on the Mac with clang and gcc 5 compilers (using static libraries because we cannot yet build with shared libraries on mac, see previous issue.) Jason may also have reported this directly to Alicia
Error running ctest on xSDKTrilinos: Could not execute "cd /Users/petsc/petsc.test/arch-osx-xsdk-opt-gcc5/externalpackages/git.xsdktrilinos/build && /Users/petsc/petsc.test/arch-osx-xsdk-opt-gcc5/bin/ctest":
Test project /Users/petsc/petsc.test/arch-osx-xsdk-opt-gcc5/externalpackages/git.xsdktrilinos/build
Start 1: xSDKTrilinos_PETScAIJMatrix
1/10 Test #1: xSDKTrilinos_PETScAIJMatrix .......... Passed 0.02 sec
Start 2: xSDKTrilinos_PETSc_Amesos2_example
2/10 Test #2: xSDKTrilinos_PETSc_Amesos2_example ... Passed 0.02 sec
Start 3: xSDKTrilinos_PETSc_Anasazi_example
3/10 Test #3: xSDKTrilinos_PETSc_Anasazi_example ... Passed 0.16 sec
Start 4: xSDKTrilinos_PETSc_Ifpack2_example
4/10 Test #4: xSDKTrilinos_PETSc_Ifpack2_example ...***Failed 0.02 sec
Start 5: xSDKTrilinos_PETSc_MueLu_example
5/10 Test #5: xSDKTrilinos_PETSc_MueLu_example ..... Passed 0.05 sec
Start 6: xSDKTrilinos_example_TpetraKSP
6/10 Test #6: xSDKTrilinos_example_TpetraKSP ....... Passed 0.02 sec
Start 7: xSDKTrilinos_example_EpetraKSP
7/10 Test #7: xSDKTrilinos_example_EpetraKSP ....... Passed 0.01 sec
Start 8: xSDKTrilinos_HypreTest
8/10 Test #8: xSDKTrilinos_HypreTest ............... Passed 0.02 sec
Start 9: xSDKTrilinos_Hypre_Belos_example
9/10 Test #9: xSDKTrilinos_Hypre_Belos_example ..... Passed 0.02 sec
Start 10: xSDKTrilinos_Hypre_Solve_example
10/10 Test #10: xSDKTrilinos_Hypre_Solve_example ..... Passed 0.02 sec
90% tests passed, 1 tests failed out of 10
Label Time Summary:
xSDKTrilinos = 0.37 sec
Total Test time (real) = 0.39 sec
The following tests FAILED:
4 - xSDKTrilinos_PETSc_Ifpack2_example (Failed)Errors while running CTest
<<<<<<<<<<<<
@balay @sarich @satishbalay @jasonsarich
The text was updated successfully, but these errors were encountered: