During a recent TRT stand-up, David pointed out the extremely high pass rates of upstream kube tests, but those same tests in OpenShift fail quite a bit. There's a theory that perhaps some of the OpenShift tests like builds use up so much I/O and other resources that they introduce instability. In master we have a change that runs them separately, and it seems to have improved the situation overall. 4.10 today has a pass rate of 70% of all jobs running e2e tests, but 4.9 is around 51%. This is visible in the 4th release indicator widget on the overview page: https://sippy.ci.openshift.org/sippy-ng/release/4.10 vs https://sippy.ci.openshift.org/sippy-ng/release/4.9 It's not clear if all or any of that is attributable to that change, but we'd like to backport it to 4.9 to confirm.