- Issue created by @catch
- Status changed to Closed: outdated
4 months ago 9:20am 24 December 2024
Kernel tests are the highest CPU users in gitlab jobs.
If we mark slow tests, we can ensure that the end of the job is running lots of tests, not one test, and that may allow the same number of tests to complete in the same amount of time, but with lower concurrency.
If we can lower the concurrency, we can potentially also reduce the CPU request, without having to add an extra job.
Even if we add an extra job in the end, this may allow jobs to finish quicker and free up runners.