kind-alpha-beta-features: serial experiment #35609
Conversation
k8s-ci-robot
added
cncf-cla: yes
pohly
force-pushed
the
alpha-beta-serial
branch
from
1e85b85 to
21706a7
Compare
k8s-ci-robot
added
size/M
|
Because of kubernetes/sig-release#2888 I decided to not modify the existing job and instead added another one. |
…slow) The experiment is meant to determine whether running serial tests in the same job as the parallel tests works, how much slower it becomes, and how stable the job is (hence periodic). Slow, deprecated and disruptive tests are also allowed. The goal is full coverage.
pohly
force-pushed
the
alpha-beta-serial
branch
from
21706a7 to
ef9be07
Compare
k8s-ci-robot
removed
the
needs-rebase
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea, pohly 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 |
k8s-ci-robot
added
the
approved
|
@pohly: Updated the
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-sigs/prow repository. |
pohly
changed the title
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.