-
Notifications
You must be signed in to change notification settings - Fork 578
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
Update NOX_Thyra_Eq test to clearly show why it passes or fails #2310
Update NOX_Thyra_Eq test to clearly show why it passes or fails #2310
Conversation
This was need for clear output for the test in NOX Thyra_Heq.C. I just added a simple usage of this macro. But we really need better unit tests for all of thse macros.
Before, if any of the three criteria failed, it would jsut print "Test failed". But now it prints why it failed with details. This test currently fails with Intel compilers (see trilinos#2247) but at least now it shows you why (which was not clear at all before). I also made usage of the default FancyOStream to avoid logic about what process you are on for when you should be printing or not. That is the best way to handle parallel output and better test output control.
Status Flag 'Pre-Test Inspection' - Auto Inspected - Inspection Is Not Necessary for this Pull Request. |
Status Flag 'Pull Request AutoTester' - Testing Jenkins Projects: Pull Request Auto Testing STARTING (click to expand)Build InformationTest Name: Trilinos_autotester_test
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
Using Repos:
Pull Request Author: bartlettroscoe |
Status Flag 'Pull Request AutoTester' - Jenkins Testing: 1 or more Jobs FAILED Note: Testing will normally be attempted again in approx. 4:00:00. If a change to the Pull Request source branch occurs, the testing will be attempted again. Pull Request Auto Testing has FAILED (click to expand)Build InformationTest Name: Trilinos_autotester_test
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
|
This build is not showing up on the dashboard: The end of the console output in Jenkins simply says: Error(s) when configuring the project Single configure/build/test failed. The error code was: 255 |
This build is supposed to submit to the dashboard, but it didn't. The configure step failed, but even without the submission the ctest temporary files should have given some indication. However, they are no where to be found in the build tree. The script failed to submit because the error check and abort for the configure happens before a submit. I will fix it so the next run should submit the failing configure to the dashboard as expected. |
I merged this branch locally and tested with:
and it fully passed as shown below. @atoth1, can you please review and merge this branch? Once this is merged to CHECKIN TEST RESULTS (Click to expand)
|
Looks good, but I don't think I have the permissions to perform the merge. |
Okay, I will click "Merge" then. Thanks @atoth1! |
CC: @trilinos/nox, @fryeguy52
This updates the test NOX_Thyra_Heq so that it clearly shows why the test passes or fails. This currently still fails for the Intel 17.4 compiler but at least now we can see how this test is behaving on differnet platforms.
Before, the test just showed:
which makes no sense because it says it converged!
But there was a silent check that it must solve in 18 iterations. But with Intel 17.4, it converges in 16 iterations (assuming due to better rounding with this Intel compiler). Yea!
This updates the test to print the real pass/fail criteria and I updated the criteria to all allow num interations between (14, 18) and it now prints:
I also improve the outputting by using
Teuchos::VerboseObjectBase::getDefaultOStream()
so you don't need to bother checking what proc you are on when you print.