- Feb 11, 2019
-
-
Steffen Müthing authored
-
Steffen Müthing authored
-
- Feb 07, 2019
-
-
Steffen Müthing authored
As it turns out, older versions of CTest do not output a "Completion Status" for tests that were not run, so we need a fallback. The only place for information is the test output, which we parse for certain key phrases to detect tests that were skipped or had missing requirements (typically due to compilation failures).
-
Steffen Müthing authored
The build directory does not really work here, because it will just be called build-cmake. So extract it from the CI_PROJECT_NAME variable and normalize that.
-
Steffen Müthing authored
-
Steffen Müthing authored
- dune-ctest now writes a JUnit XML result file to Testing/cmake.xml. This can be picked up by GitLab for better error reporting. - Right now, tests that fail because compilation failed are not detected as an error. This is fixed now.
-
- Jun 29, 2018
-
-
Ansgar Burchardt authored
CTest already prints the messages once. Closes: #126
-
- Oct 07, 2016
-
-
CTest returns with an error status not only when tests failed, but also when tests were only skipped. This wrapper checks the log and returns successfully if no tests failed; skipped tests do not result in an error. This behaviour is needed in a continuous integration environment, when building binary packages or in other cases where the testsuite should be run automatically. Closes issue #12
-