Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-43408

Network: non-failing T1 lanes

XMLWordPrintable

    • virt-no-retries Clone
      • Network tier-1 test always pass, and when they don't, it is quickly resolved
    • Green
    • CNV-38613 - 2024 Code Quality
    • CNV-386132024 Code Quality
    • 0% To Do, 0% In Progress, 100% Done
    • dev-ready, doc-ready, po-ready, prodsec-ready, px-ready, qe-ready, ux-ready
    • Hide

      Looking good, getting better....

      Show
      Looking good, getting better....

      Goal

      sig-network should always pass when testing good merged code on kubevirtci

      User Stories

      • 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 of 2024-06-19, out of 31 PRs that were merged in the recent week, only 13 merged cleanly. The rest (18) required a /retry to pass. 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.>

      Notes

      • <Any additional details or decisions made/needed>

              ehaas1@redhat.com Edward Haas
              dkenigsb@redhat.com Dan Kenigsberg
              Yossi Segev Yossi Segev
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: