<?xml version="1.0" encoding="UTF-8"?>
  <testsuites tests="464" disabled="340" errors="0" failures="0" time="2278.774407188">
      <testsuite name="Red Hat App Studio E2E tests" package="/tmp/tmp.LHtSA2pOeP/cmd" tests="464" disabled="88" skipped="252" errors="0" failures="0" time="2278.774407188" timestamp="2026-04-24T05:45:35">
          <properties>
              <property name="SuiteSucceeded" value="true"></property>
              <property name="SuiteHasProgrammaticFocus" value="false"></property>
              <property name="SpecialSuiteFailureReason" value=""></property>
              <property name="SuiteLabels" value="[]"></property>
              <property name="SuiteSemVerConstraints" value="[]"></property>
              <property name="SuiteComponentSemVerConstraints" value="[]"></property>
              <property name="RandomSeed" value="1777009390"></property>
              <property name="RandomizeAllSpecs" value="false"></property>
              <property name="LabelFilter" value="integration-service"></property>
              <property name="SemVerFilter" value=""></property>
              <property name="FocusStrings" value=""></property>
              <property name="SkipStrings" value=""></property>
              <property name="FocusFiles" value=""></property>
              <property name="SkipFiles" value=""></property>
              <property name="FailOnPending" value="false"></property>
              <property name="FailOnEmpty" value="false"></property>
              <property name="FailFast" value="false"></property>
              <property name="FlakeAttempts" value="0"></property>
              <property name="DryRun" value="false"></property>
              <property name="ParallelTotal" value="20"></property>
              <property name="OutputInterceptorMode" value="none"></property>
          </properties>
          <testcase name="[It] [release-pipelines-suite e2e tests for rh-advisories pipeline] Rh-advisories happy path Post-release verification verifies if release CR is created [release-pipelines, rh-advisories, rhAdvisories]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rh-advisories pipeline] Rh-advisories happy path Post-release verification verifies the advs release pipelinerun is running and succeeds [release-pipelines, rh-advisories, rhAdvisories]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rh-advisories pipeline] Rh-advisories happy path Post-release verification verifies release CR completed and set succeeded. [release-pipelines, rh-advisories, rhAdvisories]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rh-advisories pipeline] Rh-advisories happy path Post-release verification verifies if the repository URL is valid [release-pipelines, rh-advisories, rhAdvisories]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when a new Component is created triggers a build PipelineRun [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="33.206794788">
              <system-err>&gt; Enter [BeforeAll] with happy path for general flow of Integration service - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:52 @ 04/24/26 05:45:35.834&#xA;Image repository for component test-component-pac-nmdnat in namespace integration1-vdha do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [BeforeAll] with happy path for general flow of Integration service - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:52 @ 04/24/26 05:45:48.905 (13.071s)&#xA;&gt; Enter [It] triggers a build PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:85 @ 04/24/26 05:45:48.906&#xA;no pipelinerun found for component test-component-pac-nmdnat (application: integ-app-gony, namespace: integration1-vdha)&#xA;&lt; Exit [It] triggers a build PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:85 @ 04/24/26 05:46:09.04 (20.135s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 05:46:09.041&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 05:46:09.041 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when a new Component is created verifies if the build PipelineRun contains the finalizer [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.070545419">
              <system-err>&gt; Enter [It] verifies if the build PipelineRun contains the finalizer - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:90 @ 04/24/26 05:46:09.041&#xA;&lt; Exit [It] verifies if the build PipelineRun contains the finalizer - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:90 @ 04/24/26 05:46:09.111 (70ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 05:46:09.112&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 05:46:09.112 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when a new Component is created waits for build PipelineRun to succeed [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="900.201346859">
              <system-err>&gt; Enter [It] waits for build PipelineRun to succeed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:101 @ 04/24/26 05:46:09.112&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk found for Component integration1-vdha/test-component-pac-nmdnat&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: ResolvingTaskRef&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun test-component-pac-nmdnat-on-pull-request-kcwkk reason: Running&#xA;PipelineRun my-integration-test-ahod-t9z2s reason: ResolvingTaskRef&#xA;PipelineRun my-integration-test-ahod-t9z2s reason: Running&#xA;PipelineRun my-integration-test-ahod-t9z2s reason: Running&#xA;PipelineRun my-integration-test-ahod-t9z2s reason: Succeeded&#xA;&lt; Exit [It] waits for build PipelineRun to succeed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:101 @ 04/24/26 06:01:09.313 (15m0.201s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:09.313&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:09.313 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when a new Component is created should have a related PaC init PR created [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.359183553">
              <system-err>&gt; Enter [It] should have a related PaC init PR created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:107 @ 04/24/26 06:01:09.314&#xA;&lt; Exit [It] should have a related PaC init PR created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:107 @ 04/24/26 06:01:09.673 (359ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:09.673&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:09.673 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if the BuildPipelineRun have the annotation of chains signed [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.139687421">
              <system-err>&gt; Enter [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:128 @ 04/24/26 06:01:09.673&#xA;&lt; Exit [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:128 @ 04/24/26 06:01:09.813 (139ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:09.813&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:09.813 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if the Snapshot is created [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.068242438">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:132 @ 04/24/26 06:01:09.813&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:132 @ 04/24/26 06:01:09.881 (68ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:09.881&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:09.881 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if the Build PipelineRun got annotated with Snapshot name [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.13934242">
              <system-err>&gt; Enter [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:137 @ 04/24/26 06:01:09.882&#xA;&lt; Exit [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:137 @ 04/24/26 06:01:10.021 (139ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:10.021&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:10.021 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when the build pipelineRun run succeeded verifies that the finalizer has been removed from the build pipelinerun [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.069734472">
              <system-err>&gt; Enter [It] verifies that the finalizer has been removed from the build pipelinerun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:141 @ 04/24/26 06:01:10.022&#xA;&lt; Exit [It] verifies that the finalizer has been removed from the build pipelinerun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:141 @ 04/24/26 06:01:10.091 (69ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:10.091&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:10.091 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if all of the integrationPipelineRuns passed [integration-service, slow]" classname="Red Hat App Studio E2E tests" status="passed" time="0.134802505">
              <system-err>&gt; Enter [It] checks if all of the integrationPipelineRuns passed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:154 @ 04/24/26 06:01:10.092&#xA;Integration test scenario my-integration-test-ahod is found&#xA;PipelineRun my-integration-test-ahod-t9z2s reason: Succeeded&#xA;&lt; Exit [It] checks if all of the integrationPipelineRuns passed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:154 @ 04/24/26 06:01:10.226 (134ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:10.227&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:10.227 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if the passed status of integration test is reported in the Snapshot [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.069498485">
              <system-err>&gt; Enter [It] checks if the passed status of integration test is reported in the Snapshot - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:158 @ 04/24/26 06:01:10.228&#xA;&lt; Exit [It] checks if the passed status of integration test is reported in the Snapshot - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:158 @ 04/24/26 06:01:10.296 (69ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:10.297&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:10.297 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if the skipped integration test is absent from the Snapshot&#39;s status annotation [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.069385232">
              <system-err>&gt; Enter [It] checks if the skipped integration test is absent from the Snapshot&#39;s status annotation - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:173 @ 04/24/26 06:01:10.297&#xA;&lt; Exit [It] checks if the skipped integration test is absent from the Snapshot&#39;s status annotation - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:173 @ 04/24/26 06:01:10.366 (69ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:10.367&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:10.367 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if the finalizer was removed from all of the related Integration pipelineRuns [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.137026612">
              <system-err>&gt; Enter [It] checks if the finalizer was removed from all of the related Integration pipelineRuns - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:183 @ 04/24/26 06:01:10.367&#xA;Integration test scenario my-integration-test-ahod is found&#xA;&lt; Exit [It] checks if the finalizer was removed from all of the related Integration pipelineRuns - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:183 @ 04/24/26 06:01:10.504 (137ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:10.504&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:10.504 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service creates a ReleasePlan [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.147137652">
              <system-err>&gt; Enter [It] creates a ReleasePlan - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:188 @ 04/24/26 06:01:10.504&#xA;IntegrationTestScenario my-integration-test-ahod is found&#xA;IntegrationTestScenario skipped-its is found&#xA;&lt; Exit [It] creates a ReleasePlan - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:188 @ 04/24/26 06:01:10.651 (147ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:10.651&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:10.651 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service creates an snapshot of push event [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.073301998">
              <system-err>&gt; Enter [It] creates an snapshot of push event - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:198 @ 04/24/26 06:01:10.652&#xA;&lt; Exit [It] creates an snapshot of push event - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:198 @ 04/24/26 06:01:10.725 (73ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:10.725&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:10.725 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when An snapshot of push event is created checks if the global candidate is updated after push event [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.134317571">
              <system-err>&gt; Enter [It] checks if the global candidate is updated after push event - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:205 @ 04/24/26 06:01:10.726&#xA;&lt; Exit [It] checks if the global candidate is updated after push event - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:205 @ 04/24/26 06:01:10.86 (134ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:10.86&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:10.86 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when An snapshot of push event is created checks if all of the integrationPipelineRuns created by push event passed [integration-service, slow]" classname="Red Hat App Studio E2E tests" status="passed" time="20.136096294">
              <system-err>&gt; Enter [It] checks if all of the integrationPipelineRuns created by push event passed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:218 @ 04/24/26 06:01:10.861&#xA;Integration test scenario my-integration-test-ahod is found&#xA;PipelineRun my-integration-test-ahod-tndhb reason: &#xA;PipelineRun my-integration-test-ahod-tndhb reason: Succeeded&#xA;&lt; Exit [It] checks if all of the integrationPipelineRuns created by push event passed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:218 @ 04/24/26 06:01:30.996 (20.136s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:30.997&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:30.997 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when An snapshot of push event is created checks if a Release is created successfully [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="6.083496923">
              <system-err>&gt; Enter [It] checks if a Release is created successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:222 @ 04/24/26 06:01:30.997&#xA;&lt; Exit [It] checks if a Release is created successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:222 @ 04/24/26 06:01:31.065 (67ms)&#xA;&gt; Enter [AfterAll] with happy path for general flow of Integration service - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:68 @ 04/24/26 06:01:31.065&#xA;&lt; Exit [AfterAll] with happy path for general flow of Integration service - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:68 @ 04/24/26 06:01:37.08 (6.015s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:37.081&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:01:37.081 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail triggers a build PipelineRun [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="213.402638373">
              <system-err>&gt; Enter [BeforeAll] with an integration test fail - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:234 @ 04/24/26 06:01:37.082&#xA;Image repository for component test-component-pac-mszoyb in namespace integration2-mmmw do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [BeforeAll] with an integration test fail - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:234 @ 04/24/26 06:01:49.912 (12.83s)&#xA;&gt; Enter [It] triggers a build PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:266 @ 04/24/26 06:01:49.912&#xA;no pipelinerun found for component test-component-pac-mszoyb (application: integ-app-miju, namespace: integration2-mmmw)PipelineRun test-component-pac-mszoyb-on-pull-request-m8569 found for Component integration2-mmmw/test-component-pac-mszoyb&#xA;PipelineRun test-component-pac-mszoyb-on-pull-request-m8569 reason: Running&#xA;PipelineRun test-component-pac-mszoyb-on-pull-request-m8569 reason: Running&#xA;PipelineRun test-component-pac-mszoyb-on-pull-request-m8569 reason: Running&#xA;PipelineRun test-component-pac-mszoyb-on-pull-request-m8569 reason: Running&#xA;PipelineRun test-component-pac-mszoyb-on-pull-request-m8569 reason: Running&#xA;PipelineRun test-component-pac-mszoyb-on-pull-request-m8569 reason: Running&#xA;PipelineRun test-component-pac-mszoyb-on-pull-request-m8569 reason: Running&#xA;PipelineRun test-component-pac-mszoyb-on-pull-request-m8569 reason: Running&#xA;PipelineRun test-component-pac-mszoyb-on-pull-request-m8569 reason: Running&#xA;PipelineRun test-component-pac-mszoyb-on-pull-request-m8569 reason: Completed&#xA;&lt; Exit [It] triggers a build PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:266 @ 04/24/26 06:05:10.484 (3m20.571s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:10.484&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:10.484 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail should have a related PaC init PR created [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.707108297">
              <system-err>&gt; Enter [It] should have a related PaC init PR created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:273 @ 04/24/26 06:05:10.485&#xA;&lt; Exit [It] should have a related PaC init PR created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:273 @ 04/24/26 06:05:11.191 (707ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:11.192&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:11.192 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail checks if the BuildPipelineRun have the annotation of chains signed [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.141932533">
              <system-err>&gt; Enter [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:292 @ 04/24/26 06:05:11.192&#xA;&lt; Exit [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:292 @ 04/24/26 06:05:11.334 (142ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:11.334&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:11.334 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail checks if the Snapshot is created [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.068166034">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:296 @ 04/24/26 06:05:11.335&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:296 @ 04/24/26 06:05:11.402 (68ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:11.403&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:11.403 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail checks if the Build PipelineRun got annotated with Snapshot name [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.229827314">
              <system-err>&gt; Enter [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:301 @ 04/24/26 06:05:11.403&#xA;&lt; Exit [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:301 @ 04/24/26 06:05:11.633 (229ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:11.633&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:11.633 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail checks if all of the integrationPipelineRuns finished [integration-service, slow]" classname="Red Hat App Studio E2E tests" status="passed" time="20.202759102">
              <system-err>&gt; Enter [It] checks if all of the integrationPipelineRuns finished - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:305 @ 04/24/26 06:05:11.634&#xA;Integration test scenario my-integration-test-sgsc is found&#xA;PipelineRun my-integration-test-sgsc-ghhfr reason: ResolvingPipelineRef&#xA;PipelineRun my-integration-test-sgsc-ghhfr reason: Succeeded&#xA;&lt; Exit [It] checks if all of the integrationPipelineRuns finished - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:305 @ 04/24/26 06:05:31.836 (20.202s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:31.836&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:31.836 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail checks if the failed status of integration test is reported in the Snapshot [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.069310537">
              <system-err>&gt; Enter [It] checks if the failed status of integration test is reported in the Snapshot - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:309 @ 04/24/26 06:05:31.837&#xA;&lt; Exit [It] checks if the failed status of integration test is reported in the Snapshot - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:309 @ 04/24/26 06:05:31.906 (69ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:31.906&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:31.906 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail checks if the skipped integration test is absent from the Snapshot&#39;s status annotation [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.06905128">
              <system-err>&gt; Enter [It] checks if the skipped integration test is absent from the Snapshot&#39;s status annotation - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:324 @ 04/24/26 06:05:31.906&#xA;&lt; Exit [It] checks if the skipped integration test is absent from the Snapshot&#39;s status annotation - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:324 @ 04/24/26 06:05:31.975 (69ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:31.975&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:31.975 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail checks if snapshot is marked as failed [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.068243606">
              <system-err>&gt; Enter [It] checks if snapshot is marked as failed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:334 @ 04/24/26 06:05:31.976&#xA;&lt; Exit [It] checks if snapshot is marked as failed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:334 @ 04/24/26 06:05:32.044 (68ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:32.044&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:32.044 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail checks if the finalizer was removed from all of the related Integration pipelineRuns [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.134813453">
              <system-err>&gt; Enter [It] checks if the finalizer was removed from all of the related Integration pipelineRuns - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:340 @ 04/24/26 06:05:32.045&#xA;Integration test scenario my-integration-test-sgsc is found&#xA;&lt; Exit [It] checks if the finalizer was removed from all of the related Integration pipelineRuns - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:340 @ 04/24/26 06:05:32.179 (134ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:32.179&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:32.179 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail creates a new IntegrationTestScenario [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.077062925">
              <system-err>&gt; Enter [It] creates a new IntegrationTestScenario - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:344 @ 04/24/26 06:05:32.18&#xA;&lt; Exit [It] creates a new IntegrationTestScenario - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:344 @ 04/24/26 06:05:32.256 (77ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:32.257&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:32.257 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail updates the Snapshot with the re-run label for the new scenario [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.076644452">
              <system-err>&gt; Enter [It] updates the Snapshot with the re-run label for the new scenario - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:349 @ 04/24/26 06:05:32.257&#xA;&lt; Exit [It] updates the Snapshot with the re-run label for the new scenario - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:349 @ 04/24/26 06:05:32.333 (76ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:32.334&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:32.334 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail when An snapshot is updated with a re-run label for a given scenario checks if the new integration pipelineRun started [integration-service, slow]" classname="Red Hat App Studio E2E tests" status="passed" time="20.136770855">
              <system-err>&gt; Enter [It] checks if the new integration pipelineRun started - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:358 @ 04/24/26 06:05:32.334&#xA;pipelinerun %s/%s hasn&#39;t started yet integration2-mmmw my-integration-test-uxqi-f4266&#xA;&lt; Exit [It] checks if the new integration pipelineRun started - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:358 @ 04/24/26 06:05:52.471 (20.136s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:52.471&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:52.471 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail when An snapshot is updated with a re-run label for a given scenario checks if the re-run label was removed from the Snapshot [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.068298586">
              <system-err>&gt; Enter [It] checks if the re-run label was removed from the Snapshot - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:364 @ 04/24/26 06:05:52.471&#xA;&lt; Exit [It] checks if the re-run label was removed from the Snapshot - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:364 @ 04/24/26 06:05:52.539 (68ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:52.54&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:52.54 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail when An snapshot is updated with a re-run label for a given scenario checks if all integration pipelineRuns finished successfully [integration-service, slow]" classname="Red Hat App Studio E2E tests" status="passed" time="0.23650977">
              <system-err>&gt; Enter [It] checks if all integration pipelineRuns finished successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:378 @ 04/24/26 06:05:52.54&#xA;Integration test scenario my-integration-test-sgsc is found&#xA;PipelineRun my-integration-test-sgsc-ghhfr reason: Succeeded&#xA;Integration test scenario my-integration-test-uxqi is found&#xA;PipelineRun my-integration-test-uxqi-f4266 reason: Succeeded&#xA;&lt; Exit [It] checks if all integration pipelineRuns finished successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:378 @ 04/24/26 06:05:52.776 (236ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:52.777&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:52.777 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail when An snapshot is updated with a re-run label for a given scenario checks if the name of the re-triggered pipelinerun is reported in the Snapshot [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.136646492">
              <system-err>&gt; Enter [It] checks if the name of the re-triggered pipelinerun is reported in the Snapshot - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:382 @ 04/24/26 06:05:52.777&#xA;&lt; Exit [It] checks if the name of the re-triggered pipelinerun is reported in the Snapshot - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:382 @ 04/24/26 06:05:52.913 (136ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:52.914&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:52.914 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail when An snapshot is updated with a re-run label for a given scenario checks if snapshot is still marked as failed [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.068554014">
              <system-err>&gt; Enter [It] checks if snapshot is still marked as failed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:399 @ 04/24/26 06:05:52.914&#xA;&lt; Exit [It] checks if snapshot is still marked as failed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:399 @ 04/24/26 06:05:52.982 (68ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:52.982&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:52.982 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail creates an snapshot of push event [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.070824579">
              <system-err>&gt; Enter [It] creates an snapshot of push event - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:406 @ 04/24/26 06:05:52.983&#xA;&lt; Exit [It] creates an snapshot of push event - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:406 @ 04/24/26 06:05:53.053 (70ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:53.054&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:53.054 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail when An snapshot of push event is created checks no Release CRs are created [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="2.764781926">
              <system-err>&gt; Enter [It] checks no Release CRs are created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:413 @ 04/24/26 06:05:53.054&#xA;&lt; Exit [It] checks no Release CRs are created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:413 @ 04/24/26 06:05:53.121 (67ms)&#xA;&gt; Enter [AfterAll] with an integration test fail - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:250 @ 04/24/26 06:05:53.121&#xA;&lt; Exit [AfterAll] with an integration test fail - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:250 @ 04/24/26 06:05:55.818 (2.697s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:55.819&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/integration.go:49 @ 04/24/26 06:05:55.819 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when creating tenants and running initial pipelines should create both tenants concurrently [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when creating tenants and running initial pipelines should wait for all build PipelineRuns to succeed [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when backing up tenant data should create backup CRs for both tenants concurrently [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when simulating disaster by deleting namespaces should delete both tenant namespaces [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when restoring from backup should restore tenant-1 (KokoHazamar) via velero CLI method [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when restoring from backup should restore tenant-2 (MosheKipod) via oc command method [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when performing post-restore recovery should rotate SA tokens on both tenants [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when verifying restored tenants should confirm structural integrity of both tenants [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when verifying restored tenants should confirm functional pipeline execution after restore [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when creating tenants on the old Konflux version should create both tenants concurrently [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when creating tenants on the old Konflux version should wait for all build PipelineRuns to succeed [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when backing up tenant data before upgrade should create backup CRs for both tenants concurrently [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when simulating disaster by deleting namespaces should delete both tenant namespaces [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when upgrading Konflux to the new version should upgrade the cluster and verify Velero survived [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when restoring tenants from backup on the new Konflux version should restore tenant-1 (KokoHazamar) via velero CLI method [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when restoring tenants from backup on the new Konflux version should restore tenant-2 (MosheKipod) via oc command method [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when performing post-restore recovery should rotate SA tokens on both tenants [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when verifying restored tenants should confirm structural integrity of both tenants [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when verifying restored tenants should confirm functional pipeline execution after restore [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rhtap-service-push pipeline] Rhtap-service-push happy path Post-release verification verifies if the release CR is created [release-pipelines, rhtap-service-push, RhtapServicePush]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rhtap-service-push pipeline] Rhtap-service-push happy path Post-release verification verifies the rhtap release pipelinerun is running and succeeds [release-pipelines, rhtap-service-push, RhtapServicePush]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rhtap-service-push pipeline] Rhtap-service-push happy path Post-release verification verifies release CR completed and set succeeded. [release-pipelines, rhtap-service-push, RhtapServicePush]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rhtap-service-push pipeline] Rhtap-service-push happy path Post-release verification verifies if the PR in infra-deployments repo is created/updated [release-pipelines, rhtap-service-push, RhtapServicePush]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build annotations when component is created with invalid build request annotations handles invalid request annotation [build-service, github, annotations]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite Push to external registry] Post-release verification verifies that a Release CR should have been created in the dev namespace [release-pipelines, push-to-external-registry]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite Push to external registry] Post-release verification verifies that Release PipelineRun should eventually succeed [release-pipelines, push-to-external-registry]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite Push to external registry] Post-release verification tests if the image was pushed to quay [release-pipelines, push-to-external-registry]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite Push to external registry] Post-release verification verifies that a Release is marked as succeeded. [release-pipelines, push-to-external-registry]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [upgrade-suite Create users and check their state] Verify AppStudioProvisionedUser [upgrade-verify]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [upgrade-suite Create users and check their state] creates AppStudioDeactivatedUser [upgrade-verify]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [upgrade-suite Create users and check their state] creates AppStudioBannedUser [upgrade-verify]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for release-to-github pipeline] Release-to-github happy path Post-release verification verifies if release CR is created [release-pipelines, release-to-github, releaseToGithub]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for release-to-github pipeline] Release-to-github happy path Post-release verification verifies the release pipelinerun is running and succeeds [release-pipelines, release-to-github, releaseToGithub]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for release-to-github pipeline] Release-to-github happy path Post-release verification verifies release CR completed and set succeeded. [release-pipelines, release-to-github, releaseToGithub]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for release-to-github pipeline] Release-to-github happy path Post-release verification verifies if the Release exists in github repo [release-pipelines, release-to-github, releaseToGithub]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws host-pool allocation when the Component with multi-platform-build is created a PipelineRun is triggered [multi-platform, aws-host-pool]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws host-pool allocation when the Component with multi-platform-build is created the build-container task from component pipelinerun is buildah-remote [multi-platform, aws-host-pool]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws host-pool allocation when the Component with multi-platform-build is created The multi platform secret is populated [multi-platform, aws-host-pool]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws host-pool allocation when the Component with multi-platform-build is created that PipelineRun completes successfully [multi-platform, aws-host-pool]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws host-pool allocation when the Component with multi-platform-build is created test that cleanup happened successfully [multi-platform, aws-host-pool]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws dynamic allocation when the Component with multi-platform-build is created a PipelineRun is triggered [multi-platform, aws-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws dynamic allocation when the Component with multi-platform-build is created the build-container task from component pipelinerun is buildah-remote [multi-platform, aws-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws dynamic allocation when the Component with multi-platform-build is created The multi platform secret is populated [multi-platform, aws-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws dynamic allocation when the Component with multi-platform-build is created that PipelineRun completes successfully [multi-platform, aws-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws dynamic allocation when the Component with multi-platform-build is created check cleanup happened successfully [multi-platform, aws-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm system z dynamic allocation when the Component with multi-platform-build is created a PipelineRun is triggered [multi-platform, ibmz-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm system z dynamic allocation when the Component with multi-platform-build is created the build-container task from component pipelinerun is buildah-remote [multi-platform, ibmz-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm system z dynamic allocation when the Component with multi-platform-build is created The multi platform secret is populated [multi-platform, ibmz-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm system z dynamic allocation when the Component with multi-platform-build is created that PipelineRun completes successfully [multi-platform, ibmz-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm system z dynamic allocation when the Component with multi-platform-build is created check cleanup happened successfully [multi-platform, ibmz-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm power pc dynamic allocation when the Component with multi-platform-build is created a PipelineRun is triggered [multi-platform, ibmp-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm power pc dynamic allocation when the Component with multi-platform-build is created the build-container task from component pipelinerun is buildah-remote [multi-platform, ibmp-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm power pc dynamic allocation when the Component with multi-platform-build is created The multi platform secret is populated [multi-platform, ibmp-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm power pc dynamic allocation when the Component with multi-platform-build is created that PipelineRun completes successfully [multi-platform, ibmp-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm power pc dynamic allocation when the Component with multi-platform-build is created check cleanup happened successfully [multi-platform, ibmp-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created creates first component [build-service, github, pac-build, secret-lookup]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created creates second component [build-service, github, pac-build, secret-lookup]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created check first component annotation has errors [build-service, github, pac-build, secret-lookup]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created triggered PipelineRun is for component  [build-service, github, pac-build, secret-lookup]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created check only one pipelinerun should be triggered [build-service, github, pac-build, secret-lookup]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created when second component is deleted, pac pr branch should not exist in the repo [build-service, github, pac-build, secret-lookup]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rh-push-to-redhat-io pipeline] Rh-push-to-redhat-io happy path Post-release verification verifies if the release CR is created [release-pipelines, rh-push-to-registry-redhat-io, PushToRedhatIO]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rh-push-to-redhat-io pipeline] Rh-push-to-redhat-io happy path Post-release verification verifies the rhio release pipelinerun is running and succeeds [release-pipelines, rh-push-to-registry-redhat-io, PushToRedhatIO]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rh-push-to-redhat-io pipeline] Rh-push-to-redhat-io happy path Post-release verification verifies release CR completed and set succeeded. [release-pipelines, rh-push-to-registry-redhat-io, PushToRedhatIO]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rh-push-to-redhat-io pipeline] Rh-push-to-redhat-io happy path Post-release verification verifies if the MR URL is valid [release-pipelines, rh-push-to-registry-redhat-io, PushToRedhatIO]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite [RELEASE-2136] Release CR fails when block-releases true in ReleasePlanAdmission.] post-release verification. block-releases true in ReleasePlanAdmission makes a Release CR set as failed in both IsReleased and IsValid with a proper message to user. [release-service, release-neg, negBlockReleases]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] infrastructure is running verifies if the chains controller is running [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] infrastructure is running verifies the signing secret is present [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task creates signature and attestation [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task succeeds when policy is met [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task does not pass when tests are not satisfied on non-strict mode [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task fails when tests are not satisfied on strict mode [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task fails when unexpected signature is used [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task ec-cli command verifies ec cli has error handling [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task ec-cli command verifies ec validate accepts a list of image references [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task Release Policy verifies redhat products pass the redhat policy rule collection before release  [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task Release Policy verifies the release policy: Task are trusted [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task Release Policy verifies the release policy: Task references are pinned [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite [HACBS-1571]test-release-e2e-push-image-to-pyxis] Post-release verification tests that Release CR is created for the Snapshot [release-pipelines, rh-push-to-external-registry]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite [HACBS-1571]test-release-e2e-push-image-to-pyxis] Post-release verification verifies a release PipelineRun is started and succeeded in managed namespace [release-pipelines, rh-push-to-external-registry]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite [HACBS-1571]test-release-e2e-push-image-to-pyxis] Post-release verification validate the result of task create-pyxis-image contains image ids [release-pipelines, rh-push-to-external-registry]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite [HACBS-1571]test-release-e2e-push-image-to-pyxis] Post-release verification tests that Release CR has completed [release-pipelines, rh-push-to-external-registry]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite [HACBS-1571]test-release-e2e-push-image-to-pyxis] Post-release verification validates that imageIds from task create-pyxis-image exist in Pyxis. [release-pipelines, rh-push-to-external-registry]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification verifies that the ReleasePlan CR is unmatched in the beginning [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification Creates ReleasePlanAdmission CR in corresponding managed namespace [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification when ReleasePlanAdmission CR is created in managed namespace verifies that the ReleasePlan CR is set to matched [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification when ReleasePlanAdmission CR is created in managed namespace verifies that the ReleasePlanAdmission CR is set to matched [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification Creates a manual release ReleasePlan CR in devNamespace [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification when the second ReleasePlan CR is created verifies that the second ReleasePlan CR is set to matched [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification when the second ReleasePlan CR is created verifies that the ReleasePlanAdmission CR has two matched ReleasePlan CRs [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification deletes one ReleasePlan CR [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification when One ReleasePlan CR is deleted in managed namespace verifies that the ReleasePlanAdmission CR has only one matching ReleasePlan [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification deletes the ReleasePlanAdmission CR [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification when ReleasePlanAdmission CR is deleted in managed namespace verifies that the ReleasePlan CR has no matched ReleasePlanAdmission [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build creates an application [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build creates an IntegrationTestScenario for the app [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build creates new branch for the build [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build creates component konflux-demo-component (private: false) from git source https://github.com/redhat-appstudio-qe/hacbs-test-project-konflux-demo [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Component is created triggers creation of a PR in the sample repo [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Component is created verifies component build status [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Component is created should eventually lead to triggering a &#39;push&#39; event type PipelineRun after merging the PaC init branch  [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun is created does not contain an annotation with a Snapshot Name [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun is created should eventually complete successfully [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun completes successfully should validate Tekton TaskRun test results successfully [konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun completes successfully should validate that the build pipelineRun is signed [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun completes successfully should find the related Snapshot CR [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun completes successfully should validate that the build pipelineRun is annotated with the name of the Snapshot [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun completes successfully should find the related Integration Test PipelineRun [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when push pipelinerun is retriggered should eventually succeed [konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Integration Test PipelineRun is created should eventually complete successfully [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Integration Test PipelineRun completes successfully should lead to Snapshot CR being marked as passed [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Integration Test PipelineRun completes successfully should trigger creation of Release CR [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Release CR is created triggers creation of Release PipelineRun [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Release PipelineRun is triggered should eventually succeed [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Release PipelineRun is completed should lead to Release CR being marked as succeeded [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace creates component with context directory go-component [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace triggers a PipelineRun for component go-component-rdnxhe [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace should lead to a PaC PR creation for component go-component-rdnxhe [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace the PipelineRun should eventually finish successfully for component go-component-rdnxhe [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace merging the PR should be successful [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace leads to triggering on push PipelineRun [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace creates component with context directory python-component [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace triggers a PipelineRun for component python-component-kiewxu [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace should lead to a PaC PR creation for component python-component-kiewxu [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace the PipelineRun should eventually finish successfully for component python-component-kiewxu [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace merging the PR should be successful [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace leads to triggering on push PipelineRun [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace only one component is changed [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace only related pipelinerun should be triggered [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when a components is created with same git url in different namespace should fail to configure PaC for the component [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite Release service tenant pipeline] Post-release verification verifies that a Release CR should have been created in the dev namespace [release-service, tenant]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite Release service tenant pipeline] Post-release verification verifies that Tenant PipelineRun is triggered [release-service, tenant]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite Release service tenant pipeline] Post-release verification verifies that a Release is marked as succeeded. [release-service, tenant]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [task-suite tkn bundle task] creates Tekton bundles with different params when context points to a file [build-templates]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [task-suite tkn bundle task] creates Tekton bundles with different params creates Tekton bundles from specific context [build-templates]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [task-suite tkn bundle task] creates Tekton bundles with different params when context is the root directory [build-templates]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [task-suite tkn bundle task] creates Tekton bundles with different params creates Tekton bundles when context points to a file and a directory [build-templates]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [task-suite tkn bundle task] creates Tekton bundles with different params creates Tekton bundles when using negation [build-templates]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [task-suite tkn bundle task] creates Tekton bundles with different params allows overriding HOME environment variable [build-templates]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [task-suite tkn bundle task] creates Tekton bundles with different params allows overriding STEP image [build-templates]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite Release service happy path] Post-release verification verifies that a Release CR should have been created in the dev namespace [release-service, happy-path]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite Release service happy path] Post-release verification verifies that Release PipelineRun is triggered [release-service, happy-path]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite Release service happy path] Post-release verification verifies that Enterprise Contract Task has succeeded in the Release PipelineRun [release-service, happy-path]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite Release service happy path] Post-release verification verifies that a Release is marked as succeeded. [release-service, happy-path]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for multi arch with rh-advisories pipeline] Multi arch test happy path Post-release verification verifies the release CR is created [release-pipelines, rh-advisories, multiarch-advisories, multiArchAdvisories]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for multi arch with rh-advisories pipeline] Multi arch test happy path Post-release verification verifies the multiarch release pipelinerun is running and succeeds [release-pipelines, rh-advisories, multiarch-advisories, multiArchAdvisories]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for multi arch with rh-advisories pipeline] Multi arch test happy path Post-release verification verifies release CR completed and set succeeded. [release-pipelines, rh-advisories, multiarch-advisories, multiArchAdvisories]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for multi arch with rh-advisories pipeline] Multi arch test happy path Post-release verification verifies if the repository URL is valid [release-pipelines, rh-advisories, multiarch-advisories, multiArchAdvisories]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC happy path Post-release verification creates component from git source https://github.com/redhat-appstudio-qe/fbc-sample-repo-test [release-pipelines, fbc-release, fbcHappyPath]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC happy path Post-release verification Creates a push snapshot for a release [release-pipelines, fbc-release, fbcHappyPath]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC happy path Post-release verification verifies the fbc release pipelinerun is running and succeeds [release-pipelines, fbc-release, fbcHappyPath]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC happy path Post-release verification verifies release CR completed and set succeeded. [release-pipelines, fbc-release, fbcHappyPath]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC Staged Index Post-release verification creates component from git source https://github.com/redhat-appstudio-qe/fbc-sample-repo-test [release-pipelines, fbc-release, fbcStagedIndex]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC Staged Index Post-release verification Creates a push snapshot for a release [release-pipelines, fbc-release, fbcStagedIndex]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC Staged Index Post-release verification verifies the fbc release pipelinerun is running and succeeds [release-pipelines, fbc-release, fbcStagedIndex]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC Staged Index Post-release verification verifies release CR completed and set succeeded. [release-pipelines, fbc-release, fbcStagedIndex]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC hotfix process FBC hotfix post-release verification creates component from git source https://github.com/redhat-appstudio-qe/fbc-sample-repo-test [release-pipelines, fbc-release, fbcHotfix]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC hotfix process FBC hotfix post-release verification Creates a push snapshot for a release [release-pipelines, fbc-release, fbcHotfix]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC hotfix process FBC hotfix post-release verification verifies the fbc release pipelinerun is running and succeeds [release-pipelines, fbc-release, fbcHotfix]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC hotfix process FBC hotfix post-release verification verifies release CR completed and set succeeded. [release-pipelines, fbc-release, fbcHotfix]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC pre-GA process FBC pre-GA post-release verification creates component from git source https://github.com/redhat-appstudio-qe/fbc-sample-repo-test [release-pipelines, fbc-release, fbcPreGA]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC pre-GA process FBC pre-GA post-release verification Creates a push snapshot for a release [release-pipelines, fbc-release, fbcPreGA]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC pre-GA process FBC pre-GA post-release verification verifies the fbc release pipelinerun is running and succeeds [release-pipelines, fbc-release, fbcPreGA]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC pre-GA process FBC pre-GA post-release verification verifies release CR completed and set succeeded. [release-pipelines, fbc-release, fbcPreGA]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace creates component with nudges [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace triggers a PipelineRun for parent component  [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for parent component  [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for child component  [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace should lead to a PaC PR creation for child component  [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace Merging the PaC PR should be successful for child component  [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace create dockerfile and yaml manifest that references build and distribution repositories [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace should lead to a PaC PR creation for parent component  [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace Merging the PaC PR should be successful for parent component  [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace PR merge triggers PAC PipelineRun for parent component  [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace PAC PipelineRun for parent component  is successful [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace should lead to a nudge PR creation for child component  [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace merging the PR should be successful for child component  [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace Verify the nudge updated the contents [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] post-release verification. missing ReleasePlan makes a Release CR set as failed in both IsReleased and IsValid with a proper message to user. [release-service, release-neg, negMissingReleasePlan]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] post-release verification. missing ReleasePlanAdmission makes a Release CR set as failed in both IsReleased and IsValid with a proper message to user. [release-service, release-neg, negMissingReleasePlan]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace creates component with nudges [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace triggers a PipelineRun for parent component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for parent component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for child component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace should lead to a PaC PR creation for child component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace Merging the PaC PR should be successful for child component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace create dockerfile and yaml manifest that references build and distribution repositories [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace should lead to a PaC PR creation for parent component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace Merging the PaC PR should be successful for parent component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace PR merge triggers PAC PipelineRun for parent component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace PAC PipelineRun for parent component  is successful [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace should lead to a nudge PR creation for child component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace merging the PR should be successful for child component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace Verify the nudge updated the contents [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines triggers PipelineRun for symlink component with source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic with component name test-symlink-comp-lkih [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci triggers PipelineRun for component with source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci triggers PipelineRun for component with source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci triggers PipelineRun for component with source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta-min [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) should eventually finish successfully for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) should push Dockerfile to registry [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) floating tags are created successfully [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) image manifest mediaType is correct [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) check for source images if enabled in pipeline [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) when Pipeline Results are stored for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build should have Pipeline Records [build, build-templates, HACBS, pipeline-service, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) when Pipeline Results are stored for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build should have Pipeline Logs [build, build-templates, HACBS, pipeline-service, pipeline]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) should validate tekton taskrun test results for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry verify-enterprise-contract check should pass [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry should have Hermeto content in the SBOM in case the build was hermetic [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) build-definitions ec pipelines runs ec pipeline pipelines/enterprise-contract.yaml [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) should eventually finish successfully for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) should push Dockerfile to registry [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) floating tags are created successfully [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) image manifest mediaType is correct [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) check for source images if enabled in pipeline [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) when Pipeline Results are stored for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta should have Pipeline Records [build, build-templates, HACBS, pipeline-service, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) when Pipeline Results are stored for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta should have Pipeline Logs [build, build-templates, HACBS, pipeline-service, pipeline]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) should validate tekton taskrun test results for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry verify-enterprise-contract check should pass [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry should have Hermeto content in the SBOM in case the build was hermetic [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) build-definitions ec pipelines runs ec pipeline pipelines/enterprise-contract.yaml [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) should eventually finish successfully for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta-min [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) should push Dockerfile to registry [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) floating tags are created successfully [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) image manifest mediaType is correct [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) check for source images if enabled in pipeline [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) when Pipeline Results are stored for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta-min should have Pipeline Records [build, build-templates, HACBS, pipeline-service, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) when Pipeline Results are stored for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta-min should have Pipeline Logs [build, build-templates, HACBS, pipeline-service, pipeline]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) should validate tekton taskrun test results for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta-min [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry verify-enterprise-contract check should pass [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry should have Hermeto content in the SBOM in case the build was hermetic [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) build-definitions ec pipelines runs ec pipeline pipelines/enterprise-contract.yaml [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines pipelineRun should fail for symlink component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic with component name test-symlink-comp-lkih [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace creates component with nudges [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace triggers a PipelineRun for parent component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for parent component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for child component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace should lead to a PaC PR creation for child component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace Merging the PaC PR should be successful for child component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace create dockerfile and yaml manifest that references build and distribution repositories [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace should lead to a PaC PR creation for parent component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace Merging the PaC PR should be successful for parent component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace PR merge triggers PAC PipelineRun for parent component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace PAC PipelineRun for parent component  is successful [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace should lead to a nudge PR creation for child component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace merging the PR should be successful for child component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace Verify the nudge updated the contents [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private correctly targets the default branch (that is not named &#39;main&#39;) with PaC [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private workspace parameter is set correctly in PaC repository CR [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private build pipeline uses the correct serviceAccount [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private component build status is set correctly [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private created image repo is private [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private a related PipelineRun should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private PR branch should not exist in the repo [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private related image repo and the robot account should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created should lead to a PaC init PR creation [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created created image repo is public [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created image tag is updated successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created should ensure pruning labels are set [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created eventually leads to the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated should lead to a PaC init PR update [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated PipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated eventually leads to another update of a PR about the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged does not have expiration set [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged After updating image visibility to private, it should not trigger another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged image repo is updated to private [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged retrigger the pipeline manually [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged retriggered pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the component is removed and recreated (with the same name in the same namespace) should no longer lead to a creation of a PaC PR [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private correctly targets the default branch (that is not named &#39;main&#39;) with PaC [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private workspace parameter is set correctly in PaC repository CR [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private build pipeline uses the correct serviceAccount [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private component build status is set correctly [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private created image repo is private [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private a related PipelineRun should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private PR branch should not exist in the repo [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private related image repo and the robot account should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created should lead to a PaC init PR creation [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created created image repo is public [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created image tag is updated successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created should ensure pruning labels are set [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created eventually leads to the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated should lead to a PaC init PR update [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated PipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated eventually leads to another update of a PR about the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged does not have expiration set [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged After updating image visibility to private, it should not trigger another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged image repo is updated to private [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged retrigger the pipeline manually [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged retriggered pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the component is removed and recreated (with the same name in the same namespace) should no longer lead to a creation of a PaC PR [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private correctly targets the default branch (that is not named &#39;main&#39;) with PaC [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private workspace parameter is set correctly in PaC repository CR [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private build pipeline uses the correct serviceAccount [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private component build status is set correctly [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private created image repo is private [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private a related PipelineRun should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private PR branch should not exist in the repo [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private related image repo and the robot account should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created should lead to a PaC init PR creation [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created created image repo is public [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created image tag is updated successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created should ensure pruning labels are set [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created eventually leads to the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is updated eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is updated should lead to a PaC init PR update [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is updated PipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is updated eventually leads to another update of a PR about the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged does not have expiration set [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged After updating image visibility to private, it should not trigger another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged image repo is updated to private [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged retrigger the pipeline manually [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged retriggered pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the component is removed and recreated (with the same name in the same namespace) should no longer lead to a creation of a PaC PR [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when a new Component with specified custom branch is created triggers a Build PipelineRun [integration-service, gitlab-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="43.253583663">
              <system-err>&gt; Enter [BeforeAll] Gitlab with status reporting of Integration tests in the assosiated merge request - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:45 @ 04/24/26 05:45:35.933&#xA;&lt; Exit [BeforeAll] Gitlab with status reporting of Integration tests in the assosiated merge request - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:45 @ 04/24/26 05:45:38.838 (2.905s)&#xA;&gt; Enter [BeforeAll] when a new Component with specified custom branch is created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:109 @ 04/24/26 05:45:38.838&#xA;Image repository for component test-comp-pac-gitlab-pqdipz in namespace gitlab-rep-nwvy do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component test-comp-pac-gitlab-pqdipz in namespace gitlab-rep-nwvy do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [BeforeAll] when a new Component with specified custom branch is created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:109 @ 04/24/26 05:45:58.98 (20.142s)&#xA;&gt; Enter [It] triggers a Build PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:130 @ 04/24/26 05:45:58.98&#xA;Build PipelineRun has not been created yet for the component gitlab-rep-nwvy/test-comp-pac-gitlab-pqdipz&#xA;&lt; Exit [It] triggers a Build PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:130 @ 04/24/26 05:46:19.186 (20.206s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 05:46:19.186&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 05:46:19.186 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when a new Component with specified custom branch is created does not contain an annotation with a Snapshot Name [integration-service, gitlab-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.000372111">
              <system-err>&gt; Enter [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:144 @ 04/24/26 05:46:19.187&#xA;&lt; Exit [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:144 @ 04/24/26 05:46:19.187 (0s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 05:46:19.187&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 05:46:19.187 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when a new Component with specified custom branch is created should lead to build PipelineRun finishing successfully [integration-service, gitlab-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="820.139895975">
              <system-err>&gt; Enter [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:148 @ 04/24/26 05:46:19.188&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt found for Component gitlab-rep-nwvy/test-comp-pac-gitlab-pqdipz&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: ResolvingTaskRef&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: ResolvingTaskRef&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Running&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Completed&#xA;&lt; Exit [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:148 @ 04/24/26 05:59:59.327 (13m40.139s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 05:59:59.327&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 05:59:59.327 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when a new Component with specified custom branch is created should have a related PaC init MR is created [integration-service, gitlab-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.445971306">
              <system-err>&gt; Enter [It] should have a related PaC init MR is created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:153 @ 04/24/26 05:59:59.328&#xA;&lt; Exit [It] should have a related PaC init MR is created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:153 @ 04/24/26 05:59:59.774 (446ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 05:59:59.774&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 05:59:59.774 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when a new Component with specified custom branch is created the PipelineRun should eventually finish successfully for component  [integration-service, gitlab-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.070937695">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for component  - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:172 @ 04/24/26 05:59:59.775&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt found for Component gitlab-rep-nwvy/test-comp-pac-gitlab-pqdipz&#xA;PipelineRun test-comp-pac-gitlab-pqdipz-on-pull-request-6nwwt reason: Completed&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for component  - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:172 @ 04/24/26 05:59:59.845 (71ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 05:59:59.845&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 05:59:59.845 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when the PaC build pipelineRun run succeeded checks if the BuildPipelineRun have the annotation of chains signed [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.144767705">
              <system-err>&gt; Enter [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:179 @ 04/24/26 05:59:59.846&#xA;&lt; Exit [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:179 @ 04/24/26 05:59:59.99 (144ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 05:59:59.991&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 05:59:59.991 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when the PaC build pipelineRun run succeeded checks if the Snapshot is created [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.069277527">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:183 @ 04/24/26 05:59:59.991&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:183 @ 04/24/26 06:00:00.06 (69ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:00:00.06&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:00:00.06 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when the PaC build pipelineRun run succeeded checks if the Build PipelineRun got annotated with Snapshot name [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.155388685">
              <system-err>&gt; Enter [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:188 @ 04/24/26 06:00:00.061&#xA;&lt; Exit [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:188 @ 04/24/26 06:00:00.216 (155ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:00:00.216&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:00:00.216 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when the Snapshot was created should find the Integration Test Scenario PipelineRun [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.079738022">
              <system-err>&gt; Enter [It] should find the Integration Test Scenario PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:194 @ 04/24/26 06:00:00.217&#xA;&lt; Exit [It] should find the Integration Test Scenario PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:194 @ 04/24/26 06:00:00.296 (79ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:00:00.296&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:00:00.296 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Integration PipelineRun is created should eventually complete successfully [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="60.20463809">
              <system-err>&gt; Enter [It] should eventually complete successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:207 @ 04/24/26 06:00:00.297&#xA;PipelineRun my-integration-test-wjmn-2t6lm reason: ResolvingPipelineRef&#xA;PipelineRun my-integration-test-wjmn-2t6lm reason: Running&#xA;PipelineRun my-integration-test-wjmn-2t6lm reason: Running&#xA;PipelineRun my-integration-test-wjmn-2t6lm reason: Succeeded&#xA;PipelineRun my-integration-test-etqu-gl9wr reason: Succeeded&#xA;&lt; Exit [It] should eventually complete successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:207 @ 04/24/26 06:01:00.501 (1m0.204s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:00.501&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:00.501 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Integration PipelineRun is created validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it pass [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.141469894">
              <system-err>&gt; Enter [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it pass - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:212 @ 04/24/26 06:01:00.502&#xA;&lt; Exit [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it pass - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:212 @ 04/24/26 06:01:00.643 (141ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:00.643&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:00.643 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Integration PipelineRun is created eventually leads to the integration test PipelineRun&#39;s Pass status reported at MR commit status [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.342474626">
              <system-err>&gt; Enter [It] eventually leads to the integration test PipelineRun&#39;s Pass status reported at MR commit status - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:229 @ 04/24/26 06:01:00.644&#xA;&lt; Exit [It] eventually leads to the integration test PipelineRun&#39;s Pass status reported at MR commit status - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:229 @ 04/24/26 06:01:00.986 (342ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:00.986&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:00.986 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Integration PipelineRun is created validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it fails [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.138497305">
              <system-err>&gt; Enter [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it fails - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:233 @ 04/24/26 06:01:00.987&#xA;&lt; Exit [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it fails - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:233 @ 04/24/26 06:01:01.125 (138ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:01.125&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:01.125 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Integration PipelineRun is created eventually leads to the integration test PipelineRun&#39;s Fail status reported at MR commit status [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.34969619">
              <system-err>&gt; Enter [It] eventually leads to the integration test PipelineRun&#39;s Fail status reported at MR commit status - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:250 @ 04/24/26 06:01:01.125&#xA;&lt; Exit [It] eventually leads to the integration test PipelineRun&#39;s Fail status reported at MR commit status - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:250 @ 04/24/26 06:01:01.475 (349ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:01.475&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:01.475 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Integration PipelineRun is created validates at least one MR note contains the final integration test result [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.166666622">
              <system-err>&gt; Enter [It] validates at least one MR note contains the final integration test result - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:254 @ 04/24/26 06:01:01.475&#xA;&lt; Exit [It] validates at least one MR note contains the final integration test result - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:254 @ 04/24/26 06:01:01.642 (166ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:01.642&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:01.642 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Integration PipelineRun is created merging the PR should be successful [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="1.337486541">
              <system-err>&gt; Enter [It] merging the PR should be successful - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:278 @ 04/24/26 06:01:01.642&#xA;merged result sha: bb46c1b56a2ed915d6212d215040f404ededcaec for MR #17419&#xA;&lt; Exit [It] merging the PR should be successful - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:278 @ 04/24/26 06:01:02.98 (1.337s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:02.98&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:02.98 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Integration PipelineRun is created leads to triggering on push PipelineRun [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.136708632">
              <system-err>&gt; Enter [It] leads to triggering on push PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:288 @ 04/24/26 06:01:02.98&#xA;&lt; Exit [It] leads to triggering on push PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:288 @ 04/24/26 06:01:03.117 (136ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:03.117&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:03.117 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Run integration tests after Merged MR should eventually complete successfully [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.136606339">
              <system-err>&gt; Enter [It] should eventually complete successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:303 @ 04/24/26 06:01:03.118&#xA;PipelineRun my-integration-test-wjmn-2t6lm reason: Succeeded&#xA;PipelineRun my-integration-test-etqu-gl9wr reason: Succeeded&#xA;&lt; Exit [It] should eventually complete successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:303 @ 04/24/26 06:01:03.254 (136ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:03.254&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:03.254 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Run integration tests after Merged MR validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it pass [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.145094411">
              <system-err>&gt; Enter [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it pass - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:308 @ 04/24/26 06:01:03.254&#xA;&lt; Exit [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it pass - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:308 @ 04/24/26 06:01:03.399 (145ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:03.399&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:03.399 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Run integration tests after Merged MR eventually leads to the integration test PipelineRun&#39;s Pass status reported at MR commit status [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.307188808">
              <system-err>&gt; Enter [It] eventually leads to the integration test PipelineRun&#39;s Pass status reported at MR commit status - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:325 @ 04/24/26 06:01:03.4&#xA;&lt; Exit [It] eventually leads to the integration test PipelineRun&#39;s Pass status reported at MR commit status - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:325 @ 04/24/26 06:01:03.707 (307ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:03.707&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:03.707 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Run integration tests after Merged MR validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it fails [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.147783291">
              <system-err>&gt; Enter [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it fails - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:329 @ 04/24/26 06:01:03.707&#xA;&lt; Exit [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it fails - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:329 @ 04/24/26 06:01:03.855 (147ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:03.855&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:03.855 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Run integration tests after Merged MR eventually leads to the integration test PipelineRun&#39;s Fail status reported at MR commit status [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="2.610362501">
              <system-err>&gt; Enter [It] eventually leads to the integration test PipelineRun&#39;s Fail status reported at MR commit status - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:346 @ 04/24/26 06:01:03.856&#xA;&lt; Exit [It] eventually leads to the integration test PipelineRun&#39;s Fail status reported at MR commit status - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:346 @ 04/24/26 06:01:04.234 (379ms)&#xA;&gt; Enter [AfterAll] Gitlab with status reporting of Integration tests in the assosiated merge request - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:94 @ 04/24/26 06:01:04.235&#xA;&lt; Exit [AfterAll] Gitlab with status reporting of Integration tests in the assosiated merge request - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:94 @ 04/24/26 06:01:06.465 (2.231s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:06.466&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/24/26 06:01:06.466 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when a new Component with specified custom branch is created does not contain an annotation with a Snapshot Name [integration-service, github-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="53.315248968">
              <system-err>&gt; Enter [BeforeAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:45 @ 04/24/26 05:45:36.031&#xA;Build PipelineRun has not been created yet for the component stat-rep-myzl/test-component-pac-svwack&#xA;Build PipelineRun has not been created yet for the component stat-rep-myzl/test-component-pac-svwack&#xA;&lt; Exit [BeforeAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:45 @ 04/24/26 05:46:29.343 (53.313s)&#xA;&gt; Enter [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:111 @ 04/24/26 05:46:29.344&#xA;&lt; Exit [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:111 @ 04/24/26 05:46:29.344 (0s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 05:46:29.344&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 05:46:29.344 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when a new Component with specified custom branch is created should have a related PaC init PR created [integration-service, github-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.531724">
              <system-err>&gt; Enter [It] should have a related PaC init PR created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:115 @ 04/24/26 05:46:29.344&#xA;&lt; Exit [It] should have a related PaC init PR created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:115 @ 04/24/26 05:46:29.876 (531ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 05:46:29.876&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 05:46:29.876 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when a new Component with specified custom branch is created initialized integration test status is reported to github [integration-service, github-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.744725849">
              <system-err>&gt; Enter [It] initialized integration test status is reported to github - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:134 @ 04/24/26 05:46:29.876&#xA;&lt; Exit [It] initialized integration test status is reported to github - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:134 @ 04/24/26 05:46:30.621 (744ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 05:46:30.621&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 05:46:30.621 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when a new Component with specified custom branch is created should lead to build PipelineRun finishing successfully [integration-service, github-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="820.136121073">
              <system-err>&gt; Enter [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:144 @ 04/24/26 05:46:30.622&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: ResolvingTaskRef&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Running&#xA;PipelineRun test-component-pac-svwack-on-pull-request-ckgzg reason: Completed&#xA;&lt; Exit [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:144 @ 04/24/26 06:00:10.757 (13m40.136s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:10.758&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:10.758 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when the PaC build pipelineRun run succeeded checks if the BuildPipelineRun have the annotation of chains signed [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.170884279">
              <system-err>&gt; Enter [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:151 @ 04/24/26 06:00:10.758&#xA;&lt; Exit [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:151 @ 04/24/26 06:00:10.929 (170ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:10.929&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:10.929 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when the PaC build pipelineRun run succeeded checks if the Snapshot is created [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.067594483">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:155 @ 04/24/26 06:00:10.93&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:155 @ 04/24/26 06:00:10.997 (67ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:10.997&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:10.997 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when the PaC build pipelineRun run succeeded checks if the Build PipelineRun got annotated with Snapshot name [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.17027512">
              <system-err>&gt; Enter [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:160 @ 04/24/26 06:00:10.998&#xA;&lt; Exit [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:160 @ 04/24/26 06:00:11.168 (170ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:11.168&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:11.168 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when the Snapshot was created should find both the related Integration PipelineRuns [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.272208197">
              <system-err>&gt; Enter [It] should find both the related Integration PipelineRuns - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:166 @ 04/24/26 06:00:11.168&#xA;&lt; Exit [It] should find both the related Integration PipelineRuns - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:166 @ 04/24/26 06:00:11.44 (272ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:11.44&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:11.44 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns are created should eventually complete successfully [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="40.436363681">
              <system-err>&gt; Enter [It] should eventually complete successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:190 @ 04/24/26 06:00:11.441&#xA;PipelineRun my-integration-test-lfbx-b2rbx reason: ResolvingTaskRef&#xA;PipelineRun my-integration-test-lfbx-b2rbx reason: Running&#xA;PipelineRun my-integration-test-lfbx-b2rbx reason: Succeeded&#xA;PipelineRun my-integration-test-kfpn-m9kmh reason: Succeeded&#xA;PipelineRun my-integration-test-dwde-kwcl5 reason: Succeeded&#xA;PipelineRun my-integration-test-jehm-7m7hq reason: Succeeded&#xA;&lt; Exit [It] should eventually complete successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:190 @ 04/24/26 06:00:51.877 (40.436s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:51.877&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:51.877 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully should lead to Snapshot CR being marked as failed [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.205157836">
              <system-err>&gt; Enter [It] should lead to Snapshot CR being marked as failed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:199 @ 04/24/26 06:00:51.878&#xA;&lt; Exit [It] should lead to Snapshot CR being marked as failed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:199 @ 04/24/26 06:00:52.083 (205ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:52.083&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:52.083 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully eventually leads to the status reported at Checks tab for the successful Integration PipelineRun [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.431603605">
              <system-err>&gt; Enter [It] eventually leads to the status reported at Checks tab for the successful Integration PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:213 @ 04/24/26 06:00:52.083&#xA;&lt; Exit [It] eventually leads to the status reported at Checks tab for the successful Integration PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:213 @ 04/24/26 06:00:52.514 (431ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:52.515&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:52.515 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully eventually leads to the status reported at Checks tab for the failed Integration PipelineRun [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.422151188">
              <system-err>&gt; Enter [It] eventually leads to the status reported at Checks tab for the failed Integration PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:217 @ 04/24/26 06:00:52.515&#xA;&lt; Exit [It] eventually leads to the status reported at Checks tab for the failed Integration PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:217 @ 04/24/26 06:00:52.937 (422ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:52.937&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:52.937 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully eventually leads to the status reported at Checks tab for the optional Integration PipelineRun [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.393888132">
              <system-err>&gt; Enter [It] eventually leads to the status reported at Checks tab for the optional Integration PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:221 @ 04/24/26 06:00:52.938&#xA;&lt; Exit [It] eventually leads to the status reported at Checks tab for the optional Integration PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:221 @ 04/24/26 06:00:53.331 (393ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:53.332&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:53.332 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully eventually leads to the status reported at Checks tab for the warning Integration PipelineRun [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.387189576">
              <system-err>&gt; Enter [It] eventually leads to the status reported at Checks tab for the warning Integration PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:225 @ 04/24/26 06:00:53.332&#xA;&lt; Exit [It] eventually leads to the status reported at Checks tab for the warning Integration PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:225 @ 04/24/26 06:00:53.719 (387ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:53.719&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:53.719 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully checks if the optional Integration Test Scenario status is reported in the Snapshot [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.134623955">
              <system-err>&gt; Enter [It] checks if the optional Integration Test Scenario status is reported in the Snapshot - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:229 @ 04/24/26 06:00:53.72&#xA;&lt; Exit [It] checks if the optional Integration Test Scenario status is reported in the Snapshot - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:229 @ 04/24/26 06:00:53.854 (134ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:53.855&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:53.855 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully checks if the finalizer was removed from the optional Integration PipelineRun [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.134203322">
              <system-err>&gt; Enter [It] checks if the finalizer was removed from the optional Integration PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:244 @ 04/24/26 06:00:53.855&#xA;&lt; Exit [It] checks if the finalizer was removed from the optional Integration PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:244 @ 04/24/26 06:00:53.989 (134ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:53.989&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:53.989 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully checks if the warning Integration Test Scenario status is reported in the Snapshot [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.069063668">
              <system-err>&gt; Enter [It] checks if the warning Integration Test Scenario status is reported in the Snapshot - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:248 @ 04/24/26 06:00:53.99&#xA;&lt; Exit [It] checks if the warning Integration Test Scenario status is reported in the Snapshot - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:248 @ 04/24/26 06:00:54.058 (69ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:54.059&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:54.059 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully checks if the finalizer was removed from the warning Integration PipelineRun [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.069325086">
              <system-err>&gt; Enter [It] checks if the finalizer was removed from the warning Integration PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:263 @ 04/24/26 06:00:54.059&#xA;&lt; Exit [It] checks if the finalizer was removed from the warning Integration PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:263 @ 04/24/26 06:00:54.128 (69ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:54.128&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:54.128 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully merging the PR, expected to succeed  [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="1.684734731">
              <system-err>&gt; Enter [It] merging the PR, expected to succeed  - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:267 @ 04/24/26 06:00:54.129&#xA;merged result sha: 75e18cda18d79586e023200a75cd1147948b0fcc for PR #9471&#xA;&lt; Exit [It] merging the PR, expected to succeed  - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:267 @ 04/24/26 06:00:55.813 (1.684s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:55.814&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:00:55.814 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully leads to triggering a push PipelineRun [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="20.201915914">
              <system-err>&gt; Enter [It] leads to triggering a push PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:276 @ 04/24/26 06:00:55.814&#xA;Push PipelineRun has not been created yet for the component stat-rep-myzl/test-component-pac-svwack&#xA;&lt; Exit [It] leads to triggering a push PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:276 @ 04/24/26 06:01:16.016 (20.202s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:01:16.016&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:01:16.016 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully verifies that Push PipelineRuns completed [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.237524731">
              <system-err>&gt; Enter [It] verifies that Push PipelineRuns completed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:291 @ 04/24/26 06:01:16.017&#xA;PipelineRun my-integration-test-lfbx-b2rbx reason: Succeeded&#xA;PipelineRun my-integration-test-kfpn-m9kmh reason: Succeeded&#xA;PipelineRun my-integration-test-jehm-7m7hq reason: Succeeded&#xA;&lt; Exit [It] verifies that Push PipelineRuns completed - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:291 @ 04/24/26 06:01:16.254 (237ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:01:16.254&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:01:16.254 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully validates the Integration test scenario PipelineRun is reported to merge request CheckRuns, and it pass [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.416130819">
              <system-err>&gt; Enter [It] validates the Integration test scenario PipelineRun is reported to merge request CheckRuns, and it pass - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:297 @ 04/24/26 06:01:16.255&#xA;&lt; Exit [It] validates the Integration test scenario PipelineRun is reported to merge request CheckRuns, and it pass - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:297 @ 04/24/26 06:01:16.67 (416ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:01:16.671&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:01:16.671 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully eventually leads to the status reported at Checks tab for the failed Integration PipelineRun [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.34652135">
              <system-err>&gt; Enter [It] eventually leads to the status reported at Checks tab for the failed Integration PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:302 @ 04/24/26 06:01:16.672&#xA;&lt; Exit [It] eventually leads to the status reported at Checks tab for the failed Integration PipelineRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:302 @ 04/24/26 06:01:17.018 (346ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:01:17.018&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:01:17.018 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when The git-provider annotation is missing should set the git-reporting-failure annotation correctly [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.279126116">
              <system-err>&gt; Enter [It] should set the git-reporting-failure annotation correctly - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:308 @ 04/24/26 06:01:17.019&#xA;&lt; Exit [It] should set the git-reporting-failure annotation correctly - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:308 @ 04/24/26 06:01:17.297 (279ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:01:17.297&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:01:17.297 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when build pipelinerun fails build pipelinerun is created but fails [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="18.198141075">
              <system-err>&gt; Enter [It] build pipelinerun is created but fails - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:355 @ 04/24/26 06:01:17.298&#xA;Waiting for pipeline &#34;failing-build-plr-tyxn&#34; to finish&#xA;&lt; Exit [It] build pipelinerun is created but fails - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:355 @ 04/24/26 06:01:35.496 (18.198s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:01:35.496&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:01:35.496 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when build pipelinerun fails build pipelinerun failure is reported to integration test checkRun [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="23.615124671">
              <system-err>&gt; Enter [It] build pipelinerun failure is reported to integration test checkRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:400 @ 04/24/26 06:01:35.497&#xA;failed to check expected checkRun text, actual text is %!s(&lt;nil&gt;): &#xA;%!(EXTRA string=build pipelinerun stat-rep-myzl/failing-build-plr-tyxn is still in progress)&#xA;&lt; Exit [It] build pipelinerun failure is reported to integration test checkRun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:400 @ 04/24/26 06:01:55.99 (20.493s)&#xA;&gt; Enter [AfterAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:94 @ 04/24/26 06:01:55.99&#xA;&lt; Exit [AfterAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:94 @ 04/24/26 06:01:59.111 (3.121s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:01:59.112&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/24/26 06:01:59.112 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component A creates the Component A successfully [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="23.828927216">
              <system-err>&gt; Enter [BeforeAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:60 @ 04/24/26 05:45:35.93&#xA;Successfully acquired repository lock for namespace group-vgzf&#xA;&lt; Exit [BeforeAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:60 @ 04/24/26 05:45:39.616 (3.686s)&#xA;&gt; Enter [It] creates the Component A successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:205 @ 04/24/26 05:45:39.616&#xA;Image repository for component go-component-zrwnnm in namespace group-vgzf do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component go-component-zrwnnm in namespace group-vgzf do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [It] creates the Component A successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:205 @ 04/24/26 05:45:59.758 (20.142s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 05:45:59.758&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 05:45:59.758 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component A triggers a Build PipelineRun for componentA go-component [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="40.345302578">
              <system-err>&gt; Enter [It] triggers a Build PipelineRun for componentA go-component - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:213 @ 04/24/26 05:45:59.759&#xA;Build PipelineRun has not been created yet for the componentA group-vgzf/go-component-zrwnnm&#xA;&lt; Exit [It] triggers a Build PipelineRun for componentA go-component - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:213 @ 04/24/26 05:46:40.103 (40.345s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 05:46:40.104&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 05:46:40.104 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component A does not contain an annotation with a Snapshot Name [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.00035065">
              <system-err>&gt; Enter [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:227 @ 04/24/26 05:46:40.104&#xA;&lt; Exit [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:227 @ 04/24/26 05:46:40.104 (0s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 05:46:40.104&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 05:46:40.104 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component A should lead to build PipelineRunA finishing successfully [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="1103.945902867">
              <system-err>&gt; Enter [It] should lead to build PipelineRunA finishing successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:231 @ 04/24/26 05:46:40.105&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw found for Component group-vgzf/go-component-zrwnnm&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: ResolvingTaskRef&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun has not been created yet for the Component group-vgzf/go-component-zrwnnm&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: PipelineRunStopping&#xA;PipelineRun go-component-zrwnnm-on-pull-request-49mbw reason: Failed&#xA;attempt 1/3: PipelineRun &#34;go-component-zrwnnm-on-pull-request-49mbw&#34; failed: &#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-apply-tags-pod | init container: prepare&#xA;2026/04/24 05:51:34 Entrypoint initialization&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-apply-tags-pod | container step-apply-additional-tags: &#xA;time=&#34;2026-04-24T05:51:40Z&#34; level=info msg=&#34;[param] image-url: quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#34;&#xA;time=&#34;2026-04-24T05:51:40Z&#34; level=info msg=&#34;[param] digest: sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8&#34;&#xA;time=&#34;2026-04-24T05:51:40Z&#34; level=info msg=&#34;[param] tags-from-image-label: konflux.additional-tags&#34;&#xA;time=&#34;2026-04-24T05:51:42Z&#34; level=warning msg=&#34;No tags given in &#39;konflux.additional-tags&#39; image label&#34;&#xA;{&#34;tags&#34;:[]}&#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-build-container-pod | init container: prepare&#xA;2026/04/24 05:47:42 Entrypoint initialization&#xA;&#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-build-container-pod | init container: place-scripts&#xA;2026/04/24 05:47:43 Decoded script /tekton/scripts/script-0-j9mg4&#xA;2026/04/24 05:47:43 Decoded script /tekton/scripts/script-1-89cf7&#xA;2026/04/24 05:47:43 Decoded script /tekton/scripts/script-2-sn5l7&#xA;2026/04/24 05:47:43 Decoded script /tekton/scripts/script-3-9xslc&#xA;2026/04/24 05:47:43 Decoded script /tekton/scripts/script-4-n862m&#xA;&#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-build-container-pod | init container: working-dir-initializer&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-build-container-pod | container step-build: &#xA;[2026-04-24T05:49:02,447021234+00:00] Validate context path&#xA;[2026-04-24T05:49:02,450731869+00:00] Update CA trust&#xA;[2026-04-24T05:49:02,451974884+00:00] Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#xA;&#39;/mnt/trusted-ca/ca-bundle.crt&#39; -&gt; &#39;/etc/pki/ca-trust/source/anchors/ca-bundle.crt&#39;&#xA;[2026-04-24T05:49:04,759148971+00:00] Prepare Dockerfile&#xA;Checking if /var/workdir/cachi2/output/bom.json exists.&#xA;Could not find prefetched sbom. No content_sets found for ICM&#xA;[2026-04-24T05:49:04,767714442+00:00] Prepare system (architecture: x86_64)&#xA;[2026-04-24T05:49:04,785836329+00:00] Setup prefetched&#xA;Trying to pull registry.access.redhat.com/ubi9/go-toolset:1.18.9-14...&#xA;Getting image source signatures&#xA;Checking if image destination supports signatures&#xA;Copying blob sha256:2a625e4afab51b49edb0e5f4ff37d8afbb20ec644ed1e68641358a6305557de3&#xA;Copying blob sha256:4a13c0e9217d70e608f2d5f5d3c5ffa6d9cd16908b3f83a7a97492d355d25a09&#xA;Copying blob sha256:0ab0ba77295aca9b12f463cb7198f0b8b6990b41151dbbd4e1b224fe85244b83&#xA;Copying blob sha256:e76793d6902ad1adb19ede3d720024cf0cd8427b3ff606554a4bcafba03dddf4&#xA;Copying config sha256:391a2eac28d98dc72726df1faa77db28f6899a77c91ad40f2bdad62baf041301&#xA;Writing manifest to image destination&#xA;Storing signatures&#xA;[2026-04-24T05:49:37,146230970+00:00] Unsetting proxy&#xA;{&#xA;  &#34;architecture&#34;: &#34;x86_64&#34;,&#xA;  &#34;build-date&#34;: &#34;2026-04-24T05:49:04Z&#34;,&#xA;  &#34;com.redhat.component&#34;: &#34;go-toolset-container&#34;,&#xA;  &#34;com.redhat.license_terms&#34;: &#34;https://www.redhat.com/en/about/red-hat-end-user-license-agreements#UBI&#34;,&#xA;  &#34;description&#34;: &#34;Go Toolset available as a container is a base platform for building and running various Go applications and frameworks. Go is an easy to learn, powerful, statically typed language in the C/C++ tradition with garbage collection, concurrent programming support, and memory safety features.&#34;,&#xA;  &#34;distribution-scope&#34;: &#34;public&#34;,&#xA;  &#34;io.buildah.version&#34;: &#34;1.42.2&#34;,&#xA;  &#34;io.k8s.description&#34;: &#34;Go Toolset available as a container is a base platform for building and running various Go applications and frameworks. Go is an easy to learn, powerful, statically typed language in the C/C++ tradition with garbage collection, concurrent programming support, and memory safety features.&#34;,&#xA;  &#34;io.k8s.display-name&#34;: &#34;Go 1.18.9&#34;,&#xA;  &#34;io.openshift.expose-services&#34;: &#34;&#34;,&#xA;  &#34;io.openshift.s2i.scripts-url&#34;: &#34;image:///usr/libexec/s2i&#34;,&#xA;  &#34;io.openshift.tags&#34;: &#34;builder,golang,golang118,rh-golang118,go&#34;,&#xA;  &#34;io.s2i.scripts-url&#34;: &#34;image:///usr/libexec/s2i&#34;,&#xA;  &#34;maintainer&#34;: &#34;Red Hat, Inc.&#34;,&#xA;  &#34;name&#34;: &#34;rhel9/go-toolset&#34;,&#xA;  &#34;release&#34;: &#34;14&#34;,&#xA;  &#34;summary&#34;: &#34;Platform for building and running Go Applications&#34;,&#xA;  &#34;url&#34;: &#34;https://access.redhat.com/containers/#/registry.access.redhat.com/rhel9/go-toolset/images/1.18.9-14&#34;,&#xA;  &#34;vcs-ref&#34;: &#34;93e2088996e261a167eab61824669c3c2f684469&#34;,&#xA;  &#34;vcs-type&#34;: &#34;git&#34;,&#xA;  &#34;vendor&#34;: &#34;Red Hat, Inc.&#34;,&#xA;  &#34;version&#34;: &#34;1.18.9&#34;,&#xA;  &#34;org.opencontainers.image.revision&#34;: &#34;93e2088996e261a167eab61824669c3c2f684469&#34;,&#xA;  &#34;org.opencontainers.image.source&#34;: &#34;https://github.com/redhat-appstudio-qe/group-snapshot-multi-component&#34;,&#xA;  &#34;quay.expires-after&#34;: &#34;5d&#34;,&#xA;  &#34;org.opencontainers.image.created&#34;: &#34;2026-04-24T05:49:04Z&#34;&#xA;}&#xA;[2026-04-24T05:49:37,197019378+00:00] Register sub-man&#xA;Adding the entitlement to the build&#xA;[2026-04-24T05:49:37,200835203+00:00] Add secrets&#xA;[2026-04-24T05:49:37,377139445+00:00] Run buildah build&#xA;[2026-04-24T05:49:37,378471765+00:00] buildah build --volume /tmp/entitlement:/etc/pki/entitlement --security-opt=unmask=/proc/interrupts --label architecture=x86_64 --label vcs-type=git --label vcs-ref=93e2088996e261a167eab61824669c3c2f684469 --label org.opencontainers.image.revision=93e2088996e261a167eab61824669c3c2f684469 --label org.opencontainers.image.source=https://github.com/redhat-appstudio-qe/group-snapshot-multi-component --label quay.expires-after=5d --label build-date=2026-04-24T05:49:04Z --label org.opencontainers.image.created=2026-04-24T05:49:04Z --annotation org.opencontainers.image.revision=93e2088996e261a167eab61824669c3c2f684469 --annotation org.opencontainers.image.source=https://github.com/redhat-appstudio-qe/group-snapshot-multi-component --annotation org.opencontainers.image.created=2026-04-24T05:49:04Z --tls-verify=true --no-cache --ulimit nofile=4096:4096 --http-proxy=false -f /tmp/Dockerfile.EPI5bW -t quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469 . &#xA;STEP 1/10: FROM registry.access.redhat.com/ubi9/go-toolset:1.18.9-14&#xA;STEP 2/10: COPY . .&#xA;STEP 3/10: RUN go mod download&#xA;go: no module dependencies to download&#xA;STEP 4/10: RUN go build -o ./main&#xA;STEP 5/10: ENV PORT 8081&#xA;STEP 6/10: EXPOSE 8081&#xA;STEP 7/10: CMD [ &#34;./main&#34; ]&#xA;STEP 8/10: COPY labels.json /usr/share/buildinfo/labels.json&#xA;STEP 9/10: COPY labels.json /root/buildinfo/labels.json&#xA;STEP 10/10: LABEL &#34;architecture&#34;=&#34;x86_64&#34; &#34;vcs-type&#34;=&#34;git&#34; &#34;vcs-ref&#34;=&#34;93e2088996e261a167eab61824669c3c2f684469&#34; &#34;org.opencontainers.image.revision&#34;=&#34;93e2088996e261a167eab61824669c3c2f684469&#34; &#34;org.opencontainers.image.source&#34;=&#34;https://github.com/redhat-appstudio-qe/group-snapshot-multi-component&#34; &#34;quay.expires-after&#34;=&#34;5d&#34; &#34;build-date&#34;=&#34;2026-04-24T05:49:04Z&#34; &#34;org.opencontainers.image.created&#34;=&#34;2026-04-24T05:49:04Z&#34;&#xA;COMMIT quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#xA;--&gt; 8a1b64ad758a&#xA;Successfully tagged quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#xA;8a1b64ad758aacd5add980ec470ca2f55c98293b2cd70c2758a89e2a77120936&#xA;[2026-04-24T05:49:39,899353963+00:00] Unsetting proxy&#xA;[2026-04-24T05:49:39,900775566+00:00] Add metadata&#xA;Recording base image digests used&#xA;registry.access.redhat.com/ubi9/go-toolset:1.18.9-14 registry.access.redhat.com/ubi9/go-toolset:1.18.9-14@sha256:4e320bd8b62e406dfc567886aeab4914db125c73fe9ec308b306c72883101d51&#xA;Getting image source signatures&#xA;Copying blob sha256:8a990882247a3a65f182989cb5d8a59ddc9b61ee19e7e8a562bed07f603ffc42&#xA;Copying blob sha256:d3f6a420cbadfb30033dc481690b39191ce6d2d841ccd54434c352f474ea54c3&#xA;Copying blob sha256:a653a5ff4eaef6037f4f354414ab251ac7218d2d42fc8326743fc63ecf2cabd5&#xA;Copying blob sha256:db77b3de17313a3fab2620178c01a4ef8eb60cbe722a6e9390f3cbb1132a7d22&#xA;Copying blob sha256:314640f419c581ddcac8f3618af39342a4571d5dc7a4e1f5b64d60f37e630b49&#xA;Copying config sha256:8a1b64ad758aacd5add980ec470ca2f55c98293b2cd70c2758a89e2a77120936&#xA;Writing manifest to image destination&#xA;[2026-04-24T05:49:49,206741092+00:00] End build&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-build-container-pod | container step-push: &#xA;[2026-04-24T05:49:49,604684788+00:00] Update CA trust&#xA;INFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#xA;&#39;/mnt/trusted-ca/ca-bundle.crt&#39; -&gt; &#39;/etc/pki/ca-trust/source/anchors/ca-bundle.crt&#39;&#xA;[2026-04-24T05:49:52,427544262+00:00] Convert image&#xA;[2026-04-24T05:49:52,428756131+00:00] Push image with unique tag&#xA;Pushing to quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:go-component-zrwnnm-on-pull-request-49mbw-build-container&#xA;[retry] executing: buildah push --format=docker --retry 3 --tls-verify=true quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469 docker://quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:go-component-zrwnnm-on-pull-request-49mbw-build-container&#xA;Getting image source signatures&#xA;Copying blob sha256:8a990882247a3a65f182989cb5d8a59ddc9b61ee19e7e8a562bed07f603ffc42&#xA;Copying blob sha256:d3f6a420cbadfb30033dc481690b39191ce6d2d841ccd54434c352f474ea54c3&#xA;Copying blob sha256:db77b3de17313a3fab2620178c01a4ef8eb60cbe722a6e9390f3cbb1132a7d22&#xA;Copying blob sha256:314640f419c581ddcac8f3618af39342a4571d5dc7a4e1f5b64d60f37e630b49&#xA;Copying blob sha256:a653a5ff4eaef6037f4f354414ab251ac7218d2d42fc8326743fc63ecf2cabd5&#xA;Copying config sha256:8a1b64ad758aacd5add980ec470ca2f55c98293b2cd70c2758a89e2a77120936&#xA;Writing manifest to image destination&#xA;[2026-04-24T05:50:08,125285325+00:00] Push image with git revision&#xA;Pushing to quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#xA;[retry] executing: buildah push --format=docker --retry 3 --tls-verify=true --digestfile /workspace/source/image-digest quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469 docker://quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#xA;Getting image source signatures&#xA;Copying blob sha256:8a990882247a3a65f182989cb5d8a59ddc9b61ee19e7e8a562bed07f603ffc42&#xA;Copying blob sha256:314640f419c581ddcac8f3618af39342a4571d5dc7a4e1f5b64d60f37e630b49&#xA;Copying blob sha256:a653a5ff4eaef6037f4f354414ab251ac7218d2d42fc8326743fc63ecf2cabd5&#xA;Copying blob sha256:db77b3de17313a3fab2620178c01a4ef8eb60cbe722a6e9390f3cbb1132a7d22&#xA;Copying blob sha256:d3f6a420cbadfb30033dc481690b39191ce6d2d841ccd54434c352f474ea54c3&#xA;Copying config sha256:8a1b64ad758aacd5add980ec470ca2f55c98293b2cd70c2758a89e2a77120936&#xA;Writing manifest to image destination&#xA;sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#xA;[retry] executing: kubectl get configmap cluster-config -n konflux-info -o json&#xA;Keyless signing is disabled (none of rekorInternalUrl, fulcioInternalUrl, defaultOIDCIssuer, tufInternalUrl are configured in the konflux-info/cluster-config configmap)&#xA;[2026-04-24T05:50:09,576293727+00:00] End push&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-build-container-pod | container step-sbom-syft-generate: &#xA;[2026-04-24T05:50:10,401742838+00:00] Generate SBOM&#xA;Running syft on the image&#xA;Running syft on the source code&#xA;[0000]  WARN no explicit name and version provided for directory source, deriving artifact ID from the given path (which is not ideal)&#xA;[2026-04-24T05:50:30,648389830+00:00] End sbom-syft-generate&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-build-container-pod | container step-prepare-sboms: &#xA;[2026-04-24T05:50:30,674357152+00:00] Prepare SBOM&#xA;[2026-04-24T05:50:30,678956608+00:00] Generate SBOM with mobster&#xA;Skipping SBOM validation&#xA;2026-04-24 05:50:32,839 [INFO] mobster.log: Logging level set to 20&#xA;2026-04-24 05:50:33,334 [INFO] mobster.oci: Fetching manifest for registry.access.redhat.com/ubi9/go-toolset@sha256:4e320bd8b62e406dfc567886aeab4914db125c73fe9ec308b306c72883101d51&#xA;2026-04-24 05:50:34,664 [WARNING] mobster.oci.cosign.anonymous_fetcher: Cosign fetching attestation of type spdxjson failed for registry.access.redhat.com/ubi9/go-toolset@sha256:0200988bf4773dad494d97be5aeceb005da3b329fe6827c035509a3f6eec1ef1 with output b&#39;Error: found no attestations\nerror during command execution: found no attestations\n&#39;&#xA;2026-04-24 05:50:35,103 [WARNING] mobster.oci.cosign.anonymous_fetcher: Cosign fetching attestation of type cyclonedx failed for registry.access.redhat.com/ubi9/go-toolset@sha256:0200988bf4773dad494d97be5aeceb005da3b329fe6827c035509a3f6eec1ef1 with output b&#39;Error: found no attestations\nerror during command execution: found no attestations\n&#39;&#xA;2026-04-24 05:50:36,232 [WARNING] mobster.oci.cosign.anonymous_fetcher: Cosign fetching attestation of type spdxjson failed for registry.access.redhat.com/ubi9/go-toolset@sha256:0200988bf4773dad494d97be5aeceb005da3b329fe6827c035509a3f6eec1ef1 with output b&#39;Error: found no attestations\nerror during command execution: found no attestations\n&#39;&#xA;2026-04-24 05:50:36,676 [WARNING] mobster.oci.cosign.anonymous_fetcher: Cosign fetching attestation of type cyclonedx failed for registry.access.redhat.com/ubi9/go-toolset@sha256:0200988bf4773dad494d97be5aeceb005da3b329fe6827c035509a3f6eec1ef1 with output b&#39;Error: found no attestations\nerror during command execution: found no attestations\n&#39;&#xA;2026-04-24 05:50:37,611 [WARNING] mobster.oci.cosign.anonymous_fetcher: Cosign fetching attestation of type spdxjson failed for registry.access.redhat.com/ubi9/go-toolset@sha256:0200988bf4773dad494d97be5aeceb005da3b329fe6827c035509a3f6eec1ef1 with output b&#39;Error: found no attestations\nerror during command execution: found no attestations\n&#39;&#xA;2026-04-24 05:50:38,057 [WARNING] mobster.oci.cosign.anonymous_fetcher: Cosign fetching attestation of type cyclonedx failed for registry.access.redhat.com/ubi9/go-toolset@sha256:0200988bf4773dad494d97be5aeceb005da3b329fe6827c035509a3f6eec1ef1 with output b&#39;Error: found no attestations\nerror during command execution: found no attestations\n&#39;&#xA;2026-04-24 05:50:39,108 [WARNING] mobster.oci.cosign.anonymous_fetcher: Cosign fetching attestation of type spdxjson failed for registry.access.redhat.com/ubi9/go-toolset@sha256:0200988bf4773dad494d97be5aeceb005da3b329fe6827c035509a3f6eec1ef1 with output b&#39;Error: found no attestations\nerror during command execution: found no attestations\n&#39;&#xA;2026-04-24 05:50:39,533 [WARNING] mobster.oci.cosign.anonymous_fetcher: Cosign fetching attestation of type cyclonedx failed for registry.access.redhat.com/ubi9/go-toolset@sha256:0200988bf4773dad494d97be5aeceb005da3b329fe6827c035509a3f6eec1ef1 with output b&#39;Error: found no attestations\nerror during command execution: found no attestations\n&#39;&#xA;2026-04-24 05:50:39,534 [INFO] mobster.cmd.generate.oci_image.contextual_sbom.contextualize: Contextual mechanism won&#39;t be used, there is no parent image SBOM.&#xA;2026-04-24 05:50:39,534 [INFO] mobster.cmd.generate.oci_image: Contextual SBOM workflow finished successfully.&#xA;2026-04-24 05:50:39,536 [INFO] mobster.log: Contextual workflow completed in 6.30s&#xA;2026-04-24 05:50:39,680 [INFO] mobster.main: Exiting with code 0.&#xA;[2026-04-24T05:50:39,754309341+00:00] End prepare-sboms&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-build-container-pod | container step-upload-sbom: &#xA;[2026-04-24T05:50:39,829270853+00:00] Upload SBOM&#xA;INFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#xA;&#39;/mnt/trusted-ca/ca-bundle.crt&#39; -&gt; &#39;/etc/pki/ca-trust/source/anchors/ca-bundle.crt&#39;&#xA;Using token for quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm&#xA;Pushing sbom to registry&#xA;[retry] executing: cosign attach sbom --sbom sbom.json --type spdx quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469@sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8&#xA;WARNING: SBOM attachments are deprecated and support will be removed in a Cosign release soon after 2024-02-22 (see https://github.com/sigstore/cosign/issues/2755). Instead, please use SBOM attestations.&#xA;WARNING: Attaching SBOMs this way does not sign them. To sign them, use &#39;cosign attest --predicate sbom.json --key &lt;key path&gt;&#39;.&#xA;Uploading SBOM file for [quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm@sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8] to [quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:sha256-8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8.sbom] with mediaType [text/spdx+json].&#xA;&#xA;quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm@sha256:0fad499994d707e48a397e38ad8a8c2ef84f6bb6cc0d37b6cbd5e60a4b738250&#xA;[2026-04-24T05:50:45,699261158+00:00] End upload-sbom&#xA;&#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-build-image-index-pod | init container: prepare&#xA;2026/04/24 05:50:49 Entrypoint initialization&#xA;&#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-build-image-index-pod | init container: place-scripts&#xA;2026/04/24 05:50:50 Decoded script /tekton/scripts/script-0-b4nxd&#xA;2026/04/24 05:50:50 Decoded script /tekton/scripts/script-1-c9ztd&#xA;2026/04/24 05:50:50 Decoded script /tekton/scripts/script-2-58jgd&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-build-image-index-pod | container step-build: &#xA;[2026-04-24T05:51:00,124639278+00:00] Update CA trust&#xA;INFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#xA;&#39;/mnt/trusted-ca/ca-bundle.crt&#39; -&gt; &#39;/etc/pki/ca-trust/source/anchors/ca-bundle.crt&#39;&#xA;Running konflux-build-cli&#xA;time=&#34;2026-04-24T05:51:02Z&#34; level=info msg=&#34;[param] image: quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#34;&#xA;time=&#34;2026-04-24T05:51:02Z&#34; level=info msg=&#34;[param] images: [quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469@sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8]&#34;&#xA;time=&#34;2026-04-24T05:51:02Z&#34; level=info msg=&#34;[param] buildah-format: docker&#34;&#xA;time=&#34;2026-04-24T05:51:02Z&#34; level=info msg=&#34;[param] always-build-index: false&#34;&#xA;time=&#34;2026-04-24T05:51:02Z&#34; level=info msg=&#34;[param] additional-tags: [go-component-zrwnnm-on-pull-request-49mbw-build-image-index]&#34;&#xA;time=&#34;2026-04-24T05:51:02Z&#34; level=info msg=&#34;[param] output-manifest-path: /index-build-data/manifest_data.json&#34;&#xA;time=&#34;2026-04-24T05:51:02Z&#34; level=info msg=&#34;[param] result-path-image-digest: /tekton/results/IMAGE_DIGEST&#34;&#xA;time=&#34;2026-04-24T05:51:02Z&#34; level=info msg=&#34;[param] result-path-image-url: /tekton/results/IMAGE_URL&#34;&#xA;time=&#34;2026-04-24T05:51:02Z&#34; level=info msg=&#34;[param] result-path-image-ref: /tekton/results/IMAGE_REF&#34;&#xA;time=&#34;2026-04-24T05:51:02Z&#34; level=info msg=&#34;[param] result-path-images: /tekton/results/IMAGES&#34;&#xA;time=&#34;2026-04-24T05:51:02Z&#34; level=info msg=&#34;Creating manifest list: quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#34;&#xA;time=&#34;2026-04-24T05:51:02Z&#34; level=info msg=&#34;buildah [stdout] 868411cb9bc4c78b3764c744d5bc8380d53ed5c25b9300171875178f8debc187&#34; logger=CliExecutor&#xA;time=&#34;2026-04-24T05:51:02Z&#34; level=info msg=&#34;Skipping image index generation. Returning results for single image.&#34;&#xA;{&#34;image_digest&#34;:&#34;sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8&#34;,&#34;image_url&#34;:&#34;quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#34;,&#34;image_ref&#34;:&#34;quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm@sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8&#34;,&#34;images&#34;:&#34;quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm@sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8&#34;}&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-build-image-index-pod | container step-create-sbom: &#xA;The manifest_data.json file does not exist. Skipping the SBOM creation...&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-build-image-index-pod | container step-upload-sbom: &#xA;[2026-04-24T05:51:03,636158391+00:00] Update CA trust&#xA;INFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#xA;&#39;/mnt/trusted-ca/ca-bundle.crt&#39; -&gt; &#39;/etc/pki/ca-trust/source/anchors/ca-bundle.crt&#39;&#xA;The index.spdx.json file does not exists. Skipping the SBOM upload...&#xA;&#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-clair-scan-pod | init container: prepare&#xA;2026/04/24 05:51:32 Entrypoint initialization&#xA;&#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-clair-scan-pod | init container: place-scripts&#xA;2026/04/24 05:51:36 Decoded script /tekton/scripts/script-0-rfjvl&#xA;2026/04/24 05:51:36 Decoded script /tekton/scripts/script-1-rkmg7&#xA;2026/04/24 05:51:36 Decoded script /tekton/scripts/script-2-rkb7z&#xA;2026/04/24 05:51:36 Decoded script /tekton/scripts/script-3-h9hmn&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-clair-scan-pod | container step-get-image-manifests: &#xA;Inspecting raw image manifest quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm@sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8.&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-clair-scan-pod | container step-get-vulnerabilities: &#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-clair-scan-pod | container step-oci-attach-report: &#xA;Selecting auth&#xA;Using token for quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm&#xA;Attaching clair-report-amd64.json to quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm@sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8&#xA;Executing: oras attach --no-tty --format go-template={{.digest}} --registry-config /home/oras/auth.json --artifact-type application/vnd.redhat.clair-report+json quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm@sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8 clair-report-amd64.json:application/vnd.redhat.clair-report+json&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-clair-scan-pod | container step-conftest-vulnerabilities: &#xA;[&#xA;&#x9;{&#xA;&#x9;&#x9;&#34;filename&#34;: &#34;/tekton/home/clair-result-amd64.json&#34;,&#xA;&#x9;&#x9;&#34;namespace&#34;: &#34;required_checks&#34;,&#xA;&#x9;&#x9;&#34;successes&#34;: 3,&#xA;&#x9;&#x9;&#34;warnings&#34;: [&#xA;&#x9;&#x9;&#x9;{&#xA;&#x9;&#x9;&#x9;&#x9;&#34;msg&#34;: &#34;Found packages with high vulnerabilities associated with RHSA fixes. Consider updating to a newer version of those packages, they may no longer be affected by the reported CVEs.&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#34;metadata&#34;: {&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;details&#34;: {&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;description&#34;: &#34;Vulnerabilities found: python3-cloud-what-1.29.30.1-1.el9_1 (CVE-2023-3899), glibc-2.34-40.el9_1.1 (CVE-2023-4911, CVE-2024-2961, CVE-2024-33599), python3-setuptools-53.0.0-10.el9_1.1 (CVE-2024-6345), sqlite-3.34.1-6.el9_1 (CVE-2025-6965), glibc-gconv-extra-2.34-40.el9_1.1 (CVE-2023-4911, CVE-2024-2961, CVE-2024-33599), libcurl-minimal-7.76.1-19.el9_1.1 (CVE-2023-38545), libbrotli-1.0.9-6.el9 (CVE-2025-6176), libxslt-1.1.34-9.el9 (CVE-2024-55549, CVE-2025-24855), subscription-manager-1.29.30.1-1.el9_1 (CVE-2023-3899), openssh-clients-8.7p1-24.el9_1 (CVE-2023-38408, CVE-2024-6387, CVE-2026-3497), expat-2.4.9-1.el9_1.1 (CVE-2025-59375), delve-1.8.3-1.el9 (CVE-2024-34156), go-toolset-1.18.9-1.el9_1 (CVE-2023-29403, CVE-2023-29404, CVE-2023-29405, CVE-2023-45288, CVE-2024-1394, CVE-2024-34156, CVE-2025-22874, CVE-2025-4674, CVE-2025-61726, CVE-2025-61729, CVE-2025-61731, CVE-2025-61732, CVE-2026-25679), python3-subscription-manager-rhsm-1.29.30.1-1.el9_1 (CVE-2023-3899), libwebp-devel-1.2.0-3.el9 (CVE-2023-1999, CVE-2023-4863), pam-1.5.1-12.el9 (CVE-2024-10963, CVE-2025-6020, CVE-2025-8941), nodejs-libs-1:16.18.1-3.el9_1 (CVE-2023-30581, CVE-2023-32002, CVE-2023-32006, CVE-2023-32067, CVE-2023-44487, CVE-2024-22019, CVE-2024-27983, CVE-2025-23083, CVE-2025-23166, CVE-2025-3277, CVE-2025-55130, CVE-2025-55131, CVE-2025-59465, CVE-2025-6965, CVE-2026-1526, CVE-2026-1528, CVE-2026-21710, CVE-2026-2229, CVE-2026-27135), glibc-langpack-en-2.34-40.el9_1.1 (CVE-2023-4911, CVE-2024-2961, CVE-2024-33599), git-2.31.1-3.el9_1 (CVE-2023-25652, CVE-2023-29007, CVE-2024-32002, CVE-2024-32004, CVE-2025-48384, CVE-2025-48385), glibc-locale-source-2.34-40.el9_1.1 (CVE-2023-4911, CVE-2024-2961, CVE-2024-33599), brotli-1.0.9-6.el9 (CVE-2025-6176), libxml2-2.9.13-3.el9_1 (CVE-2024-56171, CVE-2025-24928, CVE-2025-49794, CVE-2025-49796, CVE-2025-7425), glibc-devel-2.34-40.el9_1.1 (CVE-2023-4911, CVE-2024-2961, CVE-2024-33599), less-590-1.el9_0 (CVE-2024-32487), libxml2-devel-2.9.13-3.el9_1 (CVE-2024-56171, CVE-2025-24928, CVE-2025-49794, CVE-2025-49796, CVE-2025-7425), openssh-8.7p1-24.el9_1 (CVE-2023-38408, CVE-2024-6387, CVE-2026-3497), libeconf-0.4.1-2.el9 (CVE-2023-30079), freetype-2.10.4-9.el9 (CVE-2025-27363), freetype-devel-2.10.4-9.el9 (CVE-2025-27363), libtiff-devel-4.4.0-5.el9_1 (CVE-2025-8176, CVE-2025-9900), nodejs-full-i18n-1:16.18.1-3.el9_1 (CVE-2023-30581, CVE-2023-32002, CVE-2023-32006, CVE-2023-32067, CVE-2023-44487, CVE-2024-21892, CVE-2024-21896, CVE-2024-22017, CVE-2024-22019, CVE-2024-27983, CVE-2025-23083, CVE-2025-23166, CVE-2025-3277, CVE-2025-55130, CVE-2025-55131, CVE-2025-59465, CVE-2025-6965, CVE-2026-1526, CVE-2026-1528, CVE-2026-21710, CVE-2026-2229, CVE-2026-27135), libpng-2:1.6.37-12.el9 (CVE-2025-64720, CVE-2025-65018, CVE-2025-66293, CVE-2026-25646), python3-libs-3.9.14-1.el9_1.2 (CVE-2023-24329, CVE-2023-40217, CVE-2023-6597, CVE-2024-12718, CVE-2025-4138, CVE-2025-4517, CVE-2026-4519), golang-1.18.9-1.el9_1 (CVE-2023-24540, CVE-2023-29403, CVE-2023-29404, CVE-2023-29405, CVE-2023-39325, CVE-2023-44487, CVE-2023-45288, CVE-2024-1394, CVE-2024-34156, CVE-2025-22874, CVE-2025-4674, CVE-2025-61726, CVE-2025-61729, CVE-2025-61731, CVE-2025-61732, CVE-2026-25679), gnupg2-2.3.3-2.el9_0 (CVE-2025-68973), libxslt-devel-1.1.34-9.el9 (CVE-2024-55549, CVE-2025-24855), npm-1:8.19.2-1.16.18.1.3.el9_1 (CVE-2023-30581, CVE-2023-32002, CVE-2023-32006, CVE-2023-32067, CVE-2023-44487, CVE-2024-21892, CVE-2024-21896, CVE-2024-22017, CVE-2024-22019, CVE-2024-27983, CVE-2025-23083, CVE-2025-23166, CVE-2025-3277, CVE-2025-55130, CVE-2025-55131, CVE-2025-59465, CVE-2025-6965, CVE-2026-1526, CVE-2026-1528, CVE-2026-21710, CVE-2026-2229, CVE-2026-27135), emacs-filesystem-1:27.2-6.el9 (CVE-2023-2491, CVE-2023-28617, CVE-2025-1244), python3-setuptools-wheel-53.0.0-10.el9_1.1 (CVE-2024-6345), libarchive-3.5.3-3.el9 (CVE-2025-5914, CVE-2026-4111, CVE-2026-4424), python3-urllib3-1.26.5-3.el9 (CVE-2025-66418, CVE-2025-66471, CVE-2026-21441), curl-minimal-7.76.1-19.el9_1.1 (CVE-2023-38545), golang-src-1.18.9-1.el9_1 (CVE-2023-24540, CVE-2023-29403, CVE-2023-29404, CVE-2023-29405, CVE-2023-39325, CVE-2023-44487, CVE-2023-45288, CVE-2024-1394, CVE-2024-34156, CVE-2025-22874, CVE-2025-4674, CVE-2025-61726, CVE-2025-61729, CVE-2025-61731, CVE-2025-61732, CVE-2026-25679), openssl-1:3.0.1-47.el9_1 (CVE-2024-12797, CVE-2025-15467), libnghttp2-1.43.0-5.el9 (CVE-2023-44487, CVE-2026-27135), sqlite-libs-3.34.1-6.el9_1 (CVE-2025-6965), rsync-3.2.3-18.el9 (CVE-2024-12085), libdnf-plugin-subscription-manager-1.29.30.1-1.el9_1 (CVE-2023-3899), libpng-devel-2:1.6.37-12.el9 (CVE-2025-64720, CVE-2025-65018, CVE-2025-66293, CVE-2026-25646), libpq-13.5-1.el9 (CVE-2025-1094), go-srpm-macros-3.0.9-9.el9 (CVE-2025-61726, CVE-2026-25679), glibc-common-2.34-40.el9_1.1 (CVE-2023-4911, CVE-2024-2961, CVE-2024-33599), nodejs-docs-1:16.18.1-3.el9_1 (CVE-2023-30581, CVE-2023-32002, CVE-2023-32006, CVE-2023-32067, CVE-2023-44487, CVE-2024-21892, CVE-2024-21896, CVE-2024-22017, CVE-2024-22019, CVE-2024-27983, CVE-2025-23083, CVE-2025-23166, CVE-2025-3277, CVE-2025-55130, CVE-2025-55131, CVE-2025-59465, CVE-2025-6965, CVE-2026-1526, CVE-2026-1528, CVE-2026-21710, CVE-2026-2229, CVE-2026-27135), golang-bin-1.18.9-1.el9_1 (CVE-2023-24540, CVE-2023-29403, CVE-2023-29404, CVE-2023-29405, CVE-2023-39325, CVE-2023-44487, CVE-2023-45288, CVE-2024-1394, CVE-2024-34156, CVE-2025-22874, CVE-2025-4674, CVE-2025-61726, CVE-2025-61729, CVE-2025-61731, CVE-2025-61732, CVE-2026-25679), libtiff-4.4.0-5.el9_1 (CVE-2025-8176, CVE-2025-9900), git-core-doc-2.31.1-3.el9_1 (CVE-2023-25652, CVE-2023-29007, CVE-2024-32002, CVE-2024-32004, CVE-2025-48384, CVE-2025-48385), nodejs-1:16.18.1-3.el9_1 (CVE-2023-30581, CVE-2023-32002, CVE-2023-32006, CVE-2023-32067, CVE-2023-44487, CVE-2024-21892, CVE-2024-21896, CVE-2024-22017, CVE-2024-22019, CVE-2024-27983, CVE-2025-23083, CVE-2025-23166, CVE-2025-3277, CVE-2025-55130, CVE-2025-55131, CVE-2025-59465, CVE-2025-6965, CVE-2026-1526, CVE-2026-1528, CVE-2026-21710, CVE-2026-2229, CVE-2026-27135), openssl-devel-1:3.0.1-47.el9_1 (CVE-2024-12797, CVE-2025-15467), brotli-devel-1.0.9-6.el9 (CVE-2025-6176), glibc-headers-2.34-40.el9_1.1 (CVE-2023-4911, CVE-2024-2961, CVE-2024-33599), libwebp-1.2.0-3.el9 (CVE-2023-1999, CVE-2023-4863), python3-3.9.14-1.el9_1.2 (CVE-2023-24329, CVE-2023-40217, CVE-2023-6597, CVE-2024-12718, CVE-2025-4138, CVE-2025-4517, CVE-2026-4519), bsdtar-3.5.3-3.el9 (CVE-2025-5914, CVE-2026-4111, CVE-2026-4424), vim-minimal-2:8.2.2637-20.el9_1 (CVE-2026-33412), krb5-libs-1.19.1-24.el9_1 (CVE-2023-39975, CVE-2024-3596), openssl-libs-1:3.0.1-47.el9_1 (CVE-2024-12797, CVE-2025-15467), sqlite-devel-3.34.1-6.el9_1 (CVE-2025-6965), libcurl-devel-7.76.1-19.el9_1.1 (CVE-2023-38545), git-core-2.31.1-3.el9_1 (CVE-2023-25652, CVE-2023-29007, CVE-2024-32002, CVE-2024-32004, CVE-2025-48384, CVE-2025-48385), libpq-devel-13.5-1.el9 (CVE-2025-1094), perl-Git-2.31.1-3.el9_1 (CVE-2023-25652, CVE-2023-29007, CVE-2024-32002, CVE-2024-32004, CVE-2025-48384, CVE-2025-48385), glibc-minimal-langpack-2.34-40.el9_1.1 (CVE-2023-4911, CVE-2024-2961, CVE-2024-33599)&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;name&#34;: &#34;clair_high_vulnerabilities&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;url&#34;: &#34;https://access.redhat.com/articles/red_hat_vulnerability_tutorial&#34;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;},&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;vulnerabilities_number&#34;: 319&#xA;&#x9;&#x9;&#x9;&#x9;}&#xA;&#x9;&#x9;&#x9;},&#xA;&#x9;&#x9;&#x9;{&#xA;&#x9;&#x9;&#x9;&#x9;&#34;msg&#34;: &#34;Found packages with unpatched high vulnerabilities. These vulnerabilities don&#39;t have a known fix at this time.&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#34;metadata&#34;: {&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;details&#34;: {&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;description&#34;: &#34;Vulnerabilities found: libcap-2.48-8.el9 (CVE-2026-4878), openssh-clients-8.7p1-24.el9_1 (CVE-2026-35385), go-toolset-1.18.9-1.el9_1 (CVE-2025-61726, CVE-2025-61732, CVE-2026-27137, CVE-2026-27140, CVE-2026-32280, CVE-2026-33810), openssh-8.7p1-24.el9_1 (CVE-2026-35385), libtiff-devel-4.4.0-5.el9_1 (CVE-2026-4775), python3-libs-3.9.14-1.el9_1.2 (CVE-2026-4786, CVE-2026-6100), golang-1.18.9-1.el9_1 (CVE-2026-27137, CVE-2026-27140, CVE-2026-32280, CVE-2026-33810), vim-filesystem-2:8.2.2637-20.el9_1 (CVE-2026-34982), golang-src-1.18.9-1.el9_1 (CVE-2026-27137, CVE-2026-27140, CVE-2026-32280, CVE-2026-33810), rsync-3.2.3-18.el9 (CVE-2026-41035), golang-bin-1.18.9-1.el9_1 (CVE-2026-27137, CVE-2026-27140, CVE-2026-32280, CVE-2026-33810), libtiff-4.4.0-5.el9_1 (CVE-2026-4775), python3-3.9.14-1.el9_1.2 (CVE-2026-4786, CVE-2026-6100), vim-minimal-2:8.2.2637-20.el9_1 (CVE-2026-34982)&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;name&#34;: &#34;clair_unpatched_high_vulnerabilities&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;url&#34;: &#34;https://access.redhat.com/articles/red_hat_vulnerability_tutorial&#34;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;},&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;vulnerabilities_number&#34;: 30&#xA;&#x9;&#x9;&#x9;&#x9;}&#xA;&#x9;&#x9;&#x9;},&#xA;&#x9;&#x9;&#x9;{&#xA;&#x9;&#x9;&#x9;&#x9;&#34;msg&#34;: &#34;Found packages with medium vulnerabilities associated with RHSA fixes. Consider updating to a newer version of those packages, they may no longer be affected by the reported CVEs.&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#34;metadata&#34;: {&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;details&#34;: {&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;description&#34;: &#34;Vulnerabilities found: perl-if-0.60.800-479.el9 (CVE-2023-47038, CVE-2025-40909), perl-DynaLoader-1.47-479.el9 (CVE-2023-47038, CVE-2025-40909), cpp-11.3.1-2.1.el9 (CVE-2020-11023), perl-overload-1.31-479.el9 (CVE-2023-47038, CVE-2025-40909), glibc-2.34-40.el9_1.1 (CVE-2023-4527, CVE-2023-4806, CVE-2023-4813, CVE-2024-33600, CVE-2025-0395, CVE-2025-4802, CVE-2025-5702, CVE-2025-8058, CVE-2026-0915), python3-setuptools-53.0.0-10.el9_1.1 (CVE-2025-47273), perl-File-Copy-2.34-479.el9 (CVE-2023-47038, CVE-2025-40909), python3-requests-2.25.1-6.el9 (CVE-2023-32681, CVE-2024-35195, CVE-2024-47081), perl-POSIX-1.94-479.el9 (CVE-2023-47038, CVE-2025-40909), libfdisk-2.37.4-9.el9 (CVE-2025-14104), sqlite-3.34.1-6.el9_1 (CVE-2023-7104), perl-overloading-0.02-479.el9 (CVE-2023-47038, CVE-2025-40909), perl-File-stat-1.09-479.el9 (CVE-2023-47038, CVE-2025-40909), perl-File-Basename-2.85-479.el9 (CVE-2023-47038, CVE-2025-40909), glib2-devel-2.68.4-5.el9 (CVE-2024-34397, CVE-2024-52533, CVE-2025-13601, CVE-2025-4373), glibc-gconv-extra-2.34-40.el9_1.1 (CVE-2023-4527, CVE-2023-4806, CVE-2023-4813, CVE-2024-33600, CVE-2025-0395, CVE-2025-4802, CVE-2025-5702, CVE-2025-8058), libcurl-minimal-7.76.1-19.el9_1.1 (CVE-2023-23916, CVE-2023-27535, CVE-2023-27536, CVE-2023-27538, CVE-2023-28321, CVE-2023-46218, CVE-2024-2398, CVE-2025-9086), libxslt-1.1.34-9.el9 (CVE-2023-40403), libcap-2.48-8.el9 (CVE-2023-2603), libX11-1.7.0-7.el9 (CVE-2023-3138, CVE-2023-43785, CVE-2023-43786, CVE-2023-43787), perl-File-Find-1.37-479.el9 (CVE-2023-47038, CVE-2025-40909), libXpm-3.5.13-8.el9_1 (CVE-2023-43788, CVE-2023-43789), openssh-clients-8.7p1-24.el9_1 (CVE-2023-25136, CVE-2023-48795, CVE-2023-51385, CVE-2024-6409, CVE-2025-26465, CVE-2025-61984, CVE-2025-61985), libX11-xcb-1.7.0-7.el9 (CVE-2023-3138, CVE-2023-43785, CVE-2023-43786, CVE-2023-43787), expat-2.4.9-1.el9_1.1 (CVE-2023-52425, CVE-2024-28757, CVE-2024-45490, CVE-2024-45491, CVE-2024-45492, CVE-2024-50602, CVE-2024-8176), libjpeg-turbo-devel-2.0.90-5.el9 (CVE-2021-29390, CVE-2021-46822), libX11-devel-1.7.0-7.el9 (CVE-2023-3138, CVE-2023-43785, CVE-2023-43786, CVE-2023-43787), harfbuzz-devel-2.7.4-8.el9 (CVE-2023-25193), delve-1.8.3-1.el9 (CVE-2024-45336, CVE-2025-22866, CVE-2025-58183, CVE-2025-68121), libicu-devel-67.1-9.el9 (CVE-2025-5222), libstdc++-devel-11.3.1-2.1.el9 (CVE-2020-11023), go-toolset-1.18.9-1.el9_1 (CVE-2023-29402, CVE-2023-39326, CVE-2023-45285, CVE-2023-45289, CVE-2023-45290, CVE-2024-24783, CVE-2024-24784, CVE-2024-24785, CVE-2024-24789, CVE-2024-24790, CVE-2024-24791, CVE-2024-34155, CVE-2024-34158, CVE-2024-45336, CVE-2024-9355, CVE-2025-22866, CVE-2025-22871, CVE-2025-4673, CVE-2025-47906, CVE-2025-47907, CVE-2025-58183, CVE-2025-61728, CVE-2025-68121), pam-1.5.1-12.el9 (CVE-2024-10041, CVE-2024-22365), nodejs-libs-1:16.18.1-3.el9_1 (CVE-2021-35065, CVE-2022-25881, CVE-2022-4904, CVE-2023-23918, CVE-2023-23936, CVE-2023-30588, CVE-2023-30589, CVE-2023-30590, CVE-2023-31130, CVE-2023-31147, CVE-2023-32559, CVE-2024-22025, CVE-2024-27982, CVE-2024-28182, CVE-2025-22150, CVE-2025-23085, CVE-2025-31498, CVE-2025-55132, CVE-2025-59466, CVE-2026-1525, CVE-2026-1527, CVE-2026-21637, CVE-2026-21711, CVE-2026-21712, CVE-2026-21713, CVE-2026-21714, CVE-2026-21717, CVE-2026-25547, CVE-2026-2581, CVE-2026-26996, CVE-2026-27904), dbus-common-1:1.12.20-7.el9_1 (CVE-2023-34969), perl-mro-1.23-479.el9 (CVE-2023-47038, CVE-2025-40909), glibc-langpack-en-2.34-40.el9_1.1 (CVE-2023-4527, CVE-2023-4806, CVE-2023-4813, CVE-2024-33600, CVE-2025-0395, CVE-2025-4802, CVE-2025-5702, CVE-2025-8058), git-2.31.1-3.el9_1 (CVE-2022-24765, CVE-2022-29187, CVE-2022-39253, CVE-2022-39260, CVE-2023-22490, CVE-2023-23946, CVE-2024-32465, CVE-2024-52005, CVE-2025-27613, CVE-2025-27614), perl-libs-4:5.32.1-479.el9 (CVE-2023-47038, CVE-2025-40909), rpm-sign-libs-4.16.1.3-19.el9_1 (CVE-2021-35937, CVE-2021-35938, CVE-2021-35939), util-linux-2.37.4-9.el9 (CVE-2025-14104), glibc-locale-source-2.34-40.el9_1.1 (CVE-2023-4527, CVE-2023-4806, CVE-2023-4813, CVE-2024-33600, CVE-2025-0395, CVE-2025-4802, CVE-2025-5702, CVE-2025-8058), util-linux-core-2.37.4-9.el9 (CVE-2025-14104), perl-SelectSaver-1.02-479.el9 (CVE-2023-47038, CVE-2025-40909), libxml2-2.9.13-3.el9_1 (CVE-2022-49043, CVE-2023-28484, CVE-2023-29469, CVE-2023-39615, CVE-2024-25062, CVE-2025-32414, CVE-2025-32415, CVE-2025-6021, CVE-2025-9714), glibc-devel-2.34-40.el9_1.1 (CVE-2023-4527, CVE-2023-4806, CVE-2023-4813, CVE-2024-33600, CVE-2025-0395, CVE-2025-4802, CVE-2025-5702, CVE-2025-8058), less-590-1.el9_0 (CVE-2022-46663, CVE-2022-48624), binutils-gold-2.35.2-24.el9 (CVE-2022-4285, CVE-2025-11083), libxml2-devel-2.9.13-3.el9_1 (CVE-2022-49043, CVE-2023-28484, CVE-2023-29469, CVE-2023-39615, CVE-2024-25062, CVE-2025-32414, CVE-2025-32415, CVE-2025-6021, CVE-2025-9714), perl-NDBM_File-1.15-479.el9 (CVE-2023-47038, CVE-2025-40909), glib2-2.68.4-5.el9 (CVE-2024-34397, CVE-2024-52533, CVE-2025-13601, CVE-2025-4373), openssh-8.7p1-24.el9_1 (CVE-2023-25136, CVE-2023-48795, CVE-2023-51385, CVE-2024-6409, CVE-2025-26465, CVE-2025-61984, CVE-2025-61985), perl-HTTP-Tiny-0.076-460.el9 (CVE-2023-31486), libeconf-0.4.1-2.el9 (CVE-2023-22652), perl-File-Compare-1.100.600-479.el9 (CVE-2023-47038, CVE-2025-40909), libblkid-2.37.4-9.el9 (CVE-2025-14104), bzip2-devel-1.0.8-8.el9 (CVE-2019-12900), libicu-67.1-9.el9 (CVE-2025-5222), perl-lib-0.65-479.el9 (CVE-2023-47038, CVE-2025-40909), perl-Errno-1.30-479.el9 (CVE-2023-47038, CVE-2025-40909), libtiff-devel-4.4.0-5.el9_1 (CVE-2017-17095, CVE-2022-3570, CVE-2022-3597, CVE-2022-3598, CVE-2022-3599, CVE-2022-3626, CVE-2022-3627, CVE-2022-3970, CVE-2022-40090, CVE-2022-4645, CVE-2022-48281, CVE-2023-0795, CVE-2023-0796, CVE-2023-0797, CVE-2023-0798, CVE-2023-0799, CVE-2023-0800, CVE-2023-0801, CVE-2023-0802, CVE-2023-0803, CVE-2023-0804, CVE-2023-26965, CVE-2023-26966, CVE-2023-2731, CVE-2023-30086, CVE-2023-30774, CVE-2023-30775, CVE-2023-3316, CVE-2023-3576, CVE-2023-3618, CVE-2023-40745, CVE-2023-41175, CVE-2023-52355, CVE-2023-52356, CVE-2024-7006), pixman-0.40.0-5.el9 (CVE-2022-44638), dbus-libs-1:1.12.20-7.el9_1 (CVE-2023-34969), nodejs-full-i18n-1:16.18.1-3.el9_1 (CVE-2021-35065, CVE-2022-25881, CVE-2022-25883, CVE-2022-3517, CVE-2022-43548, CVE-2022-4904, CVE-2023-23918, CVE-2023-23919, CVE-2023-23936, CVE-2023-30588, CVE-2023-30589, CVE-2023-30590, CVE-2023-31130, CVE-2023-31147, CVE-2023-32559, CVE-2023-38552, CVE-2023-46809, CVE-2024-21890, CVE-2024-21891, CVE-2024-22020, CVE-2024-22025, CVE-2024-27982, CVE-2024-28182, CVE-2024-28863, CVE-2025-22150, CVE-2025-23085, CVE-2025-23167, CVE-2025-31498, CVE-2025-55132, CVE-2025-59466, CVE-2026-1525, CVE-2026-1527, CVE-2026-21637, CVE-2026-21711, CVE-2026-21712, CVE-2026-21713, CVE-2026-21714, CVE-2026-21717, CVE-2026-25547, CVE-2026-2581, CVE-2026-26996, CVE-2026-27904), libpng-2:1.6.37-12.el9 (CVE-2026-22695, CVE-2026-22801), python3-libs-3.9.14-1.el9_1.2 (CVE-2023-27043, CVE-2024-0450, CVE-2024-11168, CVE-2024-6232, CVE-2024-6923, CVE-2024-8088, CVE-2024-9287, CVE-2025-0938, CVE-2025-12084, CVE-2025-15366, CVE-2025-15367, CVE-2025-4330, CVE-2025-4435, CVE-2025-6069, CVE-2025-8194, CVE-2025-8291, CVE-2026-0865, CVE-2026-1299), perl-Symbol-1.08-479.el9 (CVE-2023-47038, CVE-2025-40909), harfbuzz-icu-2.7.4-8.el9 (CVE-2023-25193), golang-1.18.9-1.el9_1 (CVE-2023-24532, CVE-2023-24534, CVE-2023-24536, CVE-2023-24537, CVE-2023-24538, CVE-2023-24539, CVE-2023-29400, CVE-2023-29402, CVE-2023-29406, CVE-2023-29409, CVE-2023-39326, CVE-2023-45285, CVE-2023-45289, CVE-2023-45290, CVE-2024-24783, CVE-2024-24784, CVE-2024-24785, CVE-2024-24789, CVE-2024-24790, CVE-2024-24791, CVE-2024-34155, CVE-2024-34158, CVE-2024-45336, CVE-2024-9355, CVE-2025-22866, CVE-2025-22871, CVE-2025-4673, CVE-2025-47906, CVE-2025-47907, CVE-2025-58183, CVE-2025-61728, CVE-2025-68121), perl-subs-1.03-479.el9 (CVE-2023-47038, CVE-2025-40909), libmount-devel-2.37.4-9.el9 (CVE-2025-14104), bzip2-1.0.8-8.el9 (CVE-2019-12900), perl-AutoLoader-5.74-479.el9 (CVE-2023-47038, CVE-2025-40909), tpm2-tss-3.0.3-8.el9 (CVE-2023-22745), ncurses-base-6.2-8.20210508.el9 (CVE-2023-29491), libtasn1-4.16.0-8.el9_1 (CVE-2024-12133), python3-rpm-4.16.1.3-19.el9_1 (CVE-2021-35937, CVE-2021-35938, CVE-2021-35939), libxslt-devel-1.1.34-9.el9 (CVE-2023-40403), systemd-pam-250-12.el9_1.3 (CVE-2023-7008, CVE-2025-4598), tar-2:1.34-6.el9_1 (CVE-2025-45582), npm-1:8.19.2-1.16.18.1.3.el9_1 (CVE-2021-35065, CVE-2022-25881, CVE-2022-25883, CVE-2022-3517, CVE-2022-43548, CVE-2022-4904, CVE-2023-23918, CVE-2023-23919, CVE-2023-23936, CVE-2023-30588, CVE-2023-30589, CVE-2023-30590, CVE-2023-31130, CVE-2023-31147, CVE-2023-32559, CVE-2023-38552, CVE-2023-46809, CVE-2024-21890, CVE-2024-21891, CVE-2024-22020, CVE-2024-22025, CVE-2024-27982, CVE-2024-28182, CVE-2024-28863, CVE-2025-22150, CVE-2025-23085, CVE-2025-23167, CVE-2025-31498, CVE-2025-55132, CVE-2025-59466, CVE-2026-1525, CVE-2026-21637, CVE-2026-25547, CVE-2026-26996, CVE-2026-27904), emacs-filesystem-1:27.2-6.el9 (CVE-2022-45939, CVE-2022-48337, CVE-2022-48338, CVE-2022-48339, CVE-2024-30203, CVE-2024-30204, CVE-2024-30205, CVE-2024-39331, CVE-2024-53920), python3-setuptools-wheel-53.0.0-10.el9_1.1 (CVE-2025-47273), vim-filesystem-2:8.2.2637-20.el9_1 (CVE-2025-53905), libarchive-3.5.3-3.el9 (CVE-2025-25724, CVE-2026-5121), python3-urllib3-1.26.5-3.el9 (CVE-2023-43804, CVE-2023-45803, CVE-2024-37891), curl-minimal-7.76.1-19.el9_1.1 (CVE-2023-23916, CVE-2023-27535, CVE-2023-27536, CVE-2023-27538, CVE-2023-28321, CVE-2023-46218, CVE-2024-2398, CVE-2025-9086), qt5-srpm-macros-5.15.3-1.el9 (CVE-2023-33285, CVE-2023-34410), ncurses-6.2-8.20210508.el9 (CVE-2023-29491), rpm-libs-4.16.1.3-19.el9_1 (CVE-2021-35937, CVE-2021-35938, CVE-2021-35939), libsmartcols-2.37.4-9.el9 (CVE-2025-14104), golang-src-1.18.9-1.el9_1 (CVE-2023-24532, CVE-2023-24534, CVE-2023-24536, CVE-2023-24537, CVE-2023-24538, CVE-2023-24539, CVE-2023-29400, CVE-2023-29402, CVE-2023-29406, CVE-2023-29409, CVE-2023-39326, CVE-2023-45285, CVE-2023-45289, CVE-2023-45290, CVE-2024-24783, CVE-2024-24784, CVE-2024-24785, CVE-2024-24789, CVE-2024-24790, CVE-2024-24791, CVE-2024-34155, CVE-2024-34158, CVE-2024-45336, CVE-2024-9355, CVE-2025-22866, CVE-2025-22871, CVE-2025-4673, CVE-2025-47906, CVE-2025-47907, CVE-2025-58183, CVE-2025-61728, CVE-2025-68121), dmidecode-1:3.3-7.el9 (CVE-2023-30630), openssl-1:3.0.1-47.el9_1 (CVE-2023-0466, CVE-2023-2650, CVE-2023-5363, CVE-2024-6119, CVE-2025-11187, CVE-2025-69419, CVE-2025-9230), systemd-rpm-macros-250-12.el9_1.3 (CVE-2023-7008, CVE-2025-4598), libnghttp2-1.43.0-5.el9 (CVE-2024-28182), rpm-build-libs-4.16.1.3-19.el9_1 (CVE-2021-35937, CVE-2021-35938, CVE-2021-35939), perl-B-1.80-479.el9 (CVE-2023-47038, CVE-2025-40909), sqlite-libs-3.34.1-6.el9_1 (CVE-2023-7104), rsync-3.2.3-18.el9 (CVE-2024-12087, CVE-2024-12088, CVE-2024-12747, CVE-2025-10158), libpng-devel-2:1.6.37-12.el9 (CVE-2026-22695, CVE-2026-22801), libpq-13.5-1.el9 (CVE-2025-12818), go-srpm-macros-3.0.9-9.el9 (CVE-2025-47906), gcc-plugin-annobin-11.3.1-2.1.el9 (CVE-2020-11023), bzip2-libs-1.0.8-8.el9 (CVE-2019-12900), glibc-common-2.34-40.el9_1.1 (CVE-2023-4527, CVE-2023-4806, CVE-2023-4813, CVE-2024-33600, CVE-2025-0395, CVE-2025-4802, CVE-2025-5702, CVE-2025-8058), nodejs-docs-1:16.18.1-3.el9_1 (CVE-2021-35065, CVE-2022-25881, CVE-2022-25883, CVE-2022-3517, CVE-2022-43548, CVE-2022-4904, CVE-2023-23918, CVE-2023-23919, CVE-2023-23936, CVE-2023-30588, CVE-2023-30589, CVE-2023-30590, CVE-2023-31130, CVE-2023-31147, CVE-2023-32559, CVE-2023-38552, CVE-2023-46809, CVE-2024-21890, CVE-2024-21891, CVE-2024-22020, CVE-2024-22025, CVE-2024-27982, CVE-2024-28182, CVE-2024-28863, CVE-2025-22150, CVE-2025-23085, CVE-2025-23167, CVE-2025-31498, CVE-2025-55132, CVE-2025-59466, CVE-2026-1525, CVE-2026-1527, CVE-2026-21637, CVE-2026-21711, CVE-2026-21712, CVE-2026-21713, CVE-2026-21714, CVE-2026-21717, CVE-2026-25547, CVE-2026-2581, CVE-2026-26996, CVE-2026-27904), golang-bin-1.18.9-1.el9_1 (CVE-2023-24532, CVE-2023-24534, CVE-2023-24536, CVE-2023-24537, CVE-2023-24538, CVE-2023-24539, CVE-2023-29400, CVE-2023-29402, CVE-2023-29406, CVE-2023-29409, CVE-2023-39326, CVE-2023-45285, CVE-2023-45289, CVE-2023-45290, CVE-2024-24783, CVE-2024-24784, CVE-2024-24785, CVE-2024-24789, CVE-2024-24790, CVE-2024-24791, CVE-2024-34155, CVE-2024-34158, CVE-2024-45336, CVE-2024-9355, CVE-2025-22866, CVE-2025-22871, CVE-2025-4673, CVE-2025-47906, CVE-2025-47907, CVE-2025-58183, CVE-2025-61728, CVE-2025-68121), libtiff-4.4.0-5.el9_1 (CVE-2017-17095, CVE-2022-3570, CVE-2022-3597, CVE-2022-3598, CVE-2022-3599, CVE-2022-3626, CVE-2022-3627, CVE-2022-3970, CVE-2022-40090, CVE-2022-4645, CVE-2022-48281, CVE-2023-0795, CVE-2023-0796, CVE-2023-0797, CVE-2023-0798, CVE-2023-0799, CVE-2023-0800, CVE-2023-0801, CVE-2023-0802, CVE-2023-0803, CVE-2023-0804, CVE-2023-26965, CVE-2023-26966, CVE-2023-2731, CVE-2023-30086, CVE-2023-30774, CVE-2023-30775, CVE-2023-3316, CVE-2023-3576, CVE-2023-3618, CVE-2023-40745, CVE-2023-41175, CVE-2023-52355, CVE-2023-52356, CVE-2024-7006), git-core-doc-2.31.1-3.el9_1 (CVE-2022-24765, CVE-2022-29187, CVE-2022-39253, CVE-2022-39260, CVE-2023-22490, CVE-2023-23946, CVE-2024-32465, CVE-2024-52005, CVE-2025-27613, CVE-2025-27614), libmount-2.37.4-9.el9 (CVE-2025-14104), nodejs-1:16.18.1-3.el9_1 (CVE-2021-35065, CVE-2022-25881, CVE-2022-25883, CVE-2022-3517, CVE-2022-43548, CVE-2022-4904, CVE-2023-23918, CVE-2023-23919, CVE-2023-23936, CVE-2023-30588, CVE-2023-30589, CVE-2023-30590, CVE-2023-31130, CVE-2023-31147, CVE-2023-32559, CVE-2023-38552, CVE-2023-46809, CVE-2024-21890, CVE-2024-21891, CVE-2024-22020, CVE-2024-22025, CVE-2024-27982, CVE-2024-28182, CVE-2024-28863, CVE-2025-22150, CVE-2025-23085, CVE-2025-23167, CVE-2025-31498, CVE-2025-55132, CVE-2025-59466, CVE-2026-1525, CVE-2026-1527, CVE-2026-21637, CVE-2026-21711, CVE-2026-21712, CVE-2026-21713, CVE-2026-21714, CVE-2026-21717, CVE-2026-25547, CVE-2026-2581, CVE-2026-26996, CVE-2026-27904), openssl-devel-1:3.0.1-47.el9_1 (CVE-2023-0466, CVE-2023-2650, CVE-2023-5363, CVE-2024-6119, CVE-2025-11187, CVE-2025-69419, CVE-2025-9230), perl-Getopt-Std-1.12-479.el9 (CVE-2023-47038, CVE-2025-40909), perl-Fcntl-1.13-479.el9 (CVE-2023-47038, CVE-2025-40909), gmp-1:6.2.0-10.el9 (CVE-2021-43618), libstdc++-11.3.1-2.1.el9 (CVE-2020-11023), glibc-headers-2.34-40.el9_1.1 (CVE-2023-4527, CVE-2023-4806, CVE-2023-4813, CVE-2024-33600, CVE-2025-0395, CVE-2025-4802, CVE-2025-5702, CVE-2025-8058), systemd-libs-250-12.el9_1.3 (CVE-2023-7008, CVE-2025-4598), python3-3.9.14-1.el9_1.2 (CVE-2023-27043, CVE-2024-0450, CVE-2024-11168, CVE-2024-6232, CVE-2024-6923, CVE-2024-8088, CVE-2024-9287, CVE-2025-0938, CVE-2025-12084, CVE-2025-15366, CVE-2025-15367, CVE-2025-4330, CVE-2025-4435, CVE-2025-6069, CVE-2025-8194, CVE-2025-8291, CVE-2026-0865, CVE-2026-1299), wget-1.21.1-7.el9 (CVE-2024-38428), bsdtar-3.5.3-3.el9 (CVE-2025-25724, CVE-2026-5121), vim-minimal-2:8.2.2637-20.el9_1 (CVE-2025-53905, CVE-2026-25749, CVE-2026-28421), krb5-libs-1.19.1-24.el9_1 (CVE-2020-17049, CVE-2023-36054, CVE-2024-26462, CVE-2024-37370, CVE-2024-37371, CVE-2025-24528, CVE-2025-3576), dbus-1:1.12.20-7.el9_1 (CVE-2023-34969), python3-idna-2.10-7.el9 (CVE-2024-3651), libgcrypt-1.10.0-8.el9_0 (CVE-2024-2236), openssl-libs-1:3.0.1-47.el9_1 (CVE-2023-0466, CVE-2023-2650, CVE-2023-5363, CVE-2024-6119, CVE-2025-11187, CVE-2025-69419, CVE-2025-9230), gcc-c++-11.3.1-2.1.el9 (CVE-2020-11023), binutils-2.35.2-24.el9 (CVE-2022-4285, CVE-2025-11083), sqlite-devel-3.34.1-6.el9_1 (CVE-2023-7104), libcurl-devel-7.76.1-19.el9_1.1 (CVE-2023-23916, CVE-2023-27535, CVE-2023-27536, CVE-2023-27538, CVE-2023-28321, CVE-2023-46218, CVE-2024-2398, CVE-2025-9086), libjpeg-turbo-2.0.90-5.el9 (CVE-2021-29390, CVE-2021-46822), harfbuzz-2.7.4-8.el9 (CVE-2023-25193), gnutls-3.7.6-12.el9_0 (CVE-2023-0361, CVE-2023-5981, CVE-2024-0553, CVE-2024-0567, CVE-2024-12243, CVE-2024-28834, CVE-2024-28835, CVE-2025-14831, CVE-2025-32988, CVE-2025-32989, CVE-2025-32990, CVE-2025-6395), gcc-11.3.1-2.1.el9 (CVE-2020-11023), libgomp-11.3.1-2.1.el9 (CVE-2020-11023), ncurses-libs-6.2-8.20210508.el9 (CVE-2023-29491), systemd-250-12.el9_1.3 (CVE-2023-7008, CVE-2025-4598), git-core-2.31.1-3.el9_1 (CVE-2022-24765, CVE-2022-29187, CVE-2022-39253, CVE-2022-39260, CVE-2023-22490, CVE-2023-23946, CVE-2024-32465, CVE-2024-52005, CVE-2025-27613, CVE-2025-27614), perl-FileHandle-2.03-479.el9 (CVE-2023-47038, CVE-2025-40909), libXpm-devel-3.5.13-8.el9_1 (CVE-2023-43788, CVE-2023-43789), libuuid-2.37.4-9.el9 (CVE-2025-14104), perl-IPC-Open3-1.21-479.el9 (CVE-2023-47038, CVE-2025-40909), libX11-common-1.7.0-7.el9 (CVE-2023-3138, CVE-2023-43785, CVE-2023-43786, CVE-2023-43787), libpq-devel-13.5-1.el9 (CVE-2025-12818), perl-base-2.27-479.el9 (CVE-2023-47038, CVE-2025-40909), perl-Git-2.31.1-3.el9_1 (CVE-2022-24765, CVE-2022-29187, CVE-2022-39253, CVE-2022-39260, CVE-2023-22490, CVE-2023-23946, CVE-2024-32465, CVE-2024-52005, CVE-2025-27613, CVE-2025-27614), libgcc-11.3.1-2.1.el9 (CVE-2020-11023), perl-interpreter-4:5.32.1-479.el9 (CVE-2023-47038, CVE-2025-40909), perl-Class-Struct-0.66-479.el9 (CVE-2023-47038, CVE-2025-40909), libblkid-devel-2.37.4-9.el9 (CVE-2025-14104), glibc-minimal-langpack-2.34-40.el9_1.1 (CVE-2023-4527, CVE-2023-4806, CVE-2023-4813, CVE-2024-33600, CVE-2025-0395, CVE-2025-4802, CVE-2025-5702, CVE-2025-8058), rpm-4.16.1.3-19.el9_1 (CVE-2021-35937, CVE-2021-35938, CVE-2021-35939), perl-IO-1.43-479.el9 (CVE-2023-47038, CVE-2025-40909), perl-vars-1.05-479.el9 (CVE-2023-47038, CVE-2025-40909)&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;name&#34;: &#34;clair_medium_vulnerabilities&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;url&#34;: &#34;https://access.redhat.com/articles/red_hat_vulnerability_tutorial&#34;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;},&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;vulnerabilities_number&#34;: 837&#xA;&#x9;&#x9;&#x9;&#x9;}&#xA;&#x9;&#x9;&#x9;},&#xA;&#x9;&#x9;&#x9;{&#xA;&#x9;&#x9;&#x9;&#x9;&#34;msg&#34;: &#34;Found packages with unpatched medium vulnerabilities. These vulnerabilities don&#39;t have a known fix at this time.&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#34;metadata&#34;: {&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;details&#34;: {&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;description&#34;: &#34;Vulnerabilities found: glibc-2.34-40.el9_1.1 (CVE-2026-4046, CVE-2026-4437), libfdisk-2.37.4-9.el9 (CVE-2026-27456), glib2-devel-2.68.4-5.el9 (CVE-2025-14087, CVE-2025-14512, CVE-2026-1484, CVE-2026-1489), glibc-gconv-extra-2.34-40.el9_1.1 (CVE-2026-4046, CVE-2026-4437), libcurl-minimal-7.76.1-19.el9_1.1 (CVE-2025-13034, CVE-2025-14017, CVE-2026-1965, CVE-2026-3783, CVE-2026-3784, CVE-2026-3805), libxslt-1.1.34-9.el9 (CVE-2025-10911), libX11-1.7.0-7.el9 (CVE-2022-3554), xz-libs-5.2.5-8.el9_0 (CVE-2026-34743), openssh-clients-8.7p1-24.el9_1 (CVE-2023-51767, CVE-2025-32728, CVE-2026-35414), libX11-xcb-1.7.0-7.el9 (CVE-2022-3554), expat-2.4.9-1.el9_1.1 (CVE-2026-32776, CVE-2026-32777, CVE-2026-32778), libX11-devel-1.7.0-7.el9 (CVE-2022-3554), harfbuzz-devel-2.7.4-8.el9 (CVE-2026-22693), openldap-compat-2.6.2-3.el9 (CVE-2026-22185), go-toolset-1.18.9-1.el9_1 (CVE-2020-28362, CVE-2021-3115, CVE-2021-42574, CVE-2022-1705, CVE-2022-1962, CVE-2022-28131, CVE-2022-30630, CVE-2022-30631, CVE-2022-30632, CVE-2022-30633, CVE-2022-30635, CVE-2022-32148, CVE-2023-39323, CVE-2025-22870, CVE-2025-22873, CVE-2025-47912, CVE-2025-58190, CVE-2025-61724, CVE-2025-61727, CVE-2025-61728, CVE-2025-68119, CVE-2025-68121, CVE-2026-27142, CVE-2026-27143, CVE-2026-27144, CVE-2026-32281, CVE-2026-32282, CVE-2026-32288, CVE-2026-32289, CVE-2026-33809), nodejs-libs-1:16.18.1-3.el9_1 (CVE-2021-27290, CVE-2021-3807, CVE-2022-25883, CVE-2023-38552, CVE-2023-46809, CVE-2024-24806, CVE-2025-29087, CVE-2025-59464, CVE-2025-62408, CVE-2025-64118, CVE-2025-64756, CVE-2025-7458, CVE-2026-1527, CVE-2026-21712, CVE-2026-21713, CVE-2026-21714, CVE-2026-21717, CVE-2026-25547, CVE-2026-2581, CVE-2026-27903, CVE-2026-27904, CVE-2026-33671, CVE-2026-33672), glibc-langpack-en-2.34-40.el9_1.1 (CVE-2026-4046, CVE-2026-4437), fontconfig-devel-2.14.0-2.el9_1 (CVE-2026-34085), git-2.31.1-3.el9_1 (CVE-2025-48386), util-linux-2.37.4-9.el9 (CVE-2026-27456), glibc-locale-source-2.34-40.el9_1.1 (CVE-2026-4046, CVE-2026-4437), util-linux-core-2.37.4-9.el9 (CVE-2026-27456), libxml2-2.9.13-3.el9_1 (CVE-2026-0990, CVE-2026-1757), p11-kit-trust-0.24.1-2.el9 (CVE-2026-2100), glibc-devel-2.34-40.el9_1.1 (CVE-2026-4046, CVE-2026-4437), binutils-gold-2.35.2-24.el9 (CVE-2021-20197, CVE-2021-45078, CVE-2025-11081, CVE-2025-11082, CVE-2025-5245, CVE-2025-7545, CVE-2026-4647), libxml2-devel-2.9.13-3.el9_1 (CVE-2026-0990, CVE-2026-1757), glib2-2.68.4-5.el9 (CVE-2025-14087, CVE-2025-14512, CVE-2026-1484, CVE-2026-1489), openssh-8.7p1-24.el9_1 (CVE-2023-51767, CVE-2025-32728, CVE-2026-35414), libblkid-2.37.4-9.el9 (CVE-2026-27456), freetype-2.10.4-9.el9 (CVE-2026-23865), freetype-devel-2.10.4-9.el9 (CVE-2026-23865), libtiff-devel-4.4.0-5.el9_1 (CVE-2023-25433, CVE-2023-25434, CVE-2023-25435, CVE-2023-3164, CVE-2023-6277, CVE-2025-61143, CVE-2025-61144, CVE-2025-61145, CVE-2025-8851), nodejs-full-i18n-1:16.18.1-3.el9_1 (CVE-2021-27290, CVE-2021-3807, CVE-2022-25883, CVE-2023-38552, CVE-2023-46809, CVE-2024-24806, CVE-2025-29087, CVE-2025-59464, CVE-2025-62408, CVE-2025-64118, CVE-2025-64756, CVE-2025-7458, CVE-2026-1527, CVE-2026-21712, CVE-2026-21713, CVE-2026-21714, CVE-2026-21717, CVE-2026-25547, CVE-2026-2581, CVE-2026-27903, CVE-2026-27904, CVE-2026-33671, CVE-2026-33672), libpng-2:1.6.37-12.el9 (CVE-2025-28164, CVE-2025-64505, CVE-2025-64506, CVE-2026-33416, CVE-2026-33636, CVE-2026-34757), python3-libs-3.9.14-1.el9_1.2 (CVE-2025-11468, CVE-2025-12781, CVE-2025-13837, CVE-2025-15282, CVE-2025-4516, CVE-2026-0672, CVE-2026-1502, CVE-2026-3644, CVE-2026-4224, CVE-2026-5713), harfbuzz-icu-2.7.4-8.el9 (CVE-2026-22693), golang-1.18.9-1.el9_1 (CVE-2021-3115, CVE-2021-42574, CVE-2023-39323, CVE-2025-22870, CVE-2025-22873, CVE-2025-47912, CVE-2025-58190, CVE-2025-61724, CVE-2025-61727, CVE-2025-68119, CVE-2026-27142, CVE-2026-27143, CVE-2026-27144, CVE-2026-32281, CVE-2026-32282, CVE-2026-32288, CVE-2026-32289, CVE-2026-33809), libmount-devel-2.37.4-9.el9 (CVE-2026-27456), gdb-headless-10.2-10.el9 (CVE-2025-11081, CVE-2025-11082, CVE-2025-11083, CVE-2025-5245, CVE-2026-4647), tpm2-tss-3.0.3-8.el9 (CVE-2024-29040), openldap-2.6.2-3.el9 (CVE-2026-22185), gnupg2-2.3.3-2.el9_0 (CVE-2025-68972), libxslt-devel-1.1.34-9.el9 (CVE-2025-10911), systemd-pam-250-12.el9_1.3 (CVE-2026-29111, CVE-2026-4105), tar-2:1.34-6.el9_1 (CVE-2025-64118, CVE-2026-33056, CVE-2026-5704), gdb-gdbserver-10.2-10.el9 (CVE-2025-11081, CVE-2025-11082, CVE-2025-11083, CVE-2025-5245, CVE-2026-4647), npm-1:8.19.2-1.16.18.1.3.el9_1 (CVE-2021-27290, CVE-2021-3807, CVE-2022-25883, CVE-2023-38552, CVE-2023-46809, CVE-2024-24806, CVE-2025-29087, CVE-2025-59464, CVE-2025-62408, CVE-2025-64118, CVE-2025-64756, CVE-2025-7458, CVE-2026-1527, CVE-2026-21712, CVE-2026-21713, CVE-2026-21714, CVE-2026-21717, CVE-2026-25547, CVE-2026-2581, CVE-2026-27903, CVE-2026-27904, CVE-2026-33671, CVE-2026-33672), llvm-libs-14.0.6-1.el9 (CVE-2026-27903), vim-filesystem-2:8.2.2637-20.el9_1 (CVE-2025-29768, CVE-2026-28418, CVE-2026-28419, CVE-2026-28420, CVE-2026-35177, CVE-2026-39881), libarchive-3.5.3-3.el9 (CVE-2023-30571, CVE-2025-60753, CVE-2026-4426, CVE-2026-5745), curl-minimal-7.76.1-19.el9_1.1 (CVE-2025-13034, CVE-2025-14017, CVE-2026-1965, CVE-2026-3783, CVE-2026-3784, CVE-2026-3805), qt5-srpm-macros-5.15.3-1.el9 (CVE-2021-38593, CVE-2023-24607, CVE-2025-5683), libsmartcols-2.37.4-9.el9 (CVE-2026-27456), golang-src-1.18.9-1.el9_1 (CVE-2021-3115, CVE-2021-42574, CVE-2023-39323, CVE-2025-22870, CVE-2025-22873, CVE-2025-47912, CVE-2025-58190, CVE-2025-61724, CVE-2025-61727, CVE-2025-68119, CVE-2026-27142, CVE-2026-27143, CVE-2026-27144, CVE-2026-32281, CVE-2026-32282, CVE-2026-32288, CVE-2026-32289, CVE-2026-33809), openssl-1:3.0.1-47.el9_1 (CVE-2026-28390, CVE-2026-31790), systemd-rpm-macros-250-12.el9_1.3 (CVE-2026-29111, CVE-2026-4105), python3-pip-wheel-21.2.3-6.el9 (CVE-2023-45803, CVE-2025-50181, CVE-2025-50182, CVE-2026-25645, CVE-2026-32284), coreutils-single-8.32-32.el9 (CVE-2025-5278), p11-kit-0.24.1-2.el9 (CVE-2026-2100), xz-devel-5.2.5-8.el9_0 (CVE-2026-34743), rsync-3.2.3-18.el9 (CVE-2024-12086), libpng-devel-2:1.6.37-12.el9 (CVE-2025-28164, CVE-2025-64505, CVE-2025-64506, CVE-2026-33416, CVE-2026-33636, CVE-2026-34757), libpq-13.5-1.el9 (CVE-2025-4207), go-srpm-macros-3.0.9-9.el9 (CVE-2024-8244, CVE-2026-32282), glibc-common-2.34-40.el9_1.1 (CVE-2026-4046, CVE-2026-4437), nodejs-docs-1:16.18.1-3.el9_1 (CVE-2021-27290, CVE-2021-3807, CVE-2022-25883, CVE-2023-38552, CVE-2023-46809, CVE-2024-24806, CVE-2025-29087, CVE-2025-59464, CVE-2025-62408, CVE-2025-64118, CVE-2025-64756, CVE-2025-7458, CVE-2026-1527, CVE-2026-21712, CVE-2026-21713, CVE-2026-21714, CVE-2026-21717, CVE-2026-25547, CVE-2026-2581, CVE-2026-27903, CVE-2026-27904, CVE-2026-33671, CVE-2026-33672), golang-bin-1.18.9-1.el9_1 (CVE-2021-3115, CVE-2021-42574, CVE-2023-39323, CVE-2025-22870, CVE-2025-22873, CVE-2025-47912, CVE-2025-58190, CVE-2025-61724, CVE-2025-61727, CVE-2025-68119, CVE-2026-27142, CVE-2026-27143, CVE-2026-27144, CVE-2026-32281, CVE-2026-32282, CVE-2026-32288, CVE-2026-32289, CVE-2026-33809), libtiff-4.4.0-5.el9_1 (CVE-2023-25433, CVE-2023-25434, CVE-2023-25435, CVE-2023-3164, CVE-2023-6277, CVE-2025-61143, CVE-2025-61144, CVE-2025-61145, CVE-2025-8851), git-core-doc-2.31.1-3.el9_1 (CVE-2025-48386), libmount-2.37.4-9.el9 (CVE-2026-27456), nodejs-1:16.18.1-3.el9_1 (CVE-2021-27290, CVE-2021-3807, CVE-2022-25883, CVE-2023-38552, CVE-2023-46809, CVE-2024-24806, CVE-2025-29087, CVE-2025-59464, CVE-2025-62408, CVE-2025-64118, CVE-2025-64756, CVE-2025-7458, CVE-2026-1527, CVE-2026-21712, CVE-2026-21713, CVE-2026-21714, CVE-2026-21717, CVE-2026-25547, CVE-2026-2581, CVE-2026-27903, CVE-2026-27904, CVE-2026-33671, CVE-2026-33672), openssl-devel-1:3.0.1-47.el9_1 (CVE-2026-28390, CVE-2026-31790), glibc-headers-2.34-40.el9_1.1 (CVE-2026-4046, CVE-2026-4437), gdb-10.2-10.el9 (CVE-2025-11081, CVE-2025-11082, CVE-2025-11083, CVE-2025-5245, CVE-2026-4647), systemd-libs-250-12.el9_1.3 (CVE-2026-29111, CVE-2026-4105), python3-3.9.14-1.el9_1.2 (CVE-2025-11468, CVE-2025-12781, CVE-2025-13837, CVE-2025-15282, CVE-2025-4516, CVE-2026-0672, CVE-2026-1502, CVE-2026-3644, CVE-2026-4224, CVE-2026-5713), wget-1.21.1-7.el9 (CVE-2021-31879, CVE-2024-10524), bsdtar-3.5.3-3.el9 (CVE-2023-30571, CVE-2025-60753, CVE-2026-4426, CVE-2026-5745), vim-minimal-2:8.2.2637-20.el9_1 (CVE-2025-29768, CVE-2026-28418, CVE-2026-28419, CVE-2026-28420, CVE-2026-35177, CVE-2026-39881), openssl-libs-1:3.0.1-47.el9_1 (CVE-2026-28390, CVE-2026-31790), binutils-2.35.2-24.el9 (CVE-2021-20197, CVE-2021-45078, CVE-2025-11081, CVE-2025-11082, CVE-2025-5245, CVE-2025-7545, CVE-2026-4647), libcurl-devel-7.76.1-19.el9_1.1 (CVE-2025-13034, CVE-2025-14017, CVE-2026-1965, CVE-2026-3783, CVE-2026-3784, CVE-2026-3805), harfbuzz-2.7.4-8.el9 (CVE-2026-22693), fontconfig-2.14.0-2.el9_1 (CVE-2026-34085), systemd-250-12.el9_1.3 (CVE-2026-29111, CVE-2026-4105), git-core-2.31.1-3.el9_1 (CVE-2025-48386), libuuid-2.37.4-9.el9 (CVE-2026-27456), libX11-common-1.7.0-7.el9 (CVE-2022-3554), xz-5.2.5-8.el9_0 (CVE-2026-34743), libpq-devel-13.5-1.el9 (CVE-2025-4207), perl-Git-2.31.1-3.el9_1 (CVE-2025-48386), libblkid-devel-2.37.4-9.el9 (CVE-2026-27456), glibc-minimal-langpack-2.34-40.el9_1.1 (CVE-2026-4046, CVE-2026-4437)&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;name&#34;: &#34;clair_unpatched_medium_vulnerabilities&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;url&#34;: &#34;https://access.redhat.com/articles/red_hat_vulnerability_tutorial&#34;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;},&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;vulnerabilities_number&#34;: 422&#xA;&#x9;&#x9;&#x9;&#x9;}&#xA;&#x9;&#x9;&#x9;},&#xA;&#x9;&#x9;&#x9;{&#xA;&#x9;&#x9;&#x9;&#x9;&#34;msg&#34;: &#34;Found packages with low/negligible vulnerabilities associated with RHSA fixes. Consider updating to a newer version of those packages, they may no longer be affected by the reported CVEs.&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#34;metadata&#34;: {&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;details&#34;: {&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;description&#34;: &#34;Vulnerabilities found: file-5.39-10.el9 (CVE-2022-48554), glibc-2.34-40.el9_1.1 (CVE-2024-33601, CVE-2024-33602, CVE-2025-15281, CVE-2026-0861), glib2-devel-2.68.4-5.el9 (CVE-2023-29499, CVE-2023-32611, CVE-2023-32665), glibc-gconv-extra-2.34-40.el9_1.1 (CVE-2024-33601, CVE-2024-33602), libcurl-minimal-7.76.1-19.el9_1.1 (CVE-2022-35252, CVE-2022-43552, CVE-2023-27533, CVE-2023-27534, CVE-2023-28322, CVE-2023-38546), libcap-2.48-8.el9 (CVE-2023-2602), delve-1.8.3-1.el9 (CVE-2024-45341), go-toolset-1.18.9-1.el9_1 (CVE-2024-45341), nodejs-libs-1:16.18.1-3.el9_1 (CVE-2023-23920, CVE-2023-24807, CVE-2023-31124, CVE-2024-25629, CVE-2025-23165, CVE-2026-21715, CVE-2026-21716), glibc-langpack-en-2.34-40.el9_1.1 (CVE-2024-33601, CVE-2024-33602), git-2.31.1-3.el9_1 (CVE-2023-25815, CVE-2024-32020, CVE-2024-32021, CVE-2024-50349, CVE-2024-52006, CVE-2025-46835), glibc-locale-source-2.34-40.el9_1.1 (CVE-2024-33601, CVE-2024-33602), file-libs-5.39-10.el9 (CVE-2022-48554), glibc-devel-2.34-40.el9_1.1 (CVE-2024-33601, CVE-2024-33602), glib2-2.68.4-5.el9 (CVE-2023-29499, CVE-2023-32611, CVE-2023-32665), procps-ng-3.3.17-8.el9 (CVE-2023-4016), shadow-utils-2:4.9-5.el9 (CVE-2023-4641, CVE-2024-56433), libtiff-devel-4.4.0-5.el9_1 (CVE-2023-6228), nodejs-full-i18n-1:16.18.1-3.el9_1 (CVE-2023-23920, CVE-2023-24807, CVE-2023-31124, CVE-2023-39333, CVE-2023-45143, CVE-2024-22018, CVE-2024-25629, CVE-2024-36137, CVE-2025-23165, CVE-2026-21715, CVE-2026-21716), python3-libs-3.9.14-1.el9_1.2 (CVE-2024-0397, CVE-2024-4032, CVE-2024-5642, CVE-2024-7592, CVE-2025-6075), golang-1.18.9-1.el9_1 (CVE-2024-45341), gdb-headless-10.2-10.el9 (CVE-2021-3826), ncurses-base-6.2-8.20210508.el9 (CVE-2022-29458), gdb-gdbserver-10.2-10.el9 (CVE-2021-3826), npm-1:8.19.2-1.16.18.1.3.el9_1 (CVE-2023-23920, CVE-2023-24807, CVE-2023-31124, CVE-2023-39333, CVE-2023-45143, CVE-2024-22018, CVE-2024-25629, CVE-2024-36137, CVE-2025-23165), vim-filesystem-2:8.2.2637-20.el9_1 (CVE-2021-3903, CVE-2023-4752), libarchive-3.5.3-3.el9 (CVE-2022-36227), curl-minimal-7.76.1-19.el9_1.1 (CVE-2022-35252, CVE-2022-43552, CVE-2023-27533, CVE-2023-27534, CVE-2023-28322, CVE-2023-38546), qt5-srpm-macros-5.15.3-1.el9 (CVE-2023-32573), ncurses-6.2-8.20210508.el9 (CVE-2022-29458), golang-src-1.18.9-1.el9_1 (CVE-2024-45341), openssl-1:3.0.1-47.el9_1 (CVE-2022-3358, CVE-2023-0464, CVE-2023-0465, CVE-2023-1255, CVE-2023-2975, CVE-2023-3446, CVE-2023-3817, CVE-2023-5678, CVE-2023-6129, CVE-2023-6237, CVE-2024-0727, CVE-2024-2511, CVE-2024-4603, CVE-2024-4741, CVE-2024-5535, CVE-2025-15468, CVE-2025-15469, CVE-2025-66199, CVE-2025-68160, CVE-2025-69418, CVE-2025-69420, CVE-2025-69421, CVE-2026-22795, CVE-2026-22796), libpq-13.5-1.el9 (CVE-2022-41862), glibc-common-2.34-40.el9_1.1 (CVE-2024-33601, CVE-2024-33602), nodejs-docs-1:16.18.1-3.el9_1 (CVE-2023-23920, CVE-2023-24807, CVE-2023-31124, CVE-2023-39333, CVE-2023-45143, CVE-2024-22018, CVE-2024-25629, CVE-2024-36137, CVE-2025-23165, CVE-2026-21715, CVE-2026-21716), golang-bin-1.18.9-1.el9_1 (CVE-2024-45341), libtiff-4.4.0-5.el9_1 (CVE-2023-6228), git-core-doc-2.31.1-3.el9_1 (CVE-2023-25815, CVE-2024-32020, CVE-2024-32021, CVE-2024-50349, CVE-2024-52006, CVE-2025-46835), nodejs-1:16.18.1-3.el9_1 (CVE-2023-23920, CVE-2023-24807, CVE-2023-31124, CVE-2023-39333, CVE-2023-45143, CVE-2024-22018, CVE-2024-25629, CVE-2024-36137, CVE-2025-23165, CVE-2026-21715, CVE-2026-21716), openssl-devel-1:3.0.1-47.el9_1 (CVE-2022-3358, CVE-2023-0464, CVE-2023-0465, CVE-2023-1255, CVE-2023-2975, CVE-2023-3446, CVE-2023-3817, CVE-2023-5678, CVE-2023-6129, CVE-2023-6237, CVE-2024-0727, CVE-2024-2511, CVE-2024-4603, CVE-2024-4741, CVE-2024-5535, CVE-2025-15468, CVE-2025-15469, CVE-2025-66199, CVE-2025-68160, CVE-2025-69418, CVE-2025-69420, CVE-2025-69421, CVE-2026-22795, CVE-2026-22796), glibc-headers-2.34-40.el9_1.1 (CVE-2024-33601, CVE-2024-33602), gdb-10.2-10.el9 (CVE-2021-3826), lua-libs-5.4.4-2.el9_1 (CVE-2022-28805), python3-3.9.14-1.el9_1.2 (CVE-2024-0397, CVE-2024-4032, CVE-2024-5642, CVE-2024-7592, CVE-2025-6075), bsdtar-3.5.3-3.el9 (CVE-2022-36227), vim-minimal-2:8.2.2637-20.el9_1 (CVE-2021-3903, CVE-2023-4752), krb5-libs-1.19.1-24.el9_1 (CVE-2024-26458, CVE-2024-26461), openssl-libs-1:3.0.1-47.el9_1 (CVE-2022-3358, CVE-2023-0464, CVE-2023-0465, CVE-2023-1255, CVE-2023-2975, CVE-2023-3446, CVE-2023-3817, CVE-2023-5678, CVE-2023-6129, CVE-2023-6237, CVE-2024-0727, CVE-2024-2511, CVE-2024-4603, CVE-2024-4741, CVE-2024-5535, CVE-2025-15468, CVE-2025-15469, CVE-2025-66199, CVE-2025-68160, CVE-2025-69418, CVE-2025-69420, CVE-2025-69421, CVE-2026-22795, CVE-2026-22796), libcurl-devel-7.76.1-19.el9_1.1 (CVE-2022-35252, CVE-2022-43552, CVE-2023-27533, CVE-2023-27534, CVE-2023-28322, CVE-2023-38546), gnutls-3.7.6-12.el9_0 (CVE-2025-9820), ncurses-libs-6.2-8.20210508.el9 (CVE-2022-29458), git-core-2.31.1-3.el9_1 (CVE-2023-25815, CVE-2024-32020, CVE-2024-32021, CVE-2024-50349, CVE-2024-52006, CVE-2025-46835), libpq-devel-13.5-1.el9 (CVE-2022-41862), perl-Git-2.31.1-3.el9_1 (CVE-2023-25815, CVE-2024-32020, CVE-2024-32021, CVE-2024-50349, CVE-2024-52006, CVE-2025-46835), glibc-minimal-langpack-2.34-40.el9_1.1 (CVE-2024-33601, CVE-2024-33602)&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;name&#34;: &#34;clair_low_vulnerabilities&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;url&#34;: &#34;https://access.redhat.com/articles/red_hat_vulnerability_tutorial&#34;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;},&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;vulnerabilities_number&#34;: 229&#xA;&#x9;&#x9;&#x9;&#x9;}&#xA;&#x9;&#x9;&#x9;},&#xA;&#x9;&#x9;&#x9;{&#xA;&#x9;&#x9;&#x9;&#x9;&#34;msg&#34;: &#34;Found packages with unpatched low/negligible vulnerabilities. These vulnerabilities don&#39;t have a known fix at this time.&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#34;metadata&#34;: {&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;details&#34;: {&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;description&#34;: &#34;Vulnerabilities found: cpp-11.3.1-2.1.el9 (CVE-2022-27943), glibc-2.34-40.el9_1.1 (CVE-2026-4438), unzip-6.0-56.el9 (CVE-2021-4217, CVE-2022-0529, CVE-2022-0530), sqlite-3.34.1-6.el9_1 (CVE-2024-0232, CVE-2025-70873), glib2-devel-2.68.4-5.el9 (CVE-2023-32636, CVE-2025-3360, CVE-2025-7039, CVE-2026-0988, CVE-2026-1485), glibc-gconv-extra-2.34-40.el9_1.1 (CVE-2026-4438), libcurl-minimal-7.76.1-19.el9_1.1 (CVE-2024-11053, CVE-2024-7264, CVE-2024-9681, CVE-2025-14524, CVE-2025-14819, CVE-2025-15079, CVE-2025-15224), libxslt-1.1.34-9.el9 (CVE-2025-11731), libX11-1.7.0-7.el9 (CVE-2022-3555), pkgconf-m4-1.7.3-9.el9 (CVE-2023-24056), openssh-clients-8.7p1-24.el9_1 (CVE-2026-35386, CVE-2026-35387, CVE-2026-35388), libX11-xcb-1.7.0-7.el9 (CVE-2022-3555), cmake-filesystem-3.20.2-7.el9 (CVE-2025-9301), expat-2.4.9-1.el9_1.1 (CVE-2025-66382, CVE-2026-24515, CVE-2026-41080), libX11-devel-1.7.0-7.el9 (CVE-2022-3555), elfutils-debuginfod-client-0.187-5.el9 (CVE-2024-25260, CVE-2025-1371, CVE-2025-1376, CVE-2025-1377), libstdc++-devel-11.3.1-2.1.el9 (CVE-2022-27943), go-toolset-1.18.9-1.el9_1 (CVE-2026-27138, CVE-2026-27139), nodejs-libs-1:16.18.1-3.el9_1 (CVE-2023-39333, CVE-2023-45143, CVE-2024-21538, CVE-2025-47279, CVE-2025-5889, CVE-2025-70873, CVE-2026-21715, CVE-2026-21716, CVE-2026-22036, CVE-2026-27171), glibc-langpack-en-2.34-40.el9_1.1 (CVE-2026-4438), pcre2-syntax-10.40-2.el9 (CVE-2022-41409), pcre2-10.40-2.el9 (CVE-2022-41409), glibc-locale-source-2.34-40.el9_1.1 (CVE-2026-4438), elfutils-default-yama-scope-0.187-5.el9 (CVE-2024-25260, CVE-2025-1371, CVE-2025-1376, CVE-2025-1377), pcre2-utf32-10.40-2.el9 (CVE-2022-41409), libxml2-2.9.13-3.el9_1 (CVE-2023-45322, CVE-2024-34459, CVE-2025-27113, CVE-2025-6170, CVE-2026-0989, CVE-2026-0992), pkgconf-1.7.3-9.el9 (CVE-2023-24056), glibc-devel-2.34-40.el9_1.1 (CVE-2026-4438), binutils-gold-2.35.2-24.el9 (CVE-2021-3826, CVE-2022-38533, CVE-2022-44840, CVE-2022-47007, CVE-2022-47008, CVE-2022-47010, CVE-2022-47011, CVE-2023-1972, CVE-2024-57360, CVE-2025-11412, CVE-2025-11413, CVE-2025-11414, CVE-2025-11494, CVE-2025-11495, CVE-2025-1150, CVE-2025-1151, CVE-2025-1152, CVE-2025-1153, CVE-2025-11839, CVE-2025-11840, CVE-2025-3198, CVE-2025-66861, CVE-2025-66862, CVE-2025-66863, CVE-2025-66864, CVE-2025-66865, CVE-2025-66866, CVE-2025-69644, CVE-2025-69645, CVE-2025-69646, CVE-2025-69647, CVE-2025-69648, CVE-2025-69649, CVE-2025-69650, CVE-2025-69651, CVE-2025-69652), libxml2-devel-2.9.13-3.el9_1 (CVE-2023-45322, CVE-2024-34459, CVE-2025-27113, CVE-2025-6170, CVE-2026-0989, CVE-2026-0992), pcre2-devel-10.40-2.el9 (CVE-2022-41409), glib2-2.68.4-5.el9 (CVE-2023-32636, CVE-2025-3360, CVE-2025-7039, CVE-2026-0988, CVE-2026-1485), openssh-8.7p1-24.el9_1 (CVE-2026-35386, CVE-2026-35387, CVE-2026-35388), libtiff-devel-4.4.0-5.el9_1 (CVE-2017-16232, CVE-2022-1056, CVE-2023-1916, CVE-2024-13978, CVE-2025-8961, CVE-2025-9165), nodejs-full-i18n-1:16.18.1-3.el9_1 (CVE-2023-39333, CVE-2023-45143, CVE-2024-21538, CVE-2025-47279, CVE-2025-5889, CVE-2025-70873, CVE-2026-21715, CVE-2026-21716, CVE-2026-22036, CVE-2026-27171), libpng-2:1.6.37-12.el9 (CVE-2022-3857), python3-libs-3.9.14-1.el9_1.2 (CVE-2025-1795, CVE-2026-2297, CVE-2026-3479), golang-1.18.9-1.el9_1 (CVE-2026-27138, CVE-2026-27139), gdb-headless-10.2-10.el9 (CVE-2022-47007, CVE-2022-47010, CVE-2022-47011, CVE-2024-57360, CVE-2025-11412, CVE-2025-11413, CVE-2025-11414, CVE-2025-11494, CVE-2025-11495, CVE-2025-1150, CVE-2025-1151, CVE-2025-1152, CVE-2025-1153, CVE-2025-11839, CVE-2025-11840, CVE-2025-3198, CVE-2025-66861, CVE-2025-66862, CVE-2025-66863, CVE-2025-66864, CVE-2025-66865, CVE-2025-66866, CVE-2025-69644, CVE-2025-69645, CVE-2025-69646, CVE-2025-69647, CVE-2025-69648, CVE-2025-69649, CVE-2025-69650, CVE-2025-69651, CVE-2025-69652), zlib-devel-1.2.11-35.el9_1 (CVE-2026-27171), ncurses-base-6.2-8.20210508.el9 (CVE-2023-50495), libtasn1-4.16.0-8.el9_1 (CVE-2025-13151), gnupg2-2.3.3-2.el9_0 (CVE-2022-3219, CVE-2025-30258, CVE-2026-24883), libxslt-devel-1.1.34-9.el9 (CVE-2025-11731), tar-2:1.34-6.el9_1 (CVE-2023-39804), gdb-gdbserver-10.2-10.el9 (CVE-2022-47007, CVE-2022-47010, CVE-2022-47011, CVE-2024-57360, CVE-2025-11412, CVE-2025-11413, CVE-2025-11414, CVE-2025-11494, CVE-2025-11495, CVE-2025-1150, CVE-2025-1151, CVE-2025-1152, CVE-2025-1153, CVE-2025-11839, CVE-2025-11840, CVE-2025-3198, CVE-2025-66861, CVE-2025-66862, CVE-2025-66863, CVE-2025-66864, CVE-2025-66865, CVE-2025-66866, CVE-2025-69644, CVE-2025-69645, CVE-2025-69646, CVE-2025-69647, CVE-2025-69648, CVE-2025-69649, CVE-2025-69650, CVE-2025-69651, CVE-2025-69652), npm-1:8.19.2-1.16.18.1.3.el9_1 (CVE-2023-39333, CVE-2023-45143, CVE-2024-21538, CVE-2025-47279, CVE-2025-5889, CVE-2025-70873, CVE-2026-21715, CVE-2026-21716, CVE-2026-22036, CVE-2026-27171), emacs-filesystem-1:27.2-6.el9 (CVE-2017-1000383), vim-filesystem-2:8.2.2637-20.el9_1 (CVE-2021-3927, CVE-2021-3928, CVE-2021-3968, CVE-2021-3973, CVE-2021-3974, CVE-2021-4136, CVE-2021-4166, CVE-2021-4173, CVE-2021-4187, CVE-2022-0213, CVE-2022-0351, CVE-2022-1616, CVE-2022-1619, CVE-2022-1620, CVE-2022-1674, CVE-2022-1720, CVE-2022-1725, CVE-2022-2042, CVE-2022-2124, CVE-2022-2125, CVE-2022-2126, CVE-2022-2129, CVE-2022-2175, CVE-2022-2182, CVE-2022-2183, CVE-2022-2206, CVE-2022-2207, CVE-2022-2208, CVE-2022-2210, CVE-2022-2257, CVE-2022-2284, CVE-2022-2285, CVE-2022-2286, CVE-2022-2287, CVE-2022-2304, CVE-2022-2343, CVE-2022-2344, CVE-2022-2345, CVE-2022-2522, CVE-2022-2817, CVE-2022-2819, CVE-2022-2845, CVE-2022-2849, CVE-2022-2862, CVE-2022-2874, CVE-2022-2889, CVE-2022-2923, CVE-2022-2946, CVE-2022-2980, CVE-2022-2982, CVE-2022-3016, CVE-2022-3037, CVE-2022-3099, CVE-2022-3134, CVE-2022-3153, CVE-2022-3234, CVE-2022-3235, CVE-2022-3256, CVE-2022-3278, CVE-2022-3296, CVE-2022-3297, CVE-2022-3324, CVE-2022-3352, CVE-2022-3705, CVE-2022-4141, CVE-2022-4292, CVE-2022-4293, CVE-2023-0049, CVE-2023-0051, CVE-2023-0054, CVE-2023-0288, CVE-2023-0433, CVE-2023-0512, CVE-2023-1127, CVE-2023-1170, CVE-2023-1175, CVE-2023-1264, CVE-2023-2609, CVE-2023-2610, CVE-2023-46246, CVE-2023-4734, CVE-2023-4735, CVE-2023-4738, CVE-2023-4751, CVE-2023-4781, CVE-2023-48231, CVE-2023-48232, CVE-2023-48233, CVE-2023-48234, CVE-2023-48235, CVE-2023-48236, CVE-2023-48237, CVE-2023-48706, CVE-2023-5344, CVE-2023-5441, CVE-2023-5535, CVE-2024-22667, CVE-2024-41957, CVE-2024-41965, CVE-2024-43374, CVE-2024-43802, CVE-2024-45306, CVE-2024-47814, CVE-2025-1215, CVE-2025-22134, CVE-2025-24014, CVE-2025-26603, CVE-2026-26269, CVE-2026-28422), elfutils-libs-0.187-5.el9 (CVE-2024-25260, CVE-2025-1371, CVE-2025-1376, CVE-2025-1377), libarchive-3.5.3-3.el9 (CVE-2025-1632, CVE-2025-5915, CVE-2025-5916, CVE-2025-5917, CVE-2025-5918), curl-minimal-7.76.1-19.el9_1.1 (CVE-2024-11053, CVE-2024-7264, CVE-2024-9681, CVE-2025-14524, CVE-2025-14819, CVE-2025-15079, CVE-2025-15224), qt5-srpm-macros-5.15.3-1.el9 (CVE-2025-23050), ncurses-6.2-8.20210508.el9 (CVE-2023-50495), golang-src-1.18.9-1.el9_1 (CVE-2026-27138, CVE-2026-27139), openssl-1:3.0.1-47.el9_1 (CVE-2024-13176, CVE-2024-41996, CVE-2025-9232, CVE-2026-2673, CVE-2026-28386, CVE-2026-28388, CVE-2026-28389, CVE-2026-31789), python3-pip-wheel-21.2.3-6.el9 (CVE-2021-3572), sqlite-libs-3.34.1-6.el9_1 (CVE-2024-0232, CVE-2025-70873), rsync-3.2.3-18.el9 (CVE-2026-27171), libpng-devel-2:1.6.37-12.el9 (CVE-2022-3857), gcc-plugin-annobin-11.3.1-2.1.el9 (CVE-2022-27943), glibc-common-2.34-40.el9_1.1 (CVE-2026-4438), nodejs-docs-1:16.18.1-3.el9_1 (CVE-2023-39333, CVE-2023-45143, CVE-2024-21538, CVE-2025-47279, CVE-2025-5889, CVE-2025-70873, CVE-2026-21715, CVE-2026-21716, CVE-2026-22036, CVE-2026-27171), golang-bin-1.18.9-1.el9_1 (CVE-2026-27138, CVE-2026-27139), libtiff-4.4.0-5.el9_1 (CVE-2017-16232, CVE-2022-1056, CVE-2023-1916, CVE-2024-13978, CVE-2025-8961, CVE-2025-9165), pkgconf-pkg-config-1.7.3-9.el9 (CVE-2023-24056), nodejs-1:16.18.1-3.el9_1 (CVE-2023-39333, CVE-2023-45143, CVE-2024-21538, CVE-2025-47279, CVE-2025-5889, CVE-2025-70873, CVE-2026-21715, CVE-2026-21716, CVE-2026-22036, CVE-2026-27171), openssl-devel-1:3.0.1-47.el9_1 (CVE-2024-13176, CVE-2024-41996, CVE-2025-9232, CVE-2026-2673, CVE-2026-28386, CVE-2026-28388, CVE-2026-28389, CVE-2026-31789), libpkgconf-1.7.3-9.el9 (CVE-2023-24056), libstdc++-11.3.1-2.1.el9 (CVE-2022-27943), glibc-headers-2.34-40.el9_1.1 (CVE-2026-4438), gdb-10.2-10.el9 (CVE-2022-47007, CVE-2022-47010, CVE-2022-47011, CVE-2024-57360, CVE-2025-11412, CVE-2025-11413, CVE-2025-11414, CVE-2025-11494, CVE-2025-11495, CVE-2025-1150, CVE-2025-1151, CVE-2025-1152, CVE-2025-1153, CVE-2025-11839, CVE-2025-11840, CVE-2025-3198, CVE-2025-66861, CVE-2025-66862, CVE-2025-66863, CVE-2025-66864, CVE-2025-66865, CVE-2025-66866, CVE-2025-69644, CVE-2025-69645, CVE-2025-69646, CVE-2025-69647, CVE-2025-69648, CVE-2025-69649, CVE-2025-69650, CVE-2025-69651, CVE-2025-69652), python3-3.9.14-1.el9_1.2 (CVE-2025-1795, CVE-2026-2297, CVE-2026-3479), bsdtar-3.5.3-3.el9 (CVE-2025-1632, CVE-2025-5915, CVE-2025-5916, CVE-2025-5917, CVE-2025-5918), vim-minimal-2:8.2.2637-20.el9_1 (CVE-2021-3927, CVE-2021-3928, CVE-2021-3968, CVE-2021-3973, CVE-2021-3974, CVE-2021-4136, CVE-2021-4166, CVE-2021-4173, CVE-2021-4187, CVE-2022-0213, CVE-2022-0351, CVE-2022-1616, CVE-2022-1619, CVE-2022-1620, CVE-2022-1674, CVE-2022-1720, CVE-2022-1725, CVE-2022-2042, CVE-2022-2124, CVE-2022-2125, CVE-2022-2126, CVE-2022-2129, CVE-2022-2175, CVE-2022-2182, CVE-2022-2183, CVE-2022-2206, CVE-2022-2207, CVE-2022-2208, CVE-2022-2210, CVE-2022-2257, CVE-2022-2284, CVE-2022-2285, CVE-2022-2286, CVE-2022-2287, CVE-2022-2304, CVE-2022-2343, CVE-2022-2344, CVE-2022-2345, CVE-2022-2522, CVE-2022-2817, CVE-2022-2819, CVE-2022-2845, CVE-2022-2849, CVE-2022-2862, CVE-2022-2874, CVE-2022-2889, CVE-2022-2923, CVE-2022-2946, CVE-2022-2980, CVE-2022-2982, CVE-2022-3016, CVE-2022-3037, CVE-2022-3099, CVE-2022-3134, CVE-2022-3153, CVE-2022-3234, CVE-2022-3235, CVE-2022-3256, CVE-2022-3278, CVE-2022-3296, CVE-2022-3297, CVE-2022-3324, CVE-2022-3352, CVE-2022-3705, CVE-2022-4141, CVE-2022-4292, CVE-2022-4293, CVE-2023-0049, CVE-2023-0051, CVE-2023-0054, CVE-2023-0288, CVE-2023-0433, CVE-2023-0512, CVE-2023-1127, CVE-2023-1170, CVE-2023-1175, CVE-2023-1264, CVE-2023-2609, CVE-2023-2610, CVE-2023-46246, CVE-2023-4734, CVE-2023-4735, CVE-2023-4738, CVE-2023-4751, CVE-2023-4781, CVE-2023-48231, CVE-2023-48232, CVE-2023-48233, CVE-2023-48234, CVE-2023-48235, CVE-2023-48236, CVE-2023-48237, CVE-2023-48706, CVE-2023-5344, CVE-2023-5441, CVE-2023-5535, CVE-2024-22667, CVE-2024-41957, CVE-2024-41965, CVE-2024-43374, CVE-2024-43802, CVE-2024-45306, CVE-2024-47814, CVE-2025-1215, CVE-2025-22134, CVE-2025-24014, CVE-2025-26603, CVE-2026-26269, CVE-2026-28422), pcre2-utf16-10.40-2.el9 (CVE-2022-41409), openssl-libs-1:3.0.1-47.el9_1 (CVE-2024-13176, CVE-2024-41996, CVE-2025-9232, CVE-2026-2673, CVE-2026-28386, CVE-2026-28388, CVE-2026-28389, CVE-2026-31789), gcc-c++-11.3.1-2.1.el9 (CVE-2022-27943), binutils-2.35.2-24.el9 (CVE-2021-3826, CVE-2022-38533, CVE-2022-44840, CVE-2022-47007, CVE-2022-47008, CVE-2022-47010, CVE-2022-47011, CVE-2023-1972, CVE-2024-57360, CVE-2025-11412, CVE-2025-11413, CVE-2025-11414, CVE-2025-11494, CVE-2025-11495, CVE-2025-1150, CVE-2025-1151, CVE-2025-1152, CVE-2025-1153, CVE-2025-11839, CVE-2025-11840, CVE-2025-3198, CVE-2025-66861, CVE-2025-66862, CVE-2025-66863, CVE-2025-66864, CVE-2025-66865, CVE-2025-66866, CVE-2025-69644, CVE-2025-69645, CVE-2025-69646, CVE-2025-69647, CVE-2025-69648, CVE-2025-69649, CVE-2025-69650, CVE-2025-69651, CVE-2025-69652), sqlite-devel-3.34.1-6.el9_1 (CVE-2024-0232, CVE-2025-70873), libcurl-devel-7.76.1-19.el9_1.1 (CVE-2024-11053, CVE-2024-7264, CVE-2024-9681, CVE-2025-14524, CVE-2025-14819, CVE-2025-15079, CVE-2025-15224), gcc-11.3.1-2.1.el9 (CVE-2022-27943), elfutils-libelf-0.187-5.el9 (CVE-2024-25260, CVE-2025-1371, CVE-2025-1376, CVE-2025-1377), libgomp-11.3.1-2.1.el9 (CVE-2022-27943), zlib-1.2.11-35.el9_1 (CVE-2026-27171), ncurses-libs-6.2-8.20210508.el9 (CVE-2023-50495), libX11-common-1.7.0-7.el9 (CVE-2022-3555), libgcc-11.3.1-2.1.el9 (CVE-2022-27943), gawk-5.1.0-6.el9 (CVE-2023-4156), patch-2.7.6-16.el9 (CVE-2021-45261), glibc-minimal-langpack-2.34-40.el9_1.1 (CVE-2026-4438)&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;name&#34;: &#34;clair_unpatched_low_vulnerabilities&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;url&#34;: &#34;https://access.redhat.com/articles/red_hat_vulnerability_tutorial&#34;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;},&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;vulnerabilities_number&#34;: 620&#xA;&#x9;&#x9;&#x9;&#x9;}&#xA;&#x9;&#x9;&#x9;},&#xA;&#x9;&#x9;&#x9;{&#xA;&#x9;&#x9;&#x9;&#x9;&#34;msg&#34;: &#34;Found packages with unknown vulnerabilities. Consider updating to a newer version of those packages, they may no longer be affected by the reported CVEs.&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#34;metadata&#34;: {&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;details&#34;: {&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;description&#34;: &#34;Vulnerabilities found: libwebp-devel-1.2.0-3.el9 (CVE-2023-5129), libwebp-1.2.0-3.el9 (CVE-2023-5129)&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;name&#34;: &#34;clair_unknown_vulnerabilities&#34;,&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;url&#34;: &#34;https://access.redhat.com/articles/red_hat_vulnerability_tutorial&#34;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;},&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#34;vulnerabilities_number&#34;: 2&#xA;&#x9;&#x9;&#x9;&#x9;}&#xA;&#x9;&#x9;&#x9;}&#xA;&#x9;&#x9;]&#xA;&#x9;}&#xA;]&#xA;{&#34;vulnerabilities&#34;:{&#34;critical&#34;:0,&#34;high&#34;:319,&#34;medium&#34;:837,&#34;low&#34;:229,&#34;unknown&#34;:2},&#34;unpatched_vulnerabilities&#34;:{&#34;critical&#34;:0,&#34;high&#34;:30,&#34;medium&#34;:422,&#34;low&#34;:620,&#34;unknown&#34;:0}}&#xA;{&#34;image&#34;: {&#34;pullspec&#34;: &#34;quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#34;, &#34;digests&#34;: [&#34;sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8&#34;]}}&#xA;{&#34;result&#34;:&#34;SUCCESS&#34;,&#34;timestamp&#34;:&#34;2026-04-24T06:00:22+00:00&#34;,&#34;note&#34;:&#34;Task clair-scan completed: Refer to Tekton task result SCAN_OUTPUT for vulnerabilities scanned by Clair.&#34;,&#34;namespace&#34;:&#34;default&#34;,&#34;successes&#34;:0,&#34;failures&#34;:0,&#34;warnings&#34;:0}&#xA;&#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-clamav-scan-pod | init container: prepare&#xA;2026/04/24 05:51:34 Entrypoint initialization&#xA;&#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-clamav-scan-pod | init container: place-scripts&#xA;2026/04/24 05:51:37 Decoded script /tekton/scripts/script-0-7mfj7&#xA;2026/04/24 05:51:37 Decoded script /tekton/scripts/script-1-4l2gn&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-clamav-scan-pod | container step-extract-and-scan-image: &#xA;Starting clamd ...&#xA;clamd is ready!&#xA;Detecting artifact type for quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm@sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8.&#xA;Detected container image. Processing image manifests.&#xA;Running &#34;oc image extract&#34; on image of arch amd64&#xA;Scanning image for arch amd64. This operation may take a while.&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-clamav-scan-pod | container step-upload: &#xA;Selecting auth&#xA;Attaching to quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#xA;Preparing clamscan-result-amd64.log&#xA;Preparing clamscan-ec-test-amd64.json&#xA;Uploading 321434bb5ea0 clamscan-result-amd64.log&#xA;Uploading 4d496601c3a9 clamscan-ec-test-amd64.json&#xA;Exists    44136fa355b3 application/vnd.oci.empty.v1+json&#xA;Using token for quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm&#xA;Executing: oras attach --no-tty --registry-config /home/oras/auth.json --artifact-type application/vnd.clamav quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469@sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8 clamscan-result-amd64.log:text/vnd.clamav clamscan-ec-test-amd64.json:application/vnd.konflux.test_output+json&#xA;Uploaded  321434bb5ea0 clamscan-result-amd64.log&#xA;Uploaded  4d496601c3a9 clamscan-ec-test-amd64.json&#xA;Uploading 9f15c5b3e948 application/vnd.oci.image.manifest.v1+json&#xA;Uploaded  9f15c5b3e948 application/vnd.oci.image.manifest.v1+json&#xA;Attached to [registry] quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469@sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8&#xA;Digest: sha256:9f15c5b3e948382bd9c3c700ecd24c9855a24adfb5908374f945996a11fc5aed&#xA;&#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-clone-repository-pod | init container: prepare&#xA;2026/04/24 05:46:54 Entrypoint initialization&#xA;&#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-clone-repository-pod | init container: place-scripts&#xA;2026/04/24 05:46:55 Decoded script /tekton/scripts/script-0-527pp&#xA;2026/04/24 05:46:55 Decoded script /tekton/scripts/script-1-m8vkr&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-clone-repository-pod | container step-clone: &#xA;INFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#xA;{&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1777009628.086238,&#34;caller&#34;:&#34;git/git.go:394&#34;,&#34;msg&#34;:&#34;Retrying operation (attempt 1)&#34;}&#xA;{&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1777009628.5501256,&#34;caller&#34;:&#34;git/git.go:223&#34;,&#34;msg&#34;:&#34;Successfully cloned https://github.com/redhat-appstudio-qe/group-snapshot-multi-component @ 93e2088996e261a167eab61824669c3c2f684469 (grafted, HEAD) in path /workspace/output/source&#34;}&#xA;{&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1777009628.5501654,&#34;caller&#34;:&#34;git/git.go:394&#34;,&#34;msg&#34;:&#34;Retrying operation (attempt 1)&#34;}&#xA;{&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1777009628.5765214,&#34;caller&#34;:&#34;git/git.go:277&#34;,&#34;msg&#34;:&#34;Successfully initialized and updated submodules in path /workspace/output/source&#34;}&#xA;Merge option disabled. Using checked-out revision 93e2088996e261a167eab61824669c3c2f684469 directly.&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-clone-repository-pod | container step-symlink-check: &#xA;Running symlink check&#xA;&#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-init-pod | init container: prepare&#xA;2026/04/24 05:46:47 Entrypoint initialization&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-init-pod | container step-init: &#xA;time=&#34;2026-04-24T05:46:51Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-24T05:46:51Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-24T05:46:51Z&#34; level=info msg=&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai&#34;&#xA;time=&#34;2026-04-24T05:46:51Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-24T05:46:51Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-24T05:46:51Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-24T05:46:51Z&#34; level=info msg=&#34;Cache proxy is disabled via param&#34;&#xA;time=&#34;2026-04-24T05:46:51Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-24T05:46:51Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;&#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-push-dockerfile-pod | init container: prepare&#xA;2026/04/24 05:51:36 Entrypoint initialization&#xA;&#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-push-dockerfile-pod | init container: working-dir-initializer&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-push-dockerfile-pod | container step-push: &#xA;time=&#34;2026-04-24T05:51:40Z&#34; level=info msg=&#34;[param] image-url: quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#34;&#xA;time=&#34;2026-04-24T05:51:40Z&#34; level=info msg=&#34;[param] image-digest: sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8&#34;&#xA;time=&#34;2026-04-24T05:51:40Z&#34; level=info msg=&#34;[param] containerfile: docker/Dockerfile&#34;&#xA;time=&#34;2026-04-24T05:51:40Z&#34; level=info msg=&#34;[param] context: go-component&#34;&#xA;time=&#34;2026-04-24T05:51:40Z&#34; level=info msg=&#34;[param] tag-suffix: .dockerfile&#34;&#xA;time=&#34;2026-04-24T05:51:40Z&#34; level=info msg=&#34;[param] artifact-type: application/vnd.konflux.dockerfile&#34;&#xA;time=&#34;2026-04-24T05:51:40Z&#34; level=info msg=&#34;[param] source: source&#34;&#xA;time=&#34;2026-04-24T05:51:40Z&#34; level=info msg=&#34;[param] result-path-image-ref: /tekton/results/IMAGE_REF&#34;&#xA;time=&#34;2026-04-24T05:51:40Z&#34; level=info msg=&#34;[param] alternative-filename: Dockerfile&#34;&#xA;time=&#34;2026-04-24T05:51:42Z&#34; level=info msg=&#34;oras [stdout] quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm@sha256:8f203699ccdb6e426f313e5b9efc7ce29bb6dcd82f3350de53abaa8b53ed7dd1&#34; logger=CliExecutor&#xA;time=&#34;2026-04-24T05:51:42Z&#34; level=info msg=&#34;Containerfile &#39;/workspace/workspace/source/go-component/docker/Dockerfile&#39; is pushed to registry with tag: sha256-8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8.dockerfile&#34;&#xA;{&#34;image_ref&#34;:&#34;quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm@sha256:8f203699ccdb6e426f313e5b9efc7ce29bb6dcd82f3350de53abaa8b53ed7dd1&#34;}&#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-sast-shell-check-pod | init container: prepare&#xA;2026/04/24 05:51:34 Entrypoint initialization&#xA;&#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-sast-shell-check-pod | init container: place-scripts&#xA;2026/04/24 05:51:37 Decoded script /tekton/scripts/script-0-7jl78&#xA;2026/04/24 05:51:37 Decoded script /tekton/scripts/script-1-p2k42&#xA;&#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-sast-shell-check-pod | init container: working-dir-initializer&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-sast-shell-check-pod | container step-sast-shell-check: &#xA;+ source /utils.sh&#xA;++ OPM_RENDER_CACHE=/tmp/konflux-test-opm-cache&#xA;++ DEFAULT_INDEX_IMAGE=registry.redhat.io/redhat/redhat-operator-index&#xA;+ trap &#39;handle_error /tekton/results/TEST_OUTPUT&#39; EXIT&#xA;+ [[ -z &#39;&#39; ]]&#xA;+ PROJECT_NAME=go-component-zrwnnm&#xA;+ echo &#39;INFO: The PROJECT_NAME used is: go-component-zrwnnm&#39;&#xA;+ ca_bundle=/mnt/trusted-ca/ca-bundle.crt&#xA;INFO: The PROJECT_NAME used is: go-component-zrwnnm&#xA;+ &#39;[&#39; -f /mnt/trusted-ca/ca-bundle.crt &#39;]&#39;&#xA;+ echo &#39;INFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#39;&#xA;+ cp -vf /mnt/trusted-ca/ca-bundle.crt /etc/pki/ca-trust/source/anchors&#xA;INFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#xA;+ update-ca-trust&#xA;&#39;/mnt/trusted-ca/ca-bundle.crt&#39; -&gt; &#39;/etc/pki/ca-trust/source/anchors/ca-bundle.crt&#39;&#xA;++ rpm -q --queryformat &#39;%{NAME}-%{VERSION}-%{RELEASE}\n&#39; ShellCheck&#xA;+ PACKAGE_VERSION=ShellCheck-0.10.0-3.el9&#xA;+ OUTPUT_FILE=shellcheck-results.json&#xA;+ SOURCE_CODE_DIR=/workspace/workspace/source&#xA;+ declare -a ALL_TARGETS&#xA;+ IFS=,&#xA;+ read -ra TARGET_ARRAY&#xA;+ for d in &#34;${TARGET_ARRAY[@]}&#34;&#xA;+ potential_path=/workspace/workspace/source/.&#xA;++ realpath -m /workspace/workspace/source/.&#xA;+ resolved_path=/workspace/workspace/source&#xA;+ [[ /workspace/workspace/source == \/\w\o\r\k\s\p\a\c\e\/\w\o\r\k\s\p\a\c\e\/\s\o\u\r\c\e* ]]&#xA;+ ALL_TARGETS+=(&#34;$resolved_path&#34;)&#xA;+ &#39;[&#39; -z &#39;&#39; &#39;]&#39;&#xA;+ &#39;[&#39; -r /sys/fs/cgroup/cpu.max &#39;]&#39;&#xA;+ read -r quota period&#xA;+ &#39;[&#39; 800000 &#39;!=&#39; max &#39;]&#39;&#xA;+ &#39;[&#39; -n 100000 &#39;]&#39;&#xA;+ &#39;[&#39; 100000 -gt 0 &#39;]&#39;&#xA;+ export SC_JOBS=8&#xA;+ SC_JOBS=8&#xA;INFO: Setting SC_JOBS=8 based on cgroups v2 max for run-shellcheck.sh&#xA;+ echo &#39;INFO: Setting SC_JOBS=8 based on cgroups v2 max for run-shellcheck.sh&#39;&#xA;+ /usr/share/csmock/scripts/run-shellcheck.sh /workspace/workspace/source&#xA;Looking for shell scripts................ done&#xA;+ timeout 30 shellcheck --format=json1 --external-sources --source-path=/workspace/workspace/source /workspace/workspace/source/.git/hooks/applypatch-msg.sample&#xA;+ timeout 30 shellcheck --format=json1 --external-sources --source-path=/workspace/workspace/source /workspace/workspace/source/.git/hooks/commit-msg.sample&#xA;+ timeout 30 shellcheck --format=json1 --external-sources --source-path=/workspace/workspace/source /workspace/workspace/source/.git/hooks/post-update.sample&#xA;+ timeout 30 shellcheck --format=json1 --external-sources --source-path=/workspace/workspace/source /workspace/workspace/source/.git/hooks/prepare-commit-msg.sample&#xA;+ timeout 30 shellcheck --format=json1 --external-sources --source-path=/workspace/workspace/source /workspace/workspace/source/.git/hooks/pre-applypatch.sample&#xA;+ timeout 30 shellcheck --format=json1 --external-sources --source-path=/workspace/workspace/source /workspace/workspace/source/.git/hooks/pre-commit.sample&#xA;+ timeout 30 shellcheck --format=json1 --external-sources --source-path=/workspace/workspace/source /workspace/workspace/source/.git/hooks/pre-merge-commit.sample&#xA;+ timeout 30 shellcheck --format=json1 --external-sources --source-path=/workspace/workspace/source /workspace/workspace/source/.git/hooks/pre-push.sample&#xA;+ timeout 30 shellcheck --format=json1 --external-sources --source-path=/workspace/workspace/source /workspace/workspace/source/.git/hooks/pre-rebase.sample&#xA;+ timeout 30 shellcheck --format=json1 --external-sources --source-path=/workspace/workspace/source /workspace/workspace/source/.git/hooks/pre-receive.sample&#xA;+ timeout 30 shellcheck --format=json1 --external-sources --source-path=/workspace/workspace/source /workspace/workspace/source/.git/hooks/push-to-checkout.sample&#xA;+ timeout 30 shellcheck --format=json1 --external-sources --source-path=/workspace/workspace/source /workspace/workspace/source/.git/hooks/sendemail-validate.sample&#xA;+ timeout 30 shellcheck --format=json1 --external-sources --source-path=/workspace/workspace/source /workspace/workspace/source/.git/hooks/update.sample&#xA;+ CSGREP_OPTS=(--mode=json --strip-path-prefix=&#34;$SOURCE_CODE_DIR&#34;/ --remove-duplicates --embed-context=3 --set-scan-prop=&#34;ShellCheck:${PACKAGE_VERSION}&#34;)&#xA;+ [[ true == \t\r\u\e ]]&#xA;+ CSGREP_EVENT_FILTER=&#39;\[SC(1020|1035|1054|1066|1068|1073|1080|1083|1099|1113|1115|1127|1128|1143|2043|2050|&#39;&#xA;+ CSGREP_EVENT_FILTER+=&#39;2055|2057|2066|2069|2071|2077|2078|2091|2092|2157|2171|2193|2194|2195|2215|2216|&#39;&#xA;+ CSGREP_EVENT_FILTER+=&#39;2218|2224|2225|2242|2256|2258|2261)\]$&#39;&#xA;+ CSGREP_OPTS+=(--event=&#34;$CSGREP_EVENT_FILTER&#34;)&#xA;+ csgrep --mode=json --strip-path-prefix=/workspace/workspace/source/ --remove-duplicates --embed-context=3 --set-scan-prop=ShellCheck:ShellCheck-0.10.0-3.el9 &#39;--event=\[SC(1020|1035|1054|1066|1068|1073|1080|1083|1099|1113|1115|1127|1128|1143|2043|2050|2055|2057|2066|2069|2071|2077|2078|2091|2092|2157|2171|2193|2194|2195|2215|2216|2218|2224|2225|2242|2256|2258|2261)\]$&#39; ./shellcheck-results/empty.json ./shellcheck-results/sc-118.json ./shellcheck-results/sc-131.json ./shellcheck-results/sc-132.json ./shellcheck-results/sc-134.json ./shellcheck-results/sc-85.json ./shellcheck-results/sc-88.json ./shellcheck-results/sc-89.json ./shellcheck-results/sc-91.json ./shellcheck-results/sc-94.json ./shellcheck-results/sc-97.json&#xA;+ [[ SITE_DEFAULT == \S\I\T\E\_\D\E\F\A\U\L\T ]]&#xA;+ KFP_GIT_URL=https://gitlab.cee.redhat.com/osh/known-false-positives.git&#xA;+ PROBE_URL=https://gitlab.cee.redhat.com/osh/known-false-positives&#xA;+ KFP_DIR=known-false-positives&#xA;+ KFP_CLONED=0&#xA;+ mkdir known-false-positives&#xA;+ [[ -n https://gitlab.cee.redhat.com/osh/known-false-positives.git ]]&#xA;+ echo -n &#39;INFO: Probing https://gitlab.cee.redhat.com/osh/known-false-positives... &#39;&#xA;+ curl --fail --head --max-time 60 --no-progress-meter https://gitlab.cee.redhat.com/osh/known-false-positives&#xA;++ head -1&#xA;curl: (6) Could not resolve host: gitlab.cee.redhat.com&#xA;+ [[ 0 -eq 0 ]]&#xA;+ echo &#39;WARN: Failed to clone known-false-positives at https://gitlab.cee.redhat.com/osh/known-false-positives.git, scan results will not be filtered&#39;&#xA;INFO: Probing https://gitlab.cee.redhat.com/osh/known-false-positives... WARN: Failed to clone known-false-positives at https://gitlab.cee.redhat.com/osh/known-false-positives.git, scan results will not be filtered&#xA;ShellCheck results have been saved to shellcheck-results.json&#xA;+ echo &#39;ShellCheck results have been saved to shellcheck-results.json&#39;&#xA;+ csgrep --mode=evtstat shellcheck-results.json&#xA;+ csgrep --mode=sarif shellcheck-results.json&#xA;+ TEST_OUTPUT=&#xA;+ parse_test_output sast-shell-check sarif shellcheck-results.sarif&#xA;+ TEST_NAME=sast-shell-check&#xA;+ TEST_RESULT_FORMAT=sarif&#xA;+ TEST_RESULT_FILE=shellcheck-results.sarif&#xA;+ &#39;[&#39; -z sast-shell-check &#39;]&#39;&#xA;+ &#39;[&#39; -z sarif &#39;]&#39;&#xA;+ &#39;[&#39; -z shellcheck-results.sarif &#39;]&#39;&#xA;+ &#39;[&#39; &#39;!&#39; -f shellcheck-results.sarif &#39;]&#39;&#xA;+ &#39;[&#39; sarif = sarif &#39;]&#39;&#xA;+++ jq -rce &#39;(if (.runs[].results | length &gt; 0) then &#34;FAILURE&#34; else &#34;SUCCESS&#34; end)&#39; shellcheck-results.sarif&#xA;+++ jq -rce &#39;(.runs[].results | length)&#39; shellcheck-results.sarif&#xA;++ make_result_json -r SUCCESS -f 0&#xA;++ local RESULT=&#xA;++ local SUCCESSES=0&#xA;++ local FAILURES=0&#xA;++ local WARNINGS=0&#xA;++ local &#39;NOTE=For details, check Tekton task log.&#39;&#xA;++ local NAMESPACE=default&#xA;++ local OUTPUT&#xA;++ local OPTIND opt&#xA;++ getopts :r:s:f:w:t:n: opt&#xA;++ case &#34;${opt}&#34; in&#xA;++ RESULT=SUCCESS&#xA;++ getopts :r:s:f:w:t:n: opt&#xA;++ case &#34;${opt}&#34; in&#xA;++ FAILURES=0&#xA;++ getopts :r:s:f:w:t:n: opt&#xA;++ shift 4&#xA;++ &#39;[&#39; -z SUCCESS &#39;]&#39;&#xA;++ case &#34;${RESULT}&#34; in&#xA;++++ date -u --iso-8601=seconds&#xA;+++ jq -rce --arg date 2026-04-24T05:59:05+00:00 --arg result SUCCESS --arg note &#39;For details, check Tekton task log.&#39; --arg namespace default --arg successes 0 --arg failures 0 --arg warnings 0 --null-input &#39;{  result: $result,&#xA;        timestamp: $date,&#xA;        note: $note,&#xA;        namespace: $namespace,&#xA;        successes: $successes|tonumber,&#xA;        failures: $failures|tonumber,&#xA;        warnings: $warnings|tonumber&#xA;    }&#39;&#xA;++ OUTPUT=&#39;{&#34;result&#34;:&#34;SUCCESS&#34;,&#34;timestamp&#34;:&#34;2026-04-24T05:59:05+00:00&#34;,&#34;note&#34;:&#34;For details, check Tekton task log.&#34;,&#34;namespace&#34;:&#34;default&#34;,&#34;successes&#34;:0,&#34;failures&#34;:0,&#34;warnings&#34;:0}&#39;&#xA;++ echo &#39;{&#34;result&#34;:&#34;SUCCESS&#34;,&#34;timestamp&#34;:&#34;2026-04-24T05:59:05+00:00&#34;,&#34;note&#34;:&#34;For details, check Tekton task log.&#34;,&#34;namespace&#34;:&#34;default&#34;,&#34;successes&#34;:0,&#34;failures&#34;:0,&#34;warnings&#34;:0}&#39;&#xA;+ TEST_OUTPUT=&#39;{&#34;result&#34;:&#34;SUCCESS&#34;,&#34;timestamp&#34;:&#34;2026-04-24T05:59:05+00:00&#34;,&#34;note&#34;:&#34;For details, check Tekton task log.&#34;,&#34;namespace&#34;:&#34;default&#34;,&#34;successes&#34;:0,&#34;failures&#34;:0,&#34;warnings&#34;:0}&#39;&#xA;++ echo &#39;{&#34;result&#34;:&#34;SUCCESS&#34;,&#34;timestamp&#34;:&#34;2026-04-24T05:59:05+00:00&#34;,&#34;note&#34;:&#34;For details, check Tekton task log.&#34;,&#34;namespace&#34;:&#34;default&#34;,&#34;successes&#34;:0,&#34;failures&#34;:0,&#34;warnings&#34;:0}&#39;&#xA;++ jq .failures&#xA;+ &#39;[&#39; 0 -gt 0 &#39;]&#39;&#xA;+ echo &#39;{&#34;result&#34;:&#34;SUCCESS&#34;,&#34;timestamp&#34;:&#34;2026-04-24T05:59:05+00:00&#34;,&#34;note&#34;:&#34;For details, check Tekton task log.&#34;,&#34;namespace&#34;:&#34;default&#34;,&#34;successes&#34;:0,&#34;failures&#34;:0,&#34;warnings&#34;:0}&#39;&#xA;+ tee /tekton/results/TEST_OUTPUT&#xA;{&#34;result&#34;:&#34;SUCCESS&#34;,&#34;timestamp&#34;:&#34;2026-04-24T05:59:05+00:00&#34;,&#34;note&#34;:&#34;For details, check Tekton task log.&#34;,&#34;namespace&#34;:&#34;default&#34;,&#34;successes&#34;:0,&#34;failures&#34;:0,&#34;warnings&#34;:0}&#xA;+ handle_error /tekton/results/TEST_OUTPUT&#xA;+ exit_code=0&#xA;+ &#39;[&#39; 0 -ne 0 &#39;]&#39;&#xA;+ exit 0&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-sast-shell-check-pod | container step-upload: &#xA;Selecting auth&#xA;Using token for quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm&#xA;Attaching to quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#xA;Executing: oras attach --no-tty --registry-config /home/oras/auth.json --artifact-type application/sarif+json quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469@sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8 shellcheck-results.sarif:application/sarif+json&#xA;Preparing shellcheck-results.sarif&#xA;Exists    44136fa355b3 application/vnd.oci.empty.v1+json&#xA;Uploading 3b606a9dd3a1 shellcheck-results.sarif&#xA;Uploaded  3b606a9dd3a1 shellcheck-results.sarif&#xA;Uploading bc1c770746d5 application/vnd.oci.image.manifest.v1+json&#xA;Uploaded  bc1c770746d5 application/vnd.oci.image.manifest.v1+json&#xA;Attached to [registry] quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469@sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8&#xA;Digest: sha256:bc1c770746d5001b7ba968dc4b821bb811a2dc81e0fcdbaa0648964299787cdb&#xA;No excluded-findings.json exists. Skipping upload.&#xA;&#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-sast-snyk-check-pod | init container: prepare&#xA;2026/04/24 05:51:32 Entrypoint initialization&#xA;&#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-sast-snyk-check-pod | init container: place-scripts&#xA;2026/04/24 05:51:36 Decoded script /tekton/scripts/script-0-j4lkg&#xA;2026/04/24 05:51:36 Decoded script /tekton/scripts/script-1-wxkx2&#xA;&#xA; pod: go-component-zrwnnm-on-pull-request-49mbw-sast-snyk-check-pod | init container: working-dir-initializer&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-sast-snyk-check-pod | container step-sast-snyk-check: &#xA;INFO: The PROJECT_NAME used is: go-component-zrwnnm&#xA;INFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#xA;&#39;/mnt/trusted-ca/ca-bundle.crt&#39; -&gt; &#39;/etc/pki/ca-trust/source/anchors/ca-bundle.crt&#39;&#xA;{&#34;result&#34;:&#34;SKIPPED&#34;,&#34;timestamp&#34;:&#34;2026-04-24T05:59:01+00:00&#34;,&#34;note&#34;:&#34;Task sast-snyk-check skipped: If you wish to use the Snyk code SAST task, please create a secret name snyk-secret with the key &#39;snyk_token&#39; containing the Snyk token by following the steps given [here](https://konflux-ci.dev/docs/testing/build/snyk/)&#34;,&#34;namespace&#34;:&#34;default&#34;,&#34;successes&#34;:0,&#34;failures&#34;:0,&#34;warnings&#34;:0}&#xA;&#xA;pod: go-component-zrwnnm-on-pull-request-49mbw-sast-snyk-check-pod | container step-upload: &#xA;No sast_snyk_check_out.sarif exists. Skipping upload.&#xA;No excluded-findings.json exists. Skipping upload.&#xA;&#xA; pod: go-component-zrwnnm-on-pull03f414a7ecbab5588a89130040c45f82-pod | init container: prepare&#xA;2026/04/24 05:47:13 Entrypoint initialization&#xA;&#xA; pod: go-component-zrwnnm-on-pull03f414a7ecbab5588a89130040c45f82-pod | init container: place-scripts&#xA;2026/04/24 05:47:14 Decoded script /tekton/scripts/script-0-5f88r&#xA;&#xA;pod: go-component-zrwnnm-on-pull03f414a7ecbab5588a89130040c45f82-pod | container step-prefetch-dependencies: &#xA;Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#xA;&#39;/mnt/trusted-ca/ca-bundle.crt&#39; -&gt; &#39;/etc/pki/ca-trust/source/anchors/ca-bundle.crt&#39;&#xA;time=&#34;2026-04-24T05:47:35Z&#34; level=debug msg=&#34;Starting prefetch-dependencies&#34;&#xA;time=&#34;2026-04-24T05:47:35Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-24T05:47:35Z&#34; level=info msg=&#34;Not using package registry proxy because allow-package-registry-proxy is not set to `true` on the cluster level&#34; logger=PrefetchDependencies&#xA;time=&#34;2026-04-24T05:47:35Z&#34; level=info msg=&#34;[param] source-dir: /workspace/source/source&#34;&#xA;time=&#34;2026-04-24T05:47:35Z&#34; level=info msg=&#34;[param] output-dir: /workspace/source/cachi2/output&#34;&#xA;time=&#34;2026-04-24T05:47:35Z&#34; level=info msg=&#34;[param] sbom-format: spdx&#34;&#xA;time=&#34;2026-04-24T05:47:35Z&#34; level=info msg=&#34;[param] mode: strict&#34;&#xA;time=&#34;2026-04-24T05:47:35Z&#34; level=info msg=&#34;[param] output-dir-mount-point: /cachi2/output&#34;&#xA;time=&#34;2026-04-24T05:47:35Z&#34; level=info msg=&#34;[param] env-files: [/workspace/source/cachi2/cachi2.env /workspace/source/cachi2/prefetch.env /workspace/source/cachi2/prefetch-env.json]&#34;&#xA;time=&#34;2026-04-24T05:47:35Z&#34; level=info msg=&#34;[param] git-auth-directory: /workspace/git-basic-auth&#34;&#xA;time=&#34;2026-04-24T05:47:37Z&#34; level=info msg=&#34;hermeto [stdout] hermeto 0.50.1&#34; logger=CliExecutor&#xA;time=&#34;2026-04-24T05:47:37Z&#34; level=warning msg=&#34;No input provided; skipping prefetch-dependencies&#34; logger=PrefetchDependencies&#xA;time=&#34;2026-04-24T05:47:37Z&#34; level=debug msg=&#34;Finished prefetch-dependencies&#34;&#xA;&#xA; pod: go-component-zrwnnm-on-pull404ea0cc7d6a079c4e6a5501e7293721-pod | init container: prepare&#xA;2026/04/24 05:51:36 Entrypoint initialization&#xA;&#xA; pod: go-component-zrwnnm-on-pull404ea0cc7d6a079c4e6a5501e7293721-pod | init container: place-scripts&#xA;2026/04/24 05:51:38 Decoded script /tekton/scripts/script-0-5drzs&#xA;2026/04/24 05:51:38 Decoded script /tekton/scripts/script-1-lwrvl&#xA;&#xA;pod: go-component-zrwnnm-on-pull404ea0cc7d6a079c4e6a5501e7293721-pod | container step-rpms-signature-scan: &#xA;+ set -o pipefail&#xA;+ rpm_verifier --image-url quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469 --image-digest sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8 --workdir /tmp&#xA;Image: quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm@sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8&#xA;No unsigned RPMs found&#xA;&#xA;{&#39;keys&#39;: {&#39;199e2f91fd431d51&#39;: 419, &#39;unsigned&#39;: 0}}&#xA;====================================&#xA;&#xA;Final results:&#xA;{&#34;keys&#34;: {&#34;199e2f91fd431d51&#34;: 419, &#34;unsigned&#34;: 0}}&#xA;Images processed:&#xA;{&#34;image&#34;: {&#34;pullspec&#34;: &#34;quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#34;, &#34;digests&#34;: [&#34;sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8&#34;]}}&#xA;&#xA;pod: go-component-zrwnnm-on-pull404ea0cc7d6a079c4e6a5501e7293721-pod | container step-output-results: &#xA;+ source /utils.sh&#xA;++ OPM_RENDER_CACHE=/tmp/konflux-test-opm-cache&#xA;++ DEFAULT_INDEX_IMAGE=registry.redhat.io/redhat/redhat-operator-index&#xA;++ cat /tmp/status&#xA;+ status=SUCCESS&#xA;++ cat /tmp/results&#xA;+ rpms_data=&#39;{&#34;keys&#34;: {&#34;199e2f91fd431d51&#34;: 419, &#34;unsigned&#34;: 0}}&#39;&#xA;++ cat /tmp/images_processed&#xA;+ images_processed=&#39;{&#34;image&#34;: {&#34;pullspec&#34;: &#34;quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#34;, &#34;digests&#34;: [&#34;sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8&#34;]}}&#39;&#xA;+ &#39;[&#39; SUCCESS == ERROR &#39;]&#39;&#xA;+ note=&#39;Task rpms-signature-scan completed successfully&#39;&#xA;++ make_result_json -r SUCCESS -t &#39;Task rpms-signature-scan completed successfully&#39;&#xA;++ local RESULT=&#xA;++ local SUCCESSES=0&#xA;++ local FAILURES=0&#xA;++ local WARNINGS=0&#xA;++ local &#39;NOTE=For details, check Tekton task log.&#39;&#xA;++ local NAMESPACE=default&#xA;++ local OUTPUT&#xA;++ local OPTIND opt&#xA;++ getopts :r:s:f:w:t:n: opt&#xA;++ case &#34;${opt}&#34; in&#xA;++ RESULT=SUCCESS&#xA;++ getopts :r:s:f:w:t:n: opt&#xA;++ case &#34;${opt}&#34; in&#xA;++ NOTE=&#39;Task rpms-signature-scan completed successfully&#39;&#xA;++ getopts :r:s:f:w:t:n: opt&#xA;++ shift 4&#xA;++ &#39;[&#39; -z SUCCESS &#39;]&#39;&#xA;++ case &#34;${RESULT}&#34; in&#xA;++++ date -u --iso-8601=seconds&#xA;+++ jq -rce --arg date 2026-04-24T05:59:59+00:00 --arg result SUCCESS --arg note &#39;Task rpms-signature-scan completed successfully&#39; --arg namespace default --arg successes 0 --arg failures 0 --arg warnings 0 --null-input &#39;{  result: $result,&#xA;        timestamp: $date,&#xA;        note: $note,&#xA;        namespace: $namespace,&#xA;        successes: $successes|tonumber,&#xA;        failures: $failures|tonumber,&#xA;        warnings: $warnings|tonumber&#xA;    }&#39;&#xA;++ OUTPUT=&#39;{&#34;result&#34;:&#34;SUCCESS&#34;,&#34;timestamp&#34;:&#34;2026-04-24T05:59:59+00:00&#34;,&#34;note&#34;:&#34;Task rpms-signature-scan completed successfully&#34;,&#34;namespace&#34;:&#34;default&#34;,&#34;successes&#34;:0,&#34;failures&#34;:0,&#34;warnings&#34;:0}&#39;&#xA;++ echo &#39;{&#34;result&#34;:&#34;SUCCESS&#34;,&#34;timestamp&#34;:&#34;2026-04-24T05:59:59+00:00&#34;,&#34;note&#34;:&#34;Task rpms-signature-scan completed successfully&#34;,&#34;namespace&#34;:&#34;default&#34;,&#34;successes&#34;:0,&#34;failures&#34;:0,&#34;warnings&#34;:0}&#39;&#xA;+ TEST_OUTPUT=&#39;{&#34;result&#34;:&#34;SUCCESS&#34;,&#34;timestamp&#34;:&#34;2026-04-24T05:59:59+00:00&#34;,&#34;note&#34;:&#34;Task rpms-signature-scan completed successfully&#34;,&#34;namespace&#34;:&#34;default&#34;,&#34;successes&#34;:0,&#34;failures&#34;:0,&#34;warnings&#34;:0}&#39;&#xA;+ echo &#39;{&#34;result&#34;:&#34;SUCCESS&#34;,&#34;timestamp&#34;:&#34;2026-04-24T05:59:59+00:00&#34;,&#34;note&#34;:&#34;Task rpms-signature-scan completed successfully&#34;,&#34;namespace&#34;:&#34;default&#34;,&#34;successes&#34;:0,&#34;failures&#34;:0,&#34;warnings&#34;:0}&#39;&#xA;+ tee /tekton/results/TEST_OUTPUT&#xA;{&#34;result&#34;:&#34;SUCCESS&#34;,&#34;timestamp&#34;:&#34;2026-04-24T05:59:59+00:00&#34;,&#34;note&#34;:&#34;Task rpms-signature-scan completed successfully&#34;,&#34;namespace&#34;:&#34;default&#34;,&#34;successes&#34;:0,&#34;failures&#34;:0,&#34;warnings&#34;:0}&#xA;+ echo &#39;{&#34;keys&#34;: {&#34;199e2f91fd431d51&#34;: 419, &#34;unsigned&#34;: 0}}&#39;&#xA;+ tee /tekton/results/RPMS_DATA&#xA;{&#34;keys&#34;: {&#34;199e2f91fd431d51&#34;: 419, &#34;unsigned&#34;: 0}}&#xA;+ echo &#39;{&#34;image&#34;: {&#34;pullspec&#34;: &#34;quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#34;, &#34;digests&#34;: [&#34;sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8&#34;]}}&#39;&#xA;+ tee /tekton/results/IMAGES_PROCESSED&#xA;{&#34;image&#34;: {&#34;pullspec&#34;: &#34;quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#34;, &#34;digests&#34;: [&#34;sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8&#34;]}}&#xA;&#xA; pod: go-component-zrwnnm-on-pullaef26abfca3a7b07514b9fbe2fa2b941-pod | init container: prepare&#xA;2026/04/24 05:51:32 Entrypoint initialization&#xA;&#xA; pod: go-component-zrwnnm-on-pullaef26abfca3a7b07514b9fbe2fa2b941-pod | init container: place-scripts&#xA;2026/04/24 05:51:36 Decoded script /tekton/scripts/script-0-t6x9g&#xA;2026/04/24 05:51:36 Decoded script /tekton/scripts/script-1-hscqw&#xA;2026/04/24 05:51:36 Decoded script /tekton/scripts/script-2-shhbn&#xA;2026/04/24 05:51:36 Decoded script /tekton/scripts/script-3-cnvnc&#xA;2026/04/24 05:51:36 Decoded script /tekton/scripts/script-4-sd2hr&#xA;2026/04/24 05:51:36 Decoded script /tekton/scripts/script-5-2lrnw&#xA;&#xA;pod: go-component-zrwnnm-on-pullaef26abfca3a7b07514b9fbe2fa2b941-pod | container step-introspect: &#xA;Artifact type will be determined by introspection.&#xA;Checking the media type of the OCI artifact...&#xA;[retry] executing: skopeo inspect --raw --retry-times 3 docker://quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#xA;The media type of the OCI artifact is application/vnd.docker.distribution.manifest.v2+json.&#xA;Looking for image labels that indicate this might be an operator bundle...&#xA;[retry] executing: skopeo inspect --retry-times 3 docker://quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#xA;Found 0 matching labels.&#xA;Expecting 3 or more to identify this image as an operator bundle.&#xA;Introspection concludes that this artifact is of type &#34;application&#34;.&#xA;&#xA;pod: go-component-zrwnnm-on-pullaef26abfca3a7b07514b9fbe2fa2b941-pod | container step-generate-container-auth: &#xA;Selecting auth for quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#xA;Using token for quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm&#xA;Auth json written to &#34;/auth/auth.json&#34;.&#xA;&#xA;pod: go-component-zrwnnm-on-pullaef26abfca3a7b07514b9fbe2fa2b941-pod | container step-set-skip-for-bundles: &#xA;2026/04/24 05:59:04 INFO Step was skipped due to when expressions were evaluated to false.&#xA;&#xA;pod: go-component-zrwnnm-on-pullaef26abfca3a7b07514b9fbe2fa2b941-pod | container step-app-check: &#xA;time=&#34;2026-04-24T05:59:05Z&#34; level=info msg=&#34;certification library version&#34; version=&#34;1.17.2 &lt;commit: eb87e5b2d67ad110a0afe8edfb16f445e0877c4e&gt;&#34;&#xA;time=&#34;2026-04-24T05:59:05Z&#34; level=info msg=&#34;running checks for quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469 for platform amd64&#34;&#xA;time=&#34;2026-04-24T05:59:05Z&#34; level=info msg=&#34;target image&#34; image=&#34;quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#34;&#xA;time=&#34;2026-04-24T05:59:37Z&#34; level=info msg=&#34;warning: licenses directory does not exist or all of its children are empty directories: error when checking for /licenses: stat /tmp/preflight-925271169/fs/licenses: no such file or directory&#34; check=HasLicense&#xA;time=&#34;2026-04-24T05:59:37Z&#34; level=info msg=&#34;check completed&#34; check=HasLicense result=FAILED&#xA;time=&#34;2026-04-24T05:59:37Z&#34; level=info msg=&#34;check completed&#34; check=HasUniqueTag result=PASSED&#xA;time=&#34;2026-04-24T05:59:37Z&#34; level=info msg=&#34;check completed&#34; check=LayerCountAcceptable result=PASSED&#xA;time=&#34;2026-04-24T05:59:37Z&#34; level=info msg=&#34;check completed&#34; check=HasNoProhibitedPackages result=PASSED&#xA;time=&#34;2026-04-24T05:59:37Z&#34; level=info msg=&#34;check completed&#34; check=HasRequiredLabel result=PASSED&#xA;time=&#34;2026-04-24T05:59:37Z&#34; level=info msg=&#34;USER 1001 specified that is non-root&#34; check=RunAsNonRoot&#xA;time=&#34;2026-04-24T05:59:37Z&#34; level=info msg=&#34;check completed&#34; check=RunAsNonRoot result=PASSED&#xA;time=&#34;2026-04-24T06:00:05Z&#34; level=info msg=&#34;check completed&#34; check=HasModifiedFiles result=PASSED&#xA;time=&#34;2026-04-24T06:00:05Z&#34; level=info msg=&#34;check completed&#34; check=BasedOnUbi result=PASSED&#xA;time=&#34;2026-04-24T06:00:05Z&#34; level=info msg=&#34;This image&#39;s tag on-pr-93e2088996e261a167eab61824669c3c2f684469 will be paired with digest sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8 once this image has been published in accordance with Red Hat Certification policy. You may then add or remove any supplemental tags through your Red Hat Connect portal as you see fit.&#34;&#xA;{&#xA;    &#34;image&#34;: &#34;quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#34;,&#xA;    &#34;passed&#34;: false,&#xA;    &#34;test_library&#34;: {&#xA;        &#34;name&#34;: &#34;github.com/redhat-openshift-ecosystem/openshift-preflight&#34;,&#xA;        &#34;version&#34;: &#34;1.17.2&#34;,&#xA;        &#34;commit&#34;: &#34;eb87e5b2d67ad110a0afe8edfb16f445e0877c4e&#34;&#xA;    },&#xA;    &#34;results&#34;: {&#xA;        &#34;passed&#34;: [&#xA;time=&#34;2026-04-24T06:00:06Z&#34; level=info msg=&#34;Preflight result: FAILED&#34;&#xA;            {&#xA;                &#34;name&#34;: &#34;HasUniqueTag&#34;,&#xA;                &#34;elapsed_time&#34;: 0,&#xA;                &#34;description&#34;: &#34;Checking if container has a tag other than &#39;latest&#39;, so that the image can be uniquely identified.&#34;&#xA;            },&#xA;            {&#xA;                &#34;name&#34;: &#34;LayerCountAcceptable&#34;,&#xA;                &#34;elapsed_time&#34;: 0,&#xA;                &#34;description&#34;: &#34;Checking if container has less than 40 layers.  Too many layers within the container images can degrade container performance.&#34;&#xA;            },&#xA;            {&#xA;                &#34;name&#34;: &#34;HasNoProhibitedPackages&#34;,&#xA;                &#34;elapsed_time&#34;: 130,&#xA;                &#34;description&#34;: &#34;Checks to ensure that the image in use does not include prohibited packages, such as Red Hat Enterprise Linux (RHEL) kernel packages.&#34;&#xA;            },&#xA;            {&#xA;                &#34;name&#34;: &#34;HasRequiredLabel&#34;,&#xA;                &#34;elapsed_time&#34;: 0,&#xA;                &#34;description&#34;: &#34;Checking if the required labels (name, vendor, version, release, summary, description, maintainer) are present in the container metadata&#34;&#xA;            },&#xA;            {&#xA;                &#34;name&#34;: &#34;RunAsNonRoot&#34;,&#xA;                &#34;elapsed_time&#34;: 0,&#xA;                &#34;description&#34;: &#34;Checking if container runs as the root user because a container that does not specify a non-root user will fail the automatic certification, and will be subject to a manual review before the container can be approved for publication&#34;&#xA;            },&#xA;            {&#xA;                &#34;name&#34;: &#34;HasModifiedFiles&#34;,&#xA;                &#34;elapsed_time&#34;: 27862,&#xA;                &#34;description&#34;: &#34;Checks that no files installed via RPM in the base Red Hat layer have been modified&#34;&#xA;            },&#xA;            {&#xA;                &#34;name&#34;: &#34;BasedOnUbi&#34;,&#xA;                &#34;elapsed_time&#34;: 908,&#xA;                &#34;description&#34;: &#34;Checking if the container&#39;s base image is based upon the Red Hat Universal Base Image (UBI)&#34;&#xA;            }&#xA;        ],&#xA;        &#34;failed&#34;: [&#xA;            {&#xA;                &#34;name&#34;: &#34;HasLicense&#34;,&#xA;                &#34;elapsed_time&#34;: 0,&#xA;                &#34;description&#34;: &#34;Checking if terms and conditions applicable to the software including open source licensing information are present. The license must be at /licenses&#34;,&#xA;                &#34;help&#34;: &#34;Check HasLicense encountered an error. Please review the preflight.log file for more information.&#34;,&#xA;                &#34;suggestion&#34;: &#34;Create a directory named /licenses and include all relevant licensing and/or terms and conditions as text file(s) in that directory.&#34;,&#xA;                &#34;knowledgebase_url&#34;: &#34;https://access.redhat.com/documentation/en-us/red_hat_software_certification/2024/html-single/red_hat_openshift_software_certification_policy_guide/index#assembly-requirements-for-container-images_openshift-sw-cert-policy-introduction&#34;,&#xA;                &#34;check_url&#34;: &#34;https://access.redhat.com/documentation/en-us/red_hat_software_certification/2024/html-single/red_hat_openshift_software_certification_policy_guide/index#assembly-requirements-for-container-images_openshift-sw-cert-policy-introduction&#34;&#xA;            }&#xA;        ],&#xA;        &#34;errors&#34;: []&#xA;    }&#xA;}&#xA;&#xA;pod: go-component-zrwnnm-on-pullaef26abfca3a7b07514b9fbe2fa2b941-pod | container step-app-set-outcome: &#xA;[retry] executing: skopeo inspect --raw --retry-times 3 docker://quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#xA;{&#34;result&#34;:&#34;FAILURE&#34;,&#34;timestamp&#34;:&#34;1777010406&#34;,&#34;note&#34;:&#34;Task preflight is a FAILURE: Refer to Tekton task logs for more information&#34;,&#34;successes&#34;:7,&#34;failures&#34;:1,&#34;warnings&#34;:0}&#xA;pod: go-component-zrwnnm-on-pullaef26abfca3a7b07514b9fbe2fa2b941-pod | container step-final-outcome: &#xA;+ [[ ! -f /mount/konflux.results.json ]]&#xA;+ tee /tekton/steps/step-final-outcome/results/test-output&#xA;{&#34;result&#34;:&#34;FAILURE&#34;,&#34;timestamp&#34;:&#34;1777010406&#34;,&#34;note&#34;:&#34;Task preflight is a FAILURE: Refer to Tekton task logs for more information&#34;,&#34;successes&#34;:7,&#34;failures&#34;:1,&#34;warnings&#34;:0}&#xA; pod: go-component-zrwnnm-on-pullf9dded91954aa62705ffbffb4b94b434-pod | init container: prepare&#xA;2026/04/24 05:51:34 Entrypoint initialization&#xA;&#xA; pod: go-component-zrwnnm-on-pullf9dded91954aa62705ffbffb4b94b434-pod | init container: place-scripts&#xA;2026/04/24 05:51:37 Decoded script /tekton/scripts/script-0-gkxjj&#xA;2026/04/24 05:51:37 Decoded script /tekton/scripts/script-1-5fxbn&#xA;&#xA; pod: go-component-zrwnnm-on-pullf9dded91954aa62705ffbffb4b94b434-pod | init container: working-dir-initializer&#xA;&#xA;pod: go-component-zrwnnm-on-pullf9dded91954aa62705ffbffb4b94b434-pod | container step-sast-unicode-check: &#xA;+ . /utils.sh&#xA;++ OPM_RENDER_CACHE=/tmp/konflux-test-opm-cache&#xA;++ DEFAULT_INDEX_IMAGE=registry.redhat.io/redhat/redhat-operator-index&#xA;+ trap &#39;handle_error /tekton/results/TEST_OUTPUT&#39; EXIT&#xA;+ [[ -z &#39;&#39; ]]&#xA;+ PROJECT_NAME=go-component-zrwnnm&#xA;+ echo &#39;INFO: The PROJECT_NAME used is: go-component-zrwnnm&#39;&#xA;+ ca_bundle=/mnt/trusted-ca/ca-bundle.crt&#xA;INFO: The PROJECT_NAME used is: go-component-zrwnnm&#xA;+ &#39;[&#39; -f /mnt/trusted-ca/ca-bundle.crt &#39;]&#39;&#xA;INFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#xA;+ echo &#39;INFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#39;&#xA;+ cp -vf /mnt/trusted-ca/ca-bundle.crt /etc/pki/ca-trust/source/anchors&#xA;&#39;/mnt/trusted-ca/ca-bundle.crt&#39; -&gt; &#39;/etc/pki/ca-trust/source/anchors/ca-bundle.crt&#39;&#xA;+ update-ca-trust&#xA;+ SCAN_PROP=https://github.com/siddhesh/find-unicode-control.git#c2accbfbba7553a8bc1ebd97089ae08ad8347e58&#xA;+ FUC_EXIT_CODE=0&#xA;+ LANG=en_US.utf8&#xA;+ find_unicode_control.py -p bidi -v -d -t /workspace/workspace/source&#xA;+ [[ 0 -ne 0 ]]&#xA;+ sed -i raw_sast_unicode_check_out.txt -E -e &#39;s|(.*:[0-9]+)(.*)|\1: warning:\2|&#39; -e &#39;s|^|Error: UNICONTROL_WARNING:\n|&#39;&#xA;+ CSGERP_OPTS=(--mode=json --remove-duplicates --embed-context=3 --set-scan-prop=&#34;${SCAN_PROP}&#34; --strip-path-prefix=&#34;${SOURCE_CODE_DIR}&#34;/source/)&#xA;+ csgrep --mode=json --remove-duplicates --embed-context=3 --set-scan-prop=https://github.com/siddhesh/find-unicode-control.git#c2accbfbba7553a8bc1ebd97089ae08ad8347e58 --strip-path-prefix=/workspace/workspace/source/ raw_sast_unicode_check_out.txt&#xA;+ csgrep --mode=evtstat processed_sast_unicode_check_out.json&#xA;+ [[ SITE_DEFAULT == \S\I\T\E\_\D\E\F\A\U\L\T ]]&#xA;+ KFP_GIT_URL=https://gitlab.cee.redhat.com/osh/known-false-positives.git&#xA;+ PROBE_URL=https://gitlab.cee.redhat.com/osh/known-false-positives&#xA;+ KFP_DIR=known-false-positives&#xA;+ KFP_CLONED=0&#xA;+ mkdir known-false-positives&#xA;+ [[ -n https://gitlab.cee.redhat.com/osh/known-false-positives.git ]]&#xA;+ echo -n &#39;INFO: Probing https://gitlab.cee.redhat.com/osh/known-false-positives... &#39;&#xA;+ curl --fail --head --max-time 60 --no-progress-meter https://gitlab.cee.redhat.com/osh/known-false-positives&#xA;++ head -1&#xA;curl: (6) Could not resolve host: gitlab.cee.redhat.com&#xA;+ [[ 0 -eq 0 ]]&#xA;INFO: Probing https://gitlab.cee.redhat.com/osh/known-false-positives... WARN: Failed to clone known-false-positives at https://gitlab.cee.redhat.com/osh/known-false-positives.git, scan results will not be filtered&#xA;+ echo &#39;WARN: Failed to clone known-false-positives at https://gitlab.cee.redhat.com/osh/known-false-positives.git, scan results will not be filtered&#39;&#xA;+ mv processed_sast_unicode_check_out.json sast_unicode_check_out.json&#xA;+ csgrep --mode=sarif sast_unicode_check_out.json&#xA;+ [[ 0 -eq 0 ]]&#xA;+ note=&#39;Task sast-unicode-check success: No finding was detected&#39;&#xA;++ make_result_json -r SUCCESS -t &#39;Task sast-unicode-check success: No finding was detected&#39;&#xA;++ local RESULT=&#xA;++ local SUCCESSES=0&#xA;++ local FAILURES=0&#xA;++ local WARNINGS=0&#xA;++ local &#39;NOTE=For details, check Tekton task log.&#39;&#xA;++ local NAMESPACE=default&#xA;++ local OUTPUT&#xA;++ local OPTIND opt&#xA;++ getopts :r:s:f:w:t:n: opt&#xA;++ case &#34;${opt}&#34; in&#xA;++ RESULT=SUCCESS&#xA;++ getopts :r:s:f:w:t:n: opt&#xA;++ case &#34;${opt}&#34; in&#xA;++ NOTE=&#39;Task sast-unicode-check success: No finding was detected&#39;&#xA;++ getopts :r:s:f:w:t:n: opt&#xA;++ shift 4&#xA;++ &#39;[&#39; -z SUCCESS &#39;]&#39;&#xA;++ case &#34;${RESULT}&#34; in&#xA;++++ date -u --iso-8601=seconds&#xA;+++ jq -rce --arg date 2026-04-24T05:59:04+00:00 --arg result SUCCESS --arg note &#39;Task sast-unicode-check success: No finding was detected&#39; --arg namespace default --arg successes 0 --arg failures 0 --arg warnings 0 --null-input &#39;{  result: $result,&#xA;        timestamp: $date,&#xA;        note: $note,&#xA;        namespace: $namespace,&#xA;        successes: $successes|tonumber,&#xA;        failures: $failures|tonumber,&#xA;        warnings: $warnings|tonumber&#xA;    }&#39;&#xA;++ OUTPUT=&#39;{&#34;result&#34;:&#34;SUCCESS&#34;,&#34;timestamp&#34;:&#34;2026-04-24T05:59:04+00:00&#34;,&#34;note&#34;:&#34;Task sast-unicode-check success: No finding was detected&#34;,&#34;namespace&#34;:&#34;default&#34;,&#34;successes&#34;:0,&#34;failures&#34;:0,&#34;warnings&#34;:0}&#39;&#xA;++ echo &#39;{&#34;result&#34;:&#34;SUCCESS&#34;,&#34;timestamp&#34;:&#34;2026-04-24T05:59:04+00:00&#34;,&#34;note&#34;:&#34;Task sast-unicode-check success: No finding was detected&#34;,&#34;namespace&#34;:&#34;default&#34;,&#34;successes&#34;:0,&#34;failures&#34;:0,&#34;warnings&#34;:0}&#39;&#xA;+ ERROR_OUTPUT=&#39;{&#34;result&#34;:&#34;SUCCESS&#34;,&#34;timestamp&#34;:&#34;2026-04-24T05:59:04+00:00&#34;,&#34;note&#34;:&#34;Task sast-unicode-check success: No finding was detected&#34;,&#34;namespace&#34;:&#34;default&#34;,&#34;successes&#34;:0,&#34;failures&#34;:0,&#34;warnings&#34;:0}&#39;&#xA;+ echo &#39;{&#34;result&#34;:&#34;SUCCESS&#34;,&#34;timestamp&#34;:&#34;2026-04-24T05:59:04+00:00&#34;,&#34;note&#34;:&#34;Task sast-unicode-check success: No finding was detected&#34;,&#34;namespace&#34;:&#34;default&#34;,&#34;successes&#34;:0,&#34;failures&#34;:0,&#34;warnings&#34;:0}&#39;&#xA;+ tee /tekton/results/TEST_OUTPUT&#xA;{&#34;result&#34;:&#34;SUCCESS&#34;,&#34;timestamp&#34;:&#34;2026-04-24T05:59:04+00:00&#34;,&#34;note&#34;:&#34;Task sast-unicode-check success: No finding was detected&#34;,&#34;namespace&#34;:&#34;default&#34;,&#34;successes&#34;:0,&#34;failures&#34;:0,&#34;warnings&#34;:0}&#xA;+ handle_error /tekton/results/TEST_OUTPUT&#xA;+ exit_code=0&#xA;+ &#39;[&#39; 0 -ne 0 &#39;]&#39;&#xA;+ exit 0&#xA;&#xA;pod: go-component-zrwnnm-on-pullf9dded91954aa62705ffbffb4b94b434-pod | container step-upload: &#xA;Selecting auth&#xA;Using token for quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm&#xA;Attaching to quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469&#xA;Executing: oras attach --no-tty --registry-config /home/oras/auth.json --artifact-type application/sarif+json quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469@sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8 sast_unicode_check_out.sarif:application/sarif+json&#xA;Preparing sast_unicode_check_out.sarif&#xA;Uploading 1da9b99b8b41 sast_unicode_check_out.sarif&#xA;Exists    44136fa355b3 application/vnd.oci.empty.v1+json&#xA;Uploaded  1da9b99b8b41 sast_unicode_check_out.sarif&#xA;Uploading 34aa7c83453a application/vnd.oci.image.manifest.v1+json&#xA;Uploaded  34aa7c83453a application/vnd.oci.image.manifest.v1+json&#xA;Attached to [registry] quay.io/redhat-appstudio-qe/group-vgzf/go-component-zrwnnm:on-pr-93e2088996e261a167eab61824669c3c2f684469@sha256:8a30a7f71271be8b3e22f7af1ccdfc5789713e2402c47baca828b8fbb4b919c8&#xA;Digest: sha256:34aa7c83453a0c6643000b44c28616a78fac1044a92b2a7d9c7a72dcfab9534a&#xA;No excluded-findings.json exists. Skipping upload.&#xA;New PipelineRun go-component-zrwnnm-on-pull-request-58sxz found after retrigger for component group-vgzf/go-component-zrwnnm&#xA;PipelineRun go-component-zrwnnm-on-pull-request-58sxz found for Component group-vgzf/go-component-zrwnnm&#xA;PipelineRun go-component-zrwnnm-on-pull-request-58sxz reason: ResolvingTaskRef&#xA;PipelineRun go-component-zrwnnm-on-pull-request-58sxz reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-58sxz reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-58sxz reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-58sxz reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-58sxz reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-58sxz reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-58sxz reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-58sxz reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-58sxz reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-58sxz reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-58sxz reason: Running&#xA;PipelineRun go-component-zrwnnm-on-pull-request-58sxz reason: Completed&#xA;&lt; Exit [It] should lead to build PipelineRunA finishing successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:231 @ 04/24/26 06:05:04.05 (18m23.946s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:05:04.051&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:05:04.051 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component A should lead to a PaC PR creation for componentA go-component [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.591243498">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for componentA go-component - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:236 @ 04/24/26 06:05:04.051&#xA;&lt; Exit [It] should lead to a PaC PR creation for componentA go-component - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:236 @ 04/24/26 06:05:04.642 (591ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:05:04.642&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:05:04.643 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Build PLRA is finished successfully checks if the Snapshot is created [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.068576026">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:258 @ 04/24/26 06:05:04.643&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:258 @ 04/24/26 06:05:04.711 (68ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:05:04.711&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:05:04.711 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Build PLRA is finished successfully should find the related Integration PipelineRuns [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.068669619">
              <system-err>&gt; Enter [It] should find the related Integration PipelineRuns - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:263 @ 04/24/26 06:05:04.712&#xA;&lt; Exit [It] should find the related Integration PipelineRuns - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:263 @ 04/24/26 06:05:04.78 (68ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:05:04.78&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:05:04.781 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Build PLRA is finished successfully integration pipeline should end up with success [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="20.138427881">
              <system-err>&gt; Enter [It] integration pipeline should end up with success - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:270 @ 04/24/26 06:05:04.781&#xA;PipelineRun integration-resolver-pipelinerun-42h6d reason: Running&#xA;PipelineRun integration-resolver-pipelinerun-42h6d reason: Succeeded&#xA;&lt; Exit [It] integration pipeline should end up with success - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:270 @ 04/24/26 06:05:24.919 (20.138s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:05:24.919&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:05:24.919 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Snapshot testing is completed successfully should merge the init PaC PR successfully [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="1.689855998">
              <system-err>&gt; Enter [It] should merge the init PaC PR successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:277 @ 04/24/26 06:05:24.92&#xA;merged result sha: 36f9c9df50e9dee38aa310f8cf8b0c8a1d480fd9 for PR #21341&#xA;&lt; Exit [It] should merge the init PaC PR successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:277 @ 04/24/26 06:05:26.609 (1.689s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:05:26.61&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:05:26.61 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component B creates the Component B successfully [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="10.141069279">
              <system-err>&gt; Enter [It] creates the Component B successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:296 @ 04/24/26 06:05:26.61&#xA;Image repository for component python-component-eyavfg in namespace group-vgzf do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [It] creates the Component B successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:296 @ 04/24/26 06:05:36.751 (10.141s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:05:36.751&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:05:36.751 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component B triggers a Build PipelineRun for component python-component [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="20.205213802">
              <system-err>&gt; Enter [It] triggers a Build PipelineRun for component python-component - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:304 @ 04/24/26 06:05:36.752&#xA;Build PipelineRun has not been created yet for the componentB group-vgzf/python-component-eyavfg&#xA;&lt; Exit [It] triggers a Build PipelineRun for component python-component - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:304 @ 04/24/26 06:05:56.957 (20.205s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:05:56.957&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:05:56.957 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component B does not contain an annotation with a Snapshot Name [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.000294399">
              <system-err>&gt; Enter [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:318 @ 04/24/26 06:05:56.957&#xA;&lt; Exit [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:318 @ 04/24/26 06:05:56.957 (0s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:05:56.958&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:05:56.958 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component B should lead to build PipelineRun finishing successfully [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="200.205379406">
              <system-err>&gt; Enter [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:322 @ 04/24/26 06:05:56.958&#xA;PipelineRun python-component-eyavfg-on-pull-request-8tjkz found for Component group-vgzf/python-component-eyavfg&#xA;PipelineRun python-component-eyavfg-on-pull-request-8tjkz reason: Running&#xA;PipelineRun python-component-eyavfg-on-pull-request-8tjkz reason: Running&#xA;PipelineRun python-component-eyavfg-on-pull-request-8tjkz reason: Running&#xA;PipelineRun python-component-eyavfg-on-pull-request-8tjkz reason: Running&#xA;PipelineRun python-component-eyavfg-on-pull-request-8tjkz reason: Running&#xA;PipelineRun python-component-eyavfg-on-pull-request-8tjkz reason: Running&#xA;PipelineRun python-component-eyavfg-on-pull-request-8tjkz reason: Running&#xA;PipelineRun python-component-eyavfg-on-pull-request-8tjkz reason: Running&#xA;PipelineRun python-component-eyavfg-on-pull-request-8tjkz reason: Running&#xA;PipelineRun python-component-eyavfg-on-pull-request-8tjkz reason: Running&#xA;PipelineRun integration-resolver-pipelinerun-w89x8 reason: Succeeded&#xA;&lt; Exit [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:322 @ 04/24/26 06:09:17.163 (3m20.205s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:09:17.163&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:09:17.163 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component B should lead to a PaC PR creation for component python-component [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.471323781">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for component python-component - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:327 @ 04/24/26 06:09:17.164&#xA;&lt; Exit [It] should lead to a PaC PR creation for component python-component - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:327 @ 04/24/26 06:09:17.635 (471ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:09:17.635&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:09:17.635 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Build PLR is finished successfully checks if the Snapshot is created [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.06843718">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:349 @ 04/24/26 06:09:17.636&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:349 @ 04/24/26 06:09:17.704 (68ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:09:17.704&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:09:17.704 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Build PLR is finished successfully should find the related Integration PipelineRuns [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.068294215">
              <system-err>&gt; Enter [It] should find the related Integration PipelineRuns - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:354 @ 04/24/26 06:09:17.705&#xA;&lt; Exit [It] should find the related Integration PipelineRuns - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:354 @ 04/24/26 06:09:17.773 (68ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:09:17.773&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:09:17.773 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Build PLR is finished successfully integration pipeline should end up with success [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.099445725">
              <system-err>&gt; Enter [It] integration pipeline should end up with success - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:361 @ 04/24/26 06:09:17.773&#xA;PipelineRun integration-resolver-pipelinerun-w89x8 reason: Succeeded&#xA;&lt; Exit [It] integration pipeline should end up with success - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:361 @ 04/24/26 06:09:17.872 (99ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:09:17.873&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:09:17.873 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Snapshot testing is completed successfully should merge the init PaC PR successfully [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="1.797606029">
              <system-err>&gt; Enter [It] should merge the init PaC PR successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:368 @ 04/24/26 06:09:17.873&#xA;merged result sha: 8741c8a5304343e6a12714ae48ed00e4f5992a2e for PR #21343&#xA;&lt; Exit [It] should merge the init PaC PR successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:368 @ 04/24/26 06:09:19.67 (1.797s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:09:19.671&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:09:19.671 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component C creates the Component C successfully [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="10.139735118">
              <system-err>&gt; Enter [It] creates the Component C successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:387 @ 04/24/26 06:09:19.671&#xA;Image repository for component konflux-test-integration-clone-ysrmaw in namespace group-vgzf do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [It] creates the Component C successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:387 @ 04/24/26 06:09:29.811 (10.139s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:09:29.811&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:09:29.811 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component C triggers a Build PipelineRun for componentC konflux-test-integration-clone [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="20.204636543">
              <system-err>&gt; Enter [It] triggers a Build PipelineRun for componentC konflux-test-integration-clone - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:395 @ 04/24/26 06:09:29.812&#xA;Build PipelineRun has not been created yet for the componentC group-vgzf/konflux-test-integration-clone-ysrmaw&#xA;&lt; Exit [It] triggers a Build PipelineRun for componentC konflux-test-integration-clone - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:395 @ 04/24/26 06:09:50.016 (20.204s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:09:50.016&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:09:50.016 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component C does not contain an annotation with a Snapshot Name [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.000292649">
              <system-err>&gt; Enter [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:409 @ 04/24/26 06:09:50.017&#xA;&lt; Exit [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:409 @ 04/24/26 06:09:50.017 (0s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:09:50.017&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:09:50.017 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component C should lead to build PipelineRun finishing successfully [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="200.20218438">
              <system-err>&gt; Enter [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:413 @ 04/24/26 06:09:50.017&#xA;PipelineRun konflux-test-integration-clone-ysrmaw-on-pull-request-t6t64 found for Component group-vgzf/konflux-test-integration-clone-ysrmaw&#xA;PipelineRun konflux-test-integration-clone-ysrmaw-on-pull-request-t6t64 reason: Running&#xA;PipelineRun konflux-test-integration-clone-ysrmaw-on-pull-request-t6t64 reason: Running&#xA;PipelineRun konflux-test-integration-clone-ysrmaw-on-pull-request-t6t64 reason: Running&#xA;PipelineRun konflux-test-integration-clone-ysrmaw-on-pull-request-t6t64 reason: Running&#xA;PipelineRun konflux-test-integration-clone-ysrmaw-on-pull-request-t6t64 reason: Running&#xA;PipelineRun konflux-test-integration-clone-ysrmaw-on-pull-request-t6t64 reason: Running&#xA;PipelineRun konflux-test-integration-clone-ysrmaw-on-pull-request-t6t64 reason: Running&#xA;PipelineRun konflux-test-integration-clone-ysrmaw-on-pull-request-t6t64 reason: Running&#xA;PipelineRun konflux-test-integration-clone-ysrmaw-on-pull-request-t6t64 reason: Running&#xA;PipelineRun integration-resolver-pipelinerun-nm7rw reason: Running&#xA;PipelineRun integration-resolver-pipelinerun-nm7rw reason: Succeeded&#xA;&lt; Exit [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:413 @ 04/24/26 06:13:10.219 (3m20.202s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:13:10.219&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:13:10.219 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component C should lead to a PaC PR creation for componentC konflux-test-integration-clone [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.492635799">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for componentC konflux-test-integration-clone - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:418 @ 04/24/26 06:13:10.22&#xA;&lt; Exit [It] should lead to a PaC PR creation for componentC konflux-test-integration-clone - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:418 @ 04/24/26 06:13:10.712 (492ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:13:10.712&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:13:10.712 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Build PLR is finished successfully checks if the Snapshot is created [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.068700192">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:440 @ 04/24/26 06:13:10.713&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:440 @ 04/24/26 06:13:10.781 (68ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:13:10.782&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:13:10.782 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Build PLR is finished successfully should find the related Integration PipelineRuns [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.068531568">
              <system-err>&gt; Enter [It] should find the related Integration PipelineRuns - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:445 @ 04/24/26 06:13:10.782&#xA;&lt; Exit [It] should find the related Integration PipelineRuns - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:445 @ 04/24/26 06:13:10.85 (68ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:13:10.851&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:13:10.851 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Build PLR is finished successfully integration pipeline should end up with success [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.068497666">
              <system-err>&gt; Enter [It] integration pipeline should end up with success - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:452 @ 04/24/26 06:13:10.851&#xA;PipelineRun integration-resolver-pipelinerun-nm7rw reason: Succeeded&#xA;&lt; Exit [It] integration pipeline should end up with success - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:452 @ 04/24/26 06:13:10.919 (68ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:13:10.92&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:13:10.92 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Snapshot testing is completed successfully should merge the init PaC PR successfully [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="1.81698644">
              <system-err>&gt; Enter [It] should merge the init PaC PR successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:459 @ 04/24/26 06:13:10.92&#xA;merged result sha: ecfe1de79c7fe37ee11c58396af2d4674e5c5bdf for PR #8936&#xA;&lt; Exit [It] should merge the init PaC PR successfully - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:459 @ 04/24/26 06:13:12.737 (1.817s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:13:12.737&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:13:12.737 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when both the init PaC PRs are merged should make change to the root folder [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="2.758665628">
              <system-err>&gt; Enter [It] should make change to the root folder - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:479 @ 04/24/26 06:13:12.738&#xA;PR #21344 got created with sha 2b417785a3d283d22168e43207a2295ce9cc056c&#xA;&lt; Exit [It] should make change to the root folder - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:479 @ 04/24/26 06:13:15.496 (2.758s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:13:15.496&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:13:15.496 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when both the init PaC PRs are merged should make change to the multiple-repo [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="2.128583153">
              <system-err>&gt; Enter [It] should make change to the multiple-repo - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:497 @ 04/24/26 06:13:15.497&#xA;PR #8937 got created with sha cdf19bb485ae38cc57e05e16b53affcc6450c32d&#xA;&lt; Exit [It] should make change to the multiple-repo - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:497 @ 04/24/26 06:13:17.625 (2.128s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:13:17.625&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:13:17.625 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when both the init PaC PRs are merged wait for the last components build to finish [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.409537687">
              <system-err>&gt; Enter [It] wait for the last components build to finish - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:513 @ 04/24/26 06:13:17.625&#xA;PipelineRun go-component-zrwnnm-on-pull-request-58sxz found for Component group-vgzf/go-component-zrwnnm&#xA;PipelineRun go-component-zrwnnm-on-pull-request-58sxz reason: Completed&#xA;PipelineRun integration-resolver-pipelinerun-w89x8 found for Component group-vgzf/python-component-eyavfg&#xA;PipelineRun integration-resolver-pipelinerun-w89x8 reason: Succeeded&#xA;PipelineRun integration-resolver-pipelinerun-nm7rw found for Component group-vgzf/konflux-test-integration-clone-ysrmaw&#xA;PipelineRun integration-resolver-pipelinerun-nm7rw reason: Succeeded&#xA;&lt; Exit [It] wait for the last components build to finish - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:513 @ 04/24/26 06:13:18.035 (409ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:13:18.035&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:13:18.035 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when both the init PaC PRs are merged wait for all component snapshots to be created with proper PR group annotations [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.069148896">
              <system-err>&gt; Enter [It] wait for all component snapshots to be created with proper PR group annotations - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:521 @ 04/24/26 06:13:18.035&#xA;Component snapshot integ-app-iynh-20260424-060057-000 has PR group annotation: konflux-go-component-zrwnnm&#xA;Component snapshot integ-app-iynh-20260424-060539-000 has PR group annotation: konflux-python-component-eyavfg&#xA;Component snapshot integ-app-iynh-20260424-060932-000 has PR group annotation: konflux-konflux-test-integration-clone-ysrmaw&#xA;All component snapshots are ready with PR group annotations&#xA;&lt; Exit [It] wait for all component snapshots to be created with proper PR group annotations - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:521 @ 04/24/26 06:13:18.104 (69ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:13:18.104&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:13:18.104 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when both the init PaC PRs are merged get all group snapshots and check if pr-group annotation contains all components [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="305.251004271">
              <system-err>&gt; Enter [It] get all group snapshots and check if pr-group annotation contains all components - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:556 @ 04/24/26 06:13:18.105&#xA;Attempting to find group snapshots for application integ-app-iynh in namespace group-vgzf&#xA;Found 3 component snapshots:&#xA;PR Groups found: map[konflux-go-component-zrwnnm:1 konflux-konflux-test-integration-clone-ysrmaw:1 konflux-python-component-eyavfg:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-iynh in namespace group-vgzf&#xA;Found 4 component snapshots:&#xA;PR Groups found: map[konflux-go-component-zrwnnm:1 konflux-konflux-test-integration-clone-ysrmaw:1 konflux-python-component-eyavfg:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-iynh in namespace group-vgzf&#xA;Found 4 component snapshots:&#xA;PR Groups found: map[konflux-go-component-zrwnnm:1 konflux-konflux-test-integration-clone-ysrmaw:1 konflux-python-component-eyavfg:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-iynh in namespace group-vgzf&#xA;Found 4 component snapshots:&#xA;PR Groups found: map[konflux-go-component-zrwnnm:1 konflux-konflux-test-integration-clone-ysrmaw:1 konflux-python-component-eyavfg:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-iynh in namespace group-vgzf&#xA;Found 4 component snapshots:&#xA;PR Groups found: map[konflux-go-component-zrwnnm:1 konflux-konflux-test-integration-clone-ysrmaw:1 konflux-python-component-eyavfg:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-iynh in namespace group-vgzf&#xA;Found 4 component snapshots:&#xA;PR Groups found: map[konflux-go-component-zrwnnm:1 konflux-konflux-test-integration-clone-ysrmaw:1 konflux-python-component-eyavfg:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-iynh in namespace group-vgzf&#xA;Found 4 component snapshots:&#xA;PR Groups found: map[konflux-go-component-zrwnnm:1 konflux-konflux-test-integration-clone-ysrmaw:1 konflux-python-component-eyavfg:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-iynh in namespace group-vgzf&#xA;Found 4 component snapshots:&#xA;PR Groups found: map[konflux-go-component-zrwnnm:1 konflux-konflux-test-integration-clone-ysrmaw:1 konflux-python-component-eyavfg:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-iynh in namespace group-vgzf&#xA;Found 4 component snapshots:&#xA;PR Groups found: map[konflux-go-component-zrwnnm:1 konflux-konflux-test-integration-clone-ysrmaw:1 konflux-python-component-eyavfg:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-iynh in namespace group-vgzf&#xA;Found 4 component snapshots:&#xA;PR Groups found: map[konflux-go-component-zrwnnm:1 konflux-konflux-test-integration-clone-ysrmaw:1 konflux-python-component-eyavfg:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-iynh in namespace group-vgzf&#xA;Found 7 component snapshots:&#xA;PR Groups found: map[konflux-go-component-zrwnnm:1 konflux-konflux-test-integration-clone-ysrmaw:1 konflux-python-component-eyavfg:1 pr-branch-umoqpa:3]&#xA;Found 1 group snapshots!&#xA;  Group Snapshot 0: integ-app-iynh-20260424-061819-255 (type: group)&#xA;    Group Test Info: [{&#34;namespace&#34;:&#34;group-vgzf&#34;,&#34;component&#34;:&#34;go-component-zrwnnm&#34;,&#34;buildPipelineRun&#34;:&#34;go-component-zrwnnm-on-pull-request-bxc7g&#34;,&#34;snapshot&#34;:&#34;integ-app-iynh-20260424-061320-000-of&#34;,&#34;repoUrl&#34;:&#34;https://github.com/redhat-appstudio-qe/group-snapshot-multi-component&#34;,&#34;pullRequestNumber&#34;:&#34;21344&#34;},{&#34;namespace&#34;:&#34;group-vgzf&#34;,&#34;component&#34;:&#34;python-component-eyavfg&#34;,&#34;buildPipelineRun&#34;:&#34;python-component-eyavfg-on-pull-request-2nwgx&#34;,&#34;snapshot&#34;:&#34;integ-app-iynh-20260424-061320-000&#34;,&#34;repoUrl&#34;:&#34;https://github.com/redhat-appstudio-qe/group-snapshot-multi-component&#34;,&#34;pullRequestNumber&#34;:&#34;21344&#34;},{&#34;namespace&#34;:&#34;group-vgzf&#34;,&#34;component&#34;:&#34;konflux-test-integration-clone-ysrmaw&#34;,&#34;buildPipelineRun&#34;:&#34;konflux-test-integration-clone-ysrmaw-on-pull-request-4tjv2&#34;,&#34;snapshot&#34;:&#34;integ-app-iynh-20260424-061321-000&#34;,&#34;repoUrl&#34;:&#34;https://github.com/redhat-appstudio-qe/konflux-test-integration-clone&#34;,&#34;pullRequestNumber&#34;:&#34;8937&#34;}]&#xA;Validating group test info annotation: [{&#34;namespace&#34;:&#34;group-vgzf&#34;,&#34;component&#34;:&#34;go-component-zrwnnm&#34;,&#34;buildPipelineRun&#34;:&#34;go-component-zrwnnm-on-pull-request-bxc7g&#34;,&#34;snapshot&#34;:&#34;integ-app-iynh-20260424-061320-000-of&#34;,&#34;repoUrl&#34;:&#34;https://github.com/redhat-appstudio-qe/group-snapshot-multi-component&#34;,&#34;pullRequestNumber&#34;:&#34;21344&#34;},{&#34;namespace&#34;:&#34;group-vgzf&#34;,&#34;component&#34;:&#34;python-component-eyavfg&#34;,&#34;buildPipelineRun&#34;:&#34;python-component-eyavfg-on-pull-request-2nwgx&#34;,&#34;snapshot&#34;:&#34;integ-app-iynh-20260424-061320-000&#34;,&#34;repoUrl&#34;:&#34;https://github.com/redhat-appstudio-qe/group-snapshot-multi-component&#34;,&#34;pullRequestNumber&#34;:&#34;21344&#34;},{&#34;namespace&#34;:&#34;group-vgzf&#34;,&#34;component&#34;:&#34;konflux-test-integration-clone-ysrmaw&#34;,&#34;buildPipelineRun&#34;:&#34;konflux-test-integration-clone-ysrmaw-on-pull-request-4tjv2&#34;,&#34;snapshot&#34;:&#34;integ-app-iynh-20260424-061321-000&#34;,&#34;repoUrl&#34;:&#34;https://github.com/redhat-appstudio-qe/konflux-test-integration-clone&#34;,&#34;pullRequestNumber&#34;:&#34;8937&#34;}]&#xA;Group snapshot validation completed successfully&#xA;&lt; Exit [It] get all group snapshots and check if pr-group annotation contains all components - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:556 @ 04/24/26 06:18:23.356 (5m5.251s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:18:23.356&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:18:23.356 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when both the init PaC PRs are merged make sure that group snapshot contains last build pipelinerun for each component [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.309702867">
              <system-err>&gt; Enter [It] make sure that group snapshot contains last build pipelinerun for each component - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:635 @ 04/24/26 06:18:23.357&#xA;&lt; Exit [It] make sure that group snapshot contains last build pipelinerun for each component - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:635 @ 04/24/26 06:18:23.666 (309ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:18:23.666&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:18:23.666 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when Older snapshot and integration pipelinerun should be cancelled once new snapshot is created make change to the multiple-repo to trigger a new cycle of testing [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.633830185">
              <system-err>&gt; Enter [It] make change to the multiple-repo to trigger a new cycle of testing - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:648 @ 04/24/26 06:18:23.667&#xA;&lt; Exit [It] make change to the multiple-repo to trigger a new cycle of testing - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:648 @ 04/24/26 06:18:24.3 (633ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:18:24.3&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:18:24.3 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when Older snapshot and integration pipelinerun should be cancelled once new snapshot is created wait for the components A and B build to finish [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.215169401">
              <system-err>&gt; Enter [It] wait for the components A and B build to finish - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:654 @ 04/24/26 06:18:24.301&#xA;Waiting for build pipelineRun to be created for app group-vgzf/integ-app-iynh, sha: 440511e2084536ea442d03f2b161e2c01ce45d28&#xA;PipelineRun go-component-zrwnnm-on-pull-request-58sxz found for Component group-vgzf/go-component-zrwnnm&#xA;PipelineRun go-component-zrwnnm-on-pull-request-58sxz reason: Completed&#xA;PipelineRun integration-resolver-pipelinerun-jrj7p found for Component group-vgzf/python-component-eyavfg&#xA;PipelineRun integration-resolver-pipelinerun-jrj7p reason: Succeeded&#xA;&lt; Exit [It] wait for the components A and B build to finish - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:654 @ 04/24/26 06:18:24.516 (215ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:18:24.516&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:18:24.516 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when Older snapshot and integration pipelinerun should be cancelled once new snapshot is created get all component snapshots for component A and check if older snapshot has been cancelled [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="282.718352449">
              <system-err>&gt; Enter [It] get all component snapshots for component A and check if older snapshot has been cancelled - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:663 @ 04/24/26 06:18:24.517&#xA;&lt; Exit [It] get all component snapshots for component A and check if older snapshot has been cancelled - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:663 @ 04/24/26 06:23:07.235 (4m42.718s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:23:07.235&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:23:07.235 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when Older snapshot and integration pipelinerun should be cancelled once new snapshot is created get all group snapshots and check if older group snapshot is cancelled [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.139761901">
              <system-err>&gt; Enter [It] get all group snapshots and check if older group snapshot is cancelled - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:690 @ 04/24/26 06:23:07.235&#xA;&lt; Exit [It] get all group snapshots and check if older group snapshot is cancelled - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:690 @ 04/24/26 06:23:07.375 (139ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:23:07.375&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:23:07.375 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when ResolutionRequest is deleted after pipeline completes verifies that ResolutionRequest is deleted after pipeline resolution [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.467370013">
              <system-err>&gt; Enter [It] verifies that ResolutionRequest is deleted after pipeline resolution - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:720 @ 04/24/26 06:23:07.375&#xA;&lt; Exit [It] verifies that ResolutionRequest is deleted after pipeline resolution - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:720 @ 04/24/26 06:23:07.842 (467ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:23:07.843&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:23:07.843 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when ResolutionRequest is deleted after pipeline completes verifies that no orphaned ResolutionRequests remain in namespace after test completion [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.22521476">
              <system-err>&gt; Enter [It] verifies that no orphaned ResolutionRequests remain in namespace after test completion - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:740 @ 04/24/26 06:23:07.843&#xA;&lt; Exit [It] verifies that no orphaned ResolutionRequests remain in namespace after test completion - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:740 @ 04/24/26 06:23:08.068 (225ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:23:08.068&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:23:08.068 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when IntegrationTestScenario reference to task as pipelinerun resolution trigger pipelinerun for invalid integrationTestScenario by annotating snapshot and verify failing to create integration pipelinerun [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="26.209917132">
              <system-err>&gt; Enter [BeforeAll] when IntegrationTestScenario reference to task as pipelinerun resolution - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:775 @ 04/24/26 06:23:08.069&#xA;&lt; Exit [BeforeAll] when IntegrationTestScenario reference to task as pipelinerun resolution - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:775 @ 04/24/26 06:23:08.147 (79ms)&#xA;&gt; Enter [It] trigger pipelinerun for invalid integrationTestScenario by annotating snapshot and verify failing to create integration pipelinerun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:780 @ 04/24/26 06:23:08.148&#xA;&lt; Exit [It] trigger pipelinerun for invalid integrationTestScenario by annotating snapshot and verify failing to create integration pipelinerun - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:780 @ 04/24/26 06:23:28.438 (20.29s)&#xA;&gt; Enter [AfterAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:149 @ 04/24/26 06:23:28.438&#xA;&lt; Exit [AfterAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:149 @ 04/24/26 06:23:34.278 (5.841s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:23:34.279&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.LHtSA2pOeP/tests/integration-service/group-snapshots-tests.go:50 @ 04/24/26 06:23:34.279 (0s)&#xA;</system-err>
          </testcase>
      </testsuite>
  </testsuites>