Repository navigation
release-1.6: fix: remove provisional flag from promoted tests - #5260
kubernetes-prow[bot] merged 3 commits into
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rikatz The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
This issue is currently awaiting triage. If Gateway API community members determine this is a relevant issue, they will accept it by applying the The DetailsInstructions 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-sigs/prow repository. |
|
/hold I think the cherry pick missed some other tests |
…etes-sigs#5223) TCPRoute and UDPRoute graduated to the Standard channel in v1.6, but most of their conformance tests were still marked Provisional, causing them to be skipped when running the suite with --skip-provisional-tests. Remove the Provisional flag from the remaining TCPRoute and UDPRoute conformance tests so they run as Standard conformance tests, matching the already-unmarked tcproute-multiple-routes-attachment test. Signed-off-by: Shashank Varma <324153016+shashankvarma499@users.noreply.github.com> Co-authored-by: Shashank Varma <324153016+shashankvarma499@users.noreply.github.com>
a272486 to
67b30ea
Compare
|
/hold cancel |
|
Istio is passing the conformance test for 1.6.3 on a PR I have opened to test it: istio/istio#61764 |
|
/lgtm Thanks @rikatz! |
5cc08b4
into
kubernetes-sigs:release-1.6
…(#654) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [kubernetes-sigs/gateway-api](https://github.com/kubernetes-sigs/gateway-api) | Kustomization | patch | `v1.6.2` → `v1.6.3` | --- ### Release Notes <details> <summary>kubernetes-sigs/gateway-api (kubernetes-sigs/gateway-api)</summary> ### [`v1.6.3`](https://github.com/kubernetes-sigs/gateway-api/releases/tag/v1.6.3) [Compare Source](kubernetes-sigs/gateway-api@v1.6.2...v1.6.3) ### v1.6.3 #### Major Changes Since v1.6.2 ##### Conformance - Conformance tests for stable features (notable TCPRoute and UDPRoute) are no longer marked as "provisional" ([#​5260](kubernetes-sigs/gateway-api#5260), [@​rikatz](https://github.com/rikatz)) - Force the timeout for the `ExpectMirroredRequest` conformance test to `MaxTimeToConsistency` ([#​5296](kubernetes-sigs/gateway-api#5296), [@​kl52752](https://github.com/kl52752)) - *Actually* remove unused namespaces in Mesh conformance tests ([#​5251](kubernetes-sigs/gateway-api#5251), [@​xtineskim](https://github.com/xtineskim)) - Add the `GatewayInvalidParametersRef` conformance test ([#​5236](kubernetes-sigs/gateway-api#5236), [@​kl52752](https://github.com/kl52752)) #### Build - Ensure the Go toolchain matches `go.work` ([#​5234](kubernetes-sigs/gateway-api#5234), [@​snorwin](https://github.com/snorwin)) </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMzguMCIsInVwZGF0ZWRJblZlciI6IjQ0LjEzOC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
What type of PR is this?
/kind cleanup
/area conformance-test
What this PR does / why we need it:
Manual cherry-pick of #5223, #5254 and #5242
These tests were incorrectly marked as provisional, given they are already part of stable / standard channels.
Which issue(s) this PR fixes:
Fixes: This is related with #5218
Does this PR introduce a user-facing change?:
Was AI used in preparing this PR?
/label ail/0