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
Is your feature request related to a problem? Please describe.
In ctest, the detailed output is hidden by default. So if/when a workflow fails to run, the resulting workflow log only has the name of the top-level test application that failed, but there is no information about which test inside of it failed.
Describe the solution you'd like
Use the --output-on-failure option when invoking ctest. This way, if the test passes, the output is the same (quiet) but we will get the more verbose log if it should fail.
Additional context
Lack of detailed output makes it very difficult to fix a test failure that is not able to be reproduced locally for whatever reason.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In ctest, the detailed output is hidden by default. So if/when a workflow fails to run, the resulting workflow log only has the name of the top-level test application that failed, but there is no information about which test inside of it failed.
Describe the solution you'd like
Use the
--output-on-failure
option when invoking ctest. This way, if the test passes, the output is the same (quiet) but we will get the more verbose log if it should fail.Additional context
Lack of detailed output makes it very difficult to fix a test failure that is not able to be reproduced locally for whatever reason.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: