-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
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
cmd test flake: 0-length response instead of expected timeout #15453
Comments
@abstractj can you look into this one ? |
@simo5 sure! |
@miminar is this URL correct? I'm getting 404 when trying to access the report. |
@abstractj unfortunately the test results don't survive long. The latest accessible run is 3481 as of now (not mentioning anomaly 1250). |
@miminar thank you, I finally managed to reproduce the issue Code to reproduce the issue:
|
@juanvallejo I will definitely need your help on this. It seems something really tricky to debug. |
Automatic merge from submit-queue (batch tested with PRs 15885, 15973, 16000) cmd test flake: 0-length response instead of expected timeout It looks like this issue is related with HEAD request that we do. By changing it to send HTTP GET requests to our /healthz endpoint seems to fix the issue. Signed-off-by: Bruno Oliveira <[email protected]> @juanvallejo @fabianofranz it seems to fix the issue #15453
Fixed in #15885 |
Happened in job https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/3449/testReport/junit/github/com_openshift_origin_test_cmd_request-timeout/test_cmd_timeout_sh_19__executing__oc_login__u_testuser__p_test___request_timeout_1ns__expecting_failure_and_text__Timeout_exceeded_while_awaiting_headers_/
The text was updated successfully, but these errors were encountered: