Uploaded image for project: 'MicroShift'
  1. MicroShift
  2. USHIFT-1102

analyze failing tests and break down tasks for fixing them

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Done
    • Icon: Undefined Undefined
    • openshift-4.14
    • None
    • None
    • Proactive Architecture
    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • uShift Sprint 235, uShift Sprint 236, uShift Sprint 237, uShift Sprint 238

      • Around 1200 failures, but many fixed by the same change
      • Most from storage (~1100)
      • Most of the rest are due to differences in how openshift organizes resources (missing configmaps, etc.)
      • Work out a plan
      • Do the analysis to let us open ticket for individual tasks, without having 1 per failing test

              rh-ee-ckyal Chirag Kyal
              dhellman@redhat.com Doug Hellmann
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: