-
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
Can I reproduce it with just the timeout test alone? 🎵 #770
Conversation
One is the loneliest number One is the loneliest number One is the loneliest number that you'll ever do One is the loneliest One is the loneliest One is the loneliest number that you'll ever do
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bobcatfish The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
lol maybe not... AGAIN /test pull-tekton-pipeline-integration-tests |
ಠ_ಠ |
/test pull-tekton-pipeline-integration-tests |
😩 /test pull-tekton-pipeline-integration-tests |
/test pull-tekton-pipeline-integration-tests |
I mean its really seeming like just the one test on its own is never hitting this, I say, based on my sample set of 5. /test pull-tekton-pipeline-integration-tests |
Yes that was kind of my assumption too… when run alone (without any load), it seems to hold on… I think timeout is flakey under medium to heavy load on the controller, somehow |
/test pull-tekton-pipeline-integration-tests |
I'm wondering if it's something load related too 🤔🤔 🤔 which will be harder to figure out probably. It's weird tho cuz it never seems to happen locally, even using (what I think is) the same cluster setup. |
One is the loneliest number
One is the loneliest number
One is the loneliest number that you'll ever do
One is the loneliest
One is the loneliest
One is the loneliest number that you'll ever do
Investigating #731