Skip to content
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

sig-testing: uses LABEL_FILTER instead of FOCUS #32867

Merged
merged 1 commit into from
Jul 19, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 21 additions & 10 deletions config/jobs/kubernetes/sig-testing/kubernetes-kind.yaml
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
presubmits:
kubernetes/kubernetes:
# Please update the pull-kubernetes-e2e-kind-canary job first when making potentially intrusive changes.
# After the canary job is green and merged, update this job.
- name: pull-kubernetes-e2e-kind
cluster: k8s-infra-prow-build
optional: false
Expand All @@ -23,11 +25,11 @@ presubmits:
- -c
- curl -sSL https://kind.sigs.k8s.io/dl/latest/linux-amd64.tgz | tar xvfz - -C "${PATH%%:*}/" && e2e-k8s.sh
env:
- name: FOCUS
value: "."
- name: LABEL_FILTER
value: "Feature: isEmpty"
# TODO(bentheelder): reduce the skip list further
- name: SKIP
value: \[Slow\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\]|PodSecurityPolicy|LoadBalancer|load.balancer|Simple.pod.should.support.exec.through.an.HTTP.proxy|subPath.should.support.existing|NFS|nfs|inline.execution.and.attach|should.be.rejected.when.no.endpoints.exist
value: \[Slow\]|\[Disruptive\]|\[Flaky\]||PodSecurityPolicy|LoadBalancer|load.balancer|Simple.pod.should.support.exec.through.an.HTTP.proxy|subPath.should.support.existing|NFS|nfs|inline.execution.and.attach|should.be.rejected.when.no.endpoints.exist
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

did we ever test this with a canary job first? we appear to be running ZERO test cases now kubernetes/kubernetes#126401

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we did. Let's discuss on Slack.

- name: PARALLEL
value: "true"
# we need privileged mode in order to do docker in docker
Expand All @@ -46,7 +48,10 @@ presubmits:
testgrid-create-test-group: 'true'
fork-per-release: "true"


# The "canary" job for iterating on changes before promoting them to the pull-kubernetes-e2e-kind job.
# It should keep the same configuration as the pull-kubernetes-e2e-kind job except for the SKIP list.
# We can keep the canary running more tests, it is optional and can be used to get signal on PRs.
# The problem is the other way around, if the normal job runs more tests than the canary.
- name: pull-kubernetes-e2e-kind-canary
cluster: k8s-infra-prow-build
optional: true
Expand Down Expand Up @@ -93,6 +98,8 @@ presubmits:
testgrid-alert-stale-results-hours: '24'
testgrid-create-test-group: 'true'

# Please update the pull-kubernetes-e2e-kind-ipv6-canary job first when making potentially intrusive changes.
# After the canary job is green and merged, update this job.
- name: pull-kubernetes-e2e-kind-ipv6
cluster: k8s-infra-prow-build
optional: false
Expand All @@ -117,11 +124,11 @@ presubmits:
- -c
- curl -sSL https://kind.sigs.k8s.io/dl/latest/linux-amd64.tgz | tar xvfz - -C "${PATH%%:*}/" && e2e-k8s.sh
env:
- name: FOCUS
value: "."
- name: LABEL_FILTER
value: "Feature: isEmpty"
# TODO(bentheelder): reduce the skip list further
- name: SKIP
value: \[Slow\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\]|\[sig-storage\]|PodSecurityPolicy|LoadBalancer|load.balancer|In-tree.Volumes.\[Driver:.nfs\]|PersistentVolumes.NFS|Simple.pod.should.support.exec.through.an.HTTP.proxy|subPath.should.support.existing
value: \[Slow\]|\[Disruptive\]|\[Flaky\]|\[sig-storage\]|PodSecurityPolicy|LoadBalancer|load.balancer|In-tree.Volumes.\[Driver:.nfs\]|PersistentVolumes.NFS|Simple.pod.should.support.exec.through.an.HTTP.proxy|subPath.should.support.existing
- name: PARALLEL
value: "true"
# enable IPV6 in bootstrap image
Expand All @@ -146,6 +153,10 @@ presubmits:
testgrid-alert-stale-results-hours: '24'
testgrid-create-test-group: 'true'

# The "canary" job for iterating on changes before promoting them to the pull-kubernetes-e2e-kind-ipv6 job.
# It should keep the same configuration as the pull-kubernetes-e2e-kind-ipv6 job except for the SKIP list.
# We can keep the canary running more tests, it is optional and can be used to get signal on PRs.
# The problem is the other way around, if the normal job runs more tests than the canary.
- name: pull-kubernetes-e2e-kind-ipv6-canary
cluster: k8s-infra-prow-build
optional: true
Expand Down Expand Up @@ -454,10 +465,10 @@ presubmits:
value: '{"EventedPLEG":true}'
- name: RUNTIME_CONFIG
value: '{"api/alpha":"true", "api/ga":"true"}'
- name: FOCUS
Copy link
Member Author

@carlory carlory Jun 28, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pacoxu should the job pull-kubernetes-e2e-kind-evented-pleg be moved into sig-node?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this can be done later 😄

value: "."
- name: LABEL_FILTER
value: "Feature: isEmpty"
- name: SKIP
value: \[Slow\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\]|PodSecurityPolicy|LoadBalancer|load.balancer|In-tree.Volumes.\[Driver:.nfs\]|PersistentVolumes.NFS|Network.should.set.TCP.CLOSE_WAIT.timeout|Simple.pod.should.support.exec.through.an.HTTP.proxy|subPath.should.support.existing|should.provide.basic.identity
value: \[Slow\]|\[Disruptive\]|\[Flaky\]|PodSecurityPolicy|LoadBalancer|load.balancer|In-tree.Volumes.\[Driver:.nfs\]|PersistentVolumes.NFS|Network.should.set.TCP.CLOSE_WAIT.timeout|Simple.pod.should.support.exec.through.an.HTTP.proxy|subPath.should.support.existing|should.provide.basic.identity
- name: PARALLEL
value: "true"
# we need privileged mode in order to do docker in docker
Expand Down