-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Wait for Route readiness in TestSingleConcurrency #2308
Wait for Route readiness in TestSingleConcurrency #2308
Conversation
TestSingleConcurrency was waiting for the Revision to be Ready but should also wait on the Route to both be Ready and respond successfully to a request before proceeding with the rest of the test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bbrowning: 1 warning.
In response to this:
TestSingleConcurrency was waiting for the Revision to be Ready but should also wait on the Route to both be Ready and respond successfully to a request before proceeding with the rest of the test.
This pulls
probeDomain
from the blue green test out intotest.ProbeDomain
because, until #1582 is fixed, every test that sends traffic to a Route should probably probe the domain first in some way to prevent flakes.Fixes #2306
Release Note
NONE
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.
/lgtm |
/retest |
/test pull-knative-serving-integration-tests |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bbrowning, mattmoor 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 |
TestSingleConcurrency was waiting for the Revision to be Ready but should also wait on the Route to both be Ready and respond successfully to a request before proceeding with the rest of the test.
This pulls
probeDomain
from the blue green test out intotest.ProbeDomain
because, until #1582 is fixed, every test that sends traffic to a Route should probably probe the domain first in some way to prevent flakes.Fixes #2306
Release Note