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.

Sign up for GitHub

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

Jump to bottom

Fix or remove continuously failing jobs listed under sig-testing testgrid dashboard group #11

Open
7 of 17 tasks
spiffxp opened this issue Sep 30, 2021 · 9 comments
Open
7 of 17 tasks

Fix or remove continuously failing jobs listed under sig-testing testgrid dashboard group #11

spiffxp opened this issue Sep 30, 2021 · 9 comments
Assignees
@spiffxp
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/testing Categorizes an issue or PR as relevant to SIG Testing.

Comments

@spiffxp
Copy link
Member

spiffxp commented Sep 30, 2021 •
edited
Loading

We have a number of jobs that are continuously failing. I'd like to see us get our dashboards back to green.

suffixes=(
  boskos
  canaries
  e2e-framework
  images
  kind
  kubetest2
  maintenance
  misc
  prow
)
for suffix in "${suffixes[@]}"; do
  curl -s https://testgrid.k8s.io/sig-testing-$suffix/summary \
  | jq -r '
    to_entries 
    | map(
      select(.value.overall_status == "FAILING") 
      | "- [ ] https://testgrid.k8s.io/\(.value.dashboard_name)#\(.key)"
    )[]';
done

/sig testing
/kind failing-test
/kind bug
/priority important-longterm
/milestone v1.23
@k8s-ci-robot k8s-ci-robot added sig/testing Categorizes an issue or PR as relevant to SIG Testing. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. kind/bug Categorizes issue or PR as related to a bug. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Sep 30, 2021
@spiffxp spiffxp mentioned this issue Sep 30, 2021
Merged
@spiffxp
Copy link
Member Author

spiffxp commented Sep 30, 2021

The images job failures are likely due to kubernetes/test-infra#23741

@spiffxp spiffxp mentioned this issue Sep 30, 2021
Merged
@spiffxp
Copy link
Member Author

spiffxp commented Sep 30, 2021

kubernetes/test-infra#23848 should address:

@spiffxp
Copy link
Member Author

spiffxp commented Sep 30, 2021

kubernetes/test-infra#23849 should address:

@spiffxp spiffxp mentioned this issue Sep 30, 2021
Merged
@spiffxp
Copy link
Member Author

spiffxp commented Sep 30, 2021

kubernetes/test-infra#23850 should address:

@spiffxp
Copy link
Member Author

spiffxp commented Oct 1, 2021

/assign

@spiffxp
Copy link
Member Author

spiffxp commented Oct 1, 2021

https://testgrid.k8s.io/sig-testing-images#kubemci - the image build itself appears to be stale or broken, may want to consider dropping it and the jobs that use it (ref: https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/post-test-infra-push-kubemci/1443726706299899904)

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 31, 2021
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 30, 2022
@BenTheElder
Copy link
Member

/remove-lifecycle rotten
/lifecycle frozen
these still need to get removed at some point, even if folks are too busy to do it soon

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@spiffxp spiffxp

Labels
kind/bug Categorizes issue or PR as related to a bug. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@spiffxp @BenTheElder @k8s-ci-robot @k8s-triage-robot