-
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
Run the timeout test 10 times 📈 #771
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 |
🤦♀️ |
831e470
to
315d198
Compare
If running it once doesn't always reproduce the issue, maybe running it 10 times will. (Basicaly trying to narrow in on a repro case!)
315d198
to
6be9c4f
Compare
YUUUUSSSS |
agaaaaain /test pull-tekton-pipeline-integration-tests |
wait, all the tests use this same task run 🤔 |
curses! |
c715abd
to
c08abb8
Compare
I think I've made some kind of variable scoping error 🤔 |
All the tests were using the same run _still_
This looks like it might be legit: /test pull-tekton-pipeline-integration-tests |
@bobcatfish: The following test failed, say
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. |
Thanks to these 2 most recent failures:
I think I know what's going on! The timeout handler and the reconciler do not agree about when a timeout has happened, more details in #731 (comment) |
To try to be sure that we've fixed the problem, I want to re-reate the conditions from tektoncd#771 which seemed to be pretty good at re-producing the problem.
To try to be sure that we've fixed the problem, I want to re-reate the conditions from tektoncd#771 which seemed to be pretty good at re-producing the problem.
If running it once doesn't always reproduce the issue, maybe running it 10 times will.
(Basicaly trying to narrow in on a repro case!)
Investigating #731