-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Flake: TestLargerResultsSidecarLogs is flaky #6769
Comments
Also saw this in #6792 and was able to reproduce locally even when on main. Here are the logs from my cluster: https://gist.github.com/EmmaMunley/5f0a056b410bbb6ef7dc41e08e62c2f7 |
I did some digging around and found this: https://gist.github.com/JeromeJu/d19845cfac2f69d83d33c3ee385ca0cf#file-gistfile1-txt-L303-L313 For @EmmaMunley's bug, do you have access to your controller's logs? My guess is that when you were testing this on your local cluster, you did not enable access to the logs by |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
/remove-lifecycle rotten |
/assign |
@chitrangpatel Thanks for the clarification! It looks like we could close this for now unless anything other than pull issue or the feature setup, WDYT? |
Agreed. We can close this for now. |
The PipelienRun times out after waiting for 10 minutes.
Prow logs: https://prow.tekton.dev/view/gs/tekton-prow/pr-logs/pull/tektoncd_pipeline/6766/pull-tekton-pipeline-alpha-integration-tests/1664713403156926464
logs
/kind flake
The text was updated successfully, but these errors were encountered: