[DTrace-devel] [PATCH] test: increase child process runtime

[Kris Van Hees]

Withdrawn - Eugene pointed out correctly that this cannot be the correct
fix because the test already run with a timeout of 41s.

Looking at another possiblity, which is that one of the child processes is
not fully started by the time we try to put a probe on it, causing the probe
not to be found.  That would mean we may need a delay between starting the
child processes and starting dtrace.

Testing...

On Wed, Mar 06, 2024 at 03:40:32PM -0500, Kris Van Hees via DTrace-devel wrote:
> Due to recent kernel changes causing a slowdown in BPF program loading, this
> test can encounter a situation where the 'sleep 500s' is not long enough to
> ensure that the child processes are still running by the time dtrace is
> trying to enable probes.  That results in some probe(s) not being found.
> 
> Signed-off-by: Kris Van Hees <kris.van.hees at oracle.com>
> ---
>  test/unittest/pid/tst.manypids.sh | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/test/unittest/pid/tst.manypids.sh b/test/unittest/pid/tst.manypids.sh
> index 1a98d621..6ffe302c 100755
> --- a/test/unittest/pid/tst.manypids.sh
> +++ b/test/unittest/pid/tst.manypids.sh
> @@ -27,7 +27,7 @@ let i=0
>  tmpfile=$tmpdir/dtest.$$
>  
>  while [ "$i" -lt "$numkids" ]; do
> -	sleep 500 &
> +	sleep 5000 &
>  	pids[$i]=$!
>          disown %+
>  	let i=i+1
> -- 
> 2.42.0
> 
> 
> _______________________________________________
> DTrace-devel mailing list
> DTrace-devel at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/dtrace-devel