Hi Benjamin, following the discussion with IBM in https://bugs.launchpad.net/ubuntu/+source/libtracefs/+bug/2062119 "libtracefs autopkgtests fail on ppc64el"
The current archive CI for ppc64el uses an LXD testbed and skips these two tests https://autopkgtest.ubuntu.com/packages/libtracefs : https://autopkgtest.ubuntu.com/packages/libtracefs/resolute/ppc64el We have neutral results, but it's because it lacks ``isolation-machine`, so `trace-utest` and `trace-utest-valgrind` were SKIPPED. Version Triggers Env Date Duration Requester Result 1.8.2-1ubuntu1 libtracefs/1.8.2-1ubuntu1 2026-11-04 20:11:45 UTC 0h 01m 23s patriciasd neutral log artifacts Same also happens with stonking and tenacious: https://autopkgtest.ubuntu.com/packages/libtracefs/tenacious/ppc64el: 1.8.4-0ubuntu1 libtracefs/1.8.4-0ubuntu1 2026-10-22 12:23:14 UTC 0h 01m 18s - neutral log artifacts ``` 71s autopkgtest [12:23:07]: test build-examples.sh: -----------------------] 72s build-examples.sh PASS (superficial) 72s autopkgtest [12:23:08]: test build-examples.sh: - - - - - - - - - - results - - - - - - - - - - 73s autopkgtest [12:23:09]: @@@@@@@@@@@@@@@@@@@@ summary 73s trace-utest SKIP Test restriction "isolation-machine" requires testbed capability "isolation-machine" 73s trace-utest-valgrind SKIP Test restriction "isolation-machine" requires testbed capability "isolation-machine" 73s build-examples.sh PASS (superficial) ``` So, checking this manually, I ran the libtracefs autopkgtests on ppc64el (POWER9 PowerNV host, KVM guest :2 vCPUs and 4 GiB RAM) On 26.10 (stonking), `trace-utest` fails in much the same way as on 26.04 (resolute): Test: Follow events ...passed Test: Follow events clear ...FAILED 1. tracefs-utest.c:1748 - fdata.missed_hit > 0 2. tracefs-utest.c:1748 - fdata.missed_hit > 0 Test: tracefs_tracers API ...passed but `trace-utest-valgrind` behaves differently: On 26.04 it timed out in my run, while on 26.10 it sometimes finishes (in 11 to 21 minutes) and sometimes times out. 26.10 ppc64el log outputs: ``` ==2395== ERROR SUMMARY: 1209 errors from 119 contexts (suppressed: 0 from 0) make: *** [Makefile:219: test_mem] Error 1 autopkgtest [01:09:21]: test trace-utest-valgrind: -----------------------] autopkgtest [01:09:22]: test trace-utest-valgrind: - - - - - - - - - - results - - - - - - - - - - trace-utest-valgrind FAIL non-zero exit status 2 autopkgtest [01:09:22]: @@@@@@@@@@@@@@@@@@@@ summary build-examples.sh PASS (superficial) trace-utest FAIL non-zero exit status 1 trace-utest-valgrind FAIL non-zero exit status 2 qemu-system-ppc64: terminating on signal 15 from pid 505732 (/usr/bin/python3) ``` ``` ==2497== at 0x4A1C0B0: ??? (in /usr/lib/powerpc64le-linux-gnu/libtracefs.so.1.8.3) ==2497== ==2497== ERROR SUMMARY: 1210 errors from 119 contexts (suppressed: 0 from 0) make: *** [Makefile:219: test_mem] Error 1 autopkgtest [01:42:28]: test trace-utest-valgrind: -----------------------] autopkgtest [01:42:29]: test trace-utest-valgrind: - - - - - - - - - - results - - - - - - - - - - trace-utest-valgrind FAIL non-zero exit status 2 autopkgtest [01:42:29]: - - - - - - - - - - running shell - - - - - - - - - - ``` It would be useful to have these two tests running again on VM testbeds (as the older runs did) for ppc64el and arm64, instead of an LXD container. Please, let me know if I can provide any more information (I cannot send the LOG files now due to launchpad issues). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2172071 Title: trace-utest and trace-utest-valgrind autopkgtest fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtracefs/+bug/2172071/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
