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

Output from tests can be erroneously identified as test results

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • 4.22.0
    • 4.22.0
    • Test Framework
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When running tests via openshift-tests run-test, only output written to ginkgo.GinkgoWriter is captured in the test result's output field. Raw stdout/stderr output from the test is not captured and instead goes directly to the process stdout/stderr.

      If that output contains something that looks like a test result (JSONL) we'll create empty ones, as marshalling will produce an OTE result with no fields filled.

      Figuring out what to do about the output is OCPBUGS-69963, but we should fix the problem in general with incorrectly creating empty extension tests

              rh-ee-fbabcock Forrest Babcock
              stbenjam Stephen Benjamin
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: