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
Unlike most other test suites, a failed 'make check' exits with 0. For integration into package build scripts it would be much easier, as well as more conventional to exit with zero only if all tests succeed.
(Background: when building on 11 architectures, failing the build when the test suite suddenly starts failing is a great way to automatically detect problems on particular architectures, as well as forcing maintainers to keep the test suite working, and thus useful.)
The text was updated successfully, but these errors were encountered:
--- test/run-stp-tests.sh (revision 7376)
+++ test/run-stp-tests.sh (working copy)
@@ -598,6 +598,10 @@
echo "A HTML report was created in test/$strfile."
echo ""
Version: 1.3.6
CUPS.org User: martin.pitt.canonical
Unlike most other test suites, a failed 'make check' exits with 0. For integration into package build scripts it would be much easier, as well as more conventional to exit with zero only if all tests succeed.
(Background: when building on 11 architectures, failing the build when the test suite suddenly starts failing is a great way to automatically detect problems on particular architectures, as well as forcing maintainers to keep the test suite working, and thus useful.)
The text was updated successfully, but these errors were encountered: