kubernetes
Fix or reduce frequency or switch off perma-failing jobs
Data as of June 3rd, 9:00 PM Eastern. Latest data can be found here: http://storage.googleapis.com/k8s-metrics/failures-latest.json
Additional Context: https://github.com/kubernetes/test-infra/issues/18600
| CI Job | Days Failed |
|---|---|
| ci-kubernetes-e2e-gce-new-master-gci-kubectl-skew | 66 |
| ci-kubernetes-e2e-gce-stable1-latest-gci-kubectl-skew | 66 |
| ci-kubernetes-e2e-gce-stable2-stable1-gci-kubectl-skew | 36 |
@mpuckett159: The label(s) priority/soon cannot be applied, because the repository doesn't have them.
In response to this:
/triage accepted /priority soon bug
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/test-infra repository.
This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged.
Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.
You can:
- Confirm that this issue is still relevant with
/triage accepted(org members only) - Deprioritize it with
/priority important-longtermor/priority backlog - Close this issue with
/close
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/
/remove-triage accepted
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale