don't fail build on missing python requirements
Merge request reports
Activity
assigned to @andreas.dedner
added 1 commit
- 7bfe7144 - make python requirements available upstreams
added 7 commits
-
4e86a454...24804e43 - 6 commits from branch
master
- 3de3fbc1 - don't fail build on missing python requirements
-
4e86a454...24804e43 - 6 commits from branch
added 1 commit
- 869963c4 - don't add any install rules if initial installation of requirement file failed
added 1 commit
- 404d955d - don't execute tests if python setup was not successfull
added 1 commit
- 8d7ee75d - don't fail build on missing python requirements
@simon.praetorius I managed to implement something that fixes the breaking of the build if the python requirements installation fails (also for upstream modules). What is not so nice is my approach to avoid the make test failure
cmake/modules/DunePythonTestCommand.cmake
. I simply changed theadd_custom_target
to simply echo a message that the python test is disabled due to failure in the python setup. The issue is now that callingmake test
just says that the test passed, i.e., you don't see that it wasn't run. Do you see any way of getting any more meaningful information at the end ofmake test
?I think that there is a special return value in the test executable that indicates that it was not run. Something like
return 77
. Maybe we could add not only the message, but also an exit code.Edited by Simon Praetorius
added 1 commit
- df93e3cd - don't fail build on missing python requirements
enabled an automatic merge when the pipeline for df93e3cd succeeds
mentioned in commit 07134cbc