We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
the test appears to be flaky, few different PRs recently failed some of the runs with the same message
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/19673/pull-ci-origin-unit/581/ https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/20145/pull-ci-origin-unit/575/ https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/20145/pull-ci-origin-unit/573/ https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/20095/pull-ci-origin-unit/567/
The text was updated successfully, but these errors were encountered:
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/20064/pull-ci-origin-unit/595/
Sorry, something went wrong.
@wozniakjan @adambkaplan Hey guys, this is helpful, but can you chase it the extra step to find the test that actually failed?
@wozniakjan you're hitting #20136
@adambkaplan you have a different error
got it, thanks! I don't know why I thought that was actually the name of the failing test, closing this as a dupe
No branches or pull requests
the test appears to be flaky, few different PRs recently failed some of the runs with the same message
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/19673/pull-ci-origin-unit/581/
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/20145/pull-ci-origin-unit/575/
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/20145/pull-ci-origin-unit/573/
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/20095/pull-ci-origin-unit/567/
The text was updated successfully, but these errors were encountered: