XML

Word

Printable

Epic Name:
virt-no-retries2
Activity Type:
Product / Portfolio Work
Story Points:
77
Acceptance Criteria:
Hide

The failure rate (the number of times a PR fails Tier 1 tests before it is merged) must be less than 5%

This is the number of times a CI run failed divided by the total number of CI executions

Only the last code change to a PR should be evaluated. The assumption is that if the code was changed there were bugs that were being addressed.

Gating Tests should always PASS.
Show
The failure rate (the number of times a PR fails Tier 1 tests before it is merged) must be less than 5% This is the number of times a CI run failed divided by the total number of CI executions Only the last code change to a PR should be evaluated. The assumption is that if the code was changed there were bugs that were being addressed. Gating Tests should always PASS.
Epic Status:
In Progress
Feature Link:
VIRTSTRAT-334 - 2024 Code Quality
Parent Link:
VIRTSTRAT-3342024 Code Quality
Hierarchy Progress Bar:

50% To Do, 0% In Progress, 50% Done
Status Summary:

Hide

2025-01-06:
dev is working on this....

Show
2025-01-06: dev is working on this....

Goal

sig-compute should always pass when testing good merged code on kubevirtci.
- Identify and Prioritize High Priority Virt T1 Tests for Downstream Builds.
  - Use the "Conformance" label to select the Virt T1 Tests for Gating.
- Remove and/or Rewrite the tests after reviewing the tests.
Ensure the Non Productized Tests from Tier1 Jobs are skipped.
Create Full T1 Scheduled job runs for kubevirt-compute-ocs.
Update existing jobs to pick the tests labeled with Conformance.

Discussion Doc:

As a KubeVirt developer, I want to trust my tests. When they fail, I need to know that I introduced a bug. I must not assume that "this may be a flake".
- As a KubeVirt developer I would accept a failure rate of 5%, but no more.
As an OpenShift Virtualization developer, I would like to see my tests passing in downstream CI without any hiccup.
As an OpenShift Virtualization admin, I would like to receive weekly updates of my operator. I would like it to pass continuous integration smoothly and without human intervention - no failure analysis and no manual wavers.

Non-Requirements

List of things not included in this epic, to alleviate any doubt raised during the grooming process.

clones

CNV-43178 Virt: non-failing T1 lanes

is cloned by

CNV-56011 Upstream Compute: Keep retries below 5%