Fix error report in ctest when calling bash script #434
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
FabienPean
force-pushed
the
fix/cmake-test-report
branch
from
4ae019b
to
b1f5700
Compare
fghoussen
force-pushed
the
fix/cmake-test-report
branch
from
b1f5700
to
9be7551
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To stop on first error, the cmake test should be called either as
COMMAND ${BASH_PROGRAM} -eu arpackmm.shorCOMMAND arpackmm.sh. Calling bash onto the script file in ctest skips the shebang line of the script (which contains#!/bin/bash -eu). See #433 for the proof.I used the former explicit version to avoid problem if the file is not executable