Some jobs are taking exceptionally long amounts of time, causing the job to fail when the timeout on the test step is exceeded (~3h).

Example: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.12-e2e-aws-ovn-upgrade/1585545649024143360

09:37:34 upgrade starts
10:48:46 upgrade completes (total 1h10m - this is a typical timing)
10:50:18 conformance tests start running
12:42:11 tests are killed due to timeout (1h52m later - about 2x as much as normal)

We didn't get an intervals chart, but I put together the above from the logs. There doesn't appear to be once place where it's stuck, since tests keep running. It's just... slower.