-
Notifications
You must be signed in to change notification settings - Fork 689
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
adjust Gateway API conformance test runs #4513
Labels
area/gateway-api
Issues or PRs related to the Gateway (Gateway API working group) API.
area/testing
Issues or PRs related to tests or testing tools.
lifecycle/needs-triage
Indicates that an issue needs to be triaged by a project contributor.
Milestone
Comments
skriss
added
area/testing
Issues or PRs related to tests or testing tools.
area/gateway-api
Issues or PRs related to the Gateway (Gateway API working group) API.
lifecycle/needs-triage
Indicates that an issue needs to be triaged by a project contributor.
labels
May 4, 2022
sounds like a nice compromise 👍🏽 |
Blocked by #4560. |
skriss
added a commit
to skriss/contour
that referenced
this issue
Jun 15, 2022
Changes the PR/push run of Gateway API conformance to run using the go.mod version of Gateway API, and adds a daily run of the latest conformance tests. Closes projectcontour#4513. Signed-off-by: Steve Kriss <krisss@vmware.com>
skriss
added a commit
to skriss/contour
that referenced
this issue
Jun 15, 2022
Changes the PR/push run of Gateway API conformance to run using the go.mod version of Gateway API, and adds a daily run of the latest conformance tests. Closes projectcontour#4513. Signed-off-by: Steve Kriss <krisss@vmware.com>
skriss
added a commit
to skriss/contour
that referenced
this issue
Jun 15, 2022
Changes the PR/push run of Gateway API conformance to run using the go.mod version of Gateway API, and adds a daily run of the latest conformance tests. Closes projectcontour#4513. Signed-off-by: Steve Kriss <krisss@vmware.com>
skriss
added a commit
to skriss/contour
that referenced
this issue
Jun 16, 2022
Changes the PR/push run of Gateway API conformance to run using the go.mod version of Gateway API, and adds a daily run of the latest conformance tests. Closes projectcontour#4513. Signed-off-by: Steve Kriss <krisss@vmware.com>
skriss
added a commit
to skriss/contour
that referenced
this issue
Jun 16, 2022
Changes the PR/push run of Gateway API conformance to run using the go.mod version of Gateway API, and adds a daily run of the latest conformance tests. Closes projectcontour#4513. Signed-off-by: Steve Kriss <krisss@vmware.com>
skriss
added a commit
that referenced
this issue
Jun 16, 2022
Changes the PR/push run of Gateway API conformance to run using the go.mod version of Gateway API, and adds a daily run of the latest conformance tests. Closes #4513. Signed-off-by: Steve Kriss <krisss@vmware.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/gateway-api
Issues or PRs related to the Gateway (Gateway API working group) API.
area/testing
Issues or PRs related to tests or testing tools.
lifecycle/needs-triage
Indicates that an issue needs to be triaged by a project contributor.
Right now we're always running the latest and greatest Gateway API conformance tests. As @sunjayBhatia rightly pointed out, this could be problematic since it's a moving target. I propose we do the following:
*the caveat is that there aren't any conformance tests in the release-0.4 branch, so we'll have to wait until 0.5 to move to this.
The text was updated successfully, but these errors were encountered: