cluster-logging-operator
cluster-logging-operator copied to clipboard
openshift
WIP: Fix test flakes
Flush out and fix test flakes.
test/functional/outputs/cloudwatch/forward_to_cloudwatch_test.go: Wait for logs to appear with Eventually.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: alanconway
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [alanconway]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@alanconway do we believe the logs will eventually arrive? The read call already has a read timeout of 10m that checks periodically. I have added this PR to try and dump the logs on failure and I dont see they do. The only difference between now and this test passing previously (e.g. 2w ago) is that since I advanced the OCP version upon where we test from 4.9 to 4.11
@alanconway: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/e2e | ab00c1aa0424e5dd9a8815a4b62f4efffa81145c | link | true | /test e2e |
| ci/prow/functional | ab00c1aa0424e5dd9a8815a4b62f4efffa81145c | link | true | /test functional |
Full PR test history. Your PR dashboard.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.