út 11. 8. 2026 v 3:04 odesílatel Steven Rostedt <[email protected]> napsal: > > I just tested this on my VM and have the following results from "make check": > > [...] > not ok 20 - top verify -c/--cpus > # Output match failed: "^Affinity of threads: 0$" > # Affinity of threads: > [...] > not ok 21 - hist verify -c/--cpus > # Output match failed: "^Affinity of threads: 0$" > # Affinity of threads: > [...] > not ok 26 - top verify -u/--user-threads > # Output match failed: "0 kernel threads, 1 user threads" > # 0 kernel threads, 0 user threads > [...] > not ok 27 - hist verify -u/--user-threads > # Output match failed: "0 kernel threads, 1 user threads" > # 0 kernel threads, 0 user threads > [..] > > -- Steve >
tools/tracing/rtla/tests/scripts/lib/get_workload_pids.sh is for some reason not finding the user threads (as the tests for -H and -k succeeded) on your system. The threads themselves had to be running, as timerlat is reporting samples from them. The script and the related tests cases were added in 7.2 already, this pull request does not touch them so it's most likely a pre-existing issue. Either way, I will look into that, thank you for testing. It might be environment-dependent, as the test relies on the test script (executed as an --on-threshold action) being a direct child of the main rtla process - which only holds when the system() shell executes the script directly, not as a subprocess. Tomas
