On Tue, Oct 07, 2025 at 11:53:40AM +0200, Tomas Glozar wrote:
> In non-BPF mode, it takes up to 1 second for RTLA to notice that tracing
> has been stopped. That means that action tests cannot have a 1 second
> duration, as the SIGALRM will be racing with the threshold overflow.
> 
> Previously, non-BPF mode actions were buggy and always executed
> the action, even when stopping on duration or SIGINT, preventing
> this issue from manifesting. Now that this has been fixed, the tests
> have become flaky, and this has to be adjusted.
> 
> Fixes: 4e26f84abfb ("rtla/tests: Add tests for actions")
> Fixes: 05b7e10687c ("tools/rtla: Add remaining support for osnoise actions")
> Signed-off-by: Tomas Glozar <[email protected]>
> ---
>  tools/tracing/rtla/tests/osnoise.t  | 4 ++--
>  tools/tracing/rtla/tests/timerlat.t | 4 ++--
>  2 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/tools/tracing/rtla/tests/osnoise.t 
> b/tools/tracing/rtla/tests/osnoise.t
> index e3c89d45a6bb..08196443fef1 100644
> --- a/tools/tracing/rtla/tests/osnoise.t
> +++ b/tools/tracing/rtla/tests/osnoise.t
> @@ -39,9 +39,9 @@ check "hist stop at failed action" \
>  check "top stop at failed action" \
>       "timerlat top -T 2 --on-threshold shell,command='echo -n abc; false' 
> --on-threshold shell,command='echo -n defgh'" 2 "^abc" "defgh"
>  check "hist with continue" \
> -     "osnoise hist -S 2 -d 1s --on-threshold shell,command='echo TestOutput' 
> --on-threshold continue" 0 "^TestOutput$"
> +     "osnoise hist -S 2 -d 5s --on-threshold shell,command='echo TestOutput' 
> --on-threshold continue" 0 "^TestOutput$"
>  check "top with continue" \
> -     "osnoise top -q -S 2 -d 1s --on-threshold shell,command='echo 
> TestOutput' --on-threshold continue" 0 "^TestOutput$"
> +     "osnoise top -q -S 2 -d 5s --on-threshold shell,command='echo 
> TestOutput' --on-threshold continue" 0 "^TestOutput$"
>  check "hist with trace output at end" \
>       "osnoise hist -d 1s --on-end trace" 0 "^  Saving trace to 
> osnoise_trace.txt$"
>  check "top with trace output at end" \
> diff --git a/tools/tracing/rtla/tests/timerlat.t 
> b/tools/tracing/rtla/tests/timerlat.t
> index b5d1e7260a9b..b550a6ae2445 100644
> --- a/tools/tracing/rtla/tests/timerlat.t
> +++ b/tools/tracing/rtla/tests/timerlat.t
> @@ -60,9 +60,9 @@ check "hist stop at failed action" \
>  check "top stop at failed action" \
>       "timerlat top -T 2 --on-threshold shell,command='echo -n 1; false' 
> --on-threshold shell,command='echo -n 2'" 2 "^1ALL"
>  check "hist with continue" \
> -     "timerlat hist -T 2 -d 1s --on-threshold shell,command='echo 
> TestOutput' --on-threshold continue" 0 "^TestOutput$"
> +     "timerlat hist -T 2 -d 5s --on-threshold shell,command='echo 
> TestOutput' --on-threshold continue" 0 "^TestOutput$"
>  check "top with continue" \
> -     "timerlat top -q -T 2 -d 1s --on-threshold shell,command='echo 
> TestOutput' --on-threshold continue" 0 "^TestOutput$"
> +     "timerlat top -q -T 2 -d 5s --on-threshold shell,command='echo 
> TestOutput' --on-threshold continue" 0 "^TestOutput$"
>  check "hist with trace output at end" \
>       "timerlat hist -d 1s --on-end trace" 0 "^  Saving trace to 
> timerlat_trace.txt$"
>  check "top with trace output at end" \
> -- 
> 2.51.0
> 

In general, my pupils dilate when I see time based synchronization.
However, in this case, it seems harmless.

Reviewed-by: Wander Lairson Costa <[email protected]>


Reply via email to