In https://github.com/openshift/machine-config-operator/pull/1683 we added -failfast will stop test execution at the first failure. As e2e-gcp is very long tests (2.5 hours) would like to backport this to 4.4.z.. In the last weeks the pain of waiting for such longs tests to maybe fail and retest made it difficult to quickly backport critical fixes.
This is a fix to the CI job itself, so there is nothing to verify in the MCO code itself. Picking out a recent PR to the `release-4.4` branch - https://github.com/openshift/machine-config-operator/pull/1844 The `gcp-op` job - https://deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gcs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1844/pull-ci-openshift-machine-config-operator-master-e2e-gcp-op/1273866582988165120 Checking the invocation of the job: ``` $ curl -sL https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1844/pull-ci-openshift-machine-config-operator-master-e2e-gcp-op/1273866582988165120/artifacts/e2e-gcp-op/container-logs/test.log | grep failfast go test -failfast -timeout 120m -v${WHAT:+ -run="$WHAT"} ./test/e2e/ ``` The `failfast` flag is there, so marking VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2713