Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-2014

CI: Backend unit tests fails because devfile registry was updated (mock response)

    XMLWordPrintable

Details

    • ODC Sprint 226
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None

    Description

      This is a clone of issue OCPBUGS-1678. The following is the description of the original issue:
      —
      Description of problem:
      pkg/devfile/sample_test.go fails after devfile registry was updated (https://github.com/devfile/registry/pull/126)

      OCPBUGS-1677 is about updating our assertion so that the CI job runs successfully again. We might want to backport this as well.

      This is about updating the code that the test should use a mock response instead of the latest registry content OR check some specific attributes instead of comparing the full JSON response.

      Version-Release number of selected component (if applicable):
      4.12

      How reproducible:
      Always

      Steps to Reproduce:
      1. Clone openshift/console
      2. Run ./test-backend.sh

      Actual results:
      Unit tests fail

      Expected results:
      Unit tests should pass again

      Additional info:

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-2622 CI: Backend unit tests fails because devfile registry was updated (mock response)

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-2655 CI: Backend unit tests fails because devfile registry was updated (mock response)

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          clones

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-1678 CI: Backend unit tests fails because devfile registry was updated (mock response)

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-1678 CI: Backend unit tests fails because devfile registry was updated (mock response)

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-2655 CI: Backend unit tests fails because devfile registry was updated (mock response)

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          links to

          GitHub openshift/console#12137: [release-4.11] OCPBUGS-2014: Use local test data to mock a devfile registry

          Activity

            People

              jakumar jaivardhan Kumar
              openshift-crt-jira-prow OpenShift Prow Bot
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: