-
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
[WIP] Support per-path deadlines initialized from v1.Revision.Spec.TimeoutSeconds. #8203
Conversation
…into richterdavid/issue2201
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.
@richterdavid: 2 warnings.
In response to this:
Fixes #2201
Proposed Changes
- Pass v1.Revision.Spec.TimeoutSeconds through as the deadline for request paths
- Pass config.Defaults.RevisionTimeoutSeconds for the default deadline and minimum deadline
- If several revisions contribute to the same path, use the maximum of these
Release Note
Support per-path deadlines initialized from config.Defaults.RevisionTimeoutSeconds and v1.Revision.Spec.TimeoutSeconds.
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.
/test pull-knative-serving-unit-tests |
/lint |
…into richterdavid/issue2201
/test |
@richterdavid: The
Use
In response to this:
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. |
/test all |
/test pull-knative-serving-unit-tests |
/test pull-knative-serving-https |
/test pull-knative-serving-https |
…into richterdavid/issue2201
See discussion of this PR in slack: |
/test all |
The following is the coverage report on the affected files.
|
The following jobs failed:
Failed non-flaky tests preventing automatic retry of pull-knative-serving-integration-tests:
|
…into richterdavid/issue2201
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: richterdavid The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…into richterdavid/issue2201
This is blocked on knative/networking#22 being submitted and vendored in, to address feedback on Slack from @markusthoemmes |
@richterdavid: PR needs rebase. 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. |
@richterdavid the relevant PR seems to have been merged. Any news on this one? |
Sorry for the delay. I've been OOO for two weeks and am just getting caught
up on things now that I'm back. I'll circle back to this PR when I have the
chance.
…On Mon, Aug 10, 2020 at 11:40 PM Markus Thömmes ***@***.***> wrote:
@richterdavid <https://github.com/richterdavid> the relevant PR seems to
have been merged. Any news on this one?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8203 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOXGKZU7P24D3EYRYL3DEULSADRUHANCNFSM4NSZUU6Q>
.
|
@richterdavid: The following tests 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. |
/close |
@richterdavid: Closed this PR. In response to this:
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. |
Fixes #2201
Proposed Changes
Release Note