I think this issue is hardware specific, in the last cycle with 5.15.0-1040-realtime on node kopter-kernel test finished within allotted time without any problem.
With 5.15.0-1038-realtime, this test will still need 25 minutes to finish on scobee-kernel (no warning triggered by this test with this kernel))
I think this issue is hardware specific, in the last cycle with 5.15.0- 1040-realtime on node kopter-kernel test finished within allotted time without any problem.
With 5.15.0- 1038-realtime, this test will still need 25 minutes to finish on scobee-kernel (no warning triggered by this test with this kernel))