-
Notifications
You must be signed in to change notification settings - Fork 572
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ifpack2 tests broken in standrd CI build starting 8/11/2017 #1600
Comments
I am going to update TriBITS to allow the disable of just a single executable and then externally disable this test build for just the CI build. That way, this failure will not trip up anyone trying to use the checkin-test-sems.sh script to push to:
Then the Intrepid2 developers can fix this failing test in their leisure. |
…TSPub/TriBITS#216) This is just the functionality to This is needed urgently by Trilinos to disable a test that fails to build that is breaking the CI build (see #1600).
…Matrix (#1600) This disables the build and running of the test: Intrepid2_refactor_unit-test_Orientation_Serial_Test_OrientationToolsCoeffMatrix This is needed to get the CI build working again (see #1600, #1304). Build/Test Cases Summary Enabled Packages: Intrepid2 Disabled Packages: PyTrilinos,Claps,TriKota 0) MPI_RELEASE_DEBUG_SHARED_PT => passed: passed=82,notpassed=0 (3.13 min) Other local commits for this build/test group: 3a3bde5, 479735d
I just pushed the commit 00bca64:
This only impacts the standard CI build. The test will still be enabled for all local builds and other nightly builds on CDash. To revert this disable and then reproduce and fix the issue, please do:
Then do the standard CI build for Intrepid2 using:
Then one can iterative reconfigure, build, run tests, etc. as described at: Then, once new commit(s) have been made that fix the issue, please test and push with:
If you have questions about this please contact me and @trilinos/framework |
I am sorry that I did not use checkin test and did not find out the missing file in the commit. It is fixed now.
|
This is also affecting the clean and nightly builds: As I was typing this I saw that @kyungjoo-kim has put in a fix. |
…TSPub/TriBITS#216) This is just the functionality to This is needed urgently by Trilinos to disable a test that fails to build that is breaking the CI build (see trilinos#1600).
…Matrix (trilinos#1600) This disables the build and running of the test: Intrepid2_refactor_unit-test_Orientation_Serial_Test_OrientationToolsCoeffMatrix This is needed to get the CI build working again (see trilinos#1600, trilinos#1304). Build/Test Cases Summary Enabled Packages: Intrepid2 Disabled Packages: PyTrilinos,Claps,TriKota 0) MPI_RELEASE_DEBUG_SHARED_PT => passed: passed=82,notpassed=0 (3.13 min) Other local commits for this build/test group: 3a3bde5, 479735d
You forgot to revert the disable commit as instructed above:
That will turn the test on but we need to make sure it is passing before pushing. |
This is just the functionality to This is needed urgently by Trilinos to disable a test that fails to build that is breaking the CI build (see trilinos/Trilinos#1600).
CC: @trilinos/framework, @trilinos/intrepid2, @kyungjoo-kim
Description:
The package Intrepid2 is now showing a build failure in the CI build with the first breaking CI iteration yesterday shown at:
The build failures shown at:
show:
Looking at the new commits pulled for this CI iteration at:
we see that the following commits have caused this break:
Looking at the push log for Trilinos we see the push:
As you can see from that push log, there is no evidence that the checkin-test-sems.sh script was used to test and push this change.
This is just a test failure, and not a library failure. However, anyone trying to use the checkin-test-sems.sh script to push changes to any of the following packages upstream from Ifpack2 will have their push stopped due to this failing test build:
Therefore, this needs to be fixed ASAP or this test needs to be disabled so that it does not stop other people's pushes.
The text was updated successfully, but these errors were encountered: