Hi, I have repeatedly run the failing test after dpkg-buildpackage failed. So far, I consistently get a failure.
My test machine is an ancient Lenovo T60 with a "Genuine Intel(R) CPU T2500 @ 2.00GHz" CPU. ,---- | >>> profile doesn't match, args: /home/bengen/tmp/bsp/google-perftools/.libs/profiler3_unittest /tmp/profile_info/p14 vs. /tmp/profile_info/p15 | >>> Diff: | 14c14 | < 1 0.6% 99.4% 34 21.4% _init | --- | > 1 0.6% 99.4% 17 10.7% _init | 15a16 | > 0 0.0% 100.0% 17 10.7% 0x0000000000000000 `---- ,---- | >>> profile doesn't match, args: /home/bengen/tmp/bsp/google-perftools/.libs/profiler3_unittest /tmp/profile_info/p14 vs. /tmp/profile_info/p15 | >>> Diff: | 13a14 | > 0 0.0% 100.0% 22 14.0% 0x0000000000000000 | 20c21 | < 0 0.0% 100.0% 42 26.8% _init | --- | > 0 0.0% 100.0% 20 12.7% _init `---- ,---- | >>> profile doesn't match, args: /home/bengen/tmp/bsp/google-perftools/.libs/profiler3_unittest /tmp/profile_info/p14 vs. /tmp/profile_info/p15 | >>> Diff: | 13a14 | > 0 0.0% 100.0% 20 12.7% 0x0000000000000000 | 19c20 | < 0 0.0% 100.0% 43 27.2% _init | --- | > 0 0.0% 100.0% 23 14.6% _init `---- ,---- | >>> profile doesn't match, args: /home/bengen/tmp/bsp/google-perftools/.libs/profiler3_unittest /tmp/profile_info/p14 vs. /tmp/profile_info/p15 | >>> Diff: | 14a15 | > 0 0.0% 100.0% 21 13.1% 0x0000000000000000 | 21c22 | < 0 0.0% 100.0% 35 21.9% _init | --- | > 0 0.0% 100.0% 14 8.8% _init `---- NB: The test script outputs the following warning: ,---- | >>> WARNING <<< | This test looks at timing information to determine correctness. | If your system is loaded, the test may spuriously fail. | If the test does fail with an 'Actual times' error, try running again. `---- I think that this test should just be disabled (or failures ignored.) Cheers, -Hilko
