(Cc: Matt, Christian) Please send scheduler patches to all scheduler maintainers (and reviewers).
On 2/27/26 11:00 AM, Tvrtko Ursulin wrote: > Some tests are on right on the limit of targetting a one second runtime, s/targetting/targeting/ > and some of those have recently been correctly marked as slow. Lets > instead make them a bit quicker, by either reducing the amount of > submitted jobs or waiting a bit less. For the latter a comment is added to > explain why that should be fine, and for the former, they are tests which > aim to hit races via stress testing, so reducing the runtime is also fine > since the main thing is the number of test runs over time and machines. > > Signed-off-by: Tvrtko Ursulin <[email protected]> > Reported-by: Maxime Ripard <[email protected]> Should be followed by Closes:, but since the other patch resolved the issue already by flagging the tests, I think this should just be dropped. > + /* > + * Advance the timeline and make sure the second job gets scheduled and > + * completed. > + */ A bit unrelated to the patch, and I'm also not sure it adds much value, let's drop the comment. With that, Reviewed-by: Danilo Krummrich <[email protected]>
