Be less strict about warnings from "example tests" (#1045)

The build is no longer aborted when one of the "example tests" produces a
message on stderr. However, on Travis this requirement is still made. This
should catch "bad errors" via Travis while not breaking the build for users.

Fixes: https://github.com/awesomeWM/awesome/issues/821
Signed-off-by: Uli Schlachter <psychon@znc.in>
This commit is contained in:
Uli Schlachter 2016-08-20 18:59:28 +02:00 committed by Daniel Hahler
parent 63c8a310d0
commit c22b939630
2 changed files with 4 additions and 2 deletions

View File

@ -126,7 +126,7 @@ install:
return $result
}
script:
- export CMAKE_ARGS="-DLUA_LIBRARY=${LUALIBRARY} -DLUA_INCLUDE_DIR=${LUAINCLUDE} -D OVERRIDE_VERSION=$AWESOME_VERSION -D DO_COVERAGE=${DO_COVERAGE}"
- export CMAKE_ARGS="-DLUA_LIBRARY=${LUALIBRARY} -DLUA_INCLUDE_DIR=${LUAINCLUDE} -D OVERRIDE_VERSION=$AWESOME_VERSION -D DO_COVERAGE=${DO_COVERAGE} -DSTRICT_TESTS=true"
- |
set -ev
if [ -n "$BUILD_IN_DIR" ]; then

View File

@ -159,7 +159,9 @@ function(run_test test_path namespace escaped_content)
if (NOT TEST_ERROR STREQUAL "")
message("${TEST_OUTPUT}")
message("${TEST_ERROR}")
message(FATAL_ERROR ${test_path} " A test failed, bye")
if (STRICT_TESTS)
message(FATAL_ERROR ${test_path} " A test failed, bye")
endif()
endif()
# Read the code and turn it into an usage example.