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
in reference to #16850, #16940, and #19790
TestOAuthServiceAccountClientEvent is one of the integration tests that still appears to be flaky https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/19759/test_pull_request_origin_integration/18011/ https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/19759/test_pull_request_origin_integration/18027/ https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/19759/test_pull_request_origin_integration/18066/ https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/19759/test_pull_request_origin_integration/18075/
Assigning @mrogers950 as he appears to be the last one touching the test, feel free to delegate
/cc: @enj , @bparees
The text was updated successfully, but these errors were encountered:
mrogers950
No branches or pull requests
in reference to #16850, #16940, and #19790
TestOAuthServiceAccountClientEvent is one of the integration tests that still appears to be flaky
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/19759/test_pull_request_origin_integration/18011/
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/19759/test_pull_request_origin_integration/18027/
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/19759/test_pull_request_origin_integration/18066/
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/19759/test_pull_request_origin_integration/18075/
Assigning @mrogers950 as he appears to be the last one touching the test, feel free to delegate
/cc: @enj , @bparees
The text was updated successfully, but these errors were encountered: