Speaking of wasting the resources, other than numerous jobs that should be cancelled, Ubuntu CI also blindly runs all the integration tests even when it doesn't make sense. For example, the PR I mentioned (where there were 16 jobs) had nothing to do with Ubuntu and should have been skipped altogether there. If the overall throughput is really important I think it would probably make sense to address those issues first.
Speaking of wasting the resources, other than numerous jobs that should be cancelled, Ubuntu CI also blindly runs all the integration tests even when it doesn't make sense. For example, the PR I mentioned (where there were 16 jobs) had nothing to do with Ubuntu and should have been skipped altogether there. If the overall throughput is really important I think it would probably make sense to address those issues first.
Just in case, here's what's skipped on CentOS CI: /github. com/systemd/ systemd- centos- ci/blob/ master/ jenkins/ runners/ systemd- pr-build. sh /github. com/systemd/ systemd- centos- ci/blob/ 8b4e41878b3f85d 16cc6a51af401eb c49dd88f65/ agent/testsuite .sh#L45
https:/
https:/