kind-alpha-beta-features: not release informing, serial experiment #35609
+4
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The experiment is meant to determine whether running serial tests in the same job as the parallel tests works and how much slower it becomes. Even long term the job probably shouldn't be release informing because the alpha tests can break it at any time, without affecting the release. What needs to become release informing instead are the kind-alpha-beta-enabled and/or kind-alpha-beta-enabled-conformance jobs (to be determined after we are done with setting everything up and they proof to be stable).
k8s-ci-robot
added
the
cncf-cla: yes
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: pohly 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 |
k8s-ci-robot
added
area/config
|
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-sigs/prow repository. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The experiment is meant to determine whether running serial tests in the same job as the parallel tests works and how much slower it becomes.
Even long term the job probably shouldn't be release informing because the alpha tests can break it at any time, without affecting the release. What needs to become release informing instead are the kind-alpha-beta-enabled and/or kind-alpha-beta-enabled-conformance jobs (to be determined after we are done with setting everything up and they proof to be stable).
/assign @aojea
/cc @BenTheElder
From Slack:
[...]So that part should work. But you are right, we haven't really exercised that much. [...] Looking at my list I don't see any canaries for ci jobs. [...] Modifying ci-kubernetes-e2e-kind-alpha-beta-features instead of creating a new periodic seems safe enough.