test-infra icon indicating copy to clipboard operation
test-infra copied to clipboard
verified publisher icon kubernetes

capz: debug failing periodic main job

Open jackfrancis opened this issue 3 years ago • 4 comments

This PR updates the capz periodic main test job to this dedicated PR branch used for turning these flakes green:

https://github.com/kubernetes-sigs/cluster-api-provider-azure/pull/2451

As of 5 July 2022 8 of the past 10 jobs have failed, so it would be defensible to consider this job (or capz @ main) unstable. Having a dedicated branch to change and observe outcomes to test configuration (or code) changes will help us triage which of those two possibilities are true, and how best to make things healthy again.

jackfrancis avatar Jul 05 '22 15:07 jackfrancis

cc @CecileRobertMichon @jsturtevant

jackfrancis avatar Jul 05 '22 15:07 jackfrancis

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jackfrancis

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 /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

k8s-ci-robot avatar Jul 05 '22 15:07 k8s-ci-robot

/hold

CecileRobertMichon avatar Jul 06 '22 00:07 CecileRobertMichon

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-triage-robot avatar Oct 04 '22 00:10 k8s-triage-robot

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-triage-robot avatar Nov 03 '22 01:11 k8s-triage-robot