Hello Mathieu, On 24 September 2014 08:52, Mathieu Malaterre <ma...@debian.org> wrote:
> Package: tbb > Version: 4.2~20140122-3 > > Just for reference, why is the test suite not reporting an issue on i386: > > [...] > > sh ../test_summary.sh ./test_mutex.exe 1:3 > Call stack info (7): > ./test_mutex.exe(_Z16print_call_stackv+0x3d)[0x80554bd] > ./test_mutex.exe(_Z11ReportErrorPKciS0_S0_+0xd)[0x80555ad] > ./test_mutex.exe[0x805577c] > ./test_mutex.exe(_Z8TestMainv+0x25d)[0x80559dd] > ./test_mutex.exe(main+0x68)[0x8054f28] > /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0xf740c723] > ./test_mutex.exe[0x805528c] > ../../src/test/harness_tsx.h:72, assertion (EBX & rtm_ebx_mask)!=0: failed > Aborted > [...] > > and then then later on: > > [...] > > sh ../test_summary.sh ./test_mutex.exe 1:3 > Call stack info (7): > ./test_mutex.exe(_Z16print_call_stackv+0x3d)[0x805371d] > ./test_mutex.exe(_Z11ReportErrorPKciS0_S0_+0xd)[0x805381d] > ./test_mutex.exe[0x80539dc] > ./test_mutex.exe(_Z8TestMainv+0x22a)[0x8053c0a] > ./test_mutex.exe(main+0x68)[0x80531d8] > /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0xf7481723] > ./test_mutex.exe[0x80535a7] > ../../src/test/harness_tsx.h:72, assertion (EBX & rtm_ebx_mask)!=0: failed > Aborted > [...] > > Summarized as: > > 99 DEBUG tests passed. > The following DEBUG tests FAILED! > ./test_mutex.exe 1:3 > sh ./build/test_summary.sh --dump RELEASE > "./build/linux_ia32_gcc_cc4.9.1_libc2.19_kernel3.2.0_release" > 99 RELEASE tests passed. > The following RELEASE tests FAILED! > ./test_mutex.exe 1:3 > > > > ref: > > https://buildd.debian.org/status/fetch.php?pkg=tbb&arch=i386&ver=4.2~20140122-3&stamp=1411250359 > > > Could you please clarify why this test is ok to fail ? > Unfortunately on the systems I own, a desktop machine (building AMD64 and i386) and an ARMv7 Chromebook, I have not seen a single failure even after a *lot* of test builds. I am trying to gauge which unit tests are failing on which architectures/buildd's/kernels, to better understand what is firing and why. The upstream package ignores the failures by default, and I'm concerned about the validity of some of the tests; so chose to keep the build running. This is alluded to in changelog: * Unit test execution failures no longer cause build to fail; instead take a tally of passes/failures to make it easier to analyse which cases are prone to failure. + debian/patches/tally-unit-test-fails.patch I would, of course, welcome any insight into the test failures. Cheers, -- Steve
