Source: cpputest Version: 3.7.1-1 It failed to build on arm64, powerpc, ppc64el:
https://buildd.debian.org/status/package.php?p=cpputest&suite=sid The error in the build log was: ============================================================================ make[3]: *** [test-suite.log] Error 1 Testsuite summary for CppUTest 3.7.1 ============================================================================ # TOTAL: 2 # PASS: 1 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 ============================================================================ See ./test-suite.log Please report to https://github.com/cpputest/cpputest ============================================================================ (If you could make the Debian rules dump the contents of test-suite.log after a failure that would make debugging a bit easier in future.) It seems that on arm64 the explanation in test-suite.log is: FAIL: CppUTestTests =================== .... tests/UtestPlatformTest.cpp:128: error: Failure in TEST(UTestPlatformsTest_PlatformSpecificRunTestInASeperateProcess, DivisionByZeroInSeparateProcessWorks) ./include/CppUTest/TestTestingFixture.h:112: error: actual < Generic:1: error: Failure in TEST(Generic, Generic) Failed in separate process . Errors (1 failures, 1 tests, 0 ran, 0 checks, 0 ignored, 0 filtered out, 1 ms) > did not contain <Failed in separate process - killed by signal 8> It appears to be doing an integer division by zero and expecting a signal, which won't happen on arm64. I expect the same is happening on the other two architectures. The division-by-zero test should be conditional on the architecture. I would suggest that the default on an unrecognised architecture should be to not run that test. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
