kubernetes-sigs/cluster-api-provider-vsphere

pull-cluster-api-provider-vsphere-test is flaky

Open

#2,042 opened on Jul 20, 2023

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Go (320 forks)auto 404
help wantedkind/flake

Repository metrics

Stars
 (417 stars)
PR merge metrics
 (PR metrics pending)

Description

Saw a few failing runs of pull-cluster-api-provider-vsphere-test on PRs recently.

One example is this one: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_cluster-api-provider-vsphere/2023/pull-cluster-api-provider-vsphere-test/1681753835858563072

Not exactly sure what's going on, but currently don't have time to take a closer look

/kind flake

Contributor guide

Research direction
Examine the failed test log from the Prow link. Identify the test function and trace its execution path in the cluster api provider vsphere codebase. Look for race conditions or timing issues that could cause flakiness.
Tech stack
go
Domain
backendinfrastructuretesting
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
GoKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40