<?xml version="1.0" encoding="UTF-8"?>
  <testsuites tests="469" disabled="157" errors="1" failures="3" time="5242.31666054">
      <testsuite name="Red Hat App Studio E2E tests" package="/tmp/tmp.CNj1aJY7Z5/cmd" tests="469" disabled="88" skipped="69" errors="1" failures="3" time="5242.31666054" timestamp="2026-05-09T02:56:32">
          <properties>
              <property name="SuiteSucceeded" value="false"></property>
              <property name="SuiteHasProgrammaticFocus" value="false"></property>
              <property name="SpecialSuiteFailureReason" value="Suite Timeout Elapsed"></property>
              <property name="SuiteLabels" value="[]"></property>
              <property name="SuiteSemVerConstraints" value="[]"></property>
              <property name="SuiteComponentSemVerConstraints" value="[]"></property>
              <property name="RandomSeed" value="1778294165"></property>
              <property name="RandomizeAllSpecs" value="false"></property>
              <property name="LabelFilter" value=""></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] [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="passed" time="101.175473151">
              <system-err>&gt; Enter [BeforeAll] component update with renovate - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:72 @ 05/09/26 02:56:33.116&#xA;ReleaseAdmissionPlan data: {&#34;Mapping&#34;:{&#34;Components&#34;:[{&#34;Name&#34;:&#34;fj-multi-component-parent-onjp&#34;,&#34;Repository&#34;:&#34;quay.io/redhat-appstudio-qe/release-repository&#34;}]}}&#xA;&lt; Exit [BeforeAll] component update with renovate - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:72 @ 05/09/26 02:57:24.006 (50.89s)&#xA;&gt; Enter [It] creates component with nudges - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:235 @ 05/09/26 02:57:24.006&#xA;Image repository for component fj-multi-component-child-onjp in namespace build-e2e-ldxk do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component fj-multi-component-child-onjp in namespace build-e2e-ldxk do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component fj-multi-component-parent-onjp in namespace build-e2e-ldxk do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component fj-multi-component-parent-onjp in namespace build-e2e-ldxk do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [It] creates component with nudges - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:235 @ 05/09/26 02:58:14.291 (50.284s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 02:58:14.291&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 02:58:14.291 (0s)&#xA;</system-err>
          </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="failed" time="1815.179250714">
              <failure message="Timed out after 1800.000s.&#xA;timed out when waiting for the PipelineRun to start for the component fj-multi-component-parent-onjp/build-e2e-ldxk&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc000ea09b0&gt;: &#xA;    no pipelinerun found for component fj-multi-component-parent-onjp&#xA;    {&#xA;        s: &#34;no pipelinerun found for component fj-multi-component-parent-onjp&#34;,&#xA;    }" type="failed">[FAILED] Timed out after 1800.000s.&#xA;timed out when waiting for the PipelineRun to start for the component fj-multi-component-parent-onjp/build-e2e-ldxk&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc000ea09b0&gt;: &#xA;    no pipelinerun found for component fj-multi-component-parent-onjp&#xA;    {&#xA;        s: &#34;no pipelinerun found for component fj-multi-component-parent-onjp&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:272 @ 05/09/26 03:28:14.292&#xA;</failure>
              <system-err>&gt; Enter [It] triggers a PipelineRun for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:259 @ 05/09/26 02:58:14.292&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;PipelineRun has not been created yet for the component build-e2e-ldxk/fj-multi-component-parent-onjp&#xA;[FAILED] Timed out after 1800.000s.&#xA;timed out when waiting for the PipelineRun to start for the component fj-multi-component-parent-onjp/build-e2e-ldxk&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc000ea09b0&gt;: &#xA;    no pipelinerun found for component fj-multi-component-parent-onjp&#xA;    {&#xA;        s: &#34;no pipelinerun found for component fj-multi-component-parent-onjp&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:272 @ 05/09/26 03:28:14.292&#xA;&lt; Exit [It] triggers a PipelineRun for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:259 @ 05/09/26 03:28:14.292 (30m0s)&#xA;&gt; Enter [AfterAll] component update with renovate - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:214 @ 05/09/26 03:28:14.293&#xA;&lt; Exit [AfterAll] component update with renovate - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:214 @ 05/09/26 03:28:29.321 (15.029s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:28:29.321&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:28:29.471 (150ms)&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:274 @ 05/09/26 03:28:29.472&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:285 @ 05/09/26 03:28:29.472&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:289 @ 05/09/26 03:28:29.472&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:307 @ 05/09/26 03:28:29.472&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:318 @ 05/09/26 03:28:29.472&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:358 @ 05/09/26 03:28:29.473&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:375 @ 05/09/26 03:28:29.473&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:385 @ 05/09/26 03:28:29.473&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:401 @ 05/09/26 03:28:29.473&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:412 @ 05/09/26 03:28:29.473&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:429 @ 05/09/26 03:28:29.474&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:440 @ 05/09/26 03:28:29.474&#xA;</system-err>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Suite] 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="passed" time="6.353108851">
              <system-err>&gt; Enter [BeforeAll] DR Backwards-Compat - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:48 @ 05/09/26 03:56:18.501&#xA;STEP: Validating OADP operator health: pods running in openshift-adp - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:52 @ 05/09/26 03:56:20.003&#xA;STEP: Validating Velero readiness: deployment has ready replicas - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:52 @ 05/09/26 03:56:20.011&#xA;STEP: Validating BSL availability: at least one BackupStorageLocation is Available - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:52 @ 05/09/26 03:56:20.017&#xA;STEP: Validating GitHub repo is reachable: https://github.com/redhat-appstudio-qe/DR_test_MathWizz - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:52 @ 05/09/26 03:56:20.037&#xA;STEP: Validating repo structure: 3 component Dockerfiles exist - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:52 @ 05/09/26 03:56:20.037&#xA;STEP: Forking DR_test_MathWizz → DR-MathWizz-tjqtph for tenant dr-test-kokohazamar-backwards-compat-dr - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:55 @ 05/09/26 03:56:20.268&#xA;STEP: Forking DR_test_MathWizz → DR-MathWizz-xgtqhy for tenant dr-test-moshekipod-backwards-compat-dr - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:55 @ 05/09/26 03:56:21.266&#xA;&lt; Exit [BeforeAll] DR Backwards-Compat - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:48 @ 05/09/26 03:56:22.252 (3.751s)&#xA;&gt; Enter [It] should create both tenants concurrently - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:61 @ 05/09/26 03:56:22.252&#xA;STEP: Creating tenant namespace dr-test-moshekipod-backwards-compat-dr - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:22.252&#xA;STEP: Creating tenant namespace dr-test-kokohazamar-backwards-compat-dr - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:22.252&#xA;STEP: Creating Application moshekipod-backwards-compat-dr in namespace dr-test-moshekipod-backwards-compat-dr - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:23.303&#xA;STEP: Creating Application kokohazamar-backwards-compat-dr in namespace dr-test-kokohazamar-backwards-compat-dr - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:23.307&#xA;STEP: Creating Component mathwizz-web-server in namespace dr-test-moshekipod-backwards-compat-dr - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:23.32&#xA;STEP: Creating Component mathwizz-web-server in namespace dr-test-kokohazamar-backwards-compat-dr - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:23.327&#xA;STEP: Creating Component mathwizz-history-worker in namespace dr-test-moshekipod-backwards-compat-dr - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:23.341&#xA;STEP: Creating Component mathwizz-history-worker in namespace dr-test-kokohazamar-backwards-compat-dr - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:23.344&#xA;STEP: Creating Component mathwizz-frontend in namespace dr-test-moshekipod-backwards-compat-dr - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:23.359&#xA;STEP: Creating Component mathwizz-frontend in namespace dr-test-kokohazamar-backwards-compat-dr - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:23.365&#xA;STEP: Creating managed namespace dr-test-moshekipod-backwards-compat-dr-managed for release pipelines - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:23.376&#xA;STEP: Creating managed namespace dr-test-kokohazamar-backwards-compat-dr-managed for release pipelines - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:23.384&#xA;STEP: Creating release pipeline ServiceAccount release-service-account in managed namespace dr-test-moshekipod-backwards-compat-dr-managed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.418&#xA;STEP: Creating release pipeline ServiceAccount release-service-account in managed namespace dr-test-kokohazamar-backwards-compat-dr-managed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.419&#xA;STEP: Creating release pipeline RoleBinding in managed namespace dr-test-moshekipod-backwards-compat-dr-managed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.431&#xA;STEP: Creating release pipeline RoleBinding in managed namespace dr-test-kokohazamar-backwards-compat-dr-managed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.435&#xA;STEP: Creating registry auth secrets in managed namespace dr-test-moshekipod-backwards-compat-dr-managed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.457&#xA;STEP: Linking Quay auth secret to release SA in managed namespace dr-test-moshekipod-backwards-compat-dr-managed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.472&#xA;STEP: Creating cosign signing secret in managed namespace dr-test-moshekipod-backwards-compat-dr-managed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.477&#xA;STEP: Getting default Enterprise Contract policy from enterprise-contract-service namespace - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.495&#xA;STEP: Creating Enterprise Contract policy dr-ec-policy in managed namespace dr-test-moshekipod-backwards-compat-dr-managed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.501&#xA;STEP: Creating ReleasePlan dr-releaseplan in tenant namespace dr-test-moshekipod-backwards-compat-dr - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.513&#xA;STEP: Creating registry auth secrets in managed namespace dr-test-kokohazamar-backwards-compat-dr-managed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.555&#xA;STEP: Linking Quay auth secret to release SA in managed namespace dr-test-kokohazamar-backwards-compat-dr-managed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.571&#xA;STEP: Creating ReleasePlanAdmission dr-releaseplanadmission in managed namespace dr-test-moshekipod-backwards-compat-dr-managed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.573&#xA;STEP: Creating cosign signing secret in managed namespace dr-test-kokohazamar-backwards-compat-dr-managed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.575&#xA;STEP: Getting default Enterprise Contract policy from enterprise-contract-service namespace - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.594&#xA;STEP: Creating Enterprise Contract policy dr-ec-policy in managed namespace dr-test-kokohazamar-backwards-compat-dr-managed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.605&#xA;STEP: Creating ReleasePlan dr-releaseplan in tenant namespace dr-test-kokohazamar-backwards-compat-dr - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.616&#xA;STEP: Creating release PVC dr-release-pvc in managed namespace dr-test-moshekipod-backwards-compat-dr-managed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.63&#xA;STEP: Creating ReleasePlanAdmission dr-releaseplanadmission in managed namespace dr-test-kokohazamar-backwards-compat-dr-managed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.638&#xA;STEP: Creating secrets access Role in managed namespace dr-test-moshekipod-backwards-compat-dr-managed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.652&#xA;STEP: Creating release PVC dr-release-pvc in managed namespace dr-test-kokohazamar-backwards-compat-dr-managed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.658&#xA;STEP: Creating secrets access RoleBinding in managed namespace dr-test-moshekipod-backwards-compat-dr-managed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.659&#xA;STEP: Creating secrets access Role in managed namespace dr-test-kokohazamar-backwards-compat-dr-managed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.75&#xA;STEP: Creating secrets access RoleBinding in managed namespace dr-test-kokohazamar-backwards-compat-dr-managed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:68 @ 05/09/26 03:56:24.758&#xA;&lt; Exit [It] should create both tenants concurrently - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:61 @ 05/09/26 03:56:24.853 (2.601s)&#xA;&gt; Enter [AfterEach] DR Backwards-Compat - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:44 @ 05/09/26 03:56:24.854&#xA;&lt; Exit [AfterEach] DR Backwards-Compat - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:44 @ 05/09/26 03:56:24.854 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Suite] 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="timedout" time="1650.270107476">
              <failure message="A suite timeout occurred" type="timedout">[TIMEDOUT] A suite timeout occurred&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:74 @ 05/09/26 04:23:53.683&#xA;&#xA;This is the Progress Report generated when the suite timeout occurred:&#xA;  [disaster-recovery DR Suite] DR Backwards-Compat when creating tenants on the old Konflux version should wait for all build PipelineRuns to succeed (Spec Runtime: 27m28.829s)&#xA;    /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:74&#xA;    In [It] (Node Runtime: 27m28.829s)&#xA;      /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:74&#xA;      At [By Step] Waiting for test PipelineRun for mathwizz-frontend in dr-test-kokohazamar-backwards-compat-dr (base: 0) (Step Runtime: 22m28.476s)&#xA;        /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:201&#xA;&#xA;      Spec Goroutine&#xA;      goroutine 552 [sync.WaitGroup.Wait, 29 minutes]&#xA;        sync.runtime_SemacquireWaitGroup(0xc001638be0?, 0x0?)&#xA;          /usr/lib/golang/src/runtime/sema.go:114&#xA;        sync.(*WaitGroup).Wait(0xc001ab2a60)&#xA;          /usr/lib/golang/src/sync/waitgroup.go:206&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains(0xc0011f6e00, {0xc000dfcf00, 0x2, 0xc0005a8ea0?}, 0x0, 0x0)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:208&#xA;            | &#x9;}&#xA;            | }&#xA;            &gt; wg.Wait()&#xA;            | &#xA;            | // Release PipelineRuns run in the managed namespace and may not map 1:1&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.defineBackwardsCompatSpecs.func1.2.2()&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:75&#xA;            | &#xA;            | It(&#34;should wait for all build PipelineRuns to succeed&#34;, func() {&#xA;            &gt; &#x9;waitForPipelineChains(fw, bcTenants, nil, nil)&#xA;            | })&#xA;            | &#xA;        github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0xc0005a8f74?, 0xc0005a8ef0?})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.28.0/internal/node.go:585&#xA;        github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3()&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.28.0/internal/suite.go:946&#xA;        github.com/onsi/ginkgo/v2/internal.(*Suite).runNode in goroutine 84&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.28.0/internal/suite.go:911&#xA;&#xA;      Goroutines of Interest&#xA;      goroutine 553 [select]&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc000559570, {0x43884f0, 0xc000e615b0}, 0x1, {0xc0014a5480, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:558&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc000559570, {0x43884f0, 0xc000e615b0}, {0xc0014a5480, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:145&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForSucceededPRCount(0xc0011f6e00, {0x3c0c231, 0x27}, {0x3b8a42f, 0x4}, {0x3bbf87e, 0x13}, 0x1, 0x4e94914f000, 0x6fc23ac00)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:137&#xA;            | &#x9;&#x9;namespace, succeededCount, expectedCount, displayType)&#xA;            | &#x9;return succeededCount&#xA;            &gt; }, timeout, poll).Should(Equal(expectedCount),&#xA;            | &#x9;&#34;expected %d successful %s PipelineRuns in namespace %s&#34;,&#xA;            | &#x9;expectedCount, displayType, namespace)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains.func1({{0x3c0c231, 0x27}, {0x3c30bb5, 0x2f}, {0x3bec6bd, 0x1f}, {0x3c08469, 0x26}, {0xc0010a43d8, 0x12}, ...}, ...)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:203&#xA;            | &#x9;By(fmt.Sprintf(&#34;Waiting for test PipelineRun for %s in %s (base: %d)&#34;,&#xA;            | &#x9;&#x9;component.Name, tenant.Namespace, base.test))&#xA;            &gt; &#x9;waitForSucceededPRCount(fw, tenant.Namespace, &#34;test&#34;, component.Name,&#xA;            | &#x9;&#x9;base.test+1, PipelineTimeout, PipelinePoll)&#xA;            | }(t, comp)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains in goroutine 552&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:189&#xA;            | for _, comp := range Components {&#xA;            | &#x9;wg.Add(1)&#xA;            &gt; &#x9;go func(tenant Tenant, component ComponentDef) {&#xA;            | &#x9;&#x9;defer GinkgoRecover()&#xA;            | &#x9;&#x9;defer wg.Done()&#xA;&#xA;      goroutine 554 [select]&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0005bd730, {0x43884f0, 0xc001c8d710}, 0x1, {0xc001d33680, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:558&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0005bd730, {0x43884f0, 0xc001c8d710}, {0xc001d33680, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:145&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForSucceededPRCount(0xc0011f6e00, {0x3c0c231, 0x27}, {0x3b8a42f, 0x4}, {0x3bce27b, 0x17}, 0x1, 0x4e94914f000, 0x6fc23ac00)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:137&#xA;            | &#x9;&#x9;namespace, succeededCount, expectedCount, displayType)&#xA;            | &#x9;return succeededCount&#xA;            &gt; }, timeout, poll).Should(Equal(expectedCount),&#xA;            | &#x9;&#34;expected %d successful %s PipelineRuns in namespace %s&#34;,&#xA;            | &#x9;expectedCount, displayType, namespace)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains.func1({{0x3c0c231, 0x27}, {0x3c30bb5, 0x2f}, {0x3bec6bd, 0x1f}, {0x3c08469, 0x26}, {0xc0010a43d8, 0x12}, ...}, ...)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:203&#xA;            | &#x9;By(fmt.Sprintf(&#34;Waiting for test PipelineRun for %s in %s (base: %d)&#34;,&#xA;            | &#x9;&#x9;component.Name, tenant.Namespace, base.test))&#xA;            &gt; &#x9;waitForSucceededPRCount(fw, tenant.Namespace, &#34;test&#34;, component.Name,&#xA;            | &#x9;&#x9;base.test+1, PipelineTimeout, PipelinePoll)&#xA;            | }(t, comp)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains in goroutine 552&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:189&#xA;            | for _, comp := range Components {&#xA;            | &#x9;wg.Add(1)&#xA;            &gt; &#x9;go func(tenant Tenant, component ComponentDef) {&#xA;            | &#x9;&#x9;defer GinkgoRecover()&#xA;            | &#x9;&#x9;defer wg.Done()&#xA;&#xA;      goroutine 555 [select]&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc000415490, {0x43884f0, 0xc000e43560}, 0x1, {0xc001491ec0, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:558&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc000415490, {0x43884f0, 0xc000e43560}, {0xc001491ec0, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:145&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForSucceededPRCount(0xc0011f6e00, {0x3c0c231, 0x27}, {0x3b8a42f, 0x4}, {0x3bb79a4, 0x11}, 0x1, 0x4e94914f000, 0x6fc23ac00)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:137&#xA;            | &#x9;&#x9;namespace, succeededCount, expectedCount, displayType)&#xA;            | &#x9;return succeededCount&#xA;            &gt; }, timeout, poll).Should(Equal(expectedCount),&#xA;            | &#x9;&#34;expected %d successful %s PipelineRuns in namespace %s&#34;,&#xA;            | &#x9;expectedCount, displayType, namespace)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains.func1({{0x3c0c231, 0x27}, {0x3c30bb5, 0x2f}, {0x3bec6bd, 0x1f}, {0x3c08469, 0x26}, {0xc0010a43d8, 0x12}, ...}, ...)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:203&#xA;            | &#x9;By(fmt.Sprintf(&#34;Waiting for test PipelineRun for %s in %s (base: %d)&#34;,&#xA;            | &#x9;&#x9;component.Name, tenant.Namespace, base.test))&#xA;            &gt; &#x9;waitForSucceededPRCount(fw, tenant.Namespace, &#34;test&#34;, component.Name,&#xA;            | &#x9;&#x9;base.test+1, PipelineTimeout, PipelinePoll)&#xA;            | }(t, comp)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains in goroutine 552&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:189&#xA;            | for _, comp := range Components {&#xA;            | &#x9;wg.Add(1)&#xA;            &gt; &#x9;go func(tenant Tenant, component ComponentDef) {&#xA;            | &#x9;&#x9;defer GinkgoRecover()&#xA;            | &#x9;&#x9;defer wg.Done()&#xA;&#xA;      goroutine 556 [select]&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc00098de30, {0x43884f0, 0xc00050d620}, 0x1, {0xc00109a700, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:558&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc00098de30, {0x43884f0, 0xc00050d620}, {0xc00109a700, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:145&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForSucceededPRCount(0xc0011f6e00, {0x3c0848f, 0x26}, {0x3b8a42f, 0x4}, {0x3bbf87e, 0x13}, 0x1, 0x4e94914f000, 0x6fc23ac00)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:137&#xA;            | &#x9;&#x9;namespace, succeededCount, expectedCount, displayType)&#xA;            | &#x9;return succeededCount&#xA;            &gt; }, timeout, poll).Should(Equal(expectedCount),&#xA;            | &#x9;&#34;expected %d successful %s PipelineRuns in namespace %s&#34;,&#xA;            | &#x9;expectedCount, displayType, namespace)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains.func1({{0x3c0848f, 0x26}, {0x3c2bc2b, 0x2e}, {0x3be902b, 0x1e}, {0x3c0488e, 0x25}, {0xc00191e348, 0x12}, ...}, ...)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:203&#xA;            | &#x9;By(fmt.Sprintf(&#34;Waiting for test PipelineRun for %s in %s (base: %d)&#34;,&#xA;            | &#x9;&#x9;component.Name, tenant.Namespace, base.test))&#xA;            &gt; &#x9;waitForSucceededPRCount(fw, tenant.Namespace, &#34;test&#34;, component.Name,&#xA;            | &#x9;&#x9;base.test+1, PipelineTimeout, PipelinePoll)&#xA;            | }(t, comp)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains in goroutine 552&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:189&#xA;            | for _, comp := range Components {&#xA;            | &#x9;wg.Add(1)&#xA;            &gt; &#x9;go func(tenant Tenant, component ComponentDef) {&#xA;            | &#x9;&#x9;defer GinkgoRecover()&#xA;            | &#x9;&#x9;defer wg.Done()&#xA;&#xA;      goroutine 557 [select]&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc00040c540, {0x43884f0, 0xc001d50980}, 0x1, {0xc000cd3900, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:558&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc00040c540, {0x43884f0, 0xc001d50980}, {0xc000cd3900, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:145&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForSucceededPRCount(0xc0011f6e00, {0x3c0848f, 0x26}, {0x3b8a42f, 0x4}, {0x3bce27b, 0x17}, 0x1, 0x4e94914f000, 0x6fc23ac00)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:137&#xA;            | &#x9;&#x9;namespace, succeededCount, expectedCount, displayType)&#xA;            | &#x9;return succeededCount&#xA;            &gt; }, timeout, poll).Should(Equal(expectedCount),&#xA;            | &#x9;&#34;expected %d successful %s PipelineRuns in namespace %s&#34;,&#xA;            | &#x9;expectedCount, displayType, namespace)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains.func1({{0x3c0848f, 0x26}, {0x3c2bc2b, 0x2e}, {0x3be902b, 0x1e}, {0x3c0488e, 0x25}, {0xc00191e348, 0x12}, ...}, ...)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:203&#xA;            | &#x9;By(fmt.Sprintf(&#34;Waiting for test PipelineRun for %s in %s (base: %d)&#34;,&#xA;            | &#x9;&#x9;component.Name, tenant.Namespace, base.test))&#xA;            &gt; &#x9;waitForSucceededPRCount(fw, tenant.Namespace, &#34;test&#34;, component.Name,&#xA;            | &#x9;&#x9;base.test+1, PipelineTimeout, PipelinePoll)&#xA;            | }(t, comp)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains in goroutine 552&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:189&#xA;            | for _, comp := range Components {&#xA;            | &#x9;wg.Add(1)&#xA;            &gt; &#x9;go func(tenant Tenant, component ComponentDef) {&#xA;            | &#x9;&#x9;defer GinkgoRecover()&#xA;            | &#x9;&#x9;defer wg.Done()&#xA;&#xA;      goroutine 558 [select]&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0004148c0, {0x43884f0, 0xc000e422b0}, 0x1, {0xc001490700, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:558&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0004148c0, {0x43884f0, 0xc000e422b0}, {0xc001490700, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:145&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForSucceededPRCount(0xc0011f6e00, {0x3c0848f, 0x26}, {0x3b8a42f, 0x4}, {0x3bb79a4, 0x11}, 0x1, 0x4e94914f000, 0x6fc23ac00)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:137&#xA;            | &#x9;&#x9;namespace, succeededCount, expectedCount, displayType)&#xA;            | &#x9;return succeededCount&#xA;            &gt; }, timeout, poll).Should(Equal(expectedCount),&#xA;            | &#x9;&#34;expected %d successful %s PipelineRuns in namespace %s&#34;,&#xA;            | &#x9;expectedCount, displayType, namespace)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains.func1({{0x3c0848f, 0x26}, {0x3c2bc2b, 0x2e}, {0x3be902b, 0x1e}, {0x3c0488e, 0x25}, {0xc00191e348, 0x12}, ...}, ...)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:203&#xA;            | &#x9;By(fmt.Sprintf(&#34;Waiting for test PipelineRun for %s in %s (base: %d)&#34;,&#xA;            | &#x9;&#x9;component.Name, tenant.Namespace, base.test))&#xA;            &gt; &#x9;waitForSucceededPRCount(fw, tenant.Namespace, &#34;test&#34;, component.Name,&#xA;            | &#x9;&#x9;base.test+1, PipelineTimeout, PipelinePoll)&#xA;            | }(t, comp)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains in goroutine 552&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:189&#xA;            | for _, comp := range Components {&#xA;            | &#x9;wg.Add(1)&#xA;            &gt; &#x9;go func(tenant Tenant, component ComponentDef) {&#xA;            | &#x9;&#x9;defer GinkgoRecover()&#xA;            | &#x9;&#x9;defer wg.Done()&#xA;</failure>
              <system-err>&gt; Enter [It] should wait for all build PipelineRuns to succeed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:74 @ 05/09/26 03:56:24.854&#xA;STEP: Waiting for per-component build → test chains across all tenants - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:75 @ 05/09/26 03:56:24.854&#xA;STEP: Waiting for build PipelineRun for mathwizz-frontend in dr-test-moshekipod-backwards-compat-dr (base: 0) - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:196 @ 05/09/26 03:56:24.854&#xA;STEP: Waiting for build PipelineRun for mathwizz-frontend in dr-test-kokohazamar-backwards-compat-dr (base: 0) - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:196 @ 05/09/26 03:56:24.854&#xA;STEP: Waiting for build PipelineRun for mathwizz-web-server in dr-test-moshekipod-backwards-compat-dr (base: 0) - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:196 @ 05/09/26 03:56:24.854&#xA;STEP: Waiting for build PipelineRun for mathwizz-history-worker in dr-test-kokohazamar-backwards-compat-dr (base: 0) - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:196 @ 05/09/26 03:56:24.854&#xA;STEP: Waiting for build PipelineRun for mathwizz-web-server in dr-test-kokohazamar-backwards-compat-dr (base: 0) - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:196 @ 05/09/26 03:56:24.854&#xA;STEP: Waiting for build PipelineRun for mathwizz-history-worker in dr-test-moshekipod-backwards-compat-dr (base: 0) - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:196 @ 05/09/26 03:56:24.854&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 1/1 build PipelineRuns succeeded&#xA;STEP: Waiting for test PipelineRun for mathwizz-history-worker in dr-test-moshekipod-backwards-compat-dr (base: 0) - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:201 @ 05/09/26 04:00:55.076&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 1/1 build PipelineRuns succeeded&#xA;STEP: Waiting for test PipelineRun for mathwizz-web-server in dr-test-kokohazamar-backwards-compat-dr (base: 0) - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:201 @ 05/09/26 04:00:55.177&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 1/1 build PipelineRuns succeeded&#xA;STEP: Waiting for test PipelineRun for mathwizz-history-worker in dr-test-kokohazamar-backwards-compat-dr (base: 0) - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:201 @ 05/09/26 04:00:55.177&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 1/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 1/1 build PipelineRuns succeeded&#xA;STEP: Waiting for test PipelineRun for mathwizz-frontend in dr-test-moshekipod-backwards-compat-dr (base: 0) - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:201 @ 05/09/26 04:01:25.111&#xA;STEP: Waiting for test PipelineRun for mathwizz-web-server in dr-test-moshekipod-backwards-compat-dr (base: 0) - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:201 @ 05/09/26 04:01:25.111&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 1/1 build PipelineRuns succeeded&#xA;STEP: Waiting for test PipelineRun for mathwizz-frontend in dr-test-kokohazamar-backwards-compat-dr (base: 0) - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:201 @ 05/09/26 04:01:25.208&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 test PipelineRuns succeeded&#xA;[TIMEDOUT] A suite timeout occurred&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:74 @ 05/09/26 04:23:53.683&#xA;&#xA;This is the Progress Report generated when the suite timeout occurred:&#xA;  [disaster-recovery DR Suite] DR Backwards-Compat when creating tenants on the old Konflux version should wait for all build PipelineRuns to succeed (Spec Runtime: 27m28.829s)&#xA;    /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:74&#xA;    In [It] (Node Runtime: 27m28.829s)&#xA;      /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:74&#xA;      At [By Step] Waiting for test PipelineRun for mathwizz-frontend in dr-test-kokohazamar-backwards-compat-dr (base: 0) (Step Runtime: 22m28.476s)&#xA;        /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:201&#xA;&#xA;      Spec Goroutine&#xA;      goroutine 552 [sync.WaitGroup.Wait, 29 minutes]&#xA;        sync.runtime_SemacquireWaitGroup(0xc001638be0?, 0x0?)&#xA;          /usr/lib/golang/src/runtime/sema.go:114&#xA;        sync.(*WaitGroup).Wait(0xc001ab2a60)&#xA;          /usr/lib/golang/src/sync/waitgroup.go:206&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains(0xc0011f6e00, {0xc000dfcf00, 0x2, 0xc0005a8ea0?}, 0x0, 0x0)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:208&#xA;            | &#x9;}&#xA;            | }&#xA;            &gt; wg.Wait()&#xA;            | &#xA;            | // Release PipelineRuns run in the managed namespace and may not map 1:1&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.defineBackwardsCompatSpecs.func1.2.2()&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:75&#xA;            | &#xA;            | It(&#34;should wait for all build PipelineRuns to succeed&#34;, func() {&#xA;            &gt; &#x9;waitForPipelineChains(fw, bcTenants, nil, nil)&#xA;            | })&#xA;            | &#xA;        github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0xc0005a8f74?, 0xc0005a8ef0?})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.28.0/internal/node.go:585&#xA;        github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3()&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.28.0/internal/suite.go:946&#xA;        github.com/onsi/ginkgo/v2/internal.(*Suite).runNode in goroutine 84&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.28.0/internal/suite.go:911&#xA;&#xA;      Goroutines of Interest&#xA;      goroutine 553 [select]&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc000559570, {0x43884f0, 0xc000e615b0}, 0x1, {0xc0014a5480, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:558&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc000559570, {0x43884f0, 0xc000e615b0}, {0xc0014a5480, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:145&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForSucceededPRCount(0xc0011f6e00, {0x3c0c231, 0x27}, {0x3b8a42f, 0x4}, {0x3bbf87e, 0x13}, 0x1, 0x4e94914f000, 0x6fc23ac00)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:137&#xA;            | &#x9;&#x9;namespace, succeededCount, expectedCount, displayType)&#xA;            | &#x9;return succeededCount&#xA;            &gt; }, timeout, poll).Should(Equal(expectedCount),&#xA;            | &#x9;&#34;expected %d successful %s PipelineRuns in namespace %s&#34;,&#xA;            | &#x9;expectedCount, displayType, namespace)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains.func1({{0x3c0c231, 0x27}, {0x3c30bb5, 0x2f}, {0x3bec6bd, 0x1f}, {0x3c08469, 0x26}, {0xc0010a43d8, 0x12}, ...}, ...)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:203&#xA;            | &#x9;By(fmt.Sprintf(&#34;Waiting for test PipelineRun for %s in %s (base: %d)&#34;,&#xA;            | &#x9;&#x9;component.Name, tenant.Namespace, base.test))&#xA;            &gt; &#x9;waitForSucceededPRCount(fw, tenant.Namespace, &#34;test&#34;, component.Name,&#xA;            | &#x9;&#x9;base.test+1, PipelineTimeout, PipelinePoll)&#xA;            | }(t, comp)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains in goroutine 552&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:189&#xA;            | for _, comp := range Components {&#xA;            | &#x9;wg.Add(1)&#xA;            &gt; &#x9;go func(tenant Tenant, component ComponentDef) {&#xA;            | &#x9;&#x9;defer GinkgoRecover()&#xA;            | &#x9;&#x9;defer wg.Done()&#xA;&#xA;      goroutine 554 [select]&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0005bd730, {0x43884f0, 0xc001c8d710}, 0x1, {0xc001d33680, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:558&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0005bd730, {0x43884f0, 0xc001c8d710}, {0xc001d33680, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:145&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForSucceededPRCount(0xc0011f6e00, {0x3c0c231, 0x27}, {0x3b8a42f, 0x4}, {0x3bce27b, 0x17}, 0x1, 0x4e94914f000, 0x6fc23ac00)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:137&#xA;            | &#x9;&#x9;namespace, succeededCount, expectedCount, displayType)&#xA;            | &#x9;return succeededCount&#xA;            &gt; }, timeout, poll).Should(Equal(expectedCount),&#xA;            | &#x9;&#34;expected %d successful %s PipelineRuns in namespace %s&#34;,&#xA;            | &#x9;expectedCount, displayType, namespace)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains.func1({{0x3c0c231, 0x27}, {0x3c30bb5, 0x2f}, {0x3bec6bd, 0x1f}, {0x3c08469, 0x26}, {0xc0010a43d8, 0x12}, ...}, ...)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:203&#xA;            | &#x9;By(fmt.Sprintf(&#34;Waiting for test PipelineRun for %s in %s (base: %d)&#34;,&#xA;            | &#x9;&#x9;component.Name, tenant.Namespace, base.test))&#xA;            &gt; &#x9;waitForSucceededPRCount(fw, tenant.Namespace, &#34;test&#34;, component.Name,&#xA;            | &#x9;&#x9;base.test+1, PipelineTimeout, PipelinePoll)&#xA;            | }(t, comp)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains in goroutine 552&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:189&#xA;            | for _, comp := range Components {&#xA;            | &#x9;wg.Add(1)&#xA;            &gt; &#x9;go func(tenant Tenant, component ComponentDef) {&#xA;            | &#x9;&#x9;defer GinkgoRecover()&#xA;            | &#x9;&#x9;defer wg.Done()&#xA;&#xA;      goroutine 555 [select]&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc000415490, {0x43884f0, 0xc000e43560}, 0x1, {0xc001491ec0, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:558&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc000415490, {0x43884f0, 0xc000e43560}, {0xc001491ec0, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:145&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForSucceededPRCount(0xc0011f6e00, {0x3c0c231, 0x27}, {0x3b8a42f, 0x4}, {0x3bb79a4, 0x11}, 0x1, 0x4e94914f000, 0x6fc23ac00)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:137&#xA;            | &#x9;&#x9;namespace, succeededCount, expectedCount, displayType)&#xA;            | &#x9;return succeededCount&#xA;            &gt; }, timeout, poll).Should(Equal(expectedCount),&#xA;            | &#x9;&#34;expected %d successful %s PipelineRuns in namespace %s&#34;,&#xA;            | &#x9;expectedCount, displayType, namespace)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains.func1({{0x3c0c231, 0x27}, {0x3c30bb5, 0x2f}, {0x3bec6bd, 0x1f}, {0x3c08469, 0x26}, {0xc0010a43d8, 0x12}, ...}, ...)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:203&#xA;            | &#x9;By(fmt.Sprintf(&#34;Waiting for test PipelineRun for %s in %s (base: %d)&#34;,&#xA;            | &#x9;&#x9;component.Name, tenant.Namespace, base.test))&#xA;            &gt; &#x9;waitForSucceededPRCount(fw, tenant.Namespace, &#34;test&#34;, component.Name,&#xA;            | &#x9;&#x9;base.test+1, PipelineTimeout, PipelinePoll)&#xA;            | }(t, comp)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains in goroutine 552&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:189&#xA;            | for _, comp := range Components {&#xA;            | &#x9;wg.Add(1)&#xA;            &gt; &#x9;go func(tenant Tenant, component ComponentDef) {&#xA;            | &#x9;&#x9;defer GinkgoRecover()&#xA;            | &#x9;&#x9;defer wg.Done()&#xA;&#xA;      goroutine 556 [select]&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc00098de30, {0x43884f0, 0xc00050d620}, 0x1, {0xc00109a700, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:558&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc00098de30, {0x43884f0, 0xc00050d620}, {0xc00109a700, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:145&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForSucceededPRCount(0xc0011f6e00, {0x3c0848f, 0x26}, {0x3b8a42f, 0x4}, {0x3bbf87e, 0x13}, 0x1, 0x4e94914f000, 0x6fc23ac00)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:137&#xA;            | &#x9;&#x9;namespace, succeededCount, expectedCount, displayType)&#xA;            | &#x9;return succeededCount&#xA;            &gt; }, timeout, poll).Should(Equal(expectedCount),&#xA;            | &#x9;&#34;expected %d successful %s PipelineRuns in namespace %s&#34;,&#xA;            | &#x9;expectedCount, displayType, namespace)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains.func1({{0x3c0848f, 0x26}, {0x3c2bc2b, 0x2e}, {0x3be902b, 0x1e}, {0x3c0488e, 0x25}, {0xc00191e348, 0x12}, ...}, ...)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:203&#xA;            | &#x9;By(fmt.Sprintf(&#34;Waiting for test PipelineRun for %s in %s (base: %d)&#34;,&#xA;            | &#x9;&#x9;component.Name, tenant.Namespace, base.test))&#xA;            &gt; &#x9;waitForSucceededPRCount(fw, tenant.Namespace, &#34;test&#34;, component.Name,&#xA;            | &#x9;&#x9;base.test+1, PipelineTimeout, PipelinePoll)&#xA;            | }(t, comp)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains in goroutine 552&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:189&#xA;            | for _, comp := range Components {&#xA;            | &#x9;wg.Add(1)&#xA;            &gt; &#x9;go func(tenant Tenant, component ComponentDef) {&#xA;            | &#x9;&#x9;defer GinkgoRecover()&#xA;            | &#x9;&#x9;defer wg.Done()&#xA;&#xA;      goroutine 557 [select]&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc00040c540, {0x43884f0, 0xc001d50980}, 0x1, {0xc000cd3900, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:558&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc00040c540, {0x43884f0, 0xc001d50980}, {0xc000cd3900, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:145&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForSucceededPRCount(0xc0011f6e00, {0x3c0848f, 0x26}, {0x3b8a42f, 0x4}, {0x3bce27b, 0x17}, 0x1, 0x4e94914f000, 0x6fc23ac00)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:137&#xA;            | &#x9;&#x9;namespace, succeededCount, expectedCount, displayType)&#xA;            | &#x9;return succeededCount&#xA;            &gt; }, timeout, poll).Should(Equal(expectedCount),&#xA;            | &#x9;&#34;expected %d successful %s PipelineRuns in namespace %s&#34;,&#xA;            | &#x9;expectedCount, displayType, namespace)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains.func1({{0x3c0848f, 0x26}, {0x3c2bc2b, 0x2e}, {0x3be902b, 0x1e}, {0x3c0488e, 0x25}, {0xc00191e348, 0x12}, ...}, ...)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:203&#xA;            | &#x9;By(fmt.Sprintf(&#34;Waiting for test PipelineRun for %s in %s (base: %d)&#34;,&#xA;            | &#x9;&#x9;component.Name, tenant.Namespace, base.test))&#xA;            &gt; &#x9;waitForSucceededPRCount(fw, tenant.Namespace, &#34;test&#34;, component.Name,&#xA;            | &#x9;&#x9;base.test+1, PipelineTimeout, PipelinePoll)&#xA;            | }(t, comp)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains in goroutine 552&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:189&#xA;            | for _, comp := range Components {&#xA;            | &#x9;wg.Add(1)&#xA;            &gt; &#x9;go func(tenant Tenant, component ComponentDef) {&#xA;            | &#x9;&#x9;defer GinkgoRecover()&#xA;            | &#x9;&#x9;defer wg.Done()&#xA;&#xA;      goroutine 558 [select]&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0004148c0, {0x43884f0, 0xc000e422b0}, 0x1, {0xc001490700, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:558&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0004148c0, {0x43884f0, 0xc000e422b0}, {0xc001490700, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:145&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForSucceededPRCount(0xc0011f6e00, {0x3c0848f, 0x26}, {0x3b8a42f, 0x4}, {0x3bb79a4, 0x11}, 0x1, 0x4e94914f000, 0x6fc23ac00)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:137&#xA;            | &#x9;&#x9;namespace, succeededCount, expectedCount, displayType)&#xA;            | &#x9;return succeededCount&#xA;            &gt; }, timeout, poll).Should(Equal(expectedCount),&#xA;            | &#x9;&#34;expected %d successful %s PipelineRuns in namespace %s&#34;,&#xA;            | &#x9;expectedCount, displayType, namespace)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains.func1({{0x3c0848f, 0x26}, {0x3c2bc2b, 0x2e}, {0x3be902b, 0x1e}, {0x3c0488e, 0x25}, {0xc00191e348, 0x12}, ...}, ...)&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:203&#xA;            | &#x9;By(fmt.Sprintf(&#34;Waiting for test PipelineRun for %s in %s (base: %d)&#34;,&#xA;            | &#x9;&#x9;component.Name, tenant.Namespace, base.test))&#xA;            &gt; &#x9;waitForSucceededPRCount(fw, tenant.Namespace, &#34;test&#34;, component.Name,&#xA;            | &#x9;&#x9;base.test+1, PipelineTimeout, PipelinePoll)&#xA;            | }(t, comp)&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForPipelineChains in goroutine 552&#xA;          /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/tenant_application_lifecycle.go:189&#xA;            | for _, comp := range Components {&#xA;            | &#x9;wg.Add(1)&#xA;            &gt; &#x9;go func(tenant Tenant, component ComponentDef) {&#xA;            | &#x9;&#x9;defer GinkgoRecover()&#xA;            | &#x9;&#x9;defer wg.Done()&#xA;&lt; Exit [It] should wait for all build PipelineRuns to succeed - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:74 @ 05/09/26 04:23:53.684 (27m28.83s)&#xA;&gt; Enter [AfterEach] DR Backwards-Compat - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:44 @ 05/09/26 04:23:53.685&#xA;&lt; Exit [AfterEach] DR Backwards-Compat - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:44 @ 05/09/26 04:23:54.069 (385ms)&#xA;&gt; Enter [AfterAll] DR Backwards-Compat - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:153 @ 05/09/26 04:23:54.069&#xA;Deleting fork repo DR-MathWizz-tjqtph for tenant dr-test-kokohazamar-backwards-compat-dr&#xA;Deleting fork repo DR-MathWizz-xgtqhy for tenant dr-test-moshekipod-backwards-compat-dr&#xA;STEP: Collecting Velero pod information - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:156 @ 05/09/26 04:23:55.096&#xA;Velero pod: node-agent-2cd25 | Phase: Running | Ready: true&#xA;Velero pod: node-agent-gsw6l | Phase: Running | Ready: true&#xA;Velero pod: node-agent-skwvj | Phase: Running | Ready: true&#xA;Velero pod: velero-5498cfc4db-7gjf8 | Phase: Running | Ready: true&#xA;STEP: Collecting Backup CR status for tenant &#34;dr-test-kokohazamar-backwards-compat-dr&#34; - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:156 @ 05/09/26 04:23:55.105&#xA;WARNING: could not get Backup CR &#34;backup-kokohazamar-backwards-compat-dr&#34;: backups.velero.io &#34;backup-kokohazamar-backwards-compat-dr&#34; not found&#xA;STEP: Collecting Restore CR status for tenant &#34;dr-test-kokohazamar-backwards-compat-dr&#34; - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:156 @ 05/09/26 04:23:55.11&#xA;WARNING: could not get Restore CR &#34;restore-backup-kokohazamar-backwards-compat-dr&#34;: restores.velero.io &#34;restore-backup-kokohazamar-backwards-compat-dr&#34; not found&#xA;STEP: Collecting Backup CR status for tenant &#34;dr-test-moshekipod-backwards-compat-dr&#34; - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:156 @ 05/09/26 04:23:55.115&#xA;WARNING: could not get Backup CR &#34;backup-moshekipod-backwards-compat-dr&#34;: backups.velero.io &#34;backup-moshekipod-backwards-compat-dr&#34; not found&#xA;STEP: Collecting Restore CR status for tenant &#34;dr-test-moshekipod-backwards-compat-dr&#34; - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:156 @ 05/09/26 04:23:55.12&#xA;WARNING: could not get Restore CR &#34;restore-backup-moshekipod-backwards-compat-dr&#34;: restores.velero.io &#34;restore-backup-moshekipod-backwards-compat-dr&#34; not found&#xA;&lt; Exit [AfterAll] DR Backwards-Compat - /tmp/tmp.CNj1aJY7Z5/tests/disaster-recovery/dr_backwards_compat.go:153 @ 05/09/26 04:23:55.124 (1.055s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Suite] DR Backwards-Compat when creating tenants on the old Konflux version should merge PaC configuration PRs on forked repos [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 Suite] 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 Suite] 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 Suite] 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 Suite] 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 Suite] 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 Suite] 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 Suite] 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 Suite] 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] [disaster-recovery DR Suite] 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 Suite] 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 Suite] DR Same-Version Backup/Restore when creating tenants and running initial pipelines should merge PaC configuration PRs on forked repos [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 Suite] 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 Suite] 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 Suite] 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 Suite] 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 Suite] 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 Suite] 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 Suite] 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] [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="passed" time="48.925599156">
              <system-err>&gt; Enter [BeforeAll] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/missing_release_plan_and_admission.go:34 @ 05/09/26 02:56:33.414&#xA;&lt; Exit [BeforeAll] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/missing_release_plan_and_admission.go:34 @ 05/09/26 02:57:21.98 (48.566s)&#xA;&gt; Enter [It] missing ReleasePlan makes a Release CR set as failed in both IsReleased and IsValid with a proper message to user. - /tmp/tmp.CNj1aJY7Z5/tests/release/service/missing_release_plan_and_admission.go:66 @ 05/09/26 02:57:21.98&#xA;&lt; Exit [It] missing ReleasePlan makes a Release CR set as failed in both IsReleased and IsValid with a proper message to user. - /tmp/tmp.CNj1aJY7Z5/tests/release/service/missing_release_plan_and_admission.go:66 @ 05/09/26 02:57:22.339 (359ms)&#xA;&gt; Enter [AfterEach] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/missing_release_plan_and_admission.go:32 @ 05/09/26 02:57:22.339&#xA;&lt; Exit [AfterEach] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/missing_release_plan_and_admission.go:32 @ 05/09/26 02:57:22.339 (0s)&#xA;</system-err>
          </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="passed" time="32.254647392">
              <system-err>&gt; Enter [It] missing ReleasePlanAdmission makes a Release CR set as failed in both IsReleased and IsValid with a proper message to user. - /tmp/tmp.CNj1aJY7Z5/tests/release/service/missing_release_plan_and_admission.go:76 @ 05/09/26 02:57:22.34&#xA;&lt; Exit [It] missing ReleasePlanAdmission makes a Release CR set as failed in both IsReleased and IsValid with a proper message to user. - /tmp/tmp.CNj1aJY7Z5/tests/release/service/missing_release_plan_and_admission.go:76 @ 05/09/26 02:57:22.438 (98ms)&#xA;&gt; Enter [AfterEach] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/missing_release_plan_and_admission.go:32 @ 05/09/26 02:57:22.438&#xA;&lt; Exit [AfterEach] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/missing_release_plan_and_admission.go:32 @ 05/09/26 02:57:22.438 (0s)&#xA;&gt; Enter [AfterAll] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/missing_release_plan_and_admission.go:58 @ 05/09/26 02:57:22.439&#xA;&lt; Exit [AfterAll] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/missing_release_plan_and_admission.go:58 @ 05/09/26 02:57:54.594 (32.156s)&#xA;</system-err>
          </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="passed" time="87.71302043">
              <system-err>&gt; Enter [BeforeAll] [release-service-suite [RELEASE-2136] Release CR fails when block-releases true in ReleasePlanAdmission.] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/block_releases_release_plan_admission.go:34 @ 05/09/26 02:56:33.317&#xA;&lt; Exit [BeforeAll] [release-service-suite [RELEASE-2136] Release CR fails when block-releases true in ReleasePlanAdmission.] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/block_releases_release_plan_admission.go:34 @ 05/09/26 02:57:08.672 (35.356s)&#xA;&gt; Enter [It] block-releases true in ReleasePlanAdmission makes a Release CR set as failed in both IsReleased and IsValid with a proper message to user. - /tmp/tmp.CNj1aJY7Z5/tests/release/service/block_releases_release_plan_admission.go:69 @ 05/09/26 02:57:08.673&#xA;&lt; Exit [It] block-releases true in ReleasePlanAdmission makes a Release CR set as failed in both IsReleased and IsValid with a proper message to user. - /tmp/tmp.CNj1aJY7Z5/tests/release/service/block_releases_release_plan_admission.go:69 @ 05/09/26 02:57:08.865 (192ms)&#xA;&gt; Enter [AfterEach] [release-service-suite [RELEASE-2136] Release CR fails when block-releases true in ReleasePlanAdmission.] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/block_releases_release_plan_admission.go:32 @ 05/09/26 02:57:08.865&#xA;&lt; Exit [AfterEach] [release-service-suite [RELEASE-2136] Release CR fails when block-releases true in ReleasePlanAdmission.] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/block_releases_release_plan_admission.go:32 @ 05/09/26 02:57:08.865 (0s)&#xA;&gt; Enter [AfterAll] [release-service-suite [RELEASE-2136] Release CR fails when block-releases true in ReleasePlanAdmission.] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/block_releases_release_plan_admission.go:61 @ 05/09/26 02:57:08.865&#xA;&lt; Exit [AfterAll] [release-service-suite [RELEASE-2136] Release CR fails when block-releases true in ReleasePlanAdmission.] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/block_releases_release_plan_admission.go:61 @ 05/09/26 02:58:01.029 (52.164s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [upgrade-suite Create users and check their state] Verify AppStudioProvisionedUser [upgrade-verify]" classname="Red Hat App Studio E2E tests" status="panicked" time="21.751233295">
              <error message="runtime error: invalid memory address or nil pointer dereference" type="panicked">[PANICKED] Test Panicked&#xA;In [It] at: /opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.34.2/pkg/util/runtime/runtime.go:114 @ 05/09/26 02:56:55.166&#xA;&#xA;runtime error: invalid memory address or nil pointer dereference&#xA;&#xA;Full Stack Trace&#xA;  k8s.io/apimachinery/pkg/util/runtime.handleCrash({0x43a2568, 0xc0004565b0}, {0x34796c0, 0x65a16e0}, {0x0, 0x0, 0x4470a0?})&#xA;  &#x9;/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.34.2/pkg/util/runtime/runtime.go:114 +0x1a9&#xA;  k8s.io/apimachinery/pkg/util/runtime.HandleCrashWithContext({0x43a2568, 0xc0004565b0}, {0x0, 0x0, 0x0})&#xA;  &#x9;/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.34.2/pkg/util/runtime/runtime.go:78 +0x5a&#xA;  panic({0x34796c0?, 0x65a16e0?})&#xA;  &#x9;/usr/lib/golang/src/runtime/panic.go:783 +0x132&#xA;  github.com/konflux-ci/e2e-tests/pkg/sandbox.(*SandboxController).CheckUserCreatedWithSignUp.func1()&#xA;  &#x9;/tmp/tmp.CNj1aJY7Z5/pkg/sandbox/sandbox.go:319 +0x35&#xA;  github.com/konflux-ci/e2e-tests/pkg/utils.WaitUntilWithInterval.func1({0xc000456701?, 0xc00019ec18?})&#xA;  &#x9;/tmp/tmp.CNj1aJY7Z5/pkg/utils/util.go:129 +0x13&#xA;  k8s.io/apimachinery/pkg/util/wait.loopConditionUntilContext.func1({0x43a2568?, 0xc0004565b0?}, 0x43a2568?)&#xA;  &#x9;/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.34.2/pkg/util/wait/loop.go:53 +0x62&#xA;  k8s.io/apimachinery/pkg/util/wait.loopConditionUntilContext({0x43a2568, 0xc0004565b0}, {0x438d5c0, 0xc00095a940}, 0x1, 0x0, 0xc00130fd90)&#xA;  &#x9;/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.34.2/pkg/util/wait/loop.go:54 +0x115&#xA;  k8s.io/apimachinery/pkg/util/wait.PollUntilContextTimeout({0x43a2418?, 0x6653d40?}, 0xee6b2800, 0x41d765?, 0x1, 0xc00019ed90)&#xA;  &#x9;/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.34.2/pkg/util/wait/poll.go:48 +0xa5&#xA;  github.com/konflux-ci/e2e-tests/pkg/utils.WaitUntilWithInterval(0xa?, 0xc00019edd8?, 0x1?)&#xA;  &#x9;/tmp/tmp.CNj1aJY7Z5/pkg/utils/util.go:129 +0x45&#xA;  github.com/konflux-ci/e2e-tests/pkg/sandbox.(*SandboxController).CheckUserCreatedWithSignUp(0x3b9d9e8?, {0x3b9d9e8?, 0x3b9a1e1?}, 0x8?)&#xA;  &#x9;/tmp/tmp.CNj1aJY7Z5/pkg/sandbox/sandbox.go:318 +0x72&#xA;  github.com/konflux-ci/e2e-tests/pkg/sandbox.(*SandboxController).CheckUserCreated(0x0, {0x3b9d9e8, 0x9})&#xA;  &#x9;/tmp/tmp.CNj1aJY7Z5/pkg/sandbox/sandbox.go:314 +0x4b&#xA;  github.com/konflux-ci/e2e-tests/tests/upgrade/verify.VerifyAppStudioProvisionedUser(0x0?)&#xA;  &#x9;/tmp/tmp.CNj1aJY7Z5/tests/upgrade/verify/verifyUsers.go:14 +0x25&#xA;  github.com/konflux-ci/e2e-tests/tests/upgrade.init.func1.2()&#xA;  &#x9;/tmp/tmp.CNj1aJY7Z5/tests/upgrade/verifyWorkload.go:21 +0x1a&#xA;</error>
              <system-err>&gt; Enter [BeforeAll] [upgrade-suite Create users and check their state] - /tmp/tmp.CNj1aJY7Z5/tests/upgrade/verifyWorkload.go:16 @ 05/09/26 02:56:33.415&#xA;&lt; Exit [BeforeAll] [upgrade-suite Create users and check their state] - /tmp/tmp.CNj1aJY7Z5/tests/upgrade/verifyWorkload.go:16 @ 05/09/26 02:56:55.165 (21.75s)&#xA;&gt; Enter [It] Verify AppStudioProvisionedUser - /tmp/tmp.CNj1aJY7Z5/tests/upgrade/verifyWorkload.go:20 @ 05/09/26 02:56:55.166&#xA;&#34;msg&#34;=&#34;Observed a panic&#34; &#34;error&#34;=null &#34;panic&#34;=&#34;runtime error: invalid memory address or nil pointer dereference&#34; &#34;panicGoValue&#34;=&#34;\&#34;invalid memory address or nil pointer dereference\&#34;&#34; &#34;stacktrace&#34;=&#34;goroutine 119 [running]:\nk8s.io/apimachinery/pkg/util/runtime.logPanic({0x43a24c0, 0xc0014065d0}, {0x34796c0, 0x65a16e0})\n\t/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.34.2/pkg/util/runtime/runtime.go:132 +0xbc\nk8s.io/apimachinery/pkg/util/runtime.handleCrash({0x43a2568, 0xc0004565b0}, {0x34796c0, 0x65a16e0}, {0x0, 0x0, 0x4470a0?})\n\t/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.34.2/pkg/util/runtime/runtime.go:107 +0x116\nk8s.io/apimachinery/pkg/util/runtime.HandleCrashWithContext({0x43a2568, 0xc0004565b0}, {0x0, 0x0, 0x0})\n\t/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.34.2/pkg/util/runtime/runtime.go:78 +0x5a\npanic({0x34796c0?, 0x65a16e0?})\n\t/usr/lib/golang/src/runtime/panic.go:783 +0x132\ngithub.com/konflux-ci/e2e-tests/pkg/sandbox.(*SandboxController).CheckUserCreatedWithSignUp.func1()\n\t/tmp/tmp.CNj1aJY7Z5/pkg/sandbox/sandbox.go:319 +0x35\ngithub.com/konflux-ci/e2e-tests/pkg/utils.WaitUntilWithInterval.func1({0xc000456701?, 0xc00019ec18?})\n\t/tmp/tmp.CNj1aJY7Z5/pkg/utils/util.go:129 +0x13\nk8s.io/apimachinery/pkg/util/wait.loopConditionUntilContext.func1({0x43a2568?, 0xc0004565b0?}, 0x43a2568?)\n\t/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.34.2/pkg/util/wait/loop.go:53 +0x62\nk8s.io/apimachinery/pkg/util/wait.loopConditionUntilContext({0x43a2568, 0xc0004565b0}, {0x438d5c0, 0xc00095a940}, 0x1, 0x0, 0xc00019ed90)\n\t/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.34.2/pkg/util/wait/loop.go:54 +0x115\nk8s.io/apimachinery/pkg/util/wait.PollUntilContextTimeout({0x43a2418?, 0x6653d40?}, 0xee6b2800, 0x41d765?, 0x1, 0xc00019ed90)\n\t/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.34.2/pkg/util/wait/poll.go:48 +0xa5\ngithub.com/konflux-ci/e2e-tests/pkg/utils.WaitUntilWithInterval(0xa?, 0xc00019edd8?, 0x1?)\n\t/tmp/tmp.CNj1aJY7Z5/pkg/utils/util.go:129 +0x45\ngithub.com/konflux-ci/e2e-tests/pkg/sandbox.(*SandboxController).CheckUserCreatedWithSignUp(0x3b9d9e8?, {0x3b9d9e8?, 0x3b9a1e1?}, 0x8?)\n\t/tmp/tmp.CNj1aJY7Z5/pkg/sandbox/sandbox.go:318 +0x72\ngithub.com/konflux-ci/e2e-tests/pkg/sandbox.(*SandboxController).CheckUserCreated(0x0, {0x3b9d9e8, 0x9})\n\t/tmp/tmp.CNj1aJY7Z5/pkg/sandbox/sandbox.go:314 +0x4b\ngithub.com/konflux-ci/e2e-tests/tests/upgrade/verify.VerifyAppStudioProvisionedUser(0x0?)\n\t/tmp/tmp.CNj1aJY7Z5/tests/upgrade/verify/verifyUsers.go:14 +0x25\ngithub.com/konflux-ci/e2e-tests/tests/upgrade.init.func1.2()\n\t/tmp/tmp.CNj1aJY7Z5/tests/upgrade/verifyWorkload.go:21 +0x1a\ngithub.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x0?, 0x0?})\n\t/opt/app-root/src/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.28.0/internal/node.go:585 +0x13\ngithub.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3()\n\t/opt/app-root/src/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.28.0/internal/suite.go:946 +0x393\ncreated by github.com/onsi/ginkgo/v2/internal.(*Suite).runNode in goroutine 93\n\t/opt/app-root/src/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.28.0/internal/suite.go:911 +0xd90\n&#34;&#xA;[PANICKED] Test Panicked&#xA;In [It] at: /opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.34.2/pkg/util/runtime/runtime.go:114 @ 05/09/26 02:56:55.166&#xA;&#xA;runtime error: invalid memory address or nil pointer dereference&#xA;&#xA;Full Stack Trace&#xA;  k8s.io/apimachinery/pkg/util/runtime.handleCrash({0x43a2568, 0xc0004565b0}, {0x34796c0, 0x65a16e0}, {0x0, 0x0, 0x4470a0?})&#xA;  &#x9;/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.34.2/pkg/util/runtime/runtime.go:114 +0x1a9&#xA;  k8s.io/apimachinery/pkg/util/runtime.HandleCrashWithContext({0x43a2568, 0xc0004565b0}, {0x0, 0x0, 0x0})&#xA;  &#x9;/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.34.2/pkg/util/runtime/runtime.go:78 +0x5a&#xA;  panic({0x34796c0?, 0x65a16e0?})&#xA;  &#x9;/usr/lib/golang/src/runtime/panic.go:783 +0x132&#xA;  github.com/konflux-ci/e2e-tests/pkg/sandbox.(*SandboxController).CheckUserCreatedWithSignUp.func1()&#xA;  &#x9;/tmp/tmp.CNj1aJY7Z5/pkg/sandbox/sandbox.go:319 +0x35&#xA;  github.com/konflux-ci/e2e-tests/pkg/utils.WaitUntilWithInterval.func1({0xc000456701?, 0xc00019ec18?})&#xA;  &#x9;/tmp/tmp.CNj1aJY7Z5/pkg/utils/util.go:129 +0x13&#xA;  k8s.io/apimachinery/pkg/util/wait.loopConditionUntilContext.func1({0x43a2568?, 0xc0004565b0?}, 0x43a2568?)&#xA;  &#x9;/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.34.2/pkg/util/wait/loop.go:53 +0x62&#xA;  k8s.io/apimachinery/pkg/util/wait.loopConditionUntilContext({0x43a2568, 0xc0004565b0}, {0x438d5c0, 0xc00095a940}, 0x1, 0x0, 0xc00130fd90)&#xA;  &#x9;/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.34.2/pkg/util/wait/loop.go:54 +0x115&#xA;  k8s.io/apimachinery/pkg/util/wait.PollUntilContextTimeout({0x43a2418?, 0x6653d40?}, 0xee6b2800, 0x41d765?, 0x1, 0xc00019ed90)&#xA;  &#x9;/opt/app-root/src/go/pkg/mod/k8s.io/apimachinery@v0.34.2/pkg/util/wait/poll.go:48 +0xa5&#xA;  github.com/konflux-ci/e2e-tests/pkg/utils.WaitUntilWithInterval(0xa?, 0xc00019edd8?, 0x1?)&#xA;  &#x9;/tmp/tmp.CNj1aJY7Z5/pkg/utils/util.go:129 +0x45&#xA;  github.com/konflux-ci/e2e-tests/pkg/sandbox.(*SandboxController).CheckUserCreatedWithSignUp(0x3b9d9e8?, {0x3b9d9e8?, 0x3b9a1e1?}, 0x8?)&#xA;  &#x9;/tmp/tmp.CNj1aJY7Z5/pkg/sandbox/sandbox.go:318 +0x72&#xA;  github.com/konflux-ci/e2e-tests/pkg/sandbox.(*SandboxController).CheckUserCreated(0x0, {0x3b9d9e8, 0x9})&#xA;  &#x9;/tmp/tmp.CNj1aJY7Z5/pkg/sandbox/sandbox.go:314 +0x4b&#xA;  github.com/konflux-ci/e2e-tests/tests/upgrade/verify.VerifyAppStudioProvisionedUser(0x0?)&#xA;  &#x9;/tmp/tmp.CNj1aJY7Z5/tests/upgrade/verify/verifyUsers.go:14 +0x25&#xA;  github.com/konflux-ci/e2e-tests/tests/upgrade.init.func1.2()&#xA;  &#x9;/tmp/tmp.CNj1aJY7Z5/tests/upgrade/verifyWorkload.go:21 +0x1a&#xA;&lt; Exit [It] Verify AppStudioProvisionedUser - /tmp/tmp.CNj1aJY7Z5/tests/upgrade/verifyWorkload.go:20 @ 05/09/26 02:56:55.166 (0s)&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/upgrade/verifyWorkload.go:24 @ 05/09/26 02:56:55.167&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/upgrade/verifyWorkload.go:28 @ 05/09/26 02:56:55.167&#xA;</system-err>
          </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] [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="passed" time="96.192937254">
              <system-err>&gt; Enter [BeforeAll] test build annotations - /tmp/tmp.CNj1aJY7Z5/tests/build/annotations.go:35 @ 05/09/26 02:56:55.169&#xA;&lt; Exit [BeforeAll] test build annotations - /tmp/tmp.CNj1aJY7Z5/tests/build/annotations.go:35 @ 05/09/26 02:57:11.023 (15.854s)&#xA;&gt; Enter [BeforeAll] when component is created with invalid build request annotations - /tmp/tmp.CNj1aJY7Z5/tests/build/annotations.go:69 @ 05/09/26 02:57:11.023&#xA;Image repository for component test-annotations-qldozu in namespace build-e2e-qqdr do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component test-annotations-qldozu in namespace build-e2e-qqdr do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [BeforeAll] when component is created with invalid build request annotations - /tmp/tmp.CNj1aJY7Z5/tests/build/annotations.go:69 @ 05/09/26 02:57:31.085 (20.062s)&#xA;&gt; Enter [It] handles invalid request annotation - /tmp/tmp.CNj1aJY7Z5/tests/build/annotations.go:89 @ 05/09/26 02:57:31.086&#xA;build status annotation value: {&#34;message&#34;:&#34;unexpected build request: foo&#34;}&#xA;&lt; Exit [It] handles invalid request annotation - /tmp/tmp.CNj1aJY7Z5/tests/build/annotations.go:89 @ 05/09/26 02:58:31.125 (1m0.039s)&#xA;&gt; Enter [AfterAll] test build annotations - /tmp/tmp.CNj1aJY7Z5/tests/build/annotations.go:51 @ 05/09/26 02:58:31.125&#xA;&lt; Exit [AfterAll] test build annotations - /tmp/tmp.CNj1aJY7Z5/tests/build/annotations.go:51 @ 05/09/26 02:58:31.361 (237ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/annotations.go:24 @ 05/09/26 02:58:31.362&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/annotations.go:24 @ 05/09/26 02:58:31.362 (0s)&#xA;</system-err>
          </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] [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="passed" time="20.723138216">
              <system-err>&gt; Enter [BeforeAll] [release-service-suite Release service tenant pipeline] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/tenant_pipelines.go:41 @ 05/09/26 02:56:33.317&#xA;snapshotPush.Name: %s snapshot-sample-lyqg&#xA;&lt; Exit [BeforeAll] [release-service-suite Release service tenant pipeline] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/tenant_pipelines.go:41 @ 05/09/26 02:56:53.768 (20.451s)&#xA;&gt; Enter [It] verifies that a Release CR should have been created in the dev namespace - /tmp/tmp.CNj1aJY7Z5/tests/release/service/tenant_pipelines.go:110 @ 05/09/26 02:56:53.769&#xA;&lt; Exit [It] verifies that a Release CR should have been created in the dev namespace - /tmp/tmp.CNj1aJY7Z5/tests/release/service/tenant_pipelines.go:110 @ 05/09/26 02:56:54.04 (271ms)&#xA;&gt; Enter [AfterEach] [release-service-suite Release service tenant pipeline] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/tenant_pipelines.go:28 @ 05/09/26 02:56:54.04&#xA;&lt; Exit [AfterEach] [release-service-suite Release service tenant pipeline] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/tenant_pipelines.go:28 @ 05/09/26 02:56:54.04 (0s)&#xA;</system-err>
          </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="passed" time="40.010518898">
              <system-err>&gt; Enter [It] verifies that Tenant PipelineRun is triggered - /tmp/tmp.CNj1aJY7Z5/tests/release/service/tenant_pipelines.go:117 @ 05/09/26 02:56:54.041&#xA;PipelineRun has not been created yet for release %s/%s tenant-dev-uznk snapshot-sample-lyqg-hzqdg&#xA;PipelineRun tenant-nmhb7 reason: Succeeded&#xA;&lt; Exit [It] verifies that Tenant PipelineRun is triggered - /tmp/tmp.CNj1aJY7Z5/tests/release/service/tenant_pipelines.go:117 @ 05/09/26 02:57:34.051 (40.01s)&#xA;&gt; Enter [AfterEach] [release-service-suite Release service tenant pipeline] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/tenant_pipelines.go:28 @ 05/09/26 02:57:34.051&#xA;&lt; Exit [AfterEach] [release-service-suite Release service tenant pipeline] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/tenant_pipelines.go:28 @ 05/09/26 02:57:34.051 (0s)&#xA;</system-err>
          </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="passed" time="76.040001251">
              <system-err>&gt; Enter [It] verifies that a Release is marked as succeeded. - /tmp/tmp.CNj1aJY7Z5/tests/release/service/tenant_pipelines.go:121 @ 05/09/26 02:57:34.052&#xA;&lt; Exit [It] verifies that a Release is marked as succeeded. - /tmp/tmp.CNj1aJY7Z5/tests/release/service/tenant_pipelines.go:121 @ 05/09/26 02:57:34.058 (7ms)&#xA;&gt; Enter [AfterEach] [release-service-suite Release service tenant pipeline] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/tenant_pipelines.go:28 @ 05/09/26 02:57:34.058&#xA;&lt; Exit [AfterEach] [release-service-suite Release service tenant pipeline] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/tenant_pipelines.go:28 @ 05/09/26 02:57:34.058 (0s)&#xA;&gt; Enter [AfterAll] [release-service-suite Release service tenant pipeline] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/tenant_pipelines.go:102 @ 05/09/26 02:57:34.058&#xA;&lt; Exit [AfterAll] [release-service-suite Release service tenant pipeline] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/tenant_pipelines.go:102 @ 05/09/26 02:58:50.091 (1m16.033s)&#xA;</system-err>
          </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="passed" time="49.647879421">
              <system-err>&gt; Enter [BeforeAll] [release-service-suite Release service happy path] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/happy_path.go:42 @ 05/09/26 02:56:33.317&#xA;snapshotPush.Name: %s snapshot-sample-pvlf&#xA;&lt; Exit [BeforeAll] [release-service-suite Release service happy path] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/happy_path.go:42 @ 05/09/26 02:57:22.516 (49.199s)&#xA;&gt; Enter [It] verifies that a Release CR should have been created in the dev namespace - /tmp/tmp.CNj1aJY7Z5/tests/release/service/happy_path.go:151 @ 05/09/26 02:57:22.516&#xA;&lt; Exit [It] verifies that a Release CR should have been created in the dev namespace - /tmp/tmp.CNj1aJY7Z5/tests/release/service/happy_path.go:151 @ 05/09/26 02:57:22.964 (448ms)&#xA;&gt; Enter [AfterEach] [release-service-suite Release service happy path] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/happy_path.go:27 @ 05/09/26 02:57:22.964&#xA;&lt; Exit [AfterEach] [release-service-suite Release service happy path] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/happy_path.go:27 @ 05/09/26 02:57:22.964 (0s)&#xA;</system-err>
          </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="passed" time="80.030138038">
              <system-err>&gt; Enter [It] verifies that Release PipelineRun is triggered - /tmp/tmp.CNj1aJY7Z5/tests/release/service/happy_path.go:158 @ 05/09/26 02:57:22.965&#xA;PipelineRun has not been created yet for release %s/%s happy-path-wzei snapshot-sample-pvlf-htmsl&#xA;PipelineRun managed-gvkj7 reason: Running&#xA;PipelineRun managed-gvkj7 reason: Running&#xA;PipelineRun managed-gvkj7 reason: Running&#xA;PipelineRun managed-gvkj7 reason: Succeeded&#xA;&lt; Exit [It] verifies that Release PipelineRun is triggered - /tmp/tmp.CNj1aJY7Z5/tests/release/service/happy_path.go:158 @ 05/09/26 02:58:42.995 (1m20.03s)&#xA;&gt; Enter [AfterEach] [release-service-suite Release service happy path] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/happy_path.go:27 @ 05/09/26 02:58:42.995&#xA;&lt; Exit [AfterEach] [release-service-suite Release service happy path] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/happy_path.go:27 @ 05/09/26 02:58:42.995 (0s)&#xA;</system-err>
          </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="passed" time="0.062073271">
              <system-err>&gt; Enter [It] verifies that Enterprise Contract Task has succeeded in the Release PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/release/service/happy_path.go:162 @ 05/09/26 02:58:42.995&#xA;the status of the verify-conforma TaskRun on the release pipeline is: [{Succeeded True  {2026-05-09 02:58:34 +0000 UTC} Succeeded All Steps have completed executing}]&#xA;&lt; Exit [It] verifies that Enterprise Contract Task has succeeded in the Release PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/release/service/happy_path.go:162 @ 05/09/26 02:58:43.057 (62ms)&#xA;&gt; Enter [AfterEach] [release-service-suite Release service happy path] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/happy_path.go:27 @ 05/09/26 02:58:43.057&#xA;&lt; Exit [AfterEach] [release-service-suite Release service happy path] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/happy_path.go:27 @ 05/09/26 02:58:43.057 (0s)&#xA;</system-err>
          </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="passed" time="79.120285148">
              <system-err>&gt; Enter [It] verifies that a Release is marked as succeeded. - /tmp/tmp.CNj1aJY7Z5/tests/release/service/happy_path.go:174 @ 05/09/26 02:58:43.058&#xA;&lt; Exit [It] verifies that a Release is marked as succeeded. - /tmp/tmp.CNj1aJY7Z5/tests/release/service/happy_path.go:174 @ 05/09/26 02:58:43.078 (20ms)&#xA;&gt; Enter [AfterEach] [release-service-suite Release service happy path] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/happy_path.go:27 @ 05/09/26 02:58:43.078&#xA;&lt; Exit [AfterEach] [release-service-suite Release service happy path] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/happy_path.go:27 @ 05/09/26 02:58:43.078 (0s)&#xA;&gt; Enter [AfterAll] [release-service-suite Release service happy path] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/happy_path.go:142 @ 05/09/26 02:58:43.079&#xA;&lt; Exit [AfterAll] [release-service-suite Release service happy path] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/happy_path.go:142 @ 05/09/26 03:00:02.178 (1m19.1s)&#xA;</system-err>
          </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 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="passed" time="17.319552692">
              <system-err>&gt; Enter [BeforeAll] test build secret lookup - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:32 @ 05/09/26 02:56:33.319&#xA;&lt; Exit [BeforeAll] test build secret lookup - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:32 @ 05/09/26 02:56:40.155 (6.836s)&#xA;&gt; Enter [BeforeAll] when two secrets are created - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:100 @ 05/09/26 02:56:40.155&#xA;&lt; Exit [BeforeAll] when two secrets are created - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:100 @ 05/09/26 02:56:40.206 (51ms)&#xA;&gt; Enter [It] creates first component - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:123 @ 05/09/26 02:56:40.206&#xA;&lt; Exit [It] creates first component - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:123 @ 05/09/26 02:56:50.638 (10.432s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:25 @ 05/09/26 02:56:50.639&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:25 @ 05/09/26 02:56:50.639 (0s)&#xA;</system-err>
          </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="passed" time="30.274514795">
              <system-err>&gt; Enter [It] creates second component - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:140 @ 05/09/26 02:56:50.639&#xA;Image repository for component component-two-cjow in namespace build-e2e-jbdb do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component component-two-cjow in namespace build-e2e-jbdb do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [It] creates second component - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:140 @ 05/09/26 02:57:20.913 (30.274s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:25 @ 05/09/26 02:57:20.914&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:25 @ 05/09/26 02:57:20.914 (0s)&#xA;</system-err>
          </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="passed" time="20.083176038">
              <system-err>&gt; Enter [It] check first component annotation has errors - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:158 @ 05/09/26 02:57:20.914&#xA;build status annotation value: {&#34;message&#34;:&#34;waiting for spec.containerImage to be set by ImageRepository with annotation image-controller.appstudio.redhat.com/update-component-image&#34;}&#xA;build status annotation value: {&#34;message&#34;:&#34;waiting for spec.containerImage to be set by ImageRepository with annotation image-controller.appstudio.redhat.com/update-component-image&#34;}&#xA;build status annotation value: {&#34;message&#34;:&#34;waiting for spec.containerImage to be set by ImageRepository with annotation image-controller.appstudio.redhat.com/update-component-image&#34;}&#xA;build status annotation value: {&#34;message&#34;:&#34;waiting for spec.containerImage to be set by ImageRepository with annotation image-controller.appstudio.redhat.com/update-component-image&#34;}&#xA;build status annotation value: {&#34;pac&#34;:{&#34;state&#34;:&#34;error&#34;,&#34;error-id&#34;:74,&#34;error-message&#34;:&#34;74: Access token is unrecognizable by GitHub&#34;},&#34;message&#34;:&#34;done&#34;}&#xA;&lt; Exit [It] check first component annotation has errors - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:158 @ 05/09/26 02:57:40.997 (20.083s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:25 @ 05/09/26 02:57:40.997&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:25 @ 05/09/26 02:57:40.997 (0s)&#xA;</system-err>
          </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="passed" time="40.050681658">
              <system-err>&gt; Enter [It] triggered PipelineRun is for component  - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:178 @ 05/09/26 02:57:40.998&#xA;PipelineRun has not been created yet for the component build-e2e-jbdb/component-two-cjow&#xA;PipelineRun has not been created yet for the component build-e2e-jbdb/component-two-cjow&#xA;&lt; Exit [It] triggered PipelineRun is for component  - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:178 @ 05/09/26 02:58:21.048 (40.05s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:25 @ 05/09/26 02:58:21.048&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:25 @ 05/09/26 02:58:21.048 (0s)&#xA;</system-err>
          </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="passed" time="133.220896619">
              <system-err>&gt; Enter [It] check only one pipelinerun should be triggered - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:193 @ 05/09/26 02:58:21.049&#xA;&lt; Exit [It] check only one pipelinerun should be triggered - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:193 @ 05/09/26 03:00:21.05 (2m0.001s)&#xA;&gt; Enter [AfterAll] test build secret lookup - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:61 @ 05/09/26 03:00:21.05&#xA;&lt; Exit [AfterAll] test build secret lookup - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:61 @ 05/09/26 03:00:34.269 (13.219s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:25 @ 05/09/26 03:00:34.27&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/secret_lookup.go:25 @ 05/09/26 03:00:34.27 (0s)&#xA;</system-err>
          </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] [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-bzwf [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="passed" time="188.870103411">
              <system-err>&gt; Enter [BeforeAll] HACBS pipelines - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:237 @ 05/09/26 02:56:33.115&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;found credentials for image ref quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1778295404-mqxe -&gt; user: redhat-appstudio-qe+redhat_appstudio_quality&#34;&#xA;Image repository for component test-comp-awrw in namespace build-e2e-tpgf 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-awrw in namespace build-e2e-tpgf do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Created component for scenario sample-python-basic-oci: component: test-comp-awrw, repo: https://github.com/redhat-appstudio-qe/devfile-sample-python-basic, baseBranchName: base-nfhpdl, pacBranchName: konflux-test-comp-awrw&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;found credentials for image ref quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1778295431-vwxu -&gt; user: redhat-appstudio-qe+redhat_appstudio_quality&#34;&#xA;Image repository for component test-comp-jecd in namespace build-e2e-tpgf 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-jecd in namespace build-e2e-tpgf do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Created component for scenario sample-python-basic-oci: component: test-comp-jecd, repo: https://github.com/redhat-appstudio-qe/devfile-sample-python-basic, baseBranchName: base-hmzlvq, pacBranchName: konflux-test-comp-jecd&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;found credentials for image ref quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1778295459-wxdq -&gt; user: redhat-appstudio-qe+redhat_appstudio_quality&#34;&#xA;Image repository for component test-comp-npid in namespace build-e2e-tpgf do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Created component for scenario sample-python-basic-oci: component: test-comp-npid, repo: https://github.com/redhat-appstudio-qe/devfile-sample-python-basic, baseBranchName: base-lczylo, pacBranchName: konflux-test-comp-npid&#xA;Image repository for component test-symlink-comp-bzwf in namespace build-e2e-tpgf do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Created component for scenario sample-python-basic-oci: component: test-symlink-comp-bzwf, repo: https://github.com/redhat-appstudio-qe/devfile-sample-python-basic, baseBranchName: base-weofkj, pacBranchName: konflux-test-symlink-comp-bzwf&#xA;&lt; Exit [BeforeAll] HACBS pipelines - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:237 @ 05/09/26 02:58:21.737 (1m48.621s)&#xA;&gt; Enter [It] triggers PipelineRun for symlink component with source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic with component name test-symlink-comp-bzwf - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:325 @ 05/09/26 02:58:21.737&#xA;PipelineRun has not been created yet for Component build-e2e-tpgf/test-symlink-comp-bzwf&#xA;PipelineRun has not been created yet for Component build-e2e-tpgf/test-symlink-comp-bzwf&#xA;PipelineRun has not been created yet for Component build-e2e-tpgf/test-symlink-comp-bzwf&#xA;PipelineRun has not been created yet for Component build-e2e-tpgf/test-symlink-comp-bzwf&#xA;&lt; Exit [It] triggers PipelineRun for symlink component with source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic with component name test-symlink-comp-bzwf - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:325 @ 05/09/26 02:59:41.985 (1m20.248s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 02:59:41.985&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 02:59:41.985 (0s)&#xA;</system-err>
          </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="passed" time="0.089204477">
              <system-err>&gt; Enter [It] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:338 @ 05/09/26 02:59:41.986&#xA;&lt; Exit [It] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:338 @ 05/09/26 02:59:42.075 (89ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 02:59:42.075&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 02:59:42.075 (0s)&#xA;</system-err>
          </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="passed" time="0.090007168">
              <system-err>&gt; Enter [It] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:338 @ 05/09/26 02:59:42.075&#xA;&lt; Exit [It] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:338 @ 05/09/26 02:59:42.165 (90ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 02:59:42.165&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 02:59:42.165 (0s)&#xA;</system-err>
          </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="passed" time="0.064224875">
              <system-err>&gt; Enter [It] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:338 @ 05/09/26 02:59:42.166&#xA;&lt; Exit [It] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:338 @ 05/09/26 02:59:42.23 (64ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 02:59:42.23&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 02:59:42.23 (0s)&#xA;</system-err>
          </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="passed" time="505.245466915">
              <system-err>&gt; Enter [It] should eventually finish successfully for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:356 @ 05/09/26 02:59:42.231&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw found for Component build-e2e-tpgf/test-comp-jecd&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Running&#xA;PipelineRun test-comp-jecd-on-pull-request-tjgmw reason: Completed&#xA;&lt; Exit [It] should eventually finish successfully for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:356 @ 05/09/26 03:08:07.476 (8m25.245s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:07.476&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:07.476 (0s)&#xA;</system-err>
          </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="passed" time="3.998233005">
              <system-err>&gt; Enter [It] should push Dockerfile to registry - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:366 @ 05/09/26 03:08:07.476&#xA;&lt; Exit [It] should push Dockerfile to registry - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:366 @ 05/09/26 03:08:11.474 (3.998s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:11.474&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:11.474 (0s)&#xA;</system-err>
          </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.000723089">
              <skipped message="skipped - floating tag validation is not needed for: https://github.com/redhat-appstudio-qe/devfile-sample-python-basic"></skipped>
              <system-err>&gt; Enter [It] floating tags are created successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:378 @ 05/09/26 03:08:11.475&#xA;[SKIPPED] floating tag validation is not needed for: https://github.com/redhat-appstudio-qe/devfile-sample-python-basic&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:380 @ 05/09/26 03:08:11.475&#xA;&lt; Exit [It] floating tags are created successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:378 @ 05/09/26 03:08:11.475 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:11.476&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:11.476 (0s)&#xA;</system-err>
          </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="passed" time="0.386412389">
              <system-err>&gt; Enter [It] image manifest mediaType is correct - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:395 @ 05/09/26 03:08:11.476&#xA;&lt; Exit [It] image manifest mediaType is correct - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:395 @ 05/09/26 03:08:11.862 (386ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:11.863&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:11.863 (0s)&#xA;</system-err>
          </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.040520356">
              <skipped message="skipped - Skipping source image check since it is not enabled in the pipeline"></skipped>
              <system-err>&gt; Enter [It] check for source images if enabled in pipeline - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:420 @ 05/09/26 03:08:11.863&#xA;Source build is enabled: false&#xA;[SKIPPED] Skipping source image check since it is not enabled in the pipeline&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:440 @ 05/09/26 03:08:11.903&#xA;&lt; Exit [It] check for source images if enabled in pipeline - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:420 @ 05/09/26 03:08:11.903 (40ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:11.904&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:11.904 (0s)&#xA;</system-err>
          </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="passed" time="0.289115622">
              <system-err>&gt; Enter [BeforeAll] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:477 @ 05/09/26 03:08:11.904&#xA;&lt; Exit [BeforeAll] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:477 @ 05/09/26 03:08:12.007 (102ms)&#xA;&gt; Enter [It] should have Pipeline Records - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:498 @ 05/09/26 03:08:12.007&#xA;records for PipelineRun test-comp-jecd-on-pull-request-tjgmw:&#xA;&amp;{[{build-e2e-tpgf/results/8397b514-fc2c-4d81-8ec9-db2da416a73d/records/92f44f16-78f2-4296-afa7-646d3ea6a628 313cefeb-eeda-4986-97d7-b90085836cfa 313cefeb-eeda-4986-97d7-b90085836cfa} {build-e2e-tpgf/results/8397b514-fc2c-4d81-8ec9-db2da416a73d/records/9568d6b3-4eb6-41e2-a8e3-4b80b46a7916 46be831c-b69f-4147-b3be-b23ee09e3766 46be831c-b69f-4147-b3be-b23ee09e3766} {build-e2e-tpgf/results/8397b514-fc2c-4d81-8ec9-db2da416a73d/records/56313be2-555c-42c0-92f6-c03171a775d5 5925f9cf-c879-45dd-9ad2-493d34109c19 5925f9cf-c879-45dd-9ad2-493d34109c19} {build-e2e-tpgf/results/8397b514-fc2c-4d81-8ec9-db2da416a73d/records/e0a1e282-8da3-4ec0-8c95-bd776e740d8f 63e36a02-eb91-4015-af79-5898cadfe391 63e36a02-eb91-4015-af79-5898cadfe391} {build-e2e-tpgf/results/8397b514-fc2c-4d81-8ec9-db2da416a73d/records/d0d7a8d9-fc0c-4714-86a0-42aed3116d08 6b3cffd8-de59-4e05-a094-d7a1e31e61ab 6b3cffd8-de59-4e05-a094-d7a1e31e61ab} {build-e2e-tpgf/results/8397b514-fc2c-4d81-8ec9-db2da416a73d/records/2edb3852-7674-4c9a-b30d-dde51b20dda8 6f07eb1f-ca99-4264-8fed-d880e0e2e73e 6f07eb1f-ca99-4264-8fed-d880e0e2e73e} {build-e2e-tpgf/results/8397b514-fc2c-4d81-8ec9-db2da416a73d/records/12fbdf6b-db11-4d05-ad85-ca33ad7d1923 73613c44-422b-4e7c-9fbf-9263de78bd90 73613c44-422b-4e7c-9fbf-9263de78bd90} {build-e2e-tpgf/results/8397b514-fc2c-4d81-8ec9-db2da416a73d/records/06257fbf-1f54-49ac-bc0f-a55a2d9c927c 7a4274e4-cd65-461b-b1f7-05b52341ddf5 7a4274e4-cd65-461b-b1f7-05b52341ddf5} {build-e2e-tpgf/results/8397b514-fc2c-4d81-8ec9-db2da416a73d/records/a38b9481-ea50-4447-9daf-3561681cfee2 86d5bc9e-bc2c-4660-94cc-dae951226a05 86d5bc9e-bc2c-4660-94cc-dae951226a05} {build-e2e-tpgf/results/8397b514-fc2c-4d81-8ec9-db2da416a73d/records/98d85f19-cfd5-4999-867c-758caf40963b 910b90e6-7c9e-411c-82e6-bf5978c76bd6 910b90e6-7c9e-411c-82e6-bf5978c76bd6} {build-e2e-tpgf/results/8397b514-fc2c-4d81-8ec9-db2da416a73d/records/e43630da-1e05-4f8a-9493-d868970cae0d b667bfbb-ced6-47a5-acbd-3bd4cc773103 b667bfbb-ced6-47a5-acbd-3bd4cc773103} {build-e2e-tpgf/results/8397b514-fc2c-4d81-8ec9-db2da416a73d/records/8f07b484-8724-4874-8fe9-f18b5d268302 be7d894f-d49d-45a3-af11-cf5b35716d13 be7d894f-d49d-45a3-af11-cf5b35716d13} {build-e2e-tpgf/results/8397b514-fc2c-4d81-8ec9-db2da416a73d/records/33c21ddf-c77a-4dc0-ad58-63b82ab6b38d c029642b-2d55-4ceb-88e2-42300a97f03b c029642b-2d55-4ceb-88e2-42300a97f03b} {build-e2e-tpgf/results/8397b514-fc2c-4d81-8ec9-db2da416a73d/records/fd8b679e-7cc7-47eb-9819-b5307ecc90b3 c6098a89-67f3-4faf-8e4f-48f8486a896b c6098a89-67f3-4faf-8e4f-48f8486a896b} {build-e2e-tpgf/results/8397b514-fc2c-4d81-8ec9-db2da416a73d/records/8397b514-fc2c-4d81-8ec9-db2da416a73d ec176e45-7f39-4a0a-8f6d-6f987a48fba4 ec176e45-7f39-4a0a-8f6d-6f987a48fba4} {build-e2e-tpgf/results/8397b514-fc2c-4d81-8ec9-db2da416a73d/records/45294106-59a8-4910-9298-c28f257b870a ef9e54b9-bb71-4506-b51a-660a2097d935 ef9e54b9-bb71-4506-b51a-660a2097d935}]}&#xA;&lt; Exit [It] should have Pipeline Records - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:498 @ 05/09/26 03:08:12.193 (186ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:12.193&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:12.193 (0s)&#xA;</system-err>
          </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="passed" time="0.455753065">
              <system-err>&gt; Enter [It] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:540 @ 05/09/26 03:08:12.194&#xA;&lt; Exit [It] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:540 @ 05/09/26 03:08:12.649 (455ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:12.65&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:12.65 (0s)&#xA;</system-err>
          </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.025966555">
              <skipped message="skipped - Hermetic build is not enabled, skipping the test"></skipped>
              <system-err>&gt; Enter [BeforeAll] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:550 @ 05/09/26 03:08:12.651&#xA;&lt; Exit [BeforeAll] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:550 @ 05/09/26 03:08:12.676 (25ms)&#xA;&gt; Enter [It] should have Hermeto content in the SBOM in case the build was hermetic - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:661 @ 05/09/26 03:08:12.676&#xA;[SKIPPED] Hermetic build is not enabled, skipping the test&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:663 @ 05/09/26 03:08:12.676&#xA;&lt; Exit [It] should have Hermeto content in the SBOM in case the build was hermetic - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:661 @ 05/09/26 03:08:12.676 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:12.676&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:12.676 (0s)&#xA;</system-err>
          </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="passed" time="0.197823128">
              <system-err>&gt; Enter [It] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:356 @ 05/09/26 03:08:12.677&#xA;PipelineRun test-comp-npid-on-pull-request-gx29c found for Component build-e2e-tpgf/test-comp-npid&#xA;PipelineRun test-comp-npid-on-pull-request-gx29c reason: Completed&#xA;&lt; Exit [It] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:356 @ 05/09/26 03:08:12.874 (197ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:12.875&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:12.875 (0s)&#xA;</system-err>
          </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="passed" time="4.842839735">
              <system-err>&gt; Enter [It] should push Dockerfile to registry - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:366 @ 05/09/26 03:08:12.876&#xA;&lt; Exit [It] should push Dockerfile to registry - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:366 @ 05/09/26 03:08:17.718 (4.842s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:17.718&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:17.718 (0s)&#xA;</system-err>
          </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.000654558">
              <skipped message="skipped - floating tag validation is not needed for: https://github.com/redhat-appstudio-qe/devfile-sample-python-basic"></skipped>
              <system-err>&gt; Enter [It] floating tags are created successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:378 @ 05/09/26 03:08:17.719&#xA;[SKIPPED] floating tag validation is not needed for: https://github.com/redhat-appstudio-qe/devfile-sample-python-basic&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:380 @ 05/09/26 03:08:17.719&#xA;&lt; Exit [It] floating tags are created successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:378 @ 05/09/26 03:08:17.72 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:17.72&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:17.72 (0s)&#xA;</system-err>
          </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="passed" time="0.309840963">
              <system-err>&gt; Enter [It] image manifest mediaType is correct - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:395 @ 05/09/26 03:08:17.72&#xA;&lt; Exit [It] image manifest mediaType is correct - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:395 @ 05/09/26 03:08:18.03 (309ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:18.03&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:18.03 (0s)&#xA;</system-err>
          </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.29253024">
              <skipped message="skipped - Skipping source image check since it is not enabled in the pipeline"></skipped>
              <system-err>&gt; Enter [It] check for source images if enabled in pipeline - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:420 @ 05/09/26 03:08:18.031&#xA;Source build is enabled: false&#xA;[SKIPPED] Skipping source image check since it is not enabled in the pipeline&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:440 @ 05/09/26 03:08:18.322&#xA;&lt; Exit [It] check for source images if enabled in pipeline - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:420 @ 05/09/26 03:08:18.322 (292ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:18.323&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:18.323 (0s)&#xA;</system-err>
          </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="passed" time="0.499915371">
              <system-err>&gt; Enter [BeforeAll] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:477 @ 05/09/26 03:08:18.324&#xA;&lt; Exit [BeforeAll] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:477 @ 05/09/26 03:08:18.654 (331ms)&#xA;&gt; Enter [It] should have Pipeline Records - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:498 @ 05/09/26 03:08:18.655&#xA;records for PipelineRun test-comp-npid-on-pull-request-gx29c:&#xA;&amp;{[{build-e2e-tpgf/results/a49a6e7f-19a4-4931-baa6-d851ec190c37/records/80fdaa9a-04ea-484b-adf4-eef8fd6fa93c 04fedb2d-5fdf-4978-9cb2-8d09fcc40c03 04fedb2d-5fdf-4978-9cb2-8d09fcc40c03} {build-e2e-tpgf/results/a49a6e7f-19a4-4931-baa6-d851ec190c37/records/c4f3209d-0be7-4040-a5ae-4b75779950ac 3aab5fa0-4037-4cab-868a-7dd93b171703 3aab5fa0-4037-4cab-868a-7dd93b171703} {build-e2e-tpgf/results/a49a6e7f-19a4-4931-baa6-d851ec190c37/records/0520daaf-41b7-4df7-bd7f-cb0fbedc8d33 48023a7c-3ab5-436d-836b-df3c78489ec4 48023a7c-3ab5-436d-836b-df3c78489ec4} {build-e2e-tpgf/results/a49a6e7f-19a4-4931-baa6-d851ec190c37/records/1a1d7df2-afdd-4888-a178-83cf6430cd1a 4a7941e3-1a69-405b-ac3c-cbbeab9d07b7 4a7941e3-1a69-405b-ac3c-cbbeab9d07b7} {build-e2e-tpgf/results/a49a6e7f-19a4-4931-baa6-d851ec190c37/records/bb54c51d-dc95-4f34-8814-ff91397d35df 4b7fc7f5-4070-4a47-840f-e4be74519a50 4b7fc7f5-4070-4a47-840f-e4be74519a50} {build-e2e-tpgf/results/a49a6e7f-19a4-4931-baa6-d851ec190c37/records/086a9057-1075-47b0-9994-8e2f5903e7f6 5c5a1b2a-ad6d-49c0-aaea-bd754baacab6 5c5a1b2a-ad6d-49c0-aaea-bd754baacab6} {build-e2e-tpgf/results/a49a6e7f-19a4-4931-baa6-d851ec190c37/records/6ad9b090-defb-4cc6-b8ba-a06736718e7b 67db2b48-7686-4857-86fd-bed3fa74b46d 67db2b48-7686-4857-86fd-bed3fa74b46d} {build-e2e-tpgf/results/a49a6e7f-19a4-4931-baa6-d851ec190c37/records/7dd1f766-b39b-4810-84f2-25d8076c344a 68c9288d-e647-403e-8cd5-1c07288b570c 68c9288d-e647-403e-8cd5-1c07288b570c} {build-e2e-tpgf/results/a49a6e7f-19a4-4931-baa6-d851ec190c37/records/e8bff5fb-e19a-4e3c-92dc-6b2f159a04bb 759802f3-875c-4a24-89d4-dbe4b7a43cf4 759802f3-875c-4a24-89d4-dbe4b7a43cf4} {build-e2e-tpgf/results/a49a6e7f-19a4-4931-baa6-d851ec190c37/records/c1ff6fae-24d9-4af6-84a3-2fd499a2d968 75d61e3d-84a6-4d6c-9f86-8ffed957d55c 75d61e3d-84a6-4d6c-9f86-8ffed957d55c} {build-e2e-tpgf/results/a49a6e7f-19a4-4931-baa6-d851ec190c37/records/a49a6e7f-19a4-4931-baa6-d851ec190c37 7b574210-cf89-45d1-9fb1-7c5211d30407 7b574210-cf89-45d1-9fb1-7c5211d30407} {build-e2e-tpgf/results/a49a6e7f-19a4-4931-baa6-d851ec190c37/records/870bd58c-88ac-4e6e-84cf-3849b7eb5553 8525bd87-8ee1-4849-9e20-40046625bc8a 8525bd87-8ee1-4849-9e20-40046625bc8a} {build-e2e-tpgf/results/a49a6e7f-19a4-4931-baa6-d851ec190c37/records/f9414d91-6497-45de-a188-d50d93deb9a1 cabc5214-fee9-4dd6-a2fd-596ad8eb6913 cabc5214-fee9-4dd6-a2fd-596ad8eb6913} {build-e2e-tpgf/results/a49a6e7f-19a4-4931-baa6-d851ec190c37/records/e40defce-8717-468b-abfa-99d331bdfb05 cbe05d0d-9d90-48f1-b0b4-954993b6b0d3 cbe05d0d-9d90-48f1-b0b4-954993b6b0d3} {build-e2e-tpgf/results/a49a6e7f-19a4-4931-baa6-d851ec190c37/records/e4037f91-9a05-42b7-bd62-367f7e84494a d1c56cfe-b7ea-4a1b-ba9d-7f458936d954 d1c56cfe-b7ea-4a1b-ba9d-7f458936d954} {build-e2e-tpgf/results/a49a6e7f-19a4-4931-baa6-d851ec190c37/records/1f8dc87a-1da5-48f4-a891-32e68ada7e11 d4b12e23-49a1-48b6-932d-7384408d4482 d4b12e23-49a1-48b6-932d-7384408d4482}]}&#xA;&lt; Exit [It] should have Pipeline Records - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:498 @ 05/09/26 03:08:18.823 (168ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:18.823&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:18.823 (0s)&#xA;</system-err>
          </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="passed" time="0.498787351">
              <system-err>&gt; Enter [It] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:540 @ 05/09/26 03:08:18.824&#xA;&lt; Exit [It] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:540 @ 05/09/26 03:08:19.323 (498ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:19.323&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:19.323 (0s)&#xA;</system-err>
          </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.049031102">
              <skipped message="skipped - Hermetic build is not enabled, skipping the test"></skipped>
              <system-err>&gt; Enter [BeforeAll] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:550 @ 05/09/26 03:08:19.324&#xA;&lt; Exit [BeforeAll] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:550 @ 05/09/26 03:08:19.373 (48ms)&#xA;&gt; Enter [It] should have Hermeto content in the SBOM in case the build was hermetic - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:661 @ 05/09/26 03:08:19.373&#xA;[SKIPPED] Hermetic build is not enabled, skipping the test&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:663 @ 05/09/26 03:08:19.373&#xA;&lt; Exit [It] should have Hermeto content in the SBOM in case the build was hermetic - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:661 @ 05/09/26 03:08:19.373 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:19.373&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:19.373 (0s)&#xA;</system-err>
          </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="passed" time="20.828353386">
              <system-err>&gt; Enter [It] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:356 @ 05/09/26 03:08:19.374&#xA;PipelineRun test-comp-awrw-on-pull-request-k4kqx found for Component build-e2e-tpgf/test-comp-awrw&#xA;PipelineRun test-comp-awrw-on-pull-request-k4kqx reason: Running&#xA;PipelineRun test-comp-awrw-on-pull-request-k4kqx reason: Succeeded&#xA;&lt; Exit [It] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:356 @ 05/09/26 03:08:40.202 (20.828s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:40.202&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:40.202 (0s)&#xA;</system-err>
          </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.000503843">
              <skipped message="skipped - Skipping DockerBuildOciTAMin build, which does not push Dockerfile to registry"></skipped>
              <system-err>&gt; Enter [It] should push Dockerfile to registry - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:366 @ 05/09/26 03:08:40.203&#xA;[SKIPPED] Skipping DockerBuildOciTAMin build, which does not push Dockerfile to registry&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:369 @ 05/09/26 03:08:40.203&#xA;&lt; Exit [It] should push Dockerfile to registry - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:366 @ 05/09/26 03:08:40.203 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:40.203&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:40.203 (0s)&#xA;</system-err>
          </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.000413692">
              <skipped message="skipped - floating tag validation is not needed for: https://github.com/redhat-appstudio-qe/devfile-sample-python-basic"></skipped>
              <system-err>&gt; Enter [It] floating tags are created successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:378 @ 05/09/26 03:08:40.204&#xA;[SKIPPED] floating tag validation is not needed for: https://github.com/redhat-appstudio-qe/devfile-sample-python-basic&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:380 @ 05/09/26 03:08:40.204&#xA;&lt; Exit [It] floating tags are created successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:378 @ 05/09/26 03:08:40.204 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:40.204&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:40.204 (0s)&#xA;</system-err>
          </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="passed" time="0.364928139">
              <system-err>&gt; Enter [It] image manifest mediaType is correct - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:395 @ 05/09/26 03:08:40.204&#xA;&lt; Exit [It] image manifest mediaType is correct - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:395 @ 05/09/26 03:08:40.569 (365ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:40.569&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:40.569 (0s)&#xA;</system-err>
          </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.086032333">
              <skipped message="skipped - Skiping DockerBuildOciTAMin build test-comp-awrw-on-pull-request-k4kqx"></skipped>
              <system-err>&gt; Enter [It] check for source images if enabled in pipeline - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:420 @ 05/09/26 03:08:40.57&#xA;This is DockerBuildOciTAMin build, which does not require source container build.&#xA;[SKIPPED] Skiping DockerBuildOciTAMin build test-comp-awrw-on-pull-request-k4kqx&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:433 @ 05/09/26 03:08:40.655&#xA;&lt; Exit [It] check for source images if enabled in pipeline - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:420 @ 05/09/26 03:08:40.655 (86ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:40.655&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:40.656 (0s)&#xA;</system-err>
          </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="passed" time="0.260230347">
              <system-err>&gt; Enter [BeforeAll] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:477 @ 05/09/26 03:08:40.656&#xA;&lt; Exit [BeforeAll] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:477 @ 05/09/26 03:08:40.782 (125ms)&#xA;&gt; Enter [It] should have Pipeline Records - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:498 @ 05/09/26 03:08:40.782&#xA;records for PipelineRun test-comp-awrw-on-pull-request-k4kqx:&#xA;&amp;{[{build-e2e-tpgf/results/cccbad7b-1ccc-40d1-9dc3-72d7526b09a8/records/08356f5d-a4f7-4035-a9e1-480d771c02b4 00e022b0-9a8a-4289-a43a-0b165121b1fc 00e022b0-9a8a-4289-a43a-0b165121b1fc} {build-e2e-tpgf/results/cccbad7b-1ccc-40d1-9dc3-72d7526b09a8/records/1b6377c8-4158-4b60-9c35-8bea8df0c2fc 06b3c3a8-065b-4ed7-b64a-4f20debe9077 06b3c3a8-065b-4ed7-b64a-4f20debe9077} {build-e2e-tpgf/results/cccbad7b-1ccc-40d1-9dc3-72d7526b09a8/records/1d9a9cdc-90a5-4e5a-bd89-e1d22fb3c748 1c75d68e-17d1-4063-81ae-b5f2a067c480 1c75d68e-17d1-4063-81ae-b5f2a067c480} {build-e2e-tpgf/results/cccbad7b-1ccc-40d1-9dc3-72d7526b09a8/records/16a324dc-121e-427c-b465-ad41e5ee0245 309a83fe-5427-49e3-853a-5b8ea55dad4f 309a83fe-5427-49e3-853a-5b8ea55dad4f} {build-e2e-tpgf/results/cccbad7b-1ccc-40d1-9dc3-72d7526b09a8/records/858bdd0d-49a5-44c2-b932-0f301772bb10 400c7dc6-eb57-4575-9a0f-da42a94c7701 400c7dc6-eb57-4575-9a0f-da42a94c7701} {build-e2e-tpgf/results/cccbad7b-1ccc-40d1-9dc3-72d7526b09a8/records/77a586c6-40cd-4a19-b5b8-8540285935a1 4433d33e-6bc0-41d9-90cb-8eac1389fbc9 4433d33e-6bc0-41d9-90cb-8eac1389fbc9} {build-e2e-tpgf/results/cccbad7b-1ccc-40d1-9dc3-72d7526b09a8/records/d99fbc4b-ed32-44ce-92b0-166df199b505 44643436-aa21-4c43-b705-00d430d21567 44643436-aa21-4c43-b705-00d430d21567} {build-e2e-tpgf/results/cccbad7b-1ccc-40d1-9dc3-72d7526b09a8/records/a5739f6c-aa68-44b3-a186-cbaba0160fc7 6071edfd-2a46-4059-9328-6574ae4422c1 6071edfd-2a46-4059-9328-6574ae4422c1} {build-e2e-tpgf/results/cccbad7b-1ccc-40d1-9dc3-72d7526b09a8/records/bbaebd8e-70cd-49df-afc1-952a8cd5f633 66b871fd-200e-4724-85d8-8ebeb850e252 66b871fd-200e-4724-85d8-8ebeb850e252} {build-e2e-tpgf/results/cccbad7b-1ccc-40d1-9dc3-72d7526b09a8/records/cccbad7b-1ccc-40d1-9dc3-72d7526b09a8 83be5d76-abeb-41e3-92a0-53527be9a6c8 83be5d76-abeb-41e3-92a0-53527be9a6c8} {build-e2e-tpgf/results/cccbad7b-1ccc-40d1-9dc3-72d7526b09a8/records/0384f0cd-70a2-4480-b0bc-beaff42cbd74 d4ceeddf-a21b-411b-8082-4f9370b7d83a d4ceeddf-a21b-411b-8082-4f9370b7d83a} {build-e2e-tpgf/results/cccbad7b-1ccc-40d1-9dc3-72d7526b09a8/records/cba403e0-d3c3-4613-8821-faa155c7aade f9a096fd-8bef-4bbf-9714-4b69a83fe538 f9a096fd-8bef-4bbf-9714-4b69a83fe538}]}&#xA;&lt; Exit [It] should have Pipeline Records - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:498 @ 05/09/26 03:08:40.916 (134ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:40.916&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:40.916 (0s)&#xA;</system-err>
          </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="passed" time="0.083873965">
              <system-err>&gt; Enter [It] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:540 @ 05/09/26 03:08:40.919&#xA;&lt; Exit [It] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:540 @ 05/09/26 03:08:41.002 (83ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:41.002&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:41.002 (0s)&#xA;</system-err>
          </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.061303791">
              <skipped message="skipped - Hermetic build is not enabled, skipping the test"></skipped>
              <system-err>&gt; Enter [BeforeAll] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:550 @ 05/09/26 03:08:41.003&#xA;&lt; Exit [BeforeAll] 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 - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:550 @ 05/09/26 03:08:41.064 (60ms)&#xA;&gt; Enter [It] should have Hermeto content in the SBOM in case the build was hermetic - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:661 @ 05/09/26 03:08:41.064&#xA;[SKIPPED] Hermetic build is not enabled, skipping the test&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:663 @ 05/09/26 03:08:41.064&#xA;&lt; Exit [It] should have Hermeto content in the SBOM in case the build was hermetic - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:661 @ 05/09/26 03:08:41.064 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:41.064&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:41.065 (0s)&#xA;</system-err>
          </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-bzwf [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="passed" time="12.642401047">
              <system-err>&gt; Enter [It] 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-bzwf - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:816 @ 05/09/26 03:08:41.066&#xA;PipelineRun test-symlink-comp-bzwf-on-pull-request-xlhrf found for Component build-e2e-tpgf/test-symlink-comp-bzwf&#xA;PipelineRun test-symlink-comp-bzwf-on-pull-request-xlhrf reason: Failed&#xA;attempt 1/1: PipelineRun &#34;test-symlink-comp-bzwf-on-pull-request-xlhrf&#34; failed: &#xA; pod: test-symlink-comp-bzwf-on-pc1a1236fb2b724c863e3275762bd9375-pod | init container: prepare&#xA;2026/05/09 03:00:07 Entrypoint initialization&#xA;&#xA; pod: test-symlink-comp-bzwf-on-pc1a1236fb2b724c863e3275762bd9375-pod | init container: place-scripts&#xA;2026/05/09 03:00:08 Decoded script /tekton/scripts/script-0-zm7j9&#xA;2026/05/09 03:00:08 Decoded script /tekton/scripts/script-1-lmv8h&#xA;&#xA;pod: test-symlink-comp-bzwf-on-pc1a1236fb2b724c863e3275762bd9375-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;:1778295613.3664334,&#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;:1778295613.641694,&#34;caller&#34;:&#34;git/git.go:223&#34;,&#34;msg&#34;:&#34;Successfully cloned https://github.com/redhat-appstudio-qe/devfile-sample-python-basic @ 873f51a3a5511d9042b1e077e86544009649f623 (grafted, HEAD) in path /workspace/output/source&#34;}&#xA;{&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1778295613.6417403,&#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;:1778295613.668778,&#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 873f51a3a5511d9042b1e077e86544009649f623 directly.&#xA;&#xA;pod: test-symlink-comp-bzwf-on-pc1a1236fb2b724c863e3275762bd9375-pod | container step-symlink-check: &#xA;Running symlink check&#xA;The cloned repository contains symlink pointing outside of the cloned repository: /workspace/output/source/os-release-symlink&#xA;&#xA; pod: test-symlink-comp-bzwf-on-pull-request-xlhrf-init-pod | init container: prepare&#xA;2026/05/09 02:59:46 Entrypoint initialization&#xA;&#xA;pod: test-symlink-comp-bzwf-on-pull-request-xlhrf-init-pod | container step-init: &#xA;time=&#34;2026-05-09T02:59:49Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-05-09T02:59:49Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-05-09T02:59:49Z&#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-05-09T02:59:49Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-05-09T02:59:49Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-05-09T02:59:49Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-05-09T02:59:49Z&#34; level=info msg=&#34;Cache proxy is disabled via param&#34;&#xA;time=&#34;2026-05-09T02:59:49Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-05-09T02:59:49Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;&lt; Exit [It] 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-bzwf - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:816 @ 05/09/26 03:08:41.786 (720ms)&#xA;&gt; Enter [AfterAll] HACBS pipelines - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:271 @ 05/09/26 03:08:41.786&#xA;&lt; Exit [AfterAll] HACBS pipelines - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:271 @ 05/09/26 03:08:53.708 (11.921s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:53.708&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.CNj1aJY7Z5/tests/build/build_templates.go:207 @ 05/09/26 03:08:53.708 (0s)&#xA;</system-err>
          </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] [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="99.198832077">
              <system-err>&gt; Enter [BeforeAll] Gitlab with status reporting of Integration tests in the assosiated merge request - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:45 @ 05/09/26 02:56:33.115&#xA;&lt; Exit [BeforeAll] Gitlab with status reporting of Integration tests in the assosiated merge request - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:45 @ 05/09/26 02:56:44.747 (11.632s)&#xA;&gt; Enter [BeforeAll] when a new Component with specified custom branch is created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:109 @ 05/09/26 02:56:44.748&#xA;Image repository for component test-comp-pac-gitlab-rvvfkq in namespace gitlab-rep-beox 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.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:109 @ 05/09/26 02:57:07.751 (23.003s)&#xA;&gt; Enter [It] triggers a Build PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:130 @ 05/09/26 02:57:07.751&#xA;Build PipelineRun has not been created yet for the component gitlab-rep-beox/test-comp-pac-gitlab-rvvfkq&#xA;Build PipelineRun has not been created yet for the component gitlab-rep-beox/test-comp-pac-gitlab-rvvfkq&#xA;Build PipelineRun has not been created yet for the component gitlab-rep-beox/test-comp-pac-gitlab-rvvfkq&#xA;&lt; Exit [It] triggers a Build PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:130 @ 05/09/26 02:58:12.314 (1m4.563s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 02:58:12.314&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 02:58:12.314 (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.000283467">
              <system-err>&gt; Enter [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:144 @ 05/09/26 02:58:12.314&#xA;&lt; Exit [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:144 @ 05/09/26 02:58:12.314 (0s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 02:58:12.314&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 02:58:12.314 (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="640.017515874">
              <system-err>&gt; Enter [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:148 @ 05/09/26 02:58:12.315&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t found for Component gitlab-rep-beox/test-comp-pac-gitlab-rvvfkq&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: ResolvingTaskRef&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun test-comp-pac-gitlab-rvvfkq-on-pull-request-5446t reason: Running&#xA;PipelineRun my-integration-test-aivw-l4f7z reason: Running&#xA;PipelineRun my-integration-test-aivw-l4f7z reason: Succeeded&#xA;&lt; Exit [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:148 @ 05/09/26 03:08:52.332 (10m40.017s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:52.332&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:52.332 (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.374250919">
              <system-err>&gt; Enter [It] should have a related PaC init MR is created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:153 @ 05/09/26 03:08:52.333&#xA;&lt; Exit [It] should have a related PaC init MR is created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:153 @ 05/09/26 03:08:52.707 (374ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:52.707&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:52.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 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.054354225">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for component  - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:172 @ 05/09/26 03:08:52.707&#xA;PipelineRun my-integration-test-aivw-l4f7z found for Component gitlab-rep-beox/test-comp-pac-gitlab-rvvfkq&#xA;PipelineRun my-integration-test-aivw-l4f7z reason: Succeeded&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for component  - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:172 @ 05/09/26 03:08:52.761 (54ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:52.761&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:52.762 (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.021509036">
              <system-err>&gt; Enter [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:179 @ 05/09/26 03:08:52.762&#xA;&lt; Exit [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:179 @ 05/09/26 03:08:52.783 (21ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:52.784&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:52.784 (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.006651978">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:183 @ 05/09/26 03:08:52.784&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:183 @ 05/09/26 03:08:52.79 (6ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:52.791&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:52.791 (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.026724805">
              <system-err>&gt; Enter [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:188 @ 05/09/26 03:08:52.791&#xA;&lt; Exit [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:188 @ 05/09/26 03:08:52.817 (26ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:52.818&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:52.818 (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.007310376">
              <system-err>&gt; Enter [It] should find the Integration Test Scenario PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:194 @ 05/09/26 03:08:52.818&#xA;&lt; Exit [It] should find the Integration Test Scenario PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:194 @ 05/09/26 03:08:52.825 (7ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:52.826&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:52.826 (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="0.015124674">
              <system-err>&gt; Enter [It] should eventually complete successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:207 @ 05/09/26 03:08:52.826&#xA;PipelineRun my-integration-test-zurm-b27rc reason: Succeeded&#xA;PipelineRun my-integration-test-aivw-l4f7z reason: Succeeded&#xA;&lt; Exit [It] should eventually complete successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:207 @ 05/09/26 03:08:52.841 (15ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:52.841&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:52.841 (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.124968686">
              <system-err>&gt; Enter [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it pass - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:212 @ 05/09/26 03:08:52.842&#xA;&lt; Exit [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it pass - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:212 @ 05/09/26 03:08:52.966 (124ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:52.966&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:52.967 (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.296282302">
              <system-err>&gt; Enter [It] eventually leads to the integration test PipelineRun&#39;s Pass status reported at MR commit status - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:229 @ 05/09/26 03:08:52.967&#xA;&lt; Exit [It] eventually leads to the integration test PipelineRun&#39;s Pass status reported at MR commit status - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:229 @ 05/09/26 03:08:53.263 (296ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:53.263&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:53.263 (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.127606056">
              <system-err>&gt; Enter [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it fails - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:233 @ 05/09/26 03:08:53.264&#xA;&lt; Exit [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it fails - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:233 @ 05/09/26 03:08:53.391 (127ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:53.391&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:53.391 (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.266174526">
              <system-err>&gt; Enter [It] eventually leads to the integration test PipelineRun&#39;s Fail status reported at MR commit status - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:250 @ 05/09/26 03:08:53.392&#xA;&lt; Exit [It] eventually leads to the integration test PipelineRun&#39;s Fail status reported at MR commit status - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:250 @ 05/09/26 03:08:53.658 (266ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:53.658&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:53.658 (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.138919639">
              <system-err>&gt; Enter [It] validates at least one MR note contains the final integration test result - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:254 @ 05/09/26 03:08:53.658&#xA;&lt; Exit [It] validates at least one MR note contains the final integration test result - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:254 @ 05/09/26 03:08:53.797 (138ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:53.797&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:53.797 (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.249180974">
              <system-err>&gt; Enter [It] merging the PR should be successful - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:278 @ 05/09/26 03:08:53.798&#xA;merged result sha: fb58cd804ef1b212e2d022efebb3b52bd1e5b81e for MR #17559&#xA;&lt; Exit [It] merging the PR should be successful - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:278 @ 05/09/26 03:08:55.046 (1.249s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:55.047&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:55.047 (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.013234995">
              <system-err>&gt; Enter [It] leads to triggering on push PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:288 @ 05/09/26 03:08:55.047&#xA;&lt; Exit [It] leads to triggering on push PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:288 @ 05/09/26 03:08:55.06 (13ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:55.06&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:55.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 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.01272031">
              <system-err>&gt; Enter [It] should eventually complete successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:303 @ 05/09/26 03:08:55.061&#xA;PipelineRun my-integration-test-zurm-b27rc reason: Succeeded&#xA;PipelineRun my-integration-test-aivw-l4f7z reason: Succeeded&#xA;&lt; Exit [It] should eventually complete successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:303 @ 05/09/26 03:08:55.073 (12ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:55.073&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:55.073 (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.128885121">
              <system-err>&gt; Enter [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it pass - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:308 @ 05/09/26 03:08:55.074&#xA;&lt; Exit [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it pass - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:308 @ 05/09/26 03:08:55.202 (129ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:55.203&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:55.203 (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.361243871">
              <system-err>&gt; Enter [It] eventually leads to the integration test PipelineRun&#39;s Pass status reported at MR commit status - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:325 @ 05/09/26 03:08:55.203&#xA;&lt; Exit [It] eventually leads to the integration test PipelineRun&#39;s Pass status reported at MR commit status - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:325 @ 05/09/26 03:08:55.564 (361ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:55.564&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:55.564 (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.143155343">
              <system-err>&gt; Enter [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it fails - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:329 @ 05/09/26 03:08:55.565&#xA;&lt; Exit [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it fails - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:329 @ 05/09/26 03:08:55.707 (143ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:55.708&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:55.708 (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.622945171">
              <system-err>&gt; Enter [It] eventually leads to the integration test PipelineRun&#39;s Fail status reported at MR commit status - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:346 @ 05/09/26 03:08:55.708&#xA;&lt; Exit [It] eventually leads to the integration test PipelineRun&#39;s Fail status reported at MR commit status - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:346 @ 05/09/26 03:08:55.953 (245ms)&#xA;&gt; Enter [AfterAll] Gitlab with status reporting of Integration tests in the assosiated merge request - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:94 @ 05/09/26 03:08:55.953&#xA;&lt; Exit [AfterAll] Gitlab with status reporting of Integration tests in the assosiated merge request - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:94 @ 05/09/26 03:08:58.331 (2.377s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:58.331&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/gitlab-integration-reporting.go:42 @ 05/09/26 03:08:58.331 (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="68.158898404">
              <system-err>&gt; Enter [BeforeAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:45 @ 05/09/26 02:56:33.315&#xA;Image repository for component test-component-pac-vbaajp in namespace stat-rep-mfzr do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Build PipelineRun has not been created yet for the component stat-rep-mfzr/test-component-pac-vbaajp&#xA;Build PipelineRun has not been created yet for the component stat-rep-mfzr/test-component-pac-vbaajp&#xA;&lt; Exit [BeforeAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:45 @ 05/09/26 02:57:41.473 (1m8.158s)&#xA;&gt; Enter [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:111 @ 05/09/26 02:57:41.473&#xA;&lt; Exit [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:111 @ 05/09/26 02:57:41.473 (0s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 02:57:41.473&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 02:57:41.473 (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.285343632">
              <system-err>&gt; Enter [It] should have a related PaC init PR created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:115 @ 05/09/26 02:57:41.474&#xA;&lt; Exit [It] should have a related PaC init PR created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:115 @ 05/09/26 02:57:41.759 (285ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 02:57:41.759&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 02:57:41.759 (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.290912594">
              <system-err>&gt; Enter [It] initialized integration test status is reported to github - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:134 @ 05/09/26 02:57:41.76&#xA;&lt; Exit [It] initialized integration test status is reported to github - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:134 @ 05/09/26 02:57:42.05 (291ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 02:57:42.05&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 02:57:42.05 (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="640.068613834">
              <system-err>&gt; Enter [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:144 @ 05/09/26 02:57:42.051&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: ResolvingTaskRef&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Running&#xA;PipelineRun test-component-pac-vbaajp-on-pull-request-5qrf7 reason: Completed&#xA;&lt; Exit [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:144 @ 05/09/26 03:08:22.119 (10m40.068s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:22.119&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:22.119 (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.129298961">
              <system-err>&gt; Enter [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:151 @ 05/09/26 03:08:22.12&#xA;&lt; Exit [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:151 @ 05/09/26 03:08:22.249 (129ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:22.249&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:22.249 (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.206629321">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:155 @ 05/09/26 03:08:22.25&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:155 @ 05/09/26 03:08:22.456 (206ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:22.456&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:22.456 (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.239499661">
              <system-err>&gt; Enter [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:160 @ 05/09/26 03:08:22.457&#xA;&lt; Exit [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:160 @ 05/09/26 03:08:22.696 (239ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:22.696&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:22.696 (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="20.212557802">
              <system-err>&gt; Enter [It] should find both the related Integration PipelineRuns - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:166 @ 05/09/26 03:08:22.697&#xA;pipelinerun %s/%s hasn&#39;t started yet stat-rep-mfzr my-integration-test-gpkg-fljk7&#xA;&lt; Exit [It] should find both the related Integration PipelineRuns - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:166 @ 05/09/26 03:08:42.909 (20.212s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:42.909&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:42.909 (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="0.107032365">
              <system-err>&gt; Enter [It] should eventually complete successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:190 @ 05/09/26 03:08:42.91&#xA;PipelineRun my-integration-test-gpkg-fljk7 reason: Succeeded&#xA;PipelineRun my-integration-test-mmqo-6sgqc reason: Succeeded&#xA;PipelineRun my-integration-test-nart-6bkff reason: Succeeded&#xA;PipelineRun my-integration-test-uzgn-zzbmb reason: Succeeded&#xA;&lt; Exit [It] should eventually complete successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:190 @ 05/09/26 03:08:43.016 (107ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:43.017&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:43.017 (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.034919255">
              <system-err>&gt; Enter [It] should lead to Snapshot CR being marked as failed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:199 @ 05/09/26 03:08:43.017&#xA;&lt; Exit [It] should lead to Snapshot CR being marked as failed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:199 @ 05/09/26 03:08:43.052 (34ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:43.052&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:43.052 (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.330132388">
              <system-err>&gt; Enter [It] eventually leads to the status reported at Checks tab for the successful Integration PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:213 @ 05/09/26 03:08:43.053&#xA;&lt; Exit [It] eventually leads to the status reported at Checks tab for the successful Integration PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:213 @ 05/09/26 03:08:43.382 (330ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:43.383&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:43.383 (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.351931222">
              <system-err>&gt; Enter [It] eventually leads to the status reported at Checks tab for the failed Integration PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:217 @ 05/09/26 03:08:43.383&#xA;&lt; Exit [It] eventually leads to the status reported at Checks tab for the failed Integration PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:217 @ 05/09/26 03:08:43.735 (351ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:43.735&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:43.735 (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.439528696">
              <system-err>&gt; Enter [It] eventually leads to the status reported at Checks tab for the optional Integration PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:221 @ 05/09/26 03:08:43.736&#xA;&lt; Exit [It] eventually leads to the status reported at Checks tab for the optional Integration PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:221 @ 05/09/26 03:08:44.175 (439ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:44.175&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:44.175 (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.405503506">
              <system-err>&gt; Enter [It] eventually leads to the status reported at Checks tab for the warning Integration PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:225 @ 05/09/26 03:08:44.176&#xA;&lt; Exit [It] eventually leads to the status reported at Checks tab for the warning Integration PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:225 @ 05/09/26 03:08:44.581 (405ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:44.581&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:44.581 (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.017301492">
              <system-err>&gt; Enter [It] checks if the optional Integration Test Scenario status is reported in the Snapshot - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:229 @ 05/09/26 03:08:44.582&#xA;&lt; Exit [It] checks if the optional Integration Test Scenario status is reported in the Snapshot - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:229 @ 05/09/26 03:08:44.599 (17ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:44.599&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:44.599 (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.020374885">
              <system-err>&gt; Enter [It] checks if the finalizer was removed from the optional Integration PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:244 @ 05/09/26 03:08:44.599&#xA;&lt; Exit [It] checks if the finalizer was removed from the optional Integration PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:244 @ 05/09/26 03:08:44.619 (20ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:44.62&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:44.62 (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.009439093">
              <system-err>&gt; Enter [It] checks if the warning Integration Test Scenario status is reported in the Snapshot - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:248 @ 05/09/26 03:08:44.62&#xA;&lt; Exit [It] checks if the warning Integration Test Scenario status is reported in the Snapshot - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:248 @ 05/09/26 03:08:44.629 (9ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:44.63&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:44.63 (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.013120011">
              <system-err>&gt; Enter [It] checks if the finalizer was removed from the warning Integration PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:263 @ 05/09/26 03:08:44.63&#xA;&lt; Exit [It] checks if the finalizer was removed from the warning Integration PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:263 @ 05/09/26 03:08:44.643 (13ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:44.643&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:44.643 (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.62519465">
              <system-err>&gt; Enter [It] merging the PR, expected to succeed  - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:267 @ 05/09/26 03:08:44.644&#xA;merged result sha: 2f3fd5c500367ebf5b47abd820c175e31461676a for PR #9652&#xA;&lt; Exit [It] merging the PR, expected to succeed  - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:267 @ 05/09/26 03:08:46.269 (1.625s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:46.269&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:08:46.269 (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.023882213">
              <system-err>&gt; Enter [It] leads to triggering a push PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:276 @ 05/09/26 03:08:46.269&#xA;Push PipelineRun has not been created yet for the component stat-rep-mfzr/test-component-pac-vbaajp&#xA;&lt; Exit [It] leads to triggering a push PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:276 @ 05/09/26 03:09:06.293 (20.024s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:09:06.293&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:09:06.293 (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.193346467">
              <system-err>&gt; Enter [It] verifies that Push PipelineRuns completed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:291 @ 05/09/26 03:09:06.294&#xA;PipelineRun my-integration-test-gpkg-fljk7 reason: Succeeded&#xA;PipelineRun my-integration-test-mmqo-6sgqc reason: Succeeded&#xA;PipelineRun my-integration-test-uzgn-zzbmb reason: Succeeded&#xA;&lt; Exit [It] verifies that Push PipelineRuns completed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:291 @ 05/09/26 03:09:06.487 (193ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:09:06.487&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:09:06.487 (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.569729704">
              <system-err>&gt; Enter [It] validates the Integration test scenario PipelineRun is reported to merge request CheckRuns, and it pass - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:297 @ 05/09/26 03:09:06.487&#xA;&lt; Exit [It] validates the Integration test scenario PipelineRun is reported to merge request CheckRuns, and it pass - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:297 @ 05/09/26 03:09:07.057 (569ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:09:07.057&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:09:07.057 (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.364937121">
              <system-err>&gt; Enter [It] eventually leads to the status reported at Checks tab for the failed Integration PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:302 @ 05/09/26 03:09:07.058&#xA;&lt; Exit [It] eventually leads to the status reported at Checks tab for the failed Integration PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:302 @ 05/09/26 03:09:07.422 (364ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:09:07.422&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:09:07.422 (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="20.049973505">
              <system-err>&gt; Enter [It] should set the git-reporting-failure annotation correctly - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:308 @ 05/09/26 03:09:07.423&#xA;gitReportingFailureAnnotation does not exist. Annotations: map[build.appstudio.openshift.io/repo:https://github.com/redhat-appstudio-qe/konflux-test-integration-status-report?rev=3836f29e9038ff422e332a23f3fa6c74bc2a02d3 build.appstudio.redhat.com/commit_sha:3836f29e9038ff422e332a23f3fa6c74bc2a02d3 build.appstudio.redhat.com/pull_request_number:9652 build.appstudio.redhat.com/target_branch:base-zjzddq pac.test.appstudio.openshift.io/branch:base-zjzddq pac.test.appstudio.openshift.io/cancel-in-progress:true pac.test.appstudio.openshift.io/check-run-id:75125169678 pac.test.appstudio.openshift.io/controller-info:{&#34;name&#34;:&#34;default&#34;,&#34;configmap&#34;:&#34;pipelines-as-code&#34;,&#34;secret&#34;:&#34;pipelines-as-code-secret&#34;, &#34;gRepo&#34;: &#34;pipelines-as-code&#34;} pac.test.appstudio.openshift.io/event-type:pull_request pac.test.appstudio.openshift.io/git-auth-secret:pac-gitauth-zxmzwc pac.test.appstudio.openshift.io/git-provider:not-supported-provider pac.test.appstudio.openshift.io/installation-id:40773614 pac.test.appstudio.openshift.io/log-url:https://console-openshift-console.apps.rosa.kx-22069ddb59.54x8.p3.openshiftapps.com/k8s/ns/stat-rep-mfzr/tekton.dev~v1~PipelineRun/test-component-pac-vbaajp-on-pull-request-5qrf7 pac.test.appstudio.openshift.io/max-keep-runs:3 pac.test.appstudio.openshift.io/on-cel-expression:event == &#34;pull_request&#34; &amp;&amp; target_branch == &#34;base-zjzddq&#34; pac.test.appstudio.openshift.io/original-prname:test-component-pac-vbaajp-on-pull-request pac.test.appstudio.openshift.io/pull-request:9652 pac.test.appstudio.openshift.io/repo-url:https://github.com/redhat-appstudio-qe/konflux-test-integration-status-report pac.test.appstudio.openshift.io/repository:test-component-pac-vbaajp pac.test.appstudio.openshift.io/scm-reporting-plr-started:true pac.test.appstudio.openshift.io/sender:rhtap-qe-app[bot] pac.test.appstudio.openshift.io/sha:3836f29e9038ff422e332a23f3fa6c74bc2a02d3 pac.test.appstudio.openshift.io/sha-title:RHTAP-Qe-App update test-component-pac-vbaajp pac.test.appstudio.openshift.io/sha-url:https://github.com/redhat-appstudio-qe/konflux-test-integration-status-report/commit/3836f29e9038ff422e332a23f3fa6c74bc2a02d3 pac.test.appstudio.openshift.io/source-branch:konflux-test-component-pac-vbaajp pac.test.appstudio.openshift.io/source-repo-url:https://github.com/redhat-appstudio-qe/konflux-test-integration-status-report pac.test.appstudio.openshift.io/state:queued pac.test.appstudio.openshift.io/url-org:redhat-appstudio-qe pac.test.appstudio.openshift.io/url-repository:konflux-test-integration-status-report test.appstudio.openshift.io/create-groupsnapshot-status:The number 0 of component snapshots belonging to this pr group hash f9ef3e6680e9d72a644420338f2a59e522ee55ede3f231fc3827b75bf0e133 is less than 2, skipping group snapshot creation test.appstudio.openshift.io/git-reporter-status:{&#34;scenarios&#34;:{&#34;my-integration-test-gpkg-integ-app-fujj-20260509-025735-000&#34;:{&#34;lastUpdateTime&#34;:&#34;2026-05-09T03:08:34.754183007Z&#34;},&#34;my-integration-test-mmqo-integ-app-fujj-20260509-025735-000&#34;:{&#34;lastUpdateTime&#34;:&#34;2026-05-09T03:08:34.046752641Z&#34;},&#34;my-integration-test-nart-integ-app-fujj-20260509-025735-000&#34;:{&#34;lastUpdateTime&#34;:&#34;2026-05-09T03:08:36.893868567Z&#34;},&#34;my-integration-test-uzgn-integ-app-fujj-20260509-025735-000&#34;:{&#34;lastUpdateTime&#34;:&#34;2026-05-09T03:08:36.814769687Z&#34;}}} test.appstudio.openshift.io/integration-workflow:pull-request test.appstudio.openshift.io/pipelinerunstarttime:1778295455000 test.appstudio.openshift.io/pr-group:konflux-test-component-pac-vbaajp test.appstudio.openshift.io/pr-status:merged test.appstudio.openshift.io/snapshot-creation-report:SnapshotCreationFailed test.appstudio.openshift.io/source-repo-url:https://github.com/redhat-appstudio-qe/konflux-test-integration-status-report test.appstudio.openshift.io/status:[{&#34;completionTime&#34;:&#34;2026-05-09T03:08:34.046752641Z&#34;,&#34;details&#34;:&#34;Integration test failed&#34;,&#34;lastUpdateTime&#34;:&#34;2026-05-09T03:09:07Z&#34;,&#34;scenario&#34;:&#34;my-integration-test-mmqo&#34;,&#34;startTime&#34;:&#34;2026-05-09T03:08:21.48090814Z&#34;,&#34;status&#34;:&#34;TestFail&#34;,&#34;testPipelineRunName&#34;:&#34;my-integration-test-mmqo-6sgqc&#34;},{&#34;completionTime&#34;:&#34;2026-05-09T03:08:36.893868567Z&#34;,&#34;details&#34;:&#34;Integration test failed&#34;,&#34;isOptionalScenario&#34;:true,&#34;lastUpdateTime&#34;:&#34;2026-05-09T03:08:36.893868567Z&#34;,&#34;scenario&#34;:&#34;my-integration-test-nart&#34;,&#34;startTime&#34;:&#34;2026-05-09T03:08:21.634653003Z&#34;,&#34;status&#34;:&#34;TestFail&#34;,&#34;testPipelineRunName&#34;:&#34;my-integration-test-nart-6bkff&#34;},{&#34;completionTime&#34;:&#34;2026-05-09T03:08:36.814769687Z&#34;,&#34;details&#34;:&#34;Integration test passed with warnings&#34;,&#34;lastUpdateTime&#34;:&#34;2026-05-09T03:08:36.814769687Z&#34;,&#34;scenario&#34;:&#34;my-integration-test-uzgn&#34;,&#34;startTime&#34;:&#34;2026-05-09T03:08:21.820061092Z&#34;,&#34;status&#34;:&#34;BuildPLRInProgress&#34;,&#34;testPipelineRunName&#34;:&#34;my-integration-test-uzgn-zzbmb&#34;},{&#34;completionTime&#34;:&#34;2026-05-09T03:08:34.754183007Z&#34;,&#34;details&#34;:&#34;Integration test passed&#34;,&#34;lastUpdateTime&#34;:&#34;2026-05-09T03:08:34.754183007Z&#34;,&#34;scenario&#34;:&#34;my-integration-test-gpkg&#34;,&#34;startTime&#34;:&#34;2026-05-09T03:08:21.402638Z&#34;,&#34;status&#34;:&#34;TestPassed&#34;,&#34;testPipelineRunName&#34;:&#34;my-integration-test-gpkg-fljk7&#34;}]]&#xA;&lt; Exit [It] should set the git-reporting-failure annotation correctly - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:308 @ 05/09/26 03:09:27.473 (20.05s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:09:27.473&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:09:27.473 (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="9.082769378">
              <system-err>&gt; Enter [It] build pipelinerun is created but fails - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:355 @ 05/09/26 03:09:27.473&#xA;Waiting for pipeline &#34;failing-build-plr-tgzn&#34; to finish&#xA;&lt; Exit [It] build pipelinerun is created but fails - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:355 @ 05/09/26 03:09:36.556 (9.082s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:09:36.556&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:09:36.556 (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="4.2118162120000004">
              <system-err>&gt; Enter [It] build pipelinerun failure is reported to integration test checkRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:400 @ 05/09/26 03:09:36.557&#xA;&lt; Exit [It] build pipelinerun failure is reported to integration test checkRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:400 @ 05/09/26 03:09:36.886 (330ms)&#xA;&gt; Enter [AfterAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:94 @ 05/09/26 03:09:36.887&#xA;&lt; Exit [AfterAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:94 @ 05/09/26 03:09:40.768 (3.881s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:09:40.768&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 05/09/26 03:09:40.768 (0s)&#xA;</system-err>
          </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="passed" time="48.121237988">
              <system-err>&gt; Enter [BeforeAll] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:32 @ 05/09/26 02:56:33.118&#xA;&lt; Exit [BeforeAll] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:32 @ 05/09/26 02:57:21.034 (47.916s)&#xA;&gt; Enter [It] verifies that the ReleasePlan CR is unmatched in the beginning - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:57 @ 05/09/26 02:57:21.034&#xA;&lt; Exit [It] verifies that the ReleasePlan CR is unmatched in the beginning - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:57 @ 05/09/26 02:57:21.237 (203ms)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:21.238&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:21.238 (0s)&#xA;</system-err>
          </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="passed" time="0.255830466">
              <system-err>&gt; Enter [It] Creates ReleasePlanAdmission CR in corresponding managed namespace - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:72 @ 05/09/26 02:57:21.238&#xA;&lt; Exit [It] Creates ReleasePlanAdmission CR in corresponding managed namespace - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:72 @ 05/09/26 02:57:21.494 (256ms)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:21.494&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:21.494 (0s)&#xA;</system-err>
          </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="passed" time="0.277118028">
              <system-err>&gt; Enter [It] verifies that the ReleasePlan CR is set to matched - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:85 @ 05/09/26 02:57:21.494&#xA;&lt; Exit [It] verifies that the ReleasePlan CR is set to matched - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:85 @ 05/09/26 02:57:21.771 (277ms)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:21.771&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:21.771 (0s)&#xA;</system-err>
          </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="passed" time="0.098828576">
              <system-err>&gt; Enter [It] verifies that the ReleasePlanAdmission CR is set to matched - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:105 @ 05/09/26 02:57:21.772&#xA;&lt; Exit [It] verifies that the ReleasePlanAdmission CR is set to matched - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:105 @ 05/09/26 02:57:21.871 (98ms)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:21.871&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:21.871 (0s)&#xA;</system-err>
          </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="passed" time="0.19793697">
              <system-err>&gt; Enter [It] Creates a manual release ReleasePlan CR in devNamespace - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:123 @ 05/09/26 02:57:21.871&#xA;&lt; Exit [It] Creates a manual release ReleasePlan CR in devNamespace - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:123 @ 05/09/26 02:57:22.069 (197ms)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:22.069&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:22.069 (0s)&#xA;</system-err>
          </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="passed" time="0.232325384">
              <system-err>&gt; Enter [It] verifies that the second ReleasePlan CR is set to matched - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:129 @ 05/09/26 02:57:22.07&#xA;&lt; Exit [It] verifies that the second ReleasePlan CR is set to matched - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:129 @ 05/09/26 02:57:22.302 (232ms)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:22.302&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:22.302 (0s)&#xA;</system-err>
          </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="passed" time="0.053252311">
              <system-err>&gt; Enter [It] verifies that the ReleasePlanAdmission CR has two matched ReleasePlan CRs - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:150 @ 05/09/26 02:57:22.303&#xA;&lt; Exit [It] verifies that the ReleasePlanAdmission CR has two matched ReleasePlan CRs - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:150 @ 05/09/26 02:57:22.356 (53ms)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:22.356&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:22.356 (0s)&#xA;</system-err>
          </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="passed" time="0.05175594">
              <system-err>&gt; Enter [It] deletes one ReleasePlan CR - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:171 @ 05/09/26 02:57:22.356&#xA;&lt; Exit [It] deletes one ReleasePlan CR - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:171 @ 05/09/26 02:57:22.408 (51ms)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:22.408&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:22.408 (0s)&#xA;</system-err>
          </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="passed" time="0.189878344">
              <system-err>&gt; Enter [It] verifies that the ReleasePlanAdmission CR has only one matching ReleasePlan - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:177 @ 05/09/26 02:57:22.409&#xA;&lt; Exit [It] verifies that the ReleasePlanAdmission CR has only one matching ReleasePlan - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:177 @ 05/09/26 02:57:22.598 (189ms)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:22.598&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:22.598 (0s)&#xA;</system-err>
          </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="passed" time="0.032084542">
              <system-err>&gt; Enter [It] deletes the ReleasePlanAdmission CR - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:198 @ 05/09/26 02:57:22.599&#xA;&lt; Exit [It] deletes the ReleasePlanAdmission CR - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:198 @ 05/09/26 02:57:22.631 (32ms)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:22.631&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:22.631 (0s)&#xA;</system-err>
          </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="passed" time="21.537312846">
              <system-err>&gt; Enter [It] verifies that the ReleasePlan CR has no matched ReleasePlanAdmission - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:204 @ 05/09/26 02:57:22.632&#xA;&lt; Exit [It] verifies that the ReleasePlan CR has no matched ReleasePlanAdmission - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:204 @ 05/09/26 02:57:22.965 (334ms)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:22.966&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:30 @ 05/09/26 02:57:22.966 (0s)&#xA;&gt; Enter [AfterAll] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:48 @ 05/09/26 02:57:22.966&#xA;&lt; Exit [AfterAll] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.CNj1aJY7Z5/tests/release/service/release_plan_and_admission_matched.go:48 @ 05/09/26 02:57:44.169 (21.203s)&#xA;</system-err>
          </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] [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-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] [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="passed" time="2.58788107">
              <system-err>&gt; Enter [BeforeAll] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:31 @ 05/09/26 02:57:44.174&#xA;&lt; Exit [BeforeAll] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:31 @ 05/09/26 02:57:46.744 (2.57s)&#xA;&gt; Enter [It] verifies if the chains controller is running - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:43 @ 05/09/26 02:57:46.745&#xA;&lt; Exit [It] verifies if the chains controller is running - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:43 @ 05/09/26 02:57:46.762 (17ms)&#xA;&gt; Enter [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 02:57:46.762&#xA;&lt; Exit [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 02:57:46.762 (0s)&#xA;</system-err>
          </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="passed" time="0.005656594">
              <system-err>&gt; Enter [It] verifies the signing secret is present - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:48 @ 05/09/26 02:57:46.763&#xA;&lt; Exit [It] verifies the signing secret is present - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:48 @ 05/09/26 02:57:46.768 (5ms)&#xA;&gt; Enter [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 02:57:46.768&#xA;&lt; Exit [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 02:57:46.768 (0s)&#xA;</system-err>
          </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="passed" time="261.903822126">
              <system-err>&gt; Enter [BeforeAll] test creating and signing an image and task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:73 @ 05/09/26 02:57:46.769&#xA;Creating Pipeline &#34;buildah-demo-pufrqqgxeq&#34;&#xA;Waiting for pipeline &#34;buildah-demo-pufrqqgxeq&#34; to finish&#xA;The pipeline named &#34;buildah-demo-pufrqqgxeq&#34; in namespace &#34;chains-e2e-vgkz&#34; succeeded&#xA;The image signed by Tekton Chains is quay.io/redhat-appstudio-qe/test-images:buildah-demo-pufrqqgxeq@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#xA;&lt; Exit [BeforeAll] test creating and signing an image and task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:73 @ 05/09/26 03:02:07.087 (4m20.318s)&#xA;&gt; Enter [It] creates signature and attestation - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:115 @ 05/09/26 03:02:07.087&#xA;failed to get cosign result for image quay.io/redhat-appstudio-qe/test-images:buildah-demo-pufrqqgxeq@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2: failed to find cosign results for image quay.io/redhat-appstudio-qe/test-images:buildah-demo-pufrqqgxeq@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2: error when getting attestation tag: cannot get manifest digest from quay.io/redhat-appstudio-qe/test-images:sha256-918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2.att image. response body: {&#34;tags&#34;: [], &#34;page&#34;: 1, &#34;has_additional&#34;: false}&#xA;&#xA;&#xA;Cosign verify pass with .att and .sig ImageStreamTags found for quay.io/redhat-appstudio-qe/test-images:buildah-demo-pufrqqgxeq@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#xA;&lt; Exit [It] creates signature and attestation - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:115 @ 05/09/26 03:02:08.672 (1.585s)&#xA;&gt; Enter [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 03:02:08.673&#xA;&lt; Exit [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 03:02:08.673 (0s)&#xA;</system-err>
          </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="passed" time="341.765543265">
              <system-err>&gt; Enter [BeforeAll] verify-enterprise-contract task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:133 @ 05/09/26 03:02:08.673&#xA;Copy public key from openshift-pipelines/signing-secrets to a new secret&#xA;Configured Rekor host: https://rekor.sigstore.dev&#xA;Using verify EC task bundle: quay.io/conforma/tekton-task:kf-b345847182602d9a5ce9e957fa76fe02575c8018@sha256:7df8d121c09999d0376e189c1eb8a8263078aab697aa5ee966512f581427a6ce&#xA;&lt; Exit [BeforeAll] verify-enterprise-contract task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:133 @ 05/09/26 03:02:08.937 (264ms)&#xA;&gt; Enter [BeforeEach] verify-enterprise-contract task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:154 @ 05/09/26 03:02:08.937&#xA;&lt; Exit [BeforeEach] verify-enterprise-contract task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:154 @ 05/09/26 03:02:09.074 (137ms)&#xA;&gt; Enter [It] succeeds when policy is met - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:177 @ 05/09/26 03:02:09.075&#xA;Creating Pipeline &#34;verify-enterprise-contract-run-s7btr&#34;&#xA;Waiting for pipeline &#34;verify-enterprise-contract-run-s7btr&#34; to finish&#xA;*** TaskRun status:&#xA;artifacts: {}&#xA;completionTime: &#34;2026-05-09T03:07:49Z&#34;&#xA;conditions:&#xA;- lastTransitionTime: &#34;2026-05-09T03:07:49Z&#34;&#xA;  message: All Steps have completed executing&#xA;  reason: Succeeded&#xA;  status: &#34;True&#34;&#xA;  type: Succeeded&#xA;podName: verify-enterprise-contract-194cdbe0e4357557192e6db5b8f63e98-pod&#xA;provenance:&#xA;  featureFlags:&#xA;    awaitSidecarReadiness: true&#xA;    coschedule: workspaces&#xA;    enableAPIFields: alpha&#xA;    enableParamEnum: true&#xA;    enableProvenanceInStatus: true&#xA;    enforceNonfalsifiability: none&#xA;    maxResultSize: 4096&#xA;    resultExtractionMethod: termination-message&#xA;    runningInEnvWithInjectedSidecars: true&#xA;    verificationNoMatchPolicy: ignore&#xA;  refSource:&#xA;    digest:&#xA;      sha256: 7df8d121c09999d0376e189c1eb8a8263078aab697aa5ee966512f581427a6ce&#xA;    entryPoint: verify-enterprise-contract&#xA;    uri: quay.io/conforma/tekton-task&#xA;results:&#xA;- name: TEST_OUTPUT&#xA;  type: string&#xA;  value: |&#xA;    {&#34;timestamp&#34;:&#34;1778296067&#34;,&#34;namespace&#34;:&#34;&#34;,&#34;successes&#34;:5,&#34;failures&#34;:0,&#34;warnings&#34;:0,&#34;result&#34;:&#34;SUCCESS&#34;}&#xA;spanContext:&#xA;  traceparent: 00-951d4505d91dd2d4498ab0b80f023b27-949cd3b72b76755c-01&#xA;startTime: &#34;2026-05-09T03:02:10Z&#34;&#xA;steps:&#xA;- container: step-initialize-tuf&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: initialize-tuf&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://ee9ef4437d220da47861c7c1b4e0bd86681db912afb0b2fe6a567b800d2cdda3&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:07:43Z&#34;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:07:40Z&#34;&#xA;  terminationReason: Skipped&#xA;- container: step-reduce&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: reduce&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://125b6641f4a7848fe346c7b43edf45856cb8ce85b33e5d98faa71c0ce08be874&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:07:43Z&#34;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:07:41Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-validate&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: validate&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://6766d2beef3cef6b1770263cdd88eb67516a086a1d7a1a4111687b5dc54ac7ef&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:07:47Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296067\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:0,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;SUCCESS\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:07:41Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-report-json&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: report-json&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://1078414e703e05f49fc7625c241347443aec59cca2901b6e69a0755953082227&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:07:48Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296067\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:0,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;SUCCESS\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:07:48Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-summary&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: summary&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://6fc2ff582d5cdef54f163c7a17cefd8a869eb984fa5df06421430c8756649a3e&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:07:48Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296067\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:0,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;SUCCESS\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:07:48Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-version&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: version&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://d67793f4c5a0f4092b293d9f385121064b34d01d02ae54b38de55a06c3288aae&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:07:48Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296067\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:0,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;SUCCESS\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:07:48Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-show-config&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: show-config&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://7623ae0d6d36eb786a0180b8e89b2cb424ccbc4c938cb05c92890896a3bd6346&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:07:48Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296067\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:0,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;SUCCESS\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:07:48Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-detailed-report&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: detailed-report&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://9f264fbdfcf48f898b88eb4f4c5d214e17b848c9bf02cdfed88c90a8b65ae10c&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:07:48Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296067\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:0,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;SUCCESS\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:07:48Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-assert&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: assert&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://73000c668bb5b29530f435ffe657f642c9b74f8b0b8d76afd7091a7faf597b71&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:07:48Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296067\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:0,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;SUCCESS\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:07:48Z&#34;&#xA;  terminationReason: Completed&#xA;taskSpec:&#xA;  description: Verify the enterprise contract is met&#xA;  params:&#xA;  - description: |&#xA;      Spec section of an ApplicationSnapshot resource. Not all fields of the&#xA;      resource are required. A minimal example:&#xA;&#xA;      ```json&#xA;        {&#xA;          &#34;components&#34;: [&#xA;            {&#xA;              &#34;containerImage&#34;: &#34;quay.io/example/repo:latest&#34;&#xA;            }&#xA;          ]&#xA;        }&#xA;      ```&#xA;&#xA;      Each `containerImage` in the `components` array is validated.&#xA;    name: IMAGES&#xA;    type: string&#xA;  - default: enterprise-contract-service/default&#xA;    description: |&#xA;      Name of the policy configuration (EnterpriseContractPolicy&#xA;      resource) to use. `namespace/name` or `name` syntax supported. If&#xA;      namespace is omitted the namespace where the task runs is used.&#xA;      You can also specify a policy configuration using a git url, e.g.&#xA;      `github.com/conforma/config//slsa3`.&#xA;    name: POLICY_CONFIGURATION&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Public key used to verify traditional long-lived signatures. Must&#xA;      be a valid k8s cosign reference, e.g. k8s://my-space/my-secret where my-secret&#xA;      contains the expected cosign.pub attribute. Required for traditional signing&#xA;      key verification. Will be ignored if any of CERTIFICATE_IDENTITY, CERTIFICATE_IDENTITY_REGEXP,&#xA;      CERTIFICATE_OIDC_ISSUER, or CERTIFICATE_OIDC_ISSUER_REGEXP are provided.&#xA;    name: PUBLIC_KEY&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Rekor host for transparency log lookups&#xA;    name: REKOR_HOST&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Expected identity in the signing certificate for keyless verification.&#xA;      This should be the email or URI that was used when signing. You should provide&#xA;      both CERTIFICATE_OIDC_ISSUER and CERTIFICATE_IDENTITY for keyless verification.&#xA;      The PUBLIC_KEY param will be ignored if this is provided.&#xA;    name: CERTIFICATE_IDENTITY&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Expected OIDC issuer in the signing certificate for keyless verification.&#xA;      This should match the issuer that provided the identity token used for signing.&#xA;      You should provide both CERTIFICATE_OIDC_ISSUER and CERTIFICATE_IDENTITY for&#xA;      keyless verification. The PUBLIC_KEY param will be ignored if this is provided.&#xA;    name: CERTIFICATE_OIDC_ISSUER&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Similar to CERTIFICATE_IDENTITY but the value is a regexp that will&#xA;      be matched. Note that CERTIFICATE_IDENTITY takes precedence over this if both&#xA;      are present.&#xA;    name: CERTIFICATE_IDENTITY_REGEXP&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Similar to CERTIFICATE_OIDC_ISSUER but a regexp that will be matched.&#xA;      Note that CERTIFICATE_OIDC_ISSUER takes precedence over this if both are present.&#xA;    name: CERTIFICATE_OIDC_ISSUER_REGEXP&#xA;    type: string&#xA;  - default: &#34;false&#34;&#xA;    description: Skip Rekor transparency log checks during validation. Compatible&#xA;      with traditional signing secret signature checks only. If any of the CERTIFICATE_*&#xA;      keyless verification params are present, this value is disregarded and Rekor&#xA;      transparency log checks are included.&#xA;    name: IGNORE_REKOR&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: TUF mirror URL. Provide a value when NOT using public sigstore deployment.&#xA;    name: TUF_MIRROR&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: |&#xA;      Path to a directory containing SSL certs to be used when communicating&#xA;      with external services. This is useful when using the integrated registry&#xA;      and a local instance of Rekor on a development cluster which may use&#xA;      certificates issued by a not-commonly trusted root CA. In such cases,&#xA;      `/var/run/secrets/kubernetes.io/serviceaccount` is a good value. Multiple&#xA;      paths can be provided by using the `:` separator.&#xA;    name: SSL_CERT_DIR&#xA;    type: string&#xA;  - default: trusted-ca&#xA;    description: The name of the ConfigMap to read CA bundle data from.&#xA;    name: CA_TRUST_CONFIGMAP_NAME&#xA;    type: string&#xA;  - default: ca-bundle.crt&#xA;    description: The name of the key in the ConfigMap that contains the CA bundle&#xA;      data.&#xA;    name: CA_TRUST_CONFIG_MAP_KEY&#xA;    type: string&#xA;  - default: &#34;true&#34;&#xA;    description: Include rule titles and descriptions in the output. Set to `&#34;false&#34;`&#xA;      to disable it.&#xA;    name: INFO&#xA;    type: string&#xA;  - default: &#34;true&#34;&#xA;    description: Fail the task if policy fails. Set to `&#34;false&#34;` to disable it.&#xA;    name: STRICT&#xA;    type: string&#xA;  - default: /tekton/home&#xA;    description: Value for the HOME environment variable.&#xA;    name: HOMEDIR&#xA;    type: string&#xA;  - default: now&#xA;    description: Run policy checks with the provided time.&#xA;    name: EFFECTIVE_TIME&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Merge additional Rego variables into the policy data. Use syntax&#xA;      &#34;key=value,key2=value2...&#34;&#xA;    name: EXTRA_RULE_DATA&#xA;    type: string&#xA;  - default: &#34;1&#34;&#xA;    description: Number of parallel workers to use for policy evaluation.&#xA;    name: WORKERS&#xA;    type: string&#xA;  - default: &#34;false&#34;&#xA;    description: Reduce the Snapshot to only the component whose build caused the&#xA;      Snapshot to be created&#xA;    name: SINGLE_COMPONENT&#xA;    type: string&#xA;  - default: unknown&#xA;    description: |&#xA;      Name, including kind, of the Kubernetes resource to query for labels when single component mode is enabled, e.g. pr/somepipeline.&#xA;    name: SINGLE_COMPONENT_CUSTOM_RESOURCE&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: |&#xA;      Kubernetes namespace where the SINGLE_COMPONENT_NAME is found. Only used when single component mode is enabled.&#xA;    name: SINGLE_COMPONENT_CUSTOM_RESOURCE_NS&#xA;    type: string&#xA;  - default: 1s&#xA;    description: Base duration for exponential backoff calculation (e.g., &#34;1s&#34;, &#34;500ms&#34;)&#xA;    name: RETRY_DURATION&#xA;    type: string&#xA;  - default: &#34;2.0&#34;&#xA;    description: Exponential backoff multiplier (e.g., &#34;2.0&#34;, &#34;1.5&#34;)&#xA;    name: RETRY_FACTOR&#xA;    type: string&#xA;  - default: &#34;0.1&#34;&#xA;    description: Randomness factor for backoff calculation (0.0-1.0, e.g., &#34;0.1&#34;,&#xA;      &#34;0.2&#34;)&#xA;    name: RETRY_JITTER&#xA;    type: string&#xA;  - default: &#34;3&#34;&#xA;    description: Maximum number of retry attempts&#xA;    name: RETRY_MAX_RETRY&#xA;    type: string&#xA;  - default: 3s&#xA;    description: Maximum wait time between retries (e.g., &#34;3s&#34;, &#34;10s&#34;)&#xA;    name: RETRY_MAX_WAIT&#xA;    type: string&#xA;  results:&#xA;  - description: Short summary of the policy evaluation for each image&#xA;    name: TEST_OUTPUT&#xA;    type: string&#xA;  stepTemplate:&#xA;    computeResources: {}&#xA;    env:&#xA;    - name: HOME&#xA;      value: /tekton/home&#xA;  steps:&#xA;  - args:&#xA;    - sigstore&#xA;    - initialize&#xA;    - --mirror&#xA;    - &#34;&#34;&#xA;    - --root&#xA;    - /root.json&#xA;    command:&#xA;    - ec&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: initialize-tuf&#xA;    when:&#xA;    - operator: notin&#xA;      values:&#xA;      - &#34;&#34;&#xA;  - command:&#xA;    - reduce-snapshot.sh&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    env:&#xA;    - name: SNAPSHOT&#xA;      value: &#39;{&#34;application&#34;:&#34;&#34;,&#34;componentGroup&#34;:&#34;&#34;,&#34;components&#34;:[{&#34;name&#34;:&#34;&#34;,&#34;version&#34;:&#34;&#34;,&#34;containerImage&#34;:&#34;quay.io/redhat-appstudio-qe/test-images:buildah-demo-pufrqqgxeq@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#34;,&#34;source&#34;:{}}],&#34;artifacts&#34;:{}}&#39;&#xA;    - name: SINGLE_COMPONENT&#xA;      value: &#34;false&#34;&#xA;    - name: CUSTOM_RESOURCE&#xA;      value: unknown&#xA;    - name: CUSTOM_RESOURCE_NAMESPACE&#xA;    - name: SNAPSHOT_PATH&#xA;      value: /tekton/home/snapshot.json&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: reduce&#xA;    onError: continue&#xA;  - computeResources:&#xA;      limits:&#xA;        memory: 2Gi&#xA;      requests:&#xA;        cpu: 1800m&#xA;        memory: 2Gi&#xA;    env:&#xA;    - name: POLICY_CONFIGURATION&#xA;      value: ec-policy&#xA;    - name: PUBLIC_KEY&#xA;      value: k8s://chains-e2e-vgkz/cosign-public-key&#xA;    - name: CERTIFICATE_IDENTITY&#xA;    - name: CERTIFICATE_OIDC_ISSUER&#xA;    - name: CERTIFICATE_IDENTITY_REGEXP&#xA;    - name: CERTIFICATE_OIDC_ISSUER_REGEXP&#xA;    - name: REKOR_HOST&#xA;    - name: IGNORE_REKOR&#xA;      value: &#34;true&#34;&#xA;    - name: WORKERS&#xA;      value: &#34;1&#34;&#xA;    - name: INFO&#xA;      value: &#34;true&#34;&#xA;    - name: EFFECTIVE_TIME&#xA;      value: now&#xA;    - name: EXTRA_RULE_DATA&#xA;    - name: RETRY_MAX_WAIT&#xA;      value: 3s&#xA;    - name: RETRY_MAX_RETRY&#xA;      value: &#34;3&#34;&#xA;    - name: RETRY_DURATION&#xA;      value: 1s&#xA;    - name: RETRY_FACTOR&#xA;      value: &#34;2.0&#34;&#xA;    - name: RETRY_JITTER&#xA;      value: &#34;0.1&#34;&#xA;    - name: HOMEDIR&#xA;      value: /tekton/home&#xA;    - name: SSL_CERT_DIR&#xA;      value: /tekton-custom-certs:/etc/ssl/certs:/etc/pki/tls/certs:/system/etc/security/cacerts:/var/run/secrets/kubernetes.io/serviceaccount&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: validate&#xA;    onError: continue&#xA;    script: |&#xA;      #!/bin/bash&#xA;      set -euo pipefail&#xA;&#xA;      cmd_args=(&#xA;        validate&#xA;        image&#xA;        --images=&#34;${HOMEDIR}/snapshot.json&#34;&#xA;        --policy=&#34;${POLICY_CONFIGURATION}&#34;&#xA;      )&#xA;&#xA;      # To keep bash logic as thin as possible we deliberately don&#39;t sanitize&#xA;      # these params. If something is wrong or missing let Conforma handle it.&#xA;&#xA;      if [ -n &#34;${CERTIFICATE_IDENTITY}&#34; ] || \&#xA;         [ -n &#34;${CERTIFICATE_OIDC_ISSUER}&#34; ] || \&#xA;         [ -n &#34;${CERTIFICATE_IDENTITY_REGEXP}&#34; ] || \&#xA;         [ -n &#34;${CERTIFICATE_OIDC_ISSUER_REGEXP}&#34; ]; then&#xA;        # If *any* of the above are non-empty assume the intention is to&#xA;        # try keyless verification&#xA;&#xA;        if [ -n &#34;${CERTIFICATE_IDENTITY}&#34; ]; then&#xA;          cmd_args+=(&#xA;            --certificate-identity=&#34;${CERTIFICATE_IDENTITY}&#34;&#xA;          )&#xA;        elif [ -n &#34;${CERTIFICATE_IDENTITY_REGEXP}&#34; ]; then&#xA;          cmd_args+=(&#xA;            --certificate-identity-regexp=&#34;${CERTIFICATE_IDENTITY_REGEXP}&#34;&#xA;          )&#xA;        fi&#xA;&#xA;        if [ -n &#34;${CERTIFICATE_OIDC_ISSUER}&#34; ]; then&#xA;          cmd_args+=(&#xA;            --certificate-oidc-issuer=&#34;${CERTIFICATE_OIDC_ISSUER}&#34;&#xA;          )&#xA;        elif [ -n &#34;${CERTIFICATE_OIDC_ISSUER_REGEXP}&#34; ]; then&#xA;          cmd_args+=(&#xA;            --certificate-oidc-issuer-regexp=&#34;${CERTIFICATE_OIDC_ISSUER_REGEXP}&#34;&#xA;          )&#xA;        fi&#xA;&#xA;        # Force --ignore-rekor to false since we need rekor&#xA;        cmd_args+=(&#xA;          --ignore-rekor=false&#xA;        )&#xA;      else&#xA;        # Assume traditional signing secret verification&#xA;        cmd_args+=(&#xA;          --public-key=&#34;${PUBLIC_KEY}&#34;&#xA;          --ignore-rekor=&#34;${IGNORE_REKOR}&#34;&#xA;        )&#xA;      fi&#xA;&#xA;      cmd_args+=(&#xA;        --rekor-url=&#34;${REKOR_HOST}&#34;&#xA;        --workers=&#34;${WORKERS}&#34;&#xA;        --info=&#34;${INFO}&#34;&#xA;        --timeout=0&#xA;        --strict=false&#xA;        --show-successes=true&#xA;        --show-policy-docs-link=true&#xA;        --effective-time=&#34;${EFFECTIVE_TIME}&#34;&#xA;        --extra-rule-data=&#34;${EXTRA_RULE_DATA}&#34;&#xA;        --retry-max-wait=&#34;${RETRY_MAX_WAIT}&#34;&#xA;        --retry-max-retry=&#34;${RETRY_MAX_RETRY}&#34;&#xA;        --retry-duration=&#34;${RETRY_DURATION}&#34;&#xA;        --retry-factor=&#34;${RETRY_FACTOR}&#34;&#xA;        --retry-jitter=&#34;${RETRY_JITTER}&#34;&#xA;        --output=&#34;text=${HOMEDIR}/text-report.txt?show-successes=false&#34;&#xA;        --output=&#34;json=${HOMEDIR}/report-json.json&#34;&#xA;        --output=&#34;appstudio=/tekton/results/TEST_OUTPUT&#34;&#xA;      )&#xA;&#xA;&#xA;      # Execute Conforma with constructed arguments&#xA;      exec ec &#34;${cmd_args[@]}&#34;&#xA;    volumeMounts:&#xA;    - mountPath: /etc/pki/tls/certs/ca-custom-bundle.crt&#xA;      name: trusted-ca&#xA;      readOnly: true&#xA;      subPath: ca-bundle.crt&#xA;  - args:&#xA;    - jq . /tekton/home/report-json.json | awk &#39;{gsub(/^ +/, &#34;&#34;); acc += length; if&#xA;      (acc &gt;= 8000) { printf &#34;\n&#34;; acc=length } printf $0 }&#39;&#xA;    command:&#xA;    - sh&#xA;    - -c&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: report-json&#xA;    onError: continue&#xA;  - args:&#xA;    - .&#xA;    - /tekton/results/TEST_OUTPUT&#xA;    command:&#xA;    - jq&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: summary&#xA;    onError: continue&#xA;  - args:&#xA;    - version&#xA;    command:&#xA;    - ec&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: version&#xA;  - args:&#xA;    - &#39;{policy: .policy, key: .key, &#34;effective-time&#34;: .[&#34;effective-time&#34;]}&#39;&#xA;    - /tekton/home/report-json.json&#xA;    command:&#xA;    - jq&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: show-config&#xA;  - args:&#xA;    - /tekton/home/text-report.txt&#xA;    command:&#xA;    - cat&#xA;    computeResources: {}&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: detailed-report&#xA;    onError: continue&#xA;  - args:&#xA;    - --argjson&#xA;    - strict&#xA;    - &#34;true&#34;&#xA;    - -e&#xA;    - |&#xA;      .result == &#34;SUCCESS&#34; or .result == &#34;WARNING&#34; or ($strict | not)&#xA;    - /tekton/results/TEST_OUTPUT&#xA;    command:&#xA;    - jq&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: assert&#xA;  volumes:&#xA;  - configMap:&#xA;      items:&#xA;      - key: ca-bundle.crt&#xA;        path: ca-bundle.crt&#xA;      name: trusted-ca&#xA;      optional: true&#xA;    name: trusted-ca&#xA;  workspaces:&#xA;  - description: The workspace where the snapshot spec json file resides&#xA;    name: data&#xA;    optional: true&#xA;&#xA;*** Logs from pod &#39;verify-enterprise-contract-194cdbe0e4357557192e6db5b8f63e98-pod&#39;, container &#39;step-initialize-tuf&#39;:&#xA;----- START -----2026/05/09 03:07:40 INFO Step was skipped due to when expressions were evaluated to false.&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-194cdbe0e4357557192e6db5b8f63e98-pod&#39;, container &#39;step-reduce&#39;:&#xA;----- START -----Single Component mode? false&#xA;{&#xA;  &#34;application&#34;: &#34;&#34;,&#xA;  &#34;componentGroup&#34;: &#34;&#34;,&#xA;  &#34;components&#34;: [&#xA;    {&#xA;      &#34;name&#34;: &#34;&#34;,&#xA;      &#34;version&#34;: &#34;&#34;,&#xA;      &#34;containerImage&#34;: &#34;quay.io/redhat-appstudio-qe/test-images:buildah-demo-pufrqqgxeq@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#34;,&#xA;      &#34;source&#34;: {}&#xA;    }&#xA;  ],&#xA;  &#34;artifacts&#34;: {}&#xA;}&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-194cdbe0e4357557192e6db5b8f63e98-pod&#39;, container &#39;step-validate&#39;:&#xA;----- START ---------- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-194cdbe0e4357557192e6db5b8f63e98-pod&#39;, container &#39;step-report-json&#39;:&#xA;----- START -----{&#34;success&#34;: true,&#34;components&#34;: [{&#34;name&#34;: &#34;&#34;,&#34;containerImage&#34;: &#34;quay.io/redhat-appstudio-qe/test-images@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#34;,&#34;source&#34;: {},&#34;successes&#34;: [{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.signature_check&#34;,&#34;description&#34;: &#34;The attestation signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Attestation signature check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.syntax_check&#34;,&#34;description&#34;: &#34;The attestation has correct syntax.&#34;,&#34;title&#34;: &#34;Attestation syntax check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.image.signature_check&#34;,&#34;description&#34;: &#34;The image signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Image signature check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_provenance_available.allowed_predicate_types_provided&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;policy_data&#34;],&#34;description&#34;: &#34;Confirm the `allowed_predicate_types` rule data was provided, since it is required by the policy rules in this package.&#34;,&#34;title&#34;: &#34;Allowed predicate types provided&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_provenance_available.attestation_predicate_type_accepted&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the predicateType field of the attestation indicates the in-toto SLSA Provenance format was used to attest the PipelineRun.&#34;,&#34;title&#34;: &#34;Expected attestation predicate type found&#34;}}],&#34;success&#34;: true,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;&#34;,&#34;sig&#34;: &#34;MEYCIQDJfxL39hNiJGAEgBjgePDcytcqSu/duqvEfjGYl/+fvgIhAPC1E38DC+CMmhjpkxepOIYZzC2wkaSkQAONZU1BI1t/&#34;},{&#34;keyid&#34;: &#34;&#34;,&#34;sig&#34;: &#34;MEYCIQD5lUHkAzgo95QzY3djxj7J6J1uJmkzCP0k14PqfB4GcwIhAKm5biMiltqCvYwFGf0maWg7g+KwFnaRAL2jrZeu3s7y&#34;},{&#34;keyid&#34;: &#34;&#34;,&#34;sig&#34;: &#34;MEYCIQCWhOUFFV9/AU6Vu3zZEASbiVPMTbeIcAF8M59OQQaXqgIhAKhV/19siiQfZARh7ad7hqwipKPZCVvzKlHUOqLxAuCl&#34;}],&#34;attestations&#34;: [{&#34;type&#34;: &#34;https://in-toto.io/Statement/v0.1&#34;,&#34;predicateType&#34;: &#34;https://slsa.dev/provenance/v0.2&#34;,&#34;predicateBuildType&#34;: &#34;tekton.dev/v1/PipelineRun&#34;,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;SHA256:ybGxTL8yTILGa7JB0rbOG+ayq66D9nzMrFoav6G5X6c&#34;,&#34;sig&#34;: &#34;MEUCIQDhxLbpagJPRtBHcUYEmg8XPZgIIa6WSSzB7ZJ7DlCEzQIgCrRkUXEpyGTuDNmeV+KL6QI9rH0T4XhUbaodBfDulcs=&#34;}]}]}],&#34;key&#34;: &#34;-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEAm/YE3MeVX+sgrHJZa0N2EIFu31M\nM4vPqV5IXONrtJRnu1NhnewrBCeRqpRvP5EMOZ1SO3nTppSW9eQ/1dJPbQ==\n-----END PUBLIC KEY-----\n&#34;,&#34;policy&#34;: {&#34;name&#34;: &#34;Default&#34;,&#34;description&#34;: &#34;Includes rules for levels 1, 2 &amp; 3 of SLSA v0.1. This is the default config used for new Konflux applications. Source: https://github.com/conforma/config/blob/main/default/policy.yaml&#34;,&#34;sources&#34;: [{&#34;name&#34;: &#34;Default&#34;,&#34;policy&#34;: [&#34;oci::quay.io/enterprise-contract/ec-release-policy:konflux@sha256:59c6b95c02295edb7928ef187571d26d426993fd5aae0236a03c832afbd6072a&#34;],&#34;data&#34;: [&#34;git::github.com/release-engineering/rhtap-ec-policy//data?ref=67018469815ee9f81e47cfb54dae39d71ed5f389&#34;,&#34;oci::quay.io/konflux-ci/tekton-catalog/data-acceptable-bundles:latest@sha256:c75d0123e83efa6c182b6510c35982b48201143ce74a9a388680a0ee1aa4affb&#34;,&#34;oci::quay.io/konflux-ci/konflux-vanguard/data-acceptable-bundles:latest@sha256:0b31c7bc77a7463a1bc52f3d3625ef0e0e75443da7fd2de8005d7885282138ea&#34;,&#34;oci::quay.io/konflux-ci/integration-service-catalog/data-acceptable-bundles:latest@sha256:7b00455045ea3873a72caeb1e7ac7d036bd53963a26409891a4cc9d0d242b9fc&#34;],&#34;config&#34;: {&#34;include&#34;: [&#34;slsa_provenance_available&#34;]}}],&#34;publicKey&#34;: &#34;k8s://chains-e2e-vgkz/cosign-public-key&#34;},&#34;ec-version&#34;: &#34;v0.9.25&#34;,&#34;effective-time&#34;: &#34;2026-05-09T03:07:41.348855993Z&#34;}----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-194cdbe0e4357557192e6db5b8f63e98-pod&#39;, container &#39;step-summary&#39;:&#xA;----- START -----{&#xA;  &#34;timestamp&#34;: &#34;1778296067&#34;,&#xA;  &#34;namespace&#34;: &#34;&#34;,&#xA;  &#34;successes&#34;: 5,&#xA;  &#34;failures&#34;: 0,&#xA;  &#34;warnings&#34;: 0,&#xA;  &#34;result&#34;: &#34;SUCCESS&#34;&#xA;}&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-194cdbe0e4357557192e6db5b8f63e98-pod&#39;, container &#39;step-version&#39;:&#xA;----- START -----Version            v0.9.25&#xA;Source ID          b345847182602d9a5ce9e957fa76fe02575c8018&#xA;Change date        2026-04-27 12:52:43 +0000 UTC (1 week ago)&#xA;ECC                v0.1.7&#xA;OPA                v1.15.2&#xA;Conftest           v0.68.2&#xA;Cosign             v3.0.4&#xA;Sigstore           v1.10.4&#xA;Rekor              v1.5.0&#xA;Tekton Pipeline    v1.9.2&#xA;Kubernetes Client  v0.35.0&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-194cdbe0e4357557192e6db5b8f63e98-pod&#39;, container &#39;step-show-config&#39;:&#xA;----- START -----{&#xA;  &#34;policy&#34;: {&#xA;    &#34;name&#34;: &#34;Default&#34;,&#xA;    &#34;description&#34;: &#34;Includes rules for levels 1, 2 &amp; 3 of SLSA v0.1. This is the default config used for new Konflux applications. Source: https://github.com/conforma/config/blob/main/default/policy.yaml&#34;,&#xA;    &#34;sources&#34;: [&#xA;      {&#xA;        &#34;name&#34;: &#34;Default&#34;,&#xA;        &#34;policy&#34;: [&#xA;          &#34;oci::quay.io/enterprise-contract/ec-release-policy:konflux@sha256:59c6b95c02295edb7928ef187571d26d426993fd5aae0236a03c832afbd6072a&#34;&#xA;        ],&#xA;        &#34;data&#34;: [&#xA;          &#34;git::github.com/release-engineering/rhtap-ec-policy//data?ref=67018469815ee9f81e47cfb54dae39d71ed5f389&#34;,&#xA;          &#34;oci::quay.io/konflux-ci/tekton-catalog/data-acceptable-bundles:latest@sha256:c75d0123e83efa6c182b6510c35982b48201143ce74a9a388680a0ee1aa4affb&#34;,&#xA;          &#34;oci::quay.io/konflux-ci/konflux-vanguard/data-acceptable-bundles:latest@sha256:0b31c7bc77a7463a1bc52f3d3625ef0e0e75443da7fd2de8005d7885282138ea&#34;,&#xA;          &#34;oci::quay.io/konflux-ci/integration-service-catalog/data-acceptable-bundles:latest@sha256:7b00455045ea3873a72caeb1e7ac7d036bd53963a26409891a4cc9d0d242b9fc&#34;&#xA;        ],&#xA;        &#34;config&#34;: {&#xA;          &#34;include&#34;: [&#xA;            &#34;slsa_provenance_available&#34;&#xA;          ]&#xA;        }&#xA;      }&#xA;    ],&#xA;    &#34;publicKey&#34;: &#34;k8s://chains-e2e-vgkz/cosign-public-key&#34;&#xA;  },&#xA;  &#34;key&#34;: &#34;-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEAm/YE3MeVX+sgrHJZa0N2EIFu31M\nM4vPqV5IXONrtJRnu1NhnewrBCeRqpRvP5EMOZ1SO3nTppSW9eQ/1dJPbQ==\n-----END PUBLIC KEY-----\n&#34;,&#xA;  &#34;effective-time&#34;: &#34;2026-05-09T03:07:41.348855993Z&#34;&#xA;}&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-194cdbe0e4357557192e6db5b8f63e98-pod&#39;, container &#39;step-detailed-report&#39;:&#xA;----- START -----Success: true&#xA;Result: SUCCESS&#xA;Violations: 0, Warnings: 0, Successes: 5&#xA;Component: &#xA;ImageRef: quay.io/redhat-appstudio-qe/test-images@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#xA;&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-194cdbe0e4357557192e6db5b8f63e98-pod&#39;, container &#39;step-assert&#39;:&#xA;----- START -----true&#xA;----- END -----&#xA;Make sure TaskRun verify-enterprise-contract of PipelineRun verify-enterprise-contract-run-s7btr succeeded&#xA;Make sure result for TaskRun &#34;verify-enterprise-contract&#34; succeeded&#xA;&lt; Exit [It] succeeds when policy is met - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:177 @ 05/09/26 03:07:50.438 (5m41.364s)&#xA;&gt; Enter [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 03:07:50.439&#xA;&lt; Exit [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 03:07:50.439 (0s)&#xA;</system-err>
          </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="passed" time="15.542563867">
              <system-err>&gt; Enter [BeforeEach] verify-enterprise-contract task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:154 @ 05/09/26 03:07:50.439&#xA;&lt; Exit [BeforeEach] verify-enterprise-contract task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:154 @ 05/09/26 03:07:50.457 (18ms)&#xA;&gt; Enter [It] does not pass when tests are not satisfied on non-strict mode - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:197 @ 05/09/26 03:07:50.458&#xA;Creating Pipeline &#34;verify-enterprise-contract-run-xttc7&#34;&#xA;Waiting for pipeline &#34;verify-enterprise-contract-run-xttc7&#34; to finish&#xA;*** TaskRun status:&#xA;artifacts: {}&#xA;completionTime: &#34;2026-05-09T03:08:02Z&#34;&#xA;conditions:&#xA;- lastTransitionTime: &#34;2026-05-09T03:08:02Z&#34;&#xA;  message: All Steps have completed executing&#xA;  reason: Succeeded&#xA;  status: &#34;True&#34;&#xA;  type: Succeeded&#xA;podName: verify-enterprise-contract-125ef745b81267abfc14240cf4ef9db3-pod&#xA;provenance:&#xA;  featureFlags:&#xA;    awaitSidecarReadiness: true&#xA;    coschedule: workspaces&#xA;    enableAPIFields: alpha&#xA;    enableParamEnum: true&#xA;    enableProvenanceInStatus: true&#xA;    enforceNonfalsifiability: none&#xA;    maxResultSize: 4096&#xA;    resultExtractionMethod: termination-message&#xA;    runningInEnvWithInjectedSidecars: true&#xA;    verificationNoMatchPolicy: ignore&#xA;  refSource:&#xA;    digest:&#xA;      sha256: 7df8d121c09999d0376e189c1eb8a8263078aab697aa5ee966512f581427a6ce&#xA;    entryPoint: verify-enterprise-contract&#xA;    uri: quay.io/conforma/tekton-task&#xA;results:&#xA;- name: TEST_OUTPUT&#xA;  type: string&#xA;  value: |&#xA;    {&#34;timestamp&#34;:&#34;1778296081&#34;,&#34;namespace&#34;:&#34;&#34;,&#34;successes&#34;:5,&#34;failures&#34;:1,&#34;warnings&#34;:0,&#34;result&#34;:&#34;FAILURE&#34;}&#xA;spanContext:&#xA;  traceparent: 00-c61bcba352b40f5793a6ab5fcf622763-915cfd4ec1987779-01&#xA;startTime: &#34;2026-05-09T03:07:51Z&#34;&#xA;steps:&#xA;- container: step-initialize-tuf&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: initialize-tuf&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://7b6f8442872534371955ff6f88dcf1bee6b37aa256c8baeaf23464e52908a444&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:07:56Z&#34;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:07:56Z&#34;&#xA;  terminationReason: Skipped&#xA;- container: step-reduce&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: reduce&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://aa3b8b9bdff0fdcde4ffa8b1a37d43b7a21bc3a888cbfd8bac9e51ec1ef84802&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:07:56Z&#34;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:07:56Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-validate&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: validate&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://67d7d5165a456d2234bcfc99ea432e3cb4171aaa0e226e09ac00363e83a9693e&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:02Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296081\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:1,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:07:56Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-report-json&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: report-json&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://dfdfacfccafa24c0a5489db8bf7c6a749548942f93c72c23427f372dda8149e1&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:02Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296081\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:1,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:02Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-summary&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: summary&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://021e02b4fbd9a74cb5209bf14affb76833aec60db4b6b4711a13cf281b1f7fda&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:02Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296081\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:1,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:02Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-version&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: version&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://d7d03a776f13278908b962617377b18a740068c5008711ffba95f3fe34d47a34&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:02Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296081\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:1,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:02Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-show-config&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: show-config&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://4ec6ccf0cf42ddcccb671314bbdee2f1cd68f4d443ac5eddb3d1baa2b29cb8a1&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:02Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296081\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:1,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:02Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-detailed-report&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: detailed-report&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://84b2e087e83d03cbde2a96ef514b4dc63f066bb839696a55f96d58196fcc2fec&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:02Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296081\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:1,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:02Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-assert&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: assert&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://0f844b454dc2f174aa0a7a1a98753a97c84b55b3b8bb8348ae90b2ffe591f09f&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:02Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296081\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:1,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:02Z&#34;&#xA;  terminationReason: Completed&#xA;taskSpec:&#xA;  description: Verify the enterprise contract is met&#xA;  params:&#xA;  - description: |&#xA;      Spec section of an ApplicationSnapshot resource. Not all fields of the&#xA;      resource are required. A minimal example:&#xA;&#xA;      ```json&#xA;        {&#xA;          &#34;components&#34;: [&#xA;            {&#xA;              &#34;containerImage&#34;: &#34;quay.io/example/repo:latest&#34;&#xA;            }&#xA;          ]&#xA;        }&#xA;      ```&#xA;&#xA;      Each `containerImage` in the `components` array is validated.&#xA;    name: IMAGES&#xA;    type: string&#xA;  - default: enterprise-contract-service/default&#xA;    description: |&#xA;      Name of the policy configuration (EnterpriseContractPolicy&#xA;      resource) to use. `namespace/name` or `name` syntax supported. If&#xA;      namespace is omitted the namespace where the task runs is used.&#xA;      You can also specify a policy configuration using a git url, e.g.&#xA;      `github.com/conforma/config//slsa3`.&#xA;    name: POLICY_CONFIGURATION&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Public key used to verify traditional long-lived signatures. Must&#xA;      be a valid k8s cosign reference, e.g. k8s://my-space/my-secret where my-secret&#xA;      contains the expected cosign.pub attribute. Required for traditional signing&#xA;      key verification. Will be ignored if any of CERTIFICATE_IDENTITY, CERTIFICATE_IDENTITY_REGEXP,&#xA;      CERTIFICATE_OIDC_ISSUER, or CERTIFICATE_OIDC_ISSUER_REGEXP are provided.&#xA;    name: PUBLIC_KEY&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Rekor host for transparency log lookups&#xA;    name: REKOR_HOST&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Expected identity in the signing certificate for keyless verification.&#xA;      This should be the email or URI that was used when signing. You should provide&#xA;      both CERTIFICATE_OIDC_ISSUER and CERTIFICATE_IDENTITY for keyless verification.&#xA;      The PUBLIC_KEY param will be ignored if this is provided.&#xA;    name: CERTIFICATE_IDENTITY&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Expected OIDC issuer in the signing certificate for keyless verification.&#xA;      This should match the issuer that provided the identity token used for signing.&#xA;      You should provide both CERTIFICATE_OIDC_ISSUER and CERTIFICATE_IDENTITY for&#xA;      keyless verification. The PUBLIC_KEY param will be ignored if this is provided.&#xA;    name: CERTIFICATE_OIDC_ISSUER&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Similar to CERTIFICATE_IDENTITY but the value is a regexp that will&#xA;      be matched. Note that CERTIFICATE_IDENTITY takes precedence over this if both&#xA;      are present.&#xA;    name: CERTIFICATE_IDENTITY_REGEXP&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Similar to CERTIFICATE_OIDC_ISSUER but a regexp that will be matched.&#xA;      Note that CERTIFICATE_OIDC_ISSUER takes precedence over this if both are present.&#xA;    name: CERTIFICATE_OIDC_ISSUER_REGEXP&#xA;    type: string&#xA;  - default: &#34;false&#34;&#xA;    description: Skip Rekor transparency log checks during validation. Compatible&#xA;      with traditional signing secret signature checks only. If any of the CERTIFICATE_*&#xA;      keyless verification params are present, this value is disregarded and Rekor&#xA;      transparency log checks are included.&#xA;    name: IGNORE_REKOR&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: TUF mirror URL. Provide a value when NOT using public sigstore deployment.&#xA;    name: TUF_MIRROR&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: |&#xA;      Path to a directory containing SSL certs to be used when communicating&#xA;      with external services. This is useful when using the integrated registry&#xA;      and a local instance of Rekor on a development cluster which may use&#xA;      certificates issued by a not-commonly trusted root CA. In such cases,&#xA;      `/var/run/secrets/kubernetes.io/serviceaccount` is a good value. Multiple&#xA;      paths can be provided by using the `:` separator.&#xA;    name: SSL_CERT_DIR&#xA;    type: string&#xA;  - default: trusted-ca&#xA;    description: The name of the ConfigMap to read CA bundle data from.&#xA;    name: CA_TRUST_CONFIGMAP_NAME&#xA;    type: string&#xA;  - default: ca-bundle.crt&#xA;    description: The name of the key in the ConfigMap that contains the CA bundle&#xA;      data.&#xA;    name: CA_TRUST_CONFIG_MAP_KEY&#xA;    type: string&#xA;  - default: &#34;true&#34;&#xA;    description: Include rule titles and descriptions in the output. Set to `&#34;false&#34;`&#xA;      to disable it.&#xA;    name: INFO&#xA;    type: string&#xA;  - default: &#34;true&#34;&#xA;    description: Fail the task if policy fails. Set to `&#34;false&#34;` to disable it.&#xA;    name: STRICT&#xA;    type: string&#xA;  - default: /tekton/home&#xA;    description: Value for the HOME environment variable.&#xA;    name: HOMEDIR&#xA;    type: string&#xA;  - default: now&#xA;    description: Run policy checks with the provided time.&#xA;    name: EFFECTIVE_TIME&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Merge additional Rego variables into the policy data. Use syntax&#xA;      &#34;key=value,key2=value2...&#34;&#xA;    name: EXTRA_RULE_DATA&#xA;    type: string&#xA;  - default: &#34;1&#34;&#xA;    description: Number of parallel workers to use for policy evaluation.&#xA;    name: WORKERS&#xA;    type: string&#xA;  - default: &#34;false&#34;&#xA;    description: Reduce the Snapshot to only the component whose build caused the&#xA;      Snapshot to be created&#xA;    name: SINGLE_COMPONENT&#xA;    type: string&#xA;  - default: unknown&#xA;    description: |&#xA;      Name, including kind, of the Kubernetes resource to query for labels when single component mode is enabled, e.g. pr/somepipeline.&#xA;    name: SINGLE_COMPONENT_CUSTOM_RESOURCE&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: |&#xA;      Kubernetes namespace where the SINGLE_COMPONENT_NAME is found. Only used when single component mode is enabled.&#xA;    name: SINGLE_COMPONENT_CUSTOM_RESOURCE_NS&#xA;    type: string&#xA;  - default: 1s&#xA;    description: Base duration for exponential backoff calculation (e.g., &#34;1s&#34;, &#34;500ms&#34;)&#xA;    name: RETRY_DURATION&#xA;    type: string&#xA;  - default: &#34;2.0&#34;&#xA;    description: Exponential backoff multiplier (e.g., &#34;2.0&#34;, &#34;1.5&#34;)&#xA;    name: RETRY_FACTOR&#xA;    type: string&#xA;  - default: &#34;0.1&#34;&#xA;    description: Randomness factor for backoff calculation (0.0-1.0, e.g., &#34;0.1&#34;,&#xA;      &#34;0.2&#34;)&#xA;    name: RETRY_JITTER&#xA;    type: string&#xA;  - default: &#34;3&#34;&#xA;    description: Maximum number of retry attempts&#xA;    name: RETRY_MAX_RETRY&#xA;    type: string&#xA;  - default: 3s&#xA;    description: Maximum wait time between retries (e.g., &#34;3s&#34;, &#34;10s&#34;)&#xA;    name: RETRY_MAX_WAIT&#xA;    type: string&#xA;  results:&#xA;  - description: Short summary of the policy evaluation for each image&#xA;    name: TEST_OUTPUT&#xA;    type: string&#xA;  stepTemplate:&#xA;    computeResources: {}&#xA;    env:&#xA;    - name: HOME&#xA;      value: /tekton/home&#xA;  steps:&#xA;  - args:&#xA;    - sigstore&#xA;    - initialize&#xA;    - --mirror&#xA;    - &#34;&#34;&#xA;    - --root&#xA;    - /root.json&#xA;    command:&#xA;    - ec&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: initialize-tuf&#xA;    when:&#xA;    - operator: notin&#xA;      values:&#xA;      - &#34;&#34;&#xA;  - command:&#xA;    - reduce-snapshot.sh&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    env:&#xA;    - name: SNAPSHOT&#xA;      value: &#39;{&#34;application&#34;:&#34;&#34;,&#34;componentGroup&#34;:&#34;&#34;,&#34;components&#34;:[{&#34;name&#34;:&#34;&#34;,&#34;version&#34;:&#34;&#34;,&#34;containerImage&#34;:&#34;quay.io/redhat-appstudio-qe/test-images:buildah-demo-pufrqqgxeq@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#34;,&#34;source&#34;:{}}],&#34;artifacts&#34;:{}}&#39;&#xA;    - name: SINGLE_COMPONENT&#xA;      value: &#34;false&#34;&#xA;    - name: CUSTOM_RESOURCE&#xA;      value: unknown&#xA;    - name: CUSTOM_RESOURCE_NAMESPACE&#xA;    - name: SNAPSHOT_PATH&#xA;      value: /tekton/home/snapshot.json&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: reduce&#xA;    onError: continue&#xA;  - computeResources:&#xA;      limits:&#xA;        memory: 2Gi&#xA;      requests:&#xA;        cpu: 1800m&#xA;        memory: 2Gi&#xA;    env:&#xA;    - name: POLICY_CONFIGURATION&#xA;      value: ec-policy&#xA;    - name: PUBLIC_KEY&#xA;      value: k8s://chains-e2e-vgkz/cosign-public-key&#xA;    - name: CERTIFICATE_IDENTITY&#xA;    - name: CERTIFICATE_OIDC_ISSUER&#xA;    - name: CERTIFICATE_IDENTITY_REGEXP&#xA;    - name: CERTIFICATE_OIDC_ISSUER_REGEXP&#xA;    - name: REKOR_HOST&#xA;    - name: IGNORE_REKOR&#xA;      value: &#34;true&#34;&#xA;    - name: WORKERS&#xA;      value: &#34;1&#34;&#xA;    - name: INFO&#xA;      value: &#34;true&#34;&#xA;    - name: EFFECTIVE_TIME&#xA;      value: now&#xA;    - name: EXTRA_RULE_DATA&#xA;    - name: RETRY_MAX_WAIT&#xA;      value: 3s&#xA;    - name: RETRY_MAX_RETRY&#xA;      value: &#34;3&#34;&#xA;    - name: RETRY_DURATION&#xA;      value: 1s&#xA;    - name: RETRY_FACTOR&#xA;      value: &#34;2.0&#34;&#xA;    - name: RETRY_JITTER&#xA;      value: &#34;0.1&#34;&#xA;    - name: HOMEDIR&#xA;      value: /tekton/home&#xA;    - name: SSL_CERT_DIR&#xA;      value: /tekton-custom-certs:/etc/ssl/certs:/etc/pki/tls/certs:/system/etc/security/cacerts:/var/run/secrets/kubernetes.io/serviceaccount&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: validate&#xA;    onError: continue&#xA;    script: |&#xA;      #!/bin/bash&#xA;      set -euo pipefail&#xA;&#xA;      cmd_args=(&#xA;        validate&#xA;        image&#xA;        --images=&#34;${HOMEDIR}/snapshot.json&#34;&#xA;        --policy=&#34;${POLICY_CONFIGURATION}&#34;&#xA;      )&#xA;&#xA;      # To keep bash logic as thin as possible we deliberately don&#39;t sanitize&#xA;      # these params. If something is wrong or missing let Conforma handle it.&#xA;&#xA;      if [ -n &#34;${CERTIFICATE_IDENTITY}&#34; ] || \&#xA;         [ -n &#34;${CERTIFICATE_OIDC_ISSUER}&#34; ] || \&#xA;         [ -n &#34;${CERTIFICATE_IDENTITY_REGEXP}&#34; ] || \&#xA;         [ -n &#34;${CERTIFICATE_OIDC_ISSUER_REGEXP}&#34; ]; then&#xA;        # If *any* of the above are non-empty assume the intention is to&#xA;        # try keyless verification&#xA;&#xA;        if [ -n &#34;${CERTIFICATE_IDENTITY}&#34; ]; then&#xA;          cmd_args+=(&#xA;            --certificate-identity=&#34;${CERTIFICATE_IDENTITY}&#34;&#xA;          )&#xA;        elif [ -n &#34;${CERTIFICATE_IDENTITY_REGEXP}&#34; ]; then&#xA;          cmd_args+=(&#xA;            --certificate-identity-regexp=&#34;${CERTIFICATE_IDENTITY_REGEXP}&#34;&#xA;          )&#xA;        fi&#xA;&#xA;        if [ -n &#34;${CERTIFICATE_OIDC_ISSUER}&#34; ]; then&#xA;          cmd_args+=(&#xA;            --certificate-oidc-issuer=&#34;${CERTIFICATE_OIDC_ISSUER}&#34;&#xA;          )&#xA;        elif [ -n &#34;${CERTIFICATE_OIDC_ISSUER_REGEXP}&#34; ]; then&#xA;          cmd_args+=(&#xA;            --certificate-oidc-issuer-regexp=&#34;${CERTIFICATE_OIDC_ISSUER_REGEXP}&#34;&#xA;          )&#xA;        fi&#xA;&#xA;        # Force --ignore-rekor to false since we need rekor&#xA;        cmd_args+=(&#xA;          --ignore-rekor=false&#xA;        )&#xA;      else&#xA;        # Assume traditional signing secret verification&#xA;        cmd_args+=(&#xA;          --public-key=&#34;${PUBLIC_KEY}&#34;&#xA;          --ignore-rekor=&#34;${IGNORE_REKOR}&#34;&#xA;        )&#xA;      fi&#xA;&#xA;      cmd_args+=(&#xA;        --rekor-url=&#34;${REKOR_HOST}&#34;&#xA;        --workers=&#34;${WORKERS}&#34;&#xA;        --info=&#34;${INFO}&#34;&#xA;        --timeout=0&#xA;        --strict=false&#xA;        --show-successes=true&#xA;        --show-policy-docs-link=true&#xA;        --effective-time=&#34;${EFFECTIVE_TIME}&#34;&#xA;        --extra-rule-data=&#34;${EXTRA_RULE_DATA}&#34;&#xA;        --retry-max-wait=&#34;${RETRY_MAX_WAIT}&#34;&#xA;        --retry-max-retry=&#34;${RETRY_MAX_RETRY}&#34;&#xA;        --retry-duration=&#34;${RETRY_DURATION}&#34;&#xA;        --retry-factor=&#34;${RETRY_FACTOR}&#34;&#xA;        --retry-jitter=&#34;${RETRY_JITTER}&#34;&#xA;        --output=&#34;text=${HOMEDIR}/text-report.txt?show-successes=false&#34;&#xA;        --output=&#34;json=${HOMEDIR}/report-json.json&#34;&#xA;        --output=&#34;appstudio=/tekton/results/TEST_OUTPUT&#34;&#xA;      )&#xA;&#xA;&#xA;      # Execute Conforma with constructed arguments&#xA;      exec ec &#34;${cmd_args[@]}&#34;&#xA;    volumeMounts:&#xA;    - mountPath: /etc/pki/tls/certs/ca-custom-bundle.crt&#xA;      name: trusted-ca&#xA;      readOnly: true&#xA;      subPath: ca-bundle.crt&#xA;  - args:&#xA;    - jq . /tekton/home/report-json.json | awk &#39;{gsub(/^ +/, &#34;&#34;); acc += length; if&#xA;      (acc &gt;= 8000) { printf &#34;\n&#34;; acc=length } printf $0 }&#39;&#xA;    command:&#xA;    - sh&#xA;    - -c&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: report-json&#xA;    onError: continue&#xA;  - args:&#xA;    - .&#xA;    - /tekton/results/TEST_OUTPUT&#xA;    command:&#xA;    - jq&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: summary&#xA;    onError: continue&#xA;  - args:&#xA;    - version&#xA;    command:&#xA;    - ec&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: version&#xA;  - args:&#xA;    - &#39;{policy: .policy, key: .key, &#34;effective-time&#34;: .[&#34;effective-time&#34;]}&#39;&#xA;    - /tekton/home/report-json.json&#xA;    command:&#xA;    - jq&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: show-config&#xA;  - args:&#xA;    - /tekton/home/text-report.txt&#xA;    command:&#xA;    - cat&#xA;    computeResources: {}&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: detailed-report&#xA;    onError: continue&#xA;  - args:&#xA;    - --argjson&#xA;    - strict&#xA;    - &#34;false&#34;&#xA;    - -e&#xA;    - |&#xA;      .result == &#34;SUCCESS&#34; or .result == &#34;WARNING&#34; or ($strict | not)&#xA;    - /tekton/results/TEST_OUTPUT&#xA;    command:&#xA;    - jq&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: assert&#xA;  volumes:&#xA;  - configMap:&#xA;      items:&#xA;      - key: ca-bundle.crt&#xA;        path: ca-bundle.crt&#xA;      name: trusted-ca&#xA;      optional: true&#xA;    name: trusted-ca&#xA;  workspaces:&#xA;  - description: The workspace where the snapshot spec json file resides&#xA;    name: data&#xA;    optional: true&#xA;&#xA;*** Logs from pod &#39;verify-enterprise-contract-125ef745b81267abfc14240cf4ef9db3-pod&#39;, container &#39;step-initialize-tuf&#39;:&#xA;----- START -----2026/05/09 03:07:56 INFO Step was skipped due to when expressions were evaluated to false.&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-125ef745b81267abfc14240cf4ef9db3-pod&#39;, container &#39;step-reduce&#39;:&#xA;----- START -----Single Component mode? false&#xA;{&#xA;  &#34;application&#34;: &#34;&#34;,&#xA;  &#34;componentGroup&#34;: &#34;&#34;,&#xA;  &#34;components&#34;: [&#xA;    {&#xA;      &#34;name&#34;: &#34;&#34;,&#xA;      &#34;version&#34;: &#34;&#34;,&#xA;      &#34;containerImage&#34;: &#34;quay.io/redhat-appstudio-qe/test-images:buildah-demo-pufrqqgxeq@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#34;,&#xA;      &#34;source&#34;: {}&#xA;    }&#xA;  ],&#xA;  &#34;artifacts&#34;: {}&#xA;}&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-125ef745b81267abfc14240cf4ef9db3-pod&#39;, container &#39;step-validate&#39;:&#xA;----- START ---------- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-125ef745b81267abfc14240cf4ef9db3-pod&#39;, container &#39;step-report-json&#39;:&#xA;----- START -----{&#34;success&#34;: false,&#34;components&#34;: [{&#34;name&#34;: &#34;&#34;,&#34;containerImage&#34;: &#34;quay.io/redhat-appstudio-qe/test-images@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#34;,&#34;source&#34;: {},&#34;violations&#34;: [{&#34;msg&#34;: &#34;No test data found&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;test.test_data_found&#34;,&#34;collections&#34;: [&#34;redhat&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Ensure that at least one of the tasks in the pipeline includes a TEST_OUTPUT task result, which is where Conforma expects to find test result data. To exclude this rule add \&#34;test.test_data_found\&#34; to the `exclude` section of the policy configuration.&#34;,&#34;solution&#34;: &#34;Confirm at least one task in the build pipeline contains a result named TEST_OUTPUT.&#34;,&#34;title&#34;: &#34;Test data found in task results&#34;}}],&#34;successes&#34;: [{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.signature_check&#34;,&#34;description&#34;: &#34;The attestation signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Attestation signature check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.syntax_check&#34;,&#34;description&#34;: &#34;The attestation has correct syntax.&#34;,&#34;title&#34;: &#34;Attestation syntax check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.image.signature_check&#34;,&#34;description&#34;: &#34;The image signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Image signature check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;test.rule_data_provided&#34;,&#34;collections&#34;: [&#34;redhat&#34;,&#34;policy_data&#34;],&#34;description&#34;: &#34;Confirm the expected rule data keys have been provided in the expected format. The keys are `supported_tests_results`, `failed_tests_results`, `informative_tests`, `erred_tests_results`, `skipped_tests_results`, and `warned_tests_results`.&#34;,&#34;title&#34;: &#34;Rule data provided&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;test.test_all_images&#34;,&#34;collections&#34;: [&#34;redhat&#34;],&#34;description&#34;: &#34;Ensure that task producing the IMAGES_PROCESSED result contains the digests of the built image.&#34;,&#34;effective_on&#34;: &#34;2024-05-29T00:00:00Z&#34;,&#34;title&#34;: &#34;Image digest is present in IMAGES_PROCESSED result&#34;}}],&#34;success&#34;: false,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;&#34;,&#34;sig&#34;: &#34;MEYCIQDJfxL39hNiJGAEgBjgePDcytcqSu/duqvEfjGYl/+fvgIhAPC1E38DC+CMmhjpkxepOIYZzC2wkaSkQAONZU1BI1t/&#34;},{&#34;keyid&#34;: &#34;&#34;,&#34;sig&#34;: &#34;MEYCIQD5lUHkAzgo95QzY3djxj7J6J1uJmkzCP0k14PqfB4GcwIhAKm5biMiltqCvYwFGf0maWg7g+KwFnaRAL2jrZeu3s7y&#34;},{&#34;keyid&#34;: &#34;&#34;,&#34;sig&#34;: &#34;MEYCIQCWhOUFFV9/AU6Vu3zZEASbiVPMTbeIcAF8M59OQQaXqgIhAKhV/19siiQfZARh7ad7hqwipKPZCVvzKlHUOqLxAuCl&#34;}],&#34;attestations&#34;: [{&#34;type&#34;: &#34;https://in-toto.io/Statement/v0.1&#34;,&#34;predicateType&#34;: &#34;https://slsa.dev/provenance/v0.2&#34;,&#34;predicateBuildType&#34;: &#34;tekton.dev/v1/PipelineRun&#34;,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;SHA256:ybGxTL8yTILGa7JB0rbOG+ayq66D9nzMrFoav6G5X6c&#34;,&#34;sig&#34;: &#34;MEUCIQDhxLbpagJPRtBHcUYEmg8XPZgIIa6WSSzB7ZJ7DlCEzQIgCrRkUXEpyGTuDNmeV+KL6QI9rH0T4XhUbaodBfDulcs=&#34;}]}]}],&#34;key&#34;: &#34;-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEAm/YE3MeVX+sgrHJZa0N2EIFu31M\nM4vPqV5IXONrtJRnu1NhnewrBCeRqpRvP5EMOZ1SO3nTppSW9eQ/1dJPbQ==\n-----END PUBLIC KEY-----\n&#34;,&#34;policy&#34;: {&#34;name&#34;: &#34;Default&#34;,&#34;description&#34;: &#34;Includes rules for levels 1, 2 &amp; 3 of SLSA v0.1. This is the default config used for new Konflux applications. Source: https://github.com/conforma/config/blob/main/default/policy.yaml&#34;,&#34;sources&#34;: [{&#34;name&#34;: &#34;Default&#34;,&#34;policy&#34;: [&#34;oci::quay.io/enterprise-contract/ec-release-policy:konflux@sha256:59c6b95c02295edb7928ef187571d26d426993fd5aae0236a03c832afbd6072a&#34;],&#34;data&#34;: [&#34;git::github.com/release-engineering/rhtap-ec-policy//data?ref=67018469815ee9f81e47cfb54dae39d71ed5f389&#34;,&#34;oci::quay.io/konflux-ci/tekton-catalog/data-acceptable-bundles:latest@sha256:c75d0123e83efa6c182b6510c35982b48201143ce74a9a388680a0ee1aa4affb&#34;,&#34;oci::quay.io/konflux-ci/konflux-vanguard/data-acceptable-bundles:latest@sha256:0b31c7bc77a7463a1bc52f3d3625ef0e0e75443da7fd2de8005d7885282138ea&#34;,&#34;oci::quay.io/konflux-ci/integration-service-catalog/data-acceptable-bundles:latest@sha256:7b00455045ea3873a72caeb1e7ac7d036bd53963a26409891a4cc9d0d242b9fc&#34;],&#34;config&#34;: {&#34;include&#34;: [&#34;test&#34;]}}],&#34;publicKey&#34;: &#34;k8s://chains-e2e-vgkz/cosign-public-key&#34;},&#34;ec-version&#34;: &#34;v0.9.25&#34;,&#34;effective-time&#34;: &#34;2026-05-09T03:07:57.198790844Z&#34;}----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-125ef745b81267abfc14240cf4ef9db3-pod&#39;, container &#39;step-summary&#39;:&#xA;----- START -----{&#xA;  &#34;timestamp&#34;: &#34;1778296081&#34;,&#xA;  &#34;namespace&#34;: &#34;&#34;,&#xA;  &#34;successes&#34;: 5,&#xA;  &#34;failures&#34;: 1,&#xA;  &#34;warnings&#34;: 0,&#xA;  &#34;result&#34;: &#34;FAILURE&#34;&#xA;}&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-125ef745b81267abfc14240cf4ef9db3-pod&#39;, container &#39;step-version&#39;:&#xA;----- START -----Version            v0.9.25&#xA;Source ID          b345847182602d9a5ce9e957fa76fe02575c8018&#xA;Change date        2026-04-27 12:52:43 +0000 UTC (1 week ago)&#xA;ECC                v0.1.7&#xA;OPA                v1.15.2&#xA;Conftest           v0.68.2&#xA;Cosign             v3.0.4&#xA;Sigstore           v1.10.4&#xA;Rekor              v1.5.0&#xA;Tekton Pipeline    v1.9.2&#xA;Kubernetes Client  v0.35.0&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-125ef745b81267abfc14240cf4ef9db3-pod&#39;, container &#39;step-show-config&#39;:&#xA;----- START -----{&#xA;  &#34;policy&#34;: {&#xA;    &#34;name&#34;: &#34;Default&#34;,&#xA;    &#34;description&#34;: &#34;Includes rules for levels 1, 2 &amp; 3 of SLSA v0.1. This is the default config used for new Konflux applications. Source: https://github.com/conforma/config/blob/main/default/policy.yaml&#34;,&#xA;    &#34;sources&#34;: [&#xA;      {&#xA;        &#34;name&#34;: &#34;Default&#34;,&#xA;        &#34;policy&#34;: [&#xA;          &#34;oci::quay.io/enterprise-contract/ec-release-policy:konflux@sha256:59c6b95c02295edb7928ef187571d26d426993fd5aae0236a03c832afbd6072a&#34;&#xA;        ],&#xA;        &#34;data&#34;: [&#xA;          &#34;git::github.com/release-engineering/rhtap-ec-policy//data?ref=67018469815ee9f81e47cfb54dae39d71ed5f389&#34;,&#xA;          &#34;oci::quay.io/konflux-ci/tekton-catalog/data-acceptable-bundles:latest@sha256:c75d0123e83efa6c182b6510c35982b48201143ce74a9a388680a0ee1aa4affb&#34;,&#xA;          &#34;oci::quay.io/konflux-ci/konflux-vanguard/data-acceptable-bundles:latest@sha256:0b31c7bc77a7463a1bc52f3d3625ef0e0e75443da7fd2de8005d7885282138ea&#34;,&#xA;          &#34;oci::quay.io/konflux-ci/integration-service-catalog/data-acceptable-bundles:latest@sha256:7b00455045ea3873a72caeb1e7ac7d036bd53963a26409891a4cc9d0d242b9fc&#34;&#xA;        ],&#xA;        &#34;config&#34;: {&#xA;          &#34;include&#34;: [&#xA;            &#34;test&#34;&#xA;          ]&#xA;        }&#xA;      }&#xA;    ],&#xA;    &#34;publicKey&#34;: &#34;k8s://chains-e2e-vgkz/cosign-public-key&#34;&#xA;  },&#xA;  &#34;key&#34;: &#34;-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEAm/YE3MeVX+sgrHJZa0N2EIFu31M\nM4vPqV5IXONrtJRnu1NhnewrBCeRqpRvP5EMOZ1SO3nTppSW9eQ/1dJPbQ==\n-----END PUBLIC KEY-----\n&#34;,&#xA;  &#34;effective-time&#34;: &#34;2026-05-09T03:07:57.198790844Z&#34;&#xA;}&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-125ef745b81267abfc14240cf4ef9db3-pod&#39;, container &#39;step-detailed-report&#39;:&#xA;----- START -----Success: false&#xA;Result: FAILURE&#xA;Violations: 1, Warnings: 0, Successes: 5&#xA;Component: &#xA;ImageRef: quay.io/redhat-appstudio-qe/test-images@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#xA;&#xA;Results:&#xA;✕ [Violation] test.test_data_found&#xA;  ImageRef: quay.io/redhat-appstudio-qe/test-images@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#xA;  Reason: No test data found&#xA;  Title: Test data found in task results&#xA;  Description: Ensure that at least one of the tasks in the pipeline includes a TEST_OUTPUT task result, which is where Conforma&#xA;  expects to find test result data. To exclude this rule add &#34;test.test_data_found&#34; to the `exclude` section of the policy&#xA;  configuration.&#xA;  Solution: Confirm at least one task in the build pipeline contains a result named TEST_OUTPUT.&#xA;&#xA;For more information about policy issues, see the policy documentation: https://conforma.dev/docs/policy/&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-125ef745b81267abfc14240cf4ef9db3-pod&#39;, container &#39;step-assert&#39;:&#xA;----- START -----true&#xA;----- END -----&#xA;Make sure TaskRun verify-enterprise-contract of PipelineRun verify-enterprise-contract-run-xttc7 succeeded&#xA;Make sure result for TaskRun &#34;verify-enterprise-contract&#34; succeeded&#xA;&lt; Exit [It] does not pass when tests are not satisfied on non-strict mode - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:197 @ 05/09/26 03:08:05.981 (15.524s)&#xA;&gt; Enter [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 03:08:05.982&#xA;&lt; Exit [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 03:08:05.982 (0s)&#xA;</system-err>
          </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="passed" time="26.324759053">
              <system-err>&gt; Enter [BeforeEach] verify-enterprise-contract task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:154 @ 05/09/26 03:08:05.983&#xA;&lt; Exit [BeforeEach] verify-enterprise-contract task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:154 @ 05/09/26 03:08:06.005 (22ms)&#xA;&gt; Enter [It] fails when tests are not satisfied on strict mode - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:225 @ 05/09/26 03:08:06.005&#xA;Creating Pipeline &#34;verify-enterprise-contract-run-9fpkw&#34;&#xA;Waiting for pipeline &#34;verify-enterprise-contract-run-9fpkw&#34; to finish&#xA;*** TaskRun status:&#xA;artifacts: {}&#xA;completionTime: &#34;2026-05-09T03:08:31Z&#34;&#xA;conditions:&#xA;- lastTransitionTime: &#34;2026-05-09T03:08:31Z&#34;&#xA;  message: &#39;&#34;step-assert&#34; exited with code 1: Error&#39;&#xA;  reason: Failed&#xA;  status: &#34;False&#34;&#xA;  type: Succeeded&#xA;podName: verify-enterprise-contract-010062891fae8a3e7e2933423c91e1bd-pod&#xA;provenance:&#xA;  featureFlags:&#xA;    awaitSidecarReadiness: true&#xA;    coschedule: workspaces&#xA;    enableAPIFields: alpha&#xA;    enableParamEnum: true&#xA;    enableProvenanceInStatus: true&#xA;    enforceNonfalsifiability: none&#xA;    maxResultSize: 4096&#xA;    resultExtractionMethod: termination-message&#xA;    runningInEnvWithInjectedSidecars: true&#xA;    verificationNoMatchPolicy: ignore&#xA;  refSource:&#xA;    digest:&#xA;      sha256: 7df8d121c09999d0376e189c1eb8a8263078aab697aa5ee966512f581427a6ce&#xA;    entryPoint: verify-enterprise-contract&#xA;    uri: quay.io/conforma/tekton-task&#xA;results:&#xA;- name: TEST_OUTPUT&#xA;  type: string&#xA;  value: |&#xA;    {&#34;timestamp&#34;:&#34;1778296109&#34;,&#34;namespace&#34;:&#34;&#34;,&#34;successes&#34;:5,&#34;failures&#34;:1,&#34;warnings&#34;:0,&#34;result&#34;:&#34;FAILURE&#34;}&#xA;spanContext:&#xA;  traceparent: 00-9d39e7826da447a5236233f323a10ac9-d1beb1e3061dc1be-01&#xA;startTime: &#34;2026-05-09T03:08:07Z&#34;&#xA;steps:&#xA;- container: step-initialize-tuf&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: initialize-tuf&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://22ace1acc0b6ae7bbe78d9e7506068bd43a1389b5d8db32f8e37de770591f29a&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:24Z&#34;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:24Z&#34;&#xA;  terminationReason: Skipped&#xA;- container: step-reduce&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: reduce&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://97b56e15d93aaa43dfadfd8639b05db8cd813a9b2b6ed6e145ebd1b760a9442c&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:24Z&#34;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:24Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-validate&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: validate&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://2bf7123aaa41a6f701d39ebf2718dfa71a5b2f52ffc2446f328c884c56fdc969&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:29Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296109\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:1,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:24Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-report-json&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: report-json&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://82ce2523951fc47dd3c691a2c5f785a8cdfef9f9202b94fe12577d04480c500c&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:30Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296109\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:1,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:30Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-summary&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: summary&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://c26023eed22e7b5046f82b0316fad5e24d6b04dc7b75e45aa6c4fcf83141daca&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:30Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296109\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:1,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:30Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-version&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: version&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://29c277a020b1610a5303679db451de6806c09e1196fc4991f8bbf63dc4f14dbd&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:30Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296109\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:1,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:30Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-show-config&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: show-config&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://d04cb6ae2b7bfbde0a123699c3b2aa94f71d6a4606967f131da5f7228c673e05&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:30Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296109\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:1,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:30Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-detailed-report&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: detailed-report&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://1b11016ec1415c3a88240500054eb060122c21f3b7e1404248b2c09a1d66a06a&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:30Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296109\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:1,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:30Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-assert&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: assert&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://5fad33fe31905f87a0d6c6276a0ef435bfc679bee90974930c7b4984910444d0&#xA;    exitCode: 1&#xA;    finishedAt: &#34;2026-05-09T03:08:30Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296109\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:5,\&#34;failures\&#34;:1,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Error&#xA;    startedAt: &#34;2026-05-09T03:08:30Z&#34;&#xA;  terminationReason: Error&#xA;taskSpec:&#xA;  description: Verify the enterprise contract is met&#xA;  params:&#xA;  - description: |&#xA;      Spec section of an ApplicationSnapshot resource. Not all fields of the&#xA;      resource are required. A minimal example:&#xA;&#xA;      ```json&#xA;        {&#xA;          &#34;components&#34;: [&#xA;            {&#xA;              &#34;containerImage&#34;: &#34;quay.io/example/repo:latest&#34;&#xA;            }&#xA;          ]&#xA;        }&#xA;      ```&#xA;&#xA;      Each `containerImage` in the `components` array is validated.&#xA;    name: IMAGES&#xA;    type: string&#xA;  - default: enterprise-contract-service/default&#xA;    description: |&#xA;      Name of the policy configuration (EnterpriseContractPolicy&#xA;      resource) to use. `namespace/name` or `name` syntax supported. If&#xA;      namespace is omitted the namespace where the task runs is used.&#xA;      You can also specify a policy configuration using a git url, e.g.&#xA;      `github.com/conforma/config//slsa3`.&#xA;    name: POLICY_CONFIGURATION&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Public key used to verify traditional long-lived signatures. Must&#xA;      be a valid k8s cosign reference, e.g. k8s://my-space/my-secret where my-secret&#xA;      contains the expected cosign.pub attribute. Required for traditional signing&#xA;      key verification. Will be ignored if any of CERTIFICATE_IDENTITY, CERTIFICATE_IDENTITY_REGEXP,&#xA;      CERTIFICATE_OIDC_ISSUER, or CERTIFICATE_OIDC_ISSUER_REGEXP are provided.&#xA;    name: PUBLIC_KEY&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Rekor host for transparency log lookups&#xA;    name: REKOR_HOST&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Expected identity in the signing certificate for keyless verification.&#xA;      This should be the email or URI that was used when signing. You should provide&#xA;      both CERTIFICATE_OIDC_ISSUER and CERTIFICATE_IDENTITY for keyless verification.&#xA;      The PUBLIC_KEY param will be ignored if this is provided.&#xA;    name: CERTIFICATE_IDENTITY&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Expected OIDC issuer in the signing certificate for keyless verification.&#xA;      This should match the issuer that provided the identity token used for signing.&#xA;      You should provide both CERTIFICATE_OIDC_ISSUER and CERTIFICATE_IDENTITY for&#xA;      keyless verification. The PUBLIC_KEY param will be ignored if this is provided.&#xA;    name: CERTIFICATE_OIDC_ISSUER&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Similar to CERTIFICATE_IDENTITY but the value is a regexp that will&#xA;      be matched. Note that CERTIFICATE_IDENTITY takes precedence over this if both&#xA;      are present.&#xA;    name: CERTIFICATE_IDENTITY_REGEXP&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Similar to CERTIFICATE_OIDC_ISSUER but a regexp that will be matched.&#xA;      Note that CERTIFICATE_OIDC_ISSUER takes precedence over this if both are present.&#xA;    name: CERTIFICATE_OIDC_ISSUER_REGEXP&#xA;    type: string&#xA;  - default: &#34;false&#34;&#xA;    description: Skip Rekor transparency log checks during validation. Compatible&#xA;      with traditional signing secret signature checks only. If any of the CERTIFICATE_*&#xA;      keyless verification params are present, this value is disregarded and Rekor&#xA;      transparency log checks are included.&#xA;    name: IGNORE_REKOR&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: TUF mirror URL. Provide a value when NOT using public sigstore deployment.&#xA;    name: TUF_MIRROR&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: |&#xA;      Path to a directory containing SSL certs to be used when communicating&#xA;      with external services. This is useful when using the integrated registry&#xA;      and a local instance of Rekor on a development cluster which may use&#xA;      certificates issued by a not-commonly trusted root CA. In such cases,&#xA;      `/var/run/secrets/kubernetes.io/serviceaccount` is a good value. Multiple&#xA;      paths can be provided by using the `:` separator.&#xA;    name: SSL_CERT_DIR&#xA;    type: string&#xA;  - default: trusted-ca&#xA;    description: The name of the ConfigMap to read CA bundle data from.&#xA;    name: CA_TRUST_CONFIGMAP_NAME&#xA;    type: string&#xA;  - default: ca-bundle.crt&#xA;    description: The name of the key in the ConfigMap that contains the CA bundle&#xA;      data.&#xA;    name: CA_TRUST_CONFIG_MAP_KEY&#xA;    type: string&#xA;  - default: &#34;true&#34;&#xA;    description: Include rule titles and descriptions in the output. Set to `&#34;false&#34;`&#xA;      to disable it.&#xA;    name: INFO&#xA;    type: string&#xA;  - default: &#34;true&#34;&#xA;    description: Fail the task if policy fails. Set to `&#34;false&#34;` to disable it.&#xA;    name: STRICT&#xA;    type: string&#xA;  - default: /tekton/home&#xA;    description: Value for the HOME environment variable.&#xA;    name: HOMEDIR&#xA;    type: string&#xA;  - default: now&#xA;    description: Run policy checks with the provided time.&#xA;    name: EFFECTIVE_TIME&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Merge additional Rego variables into the policy data. Use syntax&#xA;      &#34;key=value,key2=value2...&#34;&#xA;    name: EXTRA_RULE_DATA&#xA;    type: string&#xA;  - default: &#34;1&#34;&#xA;    description: Number of parallel workers to use for policy evaluation.&#xA;    name: WORKERS&#xA;    type: string&#xA;  - default: &#34;false&#34;&#xA;    description: Reduce the Snapshot to only the component whose build caused the&#xA;      Snapshot to be created&#xA;    name: SINGLE_COMPONENT&#xA;    type: string&#xA;  - default: unknown&#xA;    description: |&#xA;      Name, including kind, of the Kubernetes resource to query for labels when single component mode is enabled, e.g. pr/somepipeline.&#xA;    name: SINGLE_COMPONENT_CUSTOM_RESOURCE&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: |&#xA;      Kubernetes namespace where the SINGLE_COMPONENT_NAME is found. Only used when single component mode is enabled.&#xA;    name: SINGLE_COMPONENT_CUSTOM_RESOURCE_NS&#xA;    type: string&#xA;  - default: 1s&#xA;    description: Base duration for exponential backoff calculation (e.g., &#34;1s&#34;, &#34;500ms&#34;)&#xA;    name: RETRY_DURATION&#xA;    type: string&#xA;  - default: &#34;2.0&#34;&#xA;    description: Exponential backoff multiplier (e.g., &#34;2.0&#34;, &#34;1.5&#34;)&#xA;    name: RETRY_FACTOR&#xA;    type: string&#xA;  - default: &#34;0.1&#34;&#xA;    description: Randomness factor for backoff calculation (0.0-1.0, e.g., &#34;0.1&#34;,&#xA;      &#34;0.2&#34;)&#xA;    name: RETRY_JITTER&#xA;    type: string&#xA;  - default: &#34;3&#34;&#xA;    description: Maximum number of retry attempts&#xA;    name: RETRY_MAX_RETRY&#xA;    type: string&#xA;  - default: 3s&#xA;    description: Maximum wait time between retries (e.g., &#34;3s&#34;, &#34;10s&#34;)&#xA;    name: RETRY_MAX_WAIT&#xA;    type: string&#xA;  results:&#xA;  - description: Short summary of the policy evaluation for each image&#xA;    name: TEST_OUTPUT&#xA;    type: string&#xA;  stepTemplate:&#xA;    computeResources: {}&#xA;    env:&#xA;    - name: HOME&#xA;      value: /tekton/home&#xA;  steps:&#xA;  - args:&#xA;    - sigstore&#xA;    - initialize&#xA;    - --mirror&#xA;    - &#34;&#34;&#xA;    - --root&#xA;    - /root.json&#xA;    command:&#xA;    - ec&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: initialize-tuf&#xA;    when:&#xA;    - operator: notin&#xA;      values:&#xA;      - &#34;&#34;&#xA;  - command:&#xA;    - reduce-snapshot.sh&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    env:&#xA;    - name: SNAPSHOT&#xA;      value: &#39;{&#34;application&#34;:&#34;&#34;,&#34;componentGroup&#34;:&#34;&#34;,&#34;components&#34;:[{&#34;name&#34;:&#34;&#34;,&#34;version&#34;:&#34;&#34;,&#34;containerImage&#34;:&#34;quay.io/redhat-appstudio-qe/test-images:buildah-demo-pufrqqgxeq@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#34;,&#34;source&#34;:{}}],&#34;artifacts&#34;:{}}&#39;&#xA;    - name: SINGLE_COMPONENT&#xA;      value: &#34;false&#34;&#xA;    - name: CUSTOM_RESOURCE&#xA;      value: unknown&#xA;    - name: CUSTOM_RESOURCE_NAMESPACE&#xA;    - name: SNAPSHOT_PATH&#xA;      value: /tekton/home/snapshot.json&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: reduce&#xA;    onError: continue&#xA;  - computeResources:&#xA;      limits:&#xA;        memory: 2Gi&#xA;      requests:&#xA;        cpu: 1800m&#xA;        memory: 2Gi&#xA;    env:&#xA;    - name: POLICY_CONFIGURATION&#xA;      value: ec-policy&#xA;    - name: PUBLIC_KEY&#xA;      value: k8s://chains-e2e-vgkz/cosign-public-key&#xA;    - name: CERTIFICATE_IDENTITY&#xA;    - name: CERTIFICATE_OIDC_ISSUER&#xA;    - name: CERTIFICATE_IDENTITY_REGEXP&#xA;    - name: CERTIFICATE_OIDC_ISSUER_REGEXP&#xA;    - name: REKOR_HOST&#xA;    - name: IGNORE_REKOR&#xA;      value: &#34;true&#34;&#xA;    - name: WORKERS&#xA;      value: &#34;1&#34;&#xA;    - name: INFO&#xA;      value: &#34;true&#34;&#xA;    - name: EFFECTIVE_TIME&#xA;      value: now&#xA;    - name: EXTRA_RULE_DATA&#xA;    - name: RETRY_MAX_WAIT&#xA;      value: 3s&#xA;    - name: RETRY_MAX_RETRY&#xA;      value: &#34;3&#34;&#xA;    - name: RETRY_DURATION&#xA;      value: 1s&#xA;    - name: RETRY_FACTOR&#xA;      value: &#34;2.0&#34;&#xA;    - name: RETRY_JITTER&#xA;      value: &#34;0.1&#34;&#xA;    - name: HOMEDIR&#xA;      value: /tekton/home&#xA;    - name: SSL_CERT_DIR&#xA;      value: /tekton-custom-certs:/etc/ssl/certs:/etc/pki/tls/certs:/system/etc/security/cacerts:/var/run/secrets/kubernetes.io/serviceaccount&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: validate&#xA;    onError: continue&#xA;    script: |&#xA;      #!/bin/bash&#xA;      set -euo pipefail&#xA;&#xA;      cmd_args=(&#xA;        validate&#xA;        image&#xA;        --images=&#34;${HOMEDIR}/snapshot.json&#34;&#xA;        --policy=&#34;${POLICY_CONFIGURATION}&#34;&#xA;      )&#xA;&#xA;      # To keep bash logic as thin as possible we deliberately don&#39;t sanitize&#xA;      # these params. If something is wrong or missing let Conforma handle it.&#xA;&#xA;      if [ -n &#34;${CERTIFICATE_IDENTITY}&#34; ] || \&#xA;         [ -n &#34;${CERTIFICATE_OIDC_ISSUER}&#34; ] || \&#xA;         [ -n &#34;${CERTIFICATE_IDENTITY_REGEXP}&#34; ] || \&#xA;         [ -n &#34;${CERTIFICATE_OIDC_ISSUER_REGEXP}&#34; ]; then&#xA;        # If *any* of the above are non-empty assume the intention is to&#xA;        # try keyless verification&#xA;&#xA;        if [ -n &#34;${CERTIFICATE_IDENTITY}&#34; ]; then&#xA;          cmd_args+=(&#xA;            --certificate-identity=&#34;${CERTIFICATE_IDENTITY}&#34;&#xA;          )&#xA;        elif [ -n &#34;${CERTIFICATE_IDENTITY_REGEXP}&#34; ]; then&#xA;          cmd_args+=(&#xA;            --certificate-identity-regexp=&#34;${CERTIFICATE_IDENTITY_REGEXP}&#34;&#xA;          )&#xA;        fi&#xA;&#xA;        if [ -n &#34;${CERTIFICATE_OIDC_ISSUER}&#34; ]; then&#xA;          cmd_args+=(&#xA;            --certificate-oidc-issuer=&#34;${CERTIFICATE_OIDC_ISSUER}&#34;&#xA;          )&#xA;        elif [ -n &#34;${CERTIFICATE_OIDC_ISSUER_REGEXP}&#34; ]; then&#xA;          cmd_args+=(&#xA;            --certificate-oidc-issuer-regexp=&#34;${CERTIFICATE_OIDC_ISSUER_REGEXP}&#34;&#xA;          )&#xA;        fi&#xA;&#xA;        # Force --ignore-rekor to false since we need rekor&#xA;        cmd_args+=(&#xA;          --ignore-rekor=false&#xA;        )&#xA;      else&#xA;        # Assume traditional signing secret verification&#xA;        cmd_args+=(&#xA;          --public-key=&#34;${PUBLIC_KEY}&#34;&#xA;          --ignore-rekor=&#34;${IGNORE_REKOR}&#34;&#xA;        )&#xA;      fi&#xA;&#xA;      cmd_args+=(&#xA;        --rekor-url=&#34;${REKOR_HOST}&#34;&#xA;        --workers=&#34;${WORKERS}&#34;&#xA;        --info=&#34;${INFO}&#34;&#xA;        --timeout=0&#xA;        --strict=false&#xA;        --show-successes=true&#xA;        --show-policy-docs-link=true&#xA;        --effective-time=&#34;${EFFECTIVE_TIME}&#34;&#xA;        --extra-rule-data=&#34;${EXTRA_RULE_DATA}&#34;&#xA;        --retry-max-wait=&#34;${RETRY_MAX_WAIT}&#34;&#xA;        --retry-max-retry=&#34;${RETRY_MAX_RETRY}&#34;&#xA;        --retry-duration=&#34;${RETRY_DURATION}&#34;&#xA;        --retry-factor=&#34;${RETRY_FACTOR}&#34;&#xA;        --retry-jitter=&#34;${RETRY_JITTER}&#34;&#xA;        --output=&#34;text=${HOMEDIR}/text-report.txt?show-successes=false&#34;&#xA;        --output=&#34;json=${HOMEDIR}/report-json.json&#34;&#xA;        --output=&#34;appstudio=/tekton/results/TEST_OUTPUT&#34;&#xA;      )&#xA;&#xA;&#xA;      # Execute Conforma with constructed arguments&#xA;      exec ec &#34;${cmd_args[@]}&#34;&#xA;    volumeMounts:&#xA;    - mountPath: /etc/pki/tls/certs/ca-custom-bundle.crt&#xA;      name: trusted-ca&#xA;      readOnly: true&#xA;      subPath: ca-bundle.crt&#xA;  - args:&#xA;    - jq . /tekton/home/report-json.json | awk &#39;{gsub(/^ +/, &#34;&#34;); acc += length; if&#xA;      (acc &gt;= 8000) { printf &#34;\n&#34;; acc=length } printf $0 }&#39;&#xA;    command:&#xA;    - sh&#xA;    - -c&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: report-json&#xA;    onError: continue&#xA;  - args:&#xA;    - .&#xA;    - /tekton/results/TEST_OUTPUT&#xA;    command:&#xA;    - jq&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: summary&#xA;    onError: continue&#xA;  - args:&#xA;    - version&#xA;    command:&#xA;    - ec&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: version&#xA;  - args:&#xA;    - &#39;{policy: .policy, key: .key, &#34;effective-time&#34;: .[&#34;effective-time&#34;]}&#39;&#xA;    - /tekton/home/report-json.json&#xA;    command:&#xA;    - jq&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: show-config&#xA;  - args:&#xA;    - /tekton/home/text-report.txt&#xA;    command:&#xA;    - cat&#xA;    computeResources: {}&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: detailed-report&#xA;    onError: continue&#xA;  - args:&#xA;    - --argjson&#xA;    - strict&#xA;    - &#34;true&#34;&#xA;    - -e&#xA;    - |&#xA;      .result == &#34;SUCCESS&#34; or .result == &#34;WARNING&#34; or ($strict | not)&#xA;    - /tekton/results/TEST_OUTPUT&#xA;    command:&#xA;    - jq&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: assert&#xA;  volumes:&#xA;  - configMap:&#xA;      items:&#xA;      - key: ca-bundle.crt&#xA;        path: ca-bundle.crt&#xA;      name: trusted-ca&#xA;      optional: true&#xA;    name: trusted-ca&#xA;  workspaces:&#xA;  - description: The workspace where the snapshot spec json file resides&#xA;    name: data&#xA;    optional: true&#xA;&#xA;*** Logs from pod &#39;verify-enterprise-contract-010062891fae8a3e7e2933423c91e1bd-pod&#39;, container &#39;step-initialize-tuf&#39;:&#xA;----- START -----2026/05/09 03:08:24 INFO Step was skipped due to when expressions were evaluated to false.&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-010062891fae8a3e7e2933423c91e1bd-pod&#39;, container &#39;step-reduce&#39;:&#xA;----- START -----Single Component mode? false&#xA;{&#xA;  &#34;application&#34;: &#34;&#34;,&#xA;  &#34;componentGroup&#34;: &#34;&#34;,&#xA;  &#34;components&#34;: [&#xA;    {&#xA;      &#34;name&#34;: &#34;&#34;,&#xA;      &#34;version&#34;: &#34;&#34;,&#xA;      &#34;containerImage&#34;: &#34;quay.io/redhat-appstudio-qe/test-images:buildah-demo-pufrqqgxeq@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#34;,&#xA;      &#34;source&#34;: {}&#xA;    }&#xA;  ],&#xA;  &#34;artifacts&#34;: {}&#xA;}&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-010062891fae8a3e7e2933423c91e1bd-pod&#39;, container &#39;step-validate&#39;:&#xA;----- START ---------- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-010062891fae8a3e7e2933423c91e1bd-pod&#39;, container &#39;step-report-json&#39;:&#xA;----- START -----{&#34;success&#34;: false,&#34;components&#34;: [{&#34;name&#34;: &#34;&#34;,&#34;containerImage&#34;: &#34;quay.io/redhat-appstudio-qe/test-images@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#34;,&#34;source&#34;: {},&#34;violations&#34;: [{&#34;msg&#34;: &#34;No test data found&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;test.test_data_found&#34;,&#34;collections&#34;: [&#34;redhat&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Ensure that at least one of the tasks in the pipeline includes a TEST_OUTPUT task result, which is where Conforma expects to find test result data. To exclude this rule add \&#34;test.test_data_found\&#34; to the `exclude` section of the policy configuration.&#34;,&#34;solution&#34;: &#34;Confirm at least one task in the build pipeline contains a result named TEST_OUTPUT.&#34;,&#34;title&#34;: &#34;Test data found in task results&#34;}}],&#34;successes&#34;: [{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.signature_check&#34;,&#34;description&#34;: &#34;The attestation signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Attestation signature check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.syntax_check&#34;,&#34;description&#34;: &#34;The attestation has correct syntax.&#34;,&#34;title&#34;: &#34;Attestation syntax check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.image.signature_check&#34;,&#34;description&#34;: &#34;The image signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Image signature check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;test.rule_data_provided&#34;,&#34;collections&#34;: [&#34;redhat&#34;,&#34;policy_data&#34;],&#34;description&#34;: &#34;Confirm the expected rule data keys have been provided in the expected format. The keys are `supported_tests_results`, `failed_tests_results`, `informative_tests`, `erred_tests_results`, `skipped_tests_results`, and `warned_tests_results`.&#34;,&#34;title&#34;: &#34;Rule data provided&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;test.test_all_images&#34;,&#34;collections&#34;: [&#34;redhat&#34;],&#34;description&#34;: &#34;Ensure that task producing the IMAGES_PROCESSED result contains the digests of the built image.&#34;,&#34;effective_on&#34;: &#34;2024-05-29T00:00:00Z&#34;,&#34;title&#34;: &#34;Image digest is present in IMAGES_PROCESSED result&#34;}}],&#34;success&#34;: false,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;&#34;,&#34;sig&#34;: &#34;MEYCIQDJfxL39hNiJGAEgBjgePDcytcqSu/duqvEfjGYl/+fvgIhAPC1E38DC+CMmhjpkxepOIYZzC2wkaSkQAONZU1BI1t/&#34;},{&#34;keyid&#34;: &#34;&#34;,&#34;sig&#34;: &#34;MEYCIQD5lUHkAzgo95QzY3djxj7J6J1uJmkzCP0k14PqfB4GcwIhAKm5biMiltqCvYwFGf0maWg7g+KwFnaRAL2jrZeu3s7y&#34;},{&#34;keyid&#34;: &#34;&#34;,&#34;sig&#34;: &#34;MEYCIQCWhOUFFV9/AU6Vu3zZEASbiVPMTbeIcAF8M59OQQaXqgIhAKhV/19siiQfZARh7ad7hqwipKPZCVvzKlHUOqLxAuCl&#34;}],&#34;attestations&#34;: [{&#34;type&#34;: &#34;https://in-toto.io/Statement/v0.1&#34;,&#34;predicateType&#34;: &#34;https://slsa.dev/provenance/v0.2&#34;,&#34;predicateBuildType&#34;: &#34;tekton.dev/v1/PipelineRun&#34;,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;SHA256:ybGxTL8yTILGa7JB0rbOG+ayq66D9nzMrFoav6G5X6c&#34;,&#34;sig&#34;: &#34;MEUCIQDhxLbpagJPRtBHcUYEmg8XPZgIIa6WSSzB7ZJ7DlCEzQIgCrRkUXEpyGTuDNmeV+KL6QI9rH0T4XhUbaodBfDulcs=&#34;}]}]}],&#34;key&#34;: &#34;-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEAm/YE3MeVX+sgrHJZa0N2EIFu31M\nM4vPqV5IXONrtJRnu1NhnewrBCeRqpRvP5EMOZ1SO3nTppSW9eQ/1dJPbQ==\n-----END PUBLIC KEY-----\n&#34;,&#34;policy&#34;: {&#34;name&#34;: &#34;Default&#34;,&#34;description&#34;: &#34;Includes rules for levels 1, 2 &amp; 3 of SLSA v0.1. This is the default config used for new Konflux applications. Source: https://github.com/conforma/config/blob/main/default/policy.yaml&#34;,&#34;sources&#34;: [{&#34;name&#34;: &#34;Default&#34;,&#34;policy&#34;: [&#34;oci::quay.io/enterprise-contract/ec-release-policy:konflux@sha256:59c6b95c02295edb7928ef187571d26d426993fd5aae0236a03c832afbd6072a&#34;],&#34;data&#34;: [&#34;git::github.com/release-engineering/rhtap-ec-policy//data?ref=67018469815ee9f81e47cfb54dae39d71ed5f389&#34;,&#34;oci::quay.io/konflux-ci/tekton-catalog/data-acceptable-bundles:latest@sha256:c75d0123e83efa6c182b6510c35982b48201143ce74a9a388680a0ee1aa4affb&#34;,&#34;oci::quay.io/konflux-ci/konflux-vanguard/data-acceptable-bundles:latest@sha256:0b31c7bc77a7463a1bc52f3d3625ef0e0e75443da7fd2de8005d7885282138ea&#34;,&#34;oci::quay.io/konflux-ci/integration-service-catalog/data-acceptable-bundles:latest@sha256:7b00455045ea3873a72caeb1e7ac7d036bd53963a26409891a4cc9d0d242b9fc&#34;],&#34;config&#34;: {&#34;include&#34;: [&#34;test&#34;]}}],&#34;publicKey&#34;: &#34;k8s://chains-e2e-vgkz/cosign-public-key&#34;},&#34;ec-version&#34;: &#34;v0.9.25&#34;,&#34;effective-time&#34;: &#34;2026-05-09T03:08:24.533952565Z&#34;}----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-010062891fae8a3e7e2933423c91e1bd-pod&#39;, container &#39;step-summary&#39;:&#xA;----- START -----{&#xA;  &#34;timestamp&#34;: &#34;1778296109&#34;,&#xA;  &#34;namespace&#34;: &#34;&#34;,&#xA;  &#34;successes&#34;: 5,&#xA;  &#34;failures&#34;: 1,&#xA;  &#34;warnings&#34;: 0,&#xA;  &#34;result&#34;: &#34;FAILURE&#34;&#xA;}&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-010062891fae8a3e7e2933423c91e1bd-pod&#39;, container &#39;step-version&#39;:&#xA;----- START -----Version            v0.9.25&#xA;Source ID          b345847182602d9a5ce9e957fa76fe02575c8018&#xA;Change date        2026-04-27 12:52:43 +0000 UTC (1 week ago)&#xA;ECC                v0.1.7&#xA;OPA                v1.15.2&#xA;Conftest           v0.68.2&#xA;Cosign             v3.0.4&#xA;Sigstore           v1.10.4&#xA;Rekor              v1.5.0&#xA;Tekton Pipeline    v1.9.2&#xA;Kubernetes Client  v0.35.0&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-010062891fae8a3e7e2933423c91e1bd-pod&#39;, container &#39;step-show-config&#39;:&#xA;----- START -----{&#xA;  &#34;policy&#34;: {&#xA;    &#34;name&#34;: &#34;Default&#34;,&#xA;    &#34;description&#34;: &#34;Includes rules for levels 1, 2 &amp; 3 of SLSA v0.1. This is the default config used for new Konflux applications. Source: https://github.com/conforma/config/blob/main/default/policy.yaml&#34;,&#xA;    &#34;sources&#34;: [&#xA;      {&#xA;        &#34;name&#34;: &#34;Default&#34;,&#xA;        &#34;policy&#34;: [&#xA;          &#34;oci::quay.io/enterprise-contract/ec-release-policy:konflux@sha256:59c6b95c02295edb7928ef187571d26d426993fd5aae0236a03c832afbd6072a&#34;&#xA;        ],&#xA;        &#34;data&#34;: [&#xA;          &#34;git::github.com/release-engineering/rhtap-ec-policy//data?ref=67018469815ee9f81e47cfb54dae39d71ed5f389&#34;,&#xA;          &#34;oci::quay.io/konflux-ci/tekton-catalog/data-acceptable-bundles:latest@sha256:c75d0123e83efa6c182b6510c35982b48201143ce74a9a388680a0ee1aa4affb&#34;,&#xA;          &#34;oci::quay.io/konflux-ci/konflux-vanguard/data-acceptable-bundles:latest@sha256:0b31c7bc77a7463a1bc52f3d3625ef0e0e75443da7fd2de8005d7885282138ea&#34;,&#xA;          &#34;oci::quay.io/konflux-ci/integration-service-catalog/data-acceptable-bundles:latest@sha256:7b00455045ea3873a72caeb1e7ac7d036bd53963a26409891a4cc9d0d242b9fc&#34;&#xA;        ],&#xA;        &#34;config&#34;: {&#xA;          &#34;include&#34;: [&#xA;            &#34;test&#34;&#xA;          ]&#xA;        }&#xA;      }&#xA;    ],&#xA;    &#34;publicKey&#34;: &#34;k8s://chains-e2e-vgkz/cosign-public-key&#34;&#xA;  },&#xA;  &#34;key&#34;: &#34;-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEAm/YE3MeVX+sgrHJZa0N2EIFu31M\nM4vPqV5IXONrtJRnu1NhnewrBCeRqpRvP5EMOZ1SO3nTppSW9eQ/1dJPbQ==\n-----END PUBLIC KEY-----\n&#34;,&#xA;  &#34;effective-time&#34;: &#34;2026-05-09T03:08:24.533952565Z&#34;&#xA;}&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-010062891fae8a3e7e2933423c91e1bd-pod&#39;, container &#39;step-detailed-report&#39;:&#xA;----- START -----Success: false&#xA;Result: FAILURE&#xA;Violations: 1, Warnings: 0, Successes: 5&#xA;Component: &#xA;ImageRef: quay.io/redhat-appstudio-qe/test-images@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#xA;&#xA;Results:&#xA;✕ [Violation] test.test_data_found&#xA;  ImageRef: quay.io/redhat-appstudio-qe/test-images@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#xA;  Reason: No test data found&#xA;  Title: Test data found in task results&#xA;  Description: Ensure that at least one of the tasks in the pipeline includes a TEST_OUTPUT task result, which is where Conforma&#xA;  expects to find test result data. To exclude this rule add &#34;test.test_data_found&#34; to the `exclude` section of the policy&#xA;  configuration.&#xA;  Solution: Confirm at least one task in the build pipeline contains a result named TEST_OUTPUT.&#xA;&#xA;For more information about policy issues, see the policy documentation: https://conforma.dev/docs/policy/&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-010062891fae8a3e7e2933423c91e1bd-pod&#39;, container &#39;step-assert&#39;:&#xA;----- START -----false&#xA;----- END -----&#xA;Make sure TaskRun verify-enterprise-contract of PipelineRun verify-enterprise-contract-run-9fpkw failed&#xA;&lt; Exit [It] fails when tests are not satisfied on strict mode - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:225 @ 05/09/26 03:08:32.307 (26.302s)&#xA;&gt; Enter [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 03:08:32.307&#xA;&lt; Exit [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 03:08:32.307 (0s)&#xA;</system-err>
          </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="passed" time="12.205914577">
              <system-err>&gt; Enter [BeforeEach] verify-enterprise-contract task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:154 @ 05/09/26 03:08:32.308&#xA;&lt; Exit [BeforeEach] verify-enterprise-contract task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:154 @ 05/09/26 03:08:32.33 (22ms)&#xA;&gt; Enter [It] fails when unexpected signature is used - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:251 @ 05/09/26 03:08:32.33&#xA;Create an unexpected public signing key&#xA;Creating Pipeline &#34;verify-enterprise-contract-run-h547p&#34;&#xA;Waiting for pipeline &#34;verify-enterprise-contract-run-h547p&#34; to finish&#xA;*** TaskRun status:&#xA;artifacts: {}&#xA;completionTime: &#34;2026-05-09T03:08:43Z&#34;&#xA;conditions:&#xA;- lastTransitionTime: &#34;2026-05-09T03:08:43Z&#34;&#xA;  message: &#39;&#34;step-assert&#34; exited with code 1: Error&#39;&#xA;  reason: Failed&#xA;  status: &#34;False&#34;&#xA;  type: Succeeded&#xA;podName: verify-enterprise-contract-626dca4452edc4e916d30d2d9d854f44-pod&#xA;provenance:&#xA;  featureFlags:&#xA;    awaitSidecarReadiness: true&#xA;    coschedule: workspaces&#xA;    enableAPIFields: alpha&#xA;    enableParamEnum: true&#xA;    enableProvenanceInStatus: true&#xA;    enforceNonfalsifiability: none&#xA;    maxResultSize: 4096&#xA;    resultExtractionMethod: termination-message&#xA;    runningInEnvWithInjectedSidecars: true&#xA;    verificationNoMatchPolicy: ignore&#xA;  refSource:&#xA;    digest:&#xA;      sha256: 7df8d121c09999d0376e189c1eb8a8263078aab697aa5ee966512f581427a6ce&#xA;    entryPoint: verify-enterprise-contract&#xA;    uri: quay.io/conforma/tekton-task&#xA;results:&#xA;- name: TEST_OUTPUT&#xA;  type: string&#xA;  value: |&#xA;    {&#34;timestamp&#34;:&#34;1778296121&#34;,&#34;namespace&#34;:&#34;&#34;,&#34;successes&#34;:0,&#34;failures&#34;:2,&#34;warnings&#34;:0,&#34;result&#34;:&#34;FAILURE&#34;}&#xA;startTime: &#34;2026-05-09T03:08:33Z&#34;&#xA;steps:&#xA;- container: step-initialize-tuf&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: initialize-tuf&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://32c20a99d3a8b4c981f2187cf4afabd0c83fb217ca8a47b4367f1098c9bb77d7&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:38Z&#34;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:38Z&#34;&#xA;  terminationReason: Skipped&#xA;- container: step-reduce&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: reduce&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://f29f8497d121afa6935ed5eb24f918d75b9e9e6f40da13ea976faf6e83f7fa1b&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:38Z&#34;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:38Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-validate&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: validate&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://183bfda81d2bcef7466095268dcd29ee2a02f042234d86760fdbf4dfb33d9841&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:41Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296121\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:0,\&#34;failures\&#34;:2,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:38Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-report-json&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: report-json&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://75a6df171bd8650590fd9c792f5bc5141fcfa3e39a21285db9b80fd87881bf2a&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:42Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296121\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:0,\&#34;failures\&#34;:2,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:42Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-summary&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: summary&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://11006343ec7883712b15497c03aba09586bcb7eae061fdea325f569d5d174cf6&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:42Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296121\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:0,\&#34;failures\&#34;:2,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:42Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-version&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: version&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://900e887812d3e6858bfe253a6a7e297581d5beebdb512131747947f50169d450&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:42Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296121\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:0,\&#34;failures\&#34;:2,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:42Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-show-config&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: show-config&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://b0c82415974c097f0e3104544fe957a04138b2f774ce85d2dbe73f76168f320e&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:42Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296121\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:0,\&#34;failures\&#34;:2,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:42Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-detailed-report&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: detailed-report&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://d42314cc4aac48b910991c2d603cb954ed61f4b246f3ed3a46602933dc1ac443&#xA;    exitCode: 0&#xA;    finishedAt: &#34;2026-05-09T03:08:42Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296121\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:0,\&#34;failures\&#34;:2,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Completed&#xA;    startedAt: &#34;2026-05-09T03:08:42Z&#34;&#xA;  terminationReason: Completed&#xA;- container: step-assert&#xA;  imageID: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;  name: assert&#xA;  provenance: {}&#xA;  terminated:&#xA;    containerID: cri-o://718545c97119cf923a5431dc08d090391fa7c6009ff397d4ab5909cb1e33f986&#xA;    exitCode: 1&#xA;    finishedAt: &#34;2026-05-09T03:08:42Z&#34;&#xA;    message: &#39;[{&#34;key&#34;:&#34;TEST_OUTPUT&#34;,&#34;value&#34;:&#34;{\&#34;timestamp\&#34;:\&#34;1778296121\&#34;,\&#34;namespace\&#34;:\&#34;\&#34;,\&#34;successes\&#34;:0,\&#34;failures\&#34;:2,\&#34;warnings\&#34;:0,\&#34;result\&#34;:\&#34;FAILURE\&#34;}\n&#34;,&#34;type&#34;:1}]&#39;&#xA;    reason: Error&#xA;    startedAt: &#34;2026-05-09T03:08:42Z&#34;&#xA;  terminationReason: Error&#xA;taskSpec:&#xA;  description: Verify the enterprise contract is met&#xA;  params:&#xA;  - description: |&#xA;      Spec section of an ApplicationSnapshot resource. Not all fields of the&#xA;      resource are required. A minimal example:&#xA;&#xA;      ```json&#xA;        {&#xA;          &#34;components&#34;: [&#xA;            {&#xA;              &#34;containerImage&#34;: &#34;quay.io/example/repo:latest&#34;&#xA;            }&#xA;          ]&#xA;        }&#xA;      ```&#xA;&#xA;      Each `containerImage` in the `components` array is validated.&#xA;    name: IMAGES&#xA;    type: string&#xA;  - default: enterprise-contract-service/default&#xA;    description: |&#xA;      Name of the policy configuration (EnterpriseContractPolicy&#xA;      resource) to use. `namespace/name` or `name` syntax supported. If&#xA;      namespace is omitted the namespace where the task runs is used.&#xA;      You can also specify a policy configuration using a git url, e.g.&#xA;      `github.com/conforma/config//slsa3`.&#xA;    name: POLICY_CONFIGURATION&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Public key used to verify traditional long-lived signatures. Must&#xA;      be a valid k8s cosign reference, e.g. k8s://my-space/my-secret where my-secret&#xA;      contains the expected cosign.pub attribute. Required for traditional signing&#xA;      key verification. Will be ignored if any of CERTIFICATE_IDENTITY, CERTIFICATE_IDENTITY_REGEXP,&#xA;      CERTIFICATE_OIDC_ISSUER, or CERTIFICATE_OIDC_ISSUER_REGEXP are provided.&#xA;    name: PUBLIC_KEY&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Rekor host for transparency log lookups&#xA;    name: REKOR_HOST&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Expected identity in the signing certificate for keyless verification.&#xA;      This should be the email or URI that was used when signing. You should provide&#xA;      both CERTIFICATE_OIDC_ISSUER and CERTIFICATE_IDENTITY for keyless verification.&#xA;      The PUBLIC_KEY param will be ignored if this is provided.&#xA;    name: CERTIFICATE_IDENTITY&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Expected OIDC issuer in the signing certificate for keyless verification.&#xA;      This should match the issuer that provided the identity token used for signing.&#xA;      You should provide both CERTIFICATE_OIDC_ISSUER and CERTIFICATE_IDENTITY for&#xA;      keyless verification. The PUBLIC_KEY param will be ignored if this is provided.&#xA;    name: CERTIFICATE_OIDC_ISSUER&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Similar to CERTIFICATE_IDENTITY but the value is a regexp that will&#xA;      be matched. Note that CERTIFICATE_IDENTITY takes precedence over this if both&#xA;      are present.&#xA;    name: CERTIFICATE_IDENTITY_REGEXP&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Similar to CERTIFICATE_OIDC_ISSUER but a regexp that will be matched.&#xA;      Note that CERTIFICATE_OIDC_ISSUER takes precedence over this if both are present.&#xA;    name: CERTIFICATE_OIDC_ISSUER_REGEXP&#xA;    type: string&#xA;  - default: &#34;false&#34;&#xA;    description: Skip Rekor transparency log checks during validation. Compatible&#xA;      with traditional signing secret signature checks only. If any of the CERTIFICATE_*&#xA;      keyless verification params are present, this value is disregarded and Rekor&#xA;      transparency log checks are included.&#xA;    name: IGNORE_REKOR&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: TUF mirror URL. Provide a value when NOT using public sigstore deployment.&#xA;    name: TUF_MIRROR&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: |&#xA;      Path to a directory containing SSL certs to be used when communicating&#xA;      with external services. This is useful when using the integrated registry&#xA;      and a local instance of Rekor on a development cluster which may use&#xA;      certificates issued by a not-commonly trusted root CA. In such cases,&#xA;      `/var/run/secrets/kubernetes.io/serviceaccount` is a good value. Multiple&#xA;      paths can be provided by using the `:` separator.&#xA;    name: SSL_CERT_DIR&#xA;    type: string&#xA;  - default: trusted-ca&#xA;    description: The name of the ConfigMap to read CA bundle data from.&#xA;    name: CA_TRUST_CONFIGMAP_NAME&#xA;    type: string&#xA;  - default: ca-bundle.crt&#xA;    description: The name of the key in the ConfigMap that contains the CA bundle&#xA;      data.&#xA;    name: CA_TRUST_CONFIG_MAP_KEY&#xA;    type: string&#xA;  - default: &#34;true&#34;&#xA;    description: Include rule titles and descriptions in the output. Set to `&#34;false&#34;`&#xA;      to disable it.&#xA;    name: INFO&#xA;    type: string&#xA;  - default: &#34;true&#34;&#xA;    description: Fail the task if policy fails. Set to `&#34;false&#34;` to disable it.&#xA;    name: STRICT&#xA;    type: string&#xA;  - default: /tekton/home&#xA;    description: Value for the HOME environment variable.&#xA;    name: HOMEDIR&#xA;    type: string&#xA;  - default: now&#xA;    description: Run policy checks with the provided time.&#xA;    name: EFFECTIVE_TIME&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: Merge additional Rego variables into the policy data. Use syntax&#xA;      &#34;key=value,key2=value2...&#34;&#xA;    name: EXTRA_RULE_DATA&#xA;    type: string&#xA;  - default: &#34;1&#34;&#xA;    description: Number of parallel workers to use for policy evaluation.&#xA;    name: WORKERS&#xA;    type: string&#xA;  - default: &#34;false&#34;&#xA;    description: Reduce the Snapshot to only the component whose build caused the&#xA;      Snapshot to be created&#xA;    name: SINGLE_COMPONENT&#xA;    type: string&#xA;  - default: unknown&#xA;    description: |&#xA;      Name, including kind, of the Kubernetes resource to query for labels when single component mode is enabled, e.g. pr/somepipeline.&#xA;    name: SINGLE_COMPONENT_CUSTOM_RESOURCE&#xA;    type: string&#xA;  - default: &#34;&#34;&#xA;    description: |&#xA;      Kubernetes namespace where the SINGLE_COMPONENT_NAME is found. Only used when single component mode is enabled.&#xA;    name: SINGLE_COMPONENT_CUSTOM_RESOURCE_NS&#xA;    type: string&#xA;  - default: 1s&#xA;    description: Base duration for exponential backoff calculation (e.g., &#34;1s&#34;, &#34;500ms&#34;)&#xA;    name: RETRY_DURATION&#xA;    type: string&#xA;  - default: &#34;2.0&#34;&#xA;    description: Exponential backoff multiplier (e.g., &#34;2.0&#34;, &#34;1.5&#34;)&#xA;    name: RETRY_FACTOR&#xA;    type: string&#xA;  - default: &#34;0.1&#34;&#xA;    description: Randomness factor for backoff calculation (0.0-1.0, e.g., &#34;0.1&#34;,&#xA;      &#34;0.2&#34;)&#xA;    name: RETRY_JITTER&#xA;    type: string&#xA;  - default: &#34;3&#34;&#xA;    description: Maximum number of retry attempts&#xA;    name: RETRY_MAX_RETRY&#xA;    type: string&#xA;  - default: 3s&#xA;    description: Maximum wait time between retries (e.g., &#34;3s&#34;, &#34;10s&#34;)&#xA;    name: RETRY_MAX_WAIT&#xA;    type: string&#xA;  results:&#xA;  - description: Short summary of the policy evaluation for each image&#xA;    name: TEST_OUTPUT&#xA;    type: string&#xA;  stepTemplate:&#xA;    computeResources: {}&#xA;    env:&#xA;    - name: HOME&#xA;      value: /tekton/home&#xA;  steps:&#xA;  - args:&#xA;    - sigstore&#xA;    - initialize&#xA;    - --mirror&#xA;    - &#34;&#34;&#xA;    - --root&#xA;    - /root.json&#xA;    command:&#xA;    - ec&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: initialize-tuf&#xA;    when:&#xA;    - operator: notin&#xA;      values:&#xA;      - &#34;&#34;&#xA;  - command:&#xA;    - reduce-snapshot.sh&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    env:&#xA;    - name: SNAPSHOT&#xA;      value: &#39;{&#34;application&#34;:&#34;&#34;,&#34;componentGroup&#34;:&#34;&#34;,&#34;components&#34;:[{&#34;name&#34;:&#34;&#34;,&#34;version&#34;:&#34;&#34;,&#34;containerImage&#34;:&#34;quay.io/redhat-appstudio-qe/test-images:buildah-demo-pufrqqgxeq@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#34;,&#34;source&#34;:{}}],&#34;artifacts&#34;:{}}&#39;&#xA;    - name: SINGLE_COMPONENT&#xA;      value: &#34;false&#34;&#xA;    - name: CUSTOM_RESOURCE&#xA;      value: unknown&#xA;    - name: CUSTOM_RESOURCE_NAMESPACE&#xA;    - name: SNAPSHOT_PATH&#xA;      value: /tekton/home/snapshot.json&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: reduce&#xA;    onError: continue&#xA;  - computeResources:&#xA;      limits:&#xA;        memory: 2Gi&#xA;      requests:&#xA;        cpu: 1800m&#xA;        memory: 2Gi&#xA;    env:&#xA;    - name: POLICY_CONFIGURATION&#xA;      value: ec-policy&#xA;    - name: PUBLIC_KEY&#xA;      value: k8s://chains-e2e-vgkz/dummy-public-key-gvvsvncyrp&#xA;    - name: CERTIFICATE_IDENTITY&#xA;    - name: CERTIFICATE_OIDC_ISSUER&#xA;    - name: CERTIFICATE_IDENTITY_REGEXP&#xA;    - name: CERTIFICATE_OIDC_ISSUER_REGEXP&#xA;    - name: REKOR_HOST&#xA;    - name: IGNORE_REKOR&#xA;      value: &#34;true&#34;&#xA;    - name: WORKERS&#xA;      value: &#34;1&#34;&#xA;    - name: INFO&#xA;      value: &#34;true&#34;&#xA;    - name: EFFECTIVE_TIME&#xA;      value: now&#xA;    - name: EXTRA_RULE_DATA&#xA;    - name: RETRY_MAX_WAIT&#xA;      value: 3s&#xA;    - name: RETRY_MAX_RETRY&#xA;      value: &#34;3&#34;&#xA;    - name: RETRY_DURATION&#xA;      value: 1s&#xA;    - name: RETRY_FACTOR&#xA;      value: &#34;2.0&#34;&#xA;    - name: RETRY_JITTER&#xA;      value: &#34;0.1&#34;&#xA;    - name: HOMEDIR&#xA;      value: /tekton/home&#xA;    - name: SSL_CERT_DIR&#xA;      value: /tekton-custom-certs:/etc/ssl/certs:/etc/pki/tls/certs:/system/etc/security/cacerts:/var/run/secrets/kubernetes.io/serviceaccount&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: validate&#xA;    onError: continue&#xA;    script: |&#xA;      #!/bin/bash&#xA;      set -euo pipefail&#xA;&#xA;      cmd_args=(&#xA;        validate&#xA;        image&#xA;        --images=&#34;${HOMEDIR}/snapshot.json&#34;&#xA;        --policy=&#34;${POLICY_CONFIGURATION}&#34;&#xA;      )&#xA;&#xA;      # To keep bash logic as thin as possible we deliberately don&#39;t sanitize&#xA;      # these params. If something is wrong or missing let Conforma handle it.&#xA;&#xA;      if [ -n &#34;${CERTIFICATE_IDENTITY}&#34; ] || \&#xA;         [ -n &#34;${CERTIFICATE_OIDC_ISSUER}&#34; ] || \&#xA;         [ -n &#34;${CERTIFICATE_IDENTITY_REGEXP}&#34; ] || \&#xA;         [ -n &#34;${CERTIFICATE_OIDC_ISSUER_REGEXP}&#34; ]; then&#xA;        # If *any* of the above are non-empty assume the intention is to&#xA;        # try keyless verification&#xA;&#xA;        if [ -n &#34;${CERTIFICATE_IDENTITY}&#34; ]; then&#xA;          cmd_args+=(&#xA;            --certificate-identity=&#34;${CERTIFICATE_IDENTITY}&#34;&#xA;          )&#xA;        elif [ -n &#34;${CERTIFICATE_IDENTITY_REGEXP}&#34; ]; then&#xA;          cmd_args+=(&#xA;            --certificate-identity-regexp=&#34;${CERTIFICATE_IDENTITY_REGEXP}&#34;&#xA;          )&#xA;        fi&#xA;&#xA;        if [ -n &#34;${CERTIFICATE_OIDC_ISSUER}&#34; ]; then&#xA;          cmd_args+=(&#xA;            --certificate-oidc-issuer=&#34;${CERTIFICATE_OIDC_ISSUER}&#34;&#xA;          )&#xA;        elif [ -n &#34;${CERTIFICATE_OIDC_ISSUER_REGEXP}&#34; ]; then&#xA;          cmd_args+=(&#xA;            --certificate-oidc-issuer-regexp=&#34;${CERTIFICATE_OIDC_ISSUER_REGEXP}&#34;&#xA;          )&#xA;        fi&#xA;&#xA;        # Force --ignore-rekor to false since we need rekor&#xA;        cmd_args+=(&#xA;          --ignore-rekor=false&#xA;        )&#xA;      else&#xA;        # Assume traditional signing secret verification&#xA;        cmd_args+=(&#xA;          --public-key=&#34;${PUBLIC_KEY}&#34;&#xA;          --ignore-rekor=&#34;${IGNORE_REKOR}&#34;&#xA;        )&#xA;      fi&#xA;&#xA;      cmd_args+=(&#xA;        --rekor-url=&#34;${REKOR_HOST}&#34;&#xA;        --workers=&#34;${WORKERS}&#34;&#xA;        --info=&#34;${INFO}&#34;&#xA;        --timeout=0&#xA;        --strict=false&#xA;        --show-successes=true&#xA;        --show-policy-docs-link=true&#xA;        --effective-time=&#34;${EFFECTIVE_TIME}&#34;&#xA;        --extra-rule-data=&#34;${EXTRA_RULE_DATA}&#34;&#xA;        --retry-max-wait=&#34;${RETRY_MAX_WAIT}&#34;&#xA;        --retry-max-retry=&#34;${RETRY_MAX_RETRY}&#34;&#xA;        --retry-duration=&#34;${RETRY_DURATION}&#34;&#xA;        --retry-factor=&#34;${RETRY_FACTOR}&#34;&#xA;        --retry-jitter=&#34;${RETRY_JITTER}&#34;&#xA;        --output=&#34;text=${HOMEDIR}/text-report.txt?show-successes=false&#34;&#xA;        --output=&#34;json=${HOMEDIR}/report-json.json&#34;&#xA;        --output=&#34;appstudio=/tekton/results/TEST_OUTPUT&#34;&#xA;      )&#xA;&#xA;&#xA;      # Execute Conforma with constructed arguments&#xA;      exec ec &#34;${cmd_args[@]}&#34;&#xA;    volumeMounts:&#xA;    - mountPath: /etc/pki/tls/certs/ca-custom-bundle.crt&#xA;      name: trusted-ca&#xA;      readOnly: true&#xA;      subPath: ca-bundle.crt&#xA;  - args:&#xA;    - jq . /tekton/home/report-json.json | awk &#39;{gsub(/^ +/, &#34;&#34;); acc += length; if&#xA;      (acc &gt;= 8000) { printf &#34;\n&#34;; acc=length } printf $0 }&#39;&#xA;    command:&#xA;    - sh&#xA;    - -c&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: report-json&#xA;    onError: continue&#xA;  - args:&#xA;    - .&#xA;    - /tekton/results/TEST_OUTPUT&#xA;    command:&#xA;    - jq&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: summary&#xA;    onError: continue&#xA;  - args:&#xA;    - version&#xA;    command:&#xA;    - ec&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: version&#xA;  - args:&#xA;    - &#39;{policy: .policy, key: .key, &#34;effective-time&#34;: .[&#34;effective-time&#34;]}&#39;&#xA;    - /tekton/home/report-json.json&#xA;    command:&#xA;    - jq&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: show-config&#xA;  - args:&#xA;    - /tekton/home/text-report.txt&#xA;    command:&#xA;    - cat&#xA;    computeResources: {}&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: detailed-report&#xA;    onError: continue&#xA;  - args:&#xA;    - --argjson&#xA;    - strict&#xA;    - &#34;true&#34;&#xA;    - -e&#xA;    - |&#xA;      .result == &#34;SUCCESS&#34; or .result == &#34;WARNING&#34; or ($strict | not)&#xA;    - /tekton/results/TEST_OUTPUT&#xA;    command:&#xA;    - jq&#xA;    computeResources:&#xA;      limits:&#xA;        memory: 256Mi&#xA;      requests:&#xA;        cpu: 100m&#xA;        memory: 256Mi&#xA;    image: quay.io/conforma/cli@sha256:2f5bed7fd51f678ea960aaf5bed033412b7d207a83bb1b02b108be5ca71a058d&#xA;    name: assert&#xA;  volumes:&#xA;  - configMap:&#xA;      items:&#xA;      - key: ca-bundle.crt&#xA;        path: ca-bundle.crt&#xA;      name: trusted-ca&#xA;      optional: true&#xA;    name: trusted-ca&#xA;  workspaces:&#xA;  - description: The workspace where the snapshot spec json file resides&#xA;    name: data&#xA;    optional: true&#xA;&#xA;*** Logs from pod &#39;verify-enterprise-contract-626dca4452edc4e916d30d2d9d854f44-pod&#39;, container &#39;step-initialize-tuf&#39;:&#xA;----- START -----2026/05/09 03:08:38 INFO Step was skipped due to when expressions were evaluated to false.&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-626dca4452edc4e916d30d2d9d854f44-pod&#39;, container &#39;step-reduce&#39;:&#xA;----- START -----Single Component mode? false&#xA;{&#xA;  &#34;application&#34;: &#34;&#34;,&#xA;  &#34;componentGroup&#34;: &#34;&#34;,&#xA;  &#34;components&#34;: [&#xA;    {&#xA;      &#34;name&#34;: &#34;&#34;,&#xA;      &#34;version&#34;: &#34;&#34;,&#xA;      &#34;containerImage&#34;: &#34;quay.io/redhat-appstudio-qe/test-images:buildah-demo-pufrqqgxeq@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#34;,&#xA;      &#34;source&#34;: {}&#xA;    }&#xA;  ],&#xA;  &#34;artifacts&#34;: {}&#xA;}&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-626dca4452edc4e916d30d2d9d854f44-pod&#39;, container &#39;step-validate&#39;:&#xA;----- START ---------- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-626dca4452edc4e916d30d2d9d854f44-pod&#39;, container &#39;step-report-json&#39;:&#xA;----- START -----{&#34;success&#34;: false,&#34;components&#34;: [{&#34;name&#34;: &#34;&#34;,&#34;containerImage&#34;: &#34;quay.io/redhat-appstudio-qe/test-images@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#34;,&#34;source&#34;: {},&#34;violations&#34;: [{&#34;msg&#34;: &#34;No image attestations found matching the given public key. Verify the correct public key was provided, and one or more attestations were created. Error: no matching attestations: accepted signatures do not match threshold, Found: 0, Expected 1&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.signature_check&#34;,&#34;description&#34;: &#34;The attestation signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Attestation signature check passed&#34;}},{&#34;msg&#34;: &#34;No image signatures found matching the given public key. Verify the correct public key was provided, and a signature was created. Error: no matching signatures: invalid signature when validating ASN.1 encoded signature\n invalid signature when validating ASN.1 encoded signature\n invalid signature when validating ASN.1 encoded signature&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.image.signature_check&#34;,&#34;description&#34;: &#34;The image signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Image signature check passed&#34;}}],&#34;success&#34;: false}],&#34;key&#34;: &#34;-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAENZxkE/d0fKvJ51dXHQmxXaRMTtVz\nBQWcmJD/7pcMDEmBcmk8O1yUPIiFj5TMZqabjS9CQQN+jKHG+Bfi0BYlHg==\n-----END PUBLIC KEY-----\n&#34;,&#34;policy&#34;: {&#34;name&#34;: &#34;Default&#34;,&#34;description&#34;: &#34;Includes rules for levels 1, 2 &amp; 3 of SLSA v0.1. This is the default config used for new Konflux applications. Source: https://github.com/conforma/config/blob/main/default/policy.yaml&#34;,&#34;sources&#34;: [{&#34;name&#34;: &#34;Default&#34;,&#34;policy&#34;: [&#34;oci::quay.io/enterprise-contract/ec-release-policy:konflux@sha256:59c6b95c02295edb7928ef187571d26d426993fd5aae0236a03c832afbd6072a&#34;],&#34;data&#34;: [&#34;git::github.com/release-engineering/rhtap-ec-policy//data?ref=67018469815ee9f81e47cfb54dae39d71ed5f389&#34;,&#34;oci::quay.io/konflux-ci/tekton-catalog/data-acceptable-bundles:latest@sha256:c75d0123e83efa6c182b6510c35982b48201143ce74a9a388680a0ee1aa4affb&#34;,&#34;oci::quay.io/konflux-ci/konflux-vanguard/data-acceptable-bundles:latest@sha256:0b31c7bc77a7463a1bc52f3d3625ef0e0e75443da7fd2de8005d7885282138ea&#34;,&#34;oci::quay.io/konflux-ci/integration-service-catalog/data-acceptable-bundles:latest@sha256:7b00455045ea3873a72caeb1e7ac7d036bd53963a26409891a4cc9d0d242b9fc&#34;],&#34;config&#34;: {&#34;include&#34;: [&#34;slsa_provenance_available&#34;]}}],&#34;publicKey&#34;: &#34;k8s://chains-e2e-vgkz/dummy-public-key-gvvsvncyrp&#34;},&#34;ec-version&#34;: &#34;v0.9.25&#34;,&#34;effective-time&#34;: &#34;2026-05-09T03:08:38.722660653Z&#34;}----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-626dca4452edc4e916d30d2d9d854f44-pod&#39;, container &#39;step-summary&#39;:&#xA;----- START -----{&#xA;  &#34;timestamp&#34;: &#34;1778296121&#34;,&#xA;  &#34;namespace&#34;: &#34;&#34;,&#xA;  &#34;successes&#34;: 0,&#xA;  &#34;failures&#34;: 2,&#xA;  &#34;warnings&#34;: 0,&#xA;  &#34;result&#34;: &#34;FAILURE&#34;&#xA;}&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-626dca4452edc4e916d30d2d9d854f44-pod&#39;, container &#39;step-version&#39;:&#xA;----- START -----Version            v0.9.25&#xA;Source ID          b345847182602d9a5ce9e957fa76fe02575c8018&#xA;Change date        2026-04-27 12:52:43 +0000 UTC (1 week ago)&#xA;ECC                v0.1.7&#xA;OPA                v1.15.2&#xA;Conftest           v0.68.2&#xA;Cosign             v3.0.4&#xA;Sigstore           v1.10.4&#xA;Rekor              v1.5.0&#xA;Tekton Pipeline    v1.9.2&#xA;Kubernetes Client  v0.35.0&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-626dca4452edc4e916d30d2d9d854f44-pod&#39;, container &#39;step-show-config&#39;:&#xA;----- START -----{&#xA;  &#34;policy&#34;: {&#xA;    &#34;name&#34;: &#34;Default&#34;,&#xA;    &#34;description&#34;: &#34;Includes rules for levels 1, 2 &amp; 3 of SLSA v0.1. This is the default config used for new Konflux applications. Source: https://github.com/conforma/config/blob/main/default/policy.yaml&#34;,&#xA;    &#34;sources&#34;: [&#xA;      {&#xA;        &#34;name&#34;: &#34;Default&#34;,&#xA;        &#34;policy&#34;: [&#xA;          &#34;oci::quay.io/enterprise-contract/ec-release-policy:konflux@sha256:59c6b95c02295edb7928ef187571d26d426993fd5aae0236a03c832afbd6072a&#34;&#xA;        ],&#xA;        &#34;data&#34;: [&#xA;          &#34;git::github.com/release-engineering/rhtap-ec-policy//data?ref=67018469815ee9f81e47cfb54dae39d71ed5f389&#34;,&#xA;          &#34;oci::quay.io/konflux-ci/tekton-catalog/data-acceptable-bundles:latest@sha256:c75d0123e83efa6c182b6510c35982b48201143ce74a9a388680a0ee1aa4affb&#34;,&#xA;          &#34;oci::quay.io/konflux-ci/konflux-vanguard/data-acceptable-bundles:latest@sha256:0b31c7bc77a7463a1bc52f3d3625ef0e0e75443da7fd2de8005d7885282138ea&#34;,&#xA;          &#34;oci::quay.io/konflux-ci/integration-service-catalog/data-acceptable-bundles:latest@sha256:7b00455045ea3873a72caeb1e7ac7d036bd53963a26409891a4cc9d0d242b9fc&#34;&#xA;        ],&#xA;        &#34;config&#34;: {&#xA;          &#34;include&#34;: [&#xA;            &#34;slsa_provenance_available&#34;&#xA;          ]&#xA;        }&#xA;      }&#xA;    ],&#xA;    &#34;publicKey&#34;: &#34;k8s://chains-e2e-vgkz/dummy-public-key-gvvsvncyrp&#34;&#xA;  },&#xA;  &#34;key&#34;: &#34;-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAENZxkE/d0fKvJ51dXHQmxXaRMTtVz\nBQWcmJD/7pcMDEmBcmk8O1yUPIiFj5TMZqabjS9CQQN+jKHG+Bfi0BYlHg==\n-----END PUBLIC KEY-----\n&#34;,&#xA;  &#34;effective-time&#34;: &#34;2026-05-09T03:08:38.722660653Z&#34;&#xA;}&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-626dca4452edc4e916d30d2d9d854f44-pod&#39;, container &#39;step-detailed-report&#39;:&#xA;----- START -----Success: false&#xA;Result: FAILURE&#xA;Violations: 2, Warnings: 0, Successes: 0&#xA;Component: &#xA;ImageRef: quay.io/redhat-appstudio-qe/test-images@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#xA;&#xA;Results:&#xA;✕ [Violation] builtin.attestation.signature_check&#xA;  ImageRef: quay.io/redhat-appstudio-qe/test-images@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#xA;  Reason: No image attestations found matching the given public key. Verify the correct public key was provided, and one or more&#xA;  attestations were created. Error: no matching attestations: accepted signatures do not match threshold, Found: 0, Expected 1&#xA;  Title: Attestation signature check passed&#xA;  Description: The attestation signature matches available signing materials.&#xA;&#xA;✕ [Violation] builtin.image.signature_check&#xA;  ImageRef: quay.io/redhat-appstudio-qe/test-images@sha256:918929ce19749fd530ffbbdb6bd48b9891eb308a81a0799956534a3297c78ba2&#xA;  Reason: No image signatures found matching the given public key. Verify the correct public key was provided, and a signature was&#xA;  created. Error: no matching signatures: invalid signature when validating ASN.1 encoded signature&#xA;   invalid signature when validating ASN.1 encoded signature&#xA;   invalid signature when validating ASN.1 encoded signature&#xA;  Title: Image signature check passed&#xA;  Description: The image signature matches available signing materials.&#xA;&#xA;For more information about policy issues, see the policy documentation: https://conforma.dev/docs/policy/&#xA;----- END -----&#xA;*** Logs from pod &#39;verify-enterprise-contract-626dca4452edc4e916d30d2d9d854f44-pod&#39;, container &#39;step-assert&#39;:&#xA;----- START -----false&#xA;----- END -----&#xA;Make sure TaskRun verify-enterprise-contract of PipelineRun verify-enterprise-contract-run-h547p failed&#xA;&lt; Exit [It] fails when unexpected signature is used - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:251 @ 05/09/26 03:08:44.513 (12.183s)&#xA;&gt; Enter [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 03:08:44.514&#xA;&lt; Exit [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 03:08:44.514 (0s)&#xA;</system-err>
          </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="passed" time="15.111927667">
              <system-err>&gt; Enter [BeforeEach] verify-enterprise-contract task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:154 @ 05/09/26 03:08:44.514&#xA;&lt; Exit [BeforeEach] verify-enterprise-contract task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:154 @ 05/09/26 03:08:44.53 (15ms)&#xA;&gt; Enter [It] verifies ec cli has error handling - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:279 @ 05/09/26 03:08:44.53&#xA;Creating Pipeline &#34;verify-enterprise-contract-run-vlsv7&#34;&#xA;Waiting for pipeline &#34;verify-enterprise-contract-run-vlsv7&#34; to finish&#xA;*** Logs from pod &#39;verify-enterprise-contract-69f6cd130b4e1ead486b1ee17d8f9d8d-pod&#39;, container &#39;step-report-json&#39;:&#xA;----- START -----{&#34;success&#34;: false,&#34;components&#34;: [{&#34;name&#34;: &#34;&#34;,&#34;containerImage&#34;: &#34;quay.io/konflux-ci/ec-golden-image@sha256:f1f3150e87adfcf44f0ea5fa468d4fe93b80e2c0d49ee31580407a5f1208d0a2&#34;,&#34;source&#34;: {},&#34;violations&#34;: [{&#34;msg&#34;: &#34;No image attestations found matching the given public key. Verify the correct public key was provided, and one or more attestations were created. Error: no matching attestations: accepted signatures do not match threshold, Found: 0, Expected 1&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.signature_check&#34;,&#34;description&#34;: &#34;The attestation signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Attestation signature check passed&#34;}},{&#34;msg&#34;: &#34;No image signatures found matching the given public key. Verify the correct public key was provided, and a signature was created. Error: no matching signatures: invalid signature when validating ASN.1 encoded signature&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.image.signature_check&#34;,&#34;description&#34;: &#34;The image signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Image signature check passed&#34;}}],&#34;success&#34;: false},{&#34;name&#34;: &#34;-sha256:c100497badd3edd2f02b294411b511396e71caf701f4df45db448e6cdbc686b0-amd64&#34;,&#34;containerImage&#34;: &#34;quay.io/konflux-ci/ec-golden-image@sha256:c100497badd3edd2f02b294411b511396e71caf701f4df45db448e6cdbc686b0&#34;,&#34;source&#34;: {},&#34;violations&#34;: [{&#34;msg&#34;: &#34;No image attestations found matching the given public key. Verify the correct public key was provided, and one or more attestations were created. Error: no matching attestations: accepted signatures do not match threshold, Found: 0, Expected 1&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.signature_check&#34;,&#34;description&#34;: &#34;The attestation signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Attestation signature check passed&#34;}},{&#34;msg&#34;: &#34;No image signatures found matching the given public key. Verify the correct public key was provided, and a signature was created. Error: no matching signatures: invalid signature when validating ASN.1 encoded signature\n invalid signature when validating ASN.1 encoded signature&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.image.signature_check&#34;,&#34;description&#34;: &#34;The image signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Image signature check passed&#34;}}],&#34;success&#34;: false},{&#34;name&#34;: &#34;-sha256:9024c5db8db1fa036f7c56020829f0e239db7b660d5e5f6439af84ab66489d63-arm64&#34;,&#34;containerImage&#34;: &#34;quay.io/konflux-ci/ec-golden-image@sha256:9024c5db8db1fa036f7c56020829f0e239db7b660d5e5f6439af84ab66489d63&#34;,&#34;source&#34;: {},&#34;violations&#34;: [{&#34;msg&#34;: &#34;No image attestations found matching the given public key. Verify the correct public key was provided, and one or more attestations were created. Error: no matching attestations: accepted signatures do not match threshold, Found: 0, Expected 1&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.signature_check&#34;,&#34;description&#34;: &#34;The attestation signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Attestation signature check passed&#34;}},{&#34;msg&#34;: &#34;No image signatures found matching the given public key. Verify the correct public key was provided, and a signature was created. Error: no matching signatures: invalid signature when validating ASN.1 encoded signature\n invalid signature when validating ASN.1 encoded signature&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.image.signature_check&#34;,&#34;description&#34;: &#34;The image signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Image signature check passed&#34;}}],&#34;success&#34;: false}],&#34;key&#34;: &#34;-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEAm/YE3MeVX+sgrHJZa0N2EIFu31M\nM4vPqV5IXONrtJRnu1NhnewrBCeRqpRvP5EMOZ1SO3nTppSW9eQ/1dJPbQ==\n-----END PUBLIC KEY-----\n&#34;,&#34;policy&#34;: {&#34;name&#34;: &#34;Default&#34;,&#34;description&#34;: &#34;Includes rules for levels 1, 2 &amp; 3 of SLSA v0.1. This is the default config used for new Konflux applications. Source: https://github.com/conforma/config/blob/main/default/policy.yaml&#34;,&#34;sources&#34;: [{&#34;name&#34;: &#34;Default&#34;,&#34;policy&#34;: [&#34;oci::quay.io/enterprise-contract/ec-release-policy:konflux@sha256:59c6b95c02295edb7928ef187571d26d426993fd5aae0236a03c832afbd6072a&#34;],&#34;data&#34;: [&#34;git::github.com/release-engineering/rhtap-ec-policy//data?ref=67018469815ee9f81e47cfb54dae39d71ed5f389&#34;,&#34;oci::quay.io/konflux-ci/tekton-catalog/data-acceptable-bundles:latest@sha256:c75d0123e83efa6c182b6510c35982b48201143ce74a9a388680a0ee1aa4affb&#34;,&#34;oci::quay.io/konflux-ci/konflux-vanguard/data-acceptable-bundles:latest@sha256:0b31c7bc77a7463a1bc52f3d3625ef0e0e75443da7fd2de8005d7885282138ea&#34;,&#34;oci::quay.io/konflux-ci/integration-service-catalog/data-acceptable-bundles:latest@sha256:7b00455045ea3873a72caeb1e7ac7d036bd53963a26409891a4cc9d0d242b9fc&#34;],&#34;config&#34;: {&#34;include&#34;: [&#34;slsa_provenance_available&#34;]}}],&#34;publicKey&#34;: &#34;k8s://chains-e2e-vgkz/cosign-public-key&#34;},&#34;ec-version&#34;: &#34;v0.9.25&#34;,&#34;effective-time&#34;: &#34;2026-05-09T03:08:52.03024427Z&#34;}----- END -----&#xA;&lt; Exit [It] verifies ec cli has error handling - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:279 @ 05/09/26 03:08:59.626 (15.096s)&#xA;&gt; Enter [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 03:08:59.626&#xA;&lt; Exit [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 03:08:59.626 (0s)&#xA;</system-err>
          </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="passed" time="18.107500651">
              <system-err>&gt; Enter [BeforeEach] verify-enterprise-contract task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:154 @ 05/09/26 03:08:59.627&#xA;&lt; Exit [BeforeEach] verify-enterprise-contract task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:154 @ 05/09/26 03:08:59.639 (12ms)&#xA;&gt; Enter [It] verifies ec validate accepts a list of image references - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:301 @ 05/09/26 03:08:59.639&#xA;Update public key to verify golden images&#xA;Creating Pipeline &#34;verify-enterprise-contract-run-bj66w&#34;&#xA;Waiting for pipeline &#34;verify-enterprise-contract-run-bj66w&#34; to finish&#xA;*** Logs from pod &#39;verify-enterprise-contract-34678e3c13556586b1136057dad63c59-pod&#39;, container &#39;step-report-json&#39;:&#xA;----- START -----{&#34;success&#34;: true,&#34;components&#34;: [{&#34;name&#34;: &#34;&#34;,&#34;containerImage&#34;: &#34;quay.io/konflux-ci/ec-golden-image@sha256:f1f3150e87adfcf44f0ea5fa468d4fe93b80e2c0d49ee31580407a5f1208d0a2&#34;,&#34;source&#34;: {},&#34;successes&#34;: [{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;attestation_type.known_attestation_type&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;slsa3&#34;],&#34;depends_on&#34;: [&#34;attestation_type.pipelinerun_attestation_found&#34;],&#34;description&#34;: &#34;Confirm the attestation found for the image has a known attestation type.&#34;,&#34;title&#34;: &#34;Known attestation type found&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;attestation_type.pipelinerun_attestation_found&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;slsa3&#34;],&#34;description&#34;: &#34;Confirm at least one PipelineRun attestation is present.&#34;,&#34;title&#34;: &#34;PipelineRun attestation found&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.signature_check&#34;,&#34;description&#34;: &#34;The attestation signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Attestation signature check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.syntax_check&#34;,&#34;description&#34;: &#34;The attestation has correct syntax.&#34;,&#34;title&#34;: &#34;Attestation syntax check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.image.signature_check&#34;,&#34;description&#34;: &#34;The image signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Image signature check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_build_service.allowed_builder_ids_provided&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;policy_data&#34;],&#34;description&#34;: &#34;Confirm the `allowed_builder_ids` rule data was provided, since it is required by the policy rules in this package.&#34;,&#34;title&#34;: &#34;Allowed builder IDs provided&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_build_service.slsa_builder_id_accepted&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the attestation attribute predicate.builder.id is set to one of the values in the `allowed_builder_ids` rule data, e.g. \&#34;https://tekton.dev/chains/v2\&#34;.&#34;,&#34;title&#34;: &#34;SLSA Builder ID is known and accepted&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_build_service.slsa_builder_id_found&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the attestation attribute predicate.builder.id is set.&#34;,&#34;title&#34;: &#34;SLSA Builder ID found&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_scripted_build.build_script_used&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the predicate.buildConfig.tasks.steps attribute for the task responsible for building and pushing the image is not empty.&#34;,&#34;title&#34;: &#34;Build task contains steps&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_scripted_build.build_task_image_results_found&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Confirm that a build task exists and it has the expected IMAGE_DIGEST and IMAGE_URL task results.&#34;,&#34;title&#34;: &#34;Build task set image digest and url task results&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_scripted_build.subject_build_task_matches&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify the subject of the attestations matches the IMAGE_DIGEST and IMAGE_URL values from the build task.&#34;,&#34;title&#34;: &#34;Provenance subject matches build task image result&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_provenance_available.allowed_predicate_types_provided&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;policy_data&#34;],&#34;description&#34;: &#34;Confirm the `allowed_predicate_types` rule data was provided, since it is required by the policy rules in this package.&#34;,&#34;title&#34;: &#34;Allowed predicate types provided&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_provenance_available.attestation_predicate_type_accepted&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the predicateType field of the attestation indicates the in-toto SLSA Provenance format was used to attest the PipelineRun.&#34;,&#34;title&#34;: &#34;Expected attestation predicate type found&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_correlated.attested_source_code_reference&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Attestation contains source reference.&#34;,&#34;title&#34;: &#34;Source reference&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_correlated.expected_source_code_reference&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the provided source code reference is the one being attested.&#34;,&#34;title&#34;: &#34;Expected source code reference&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_correlated.rule_data_provided&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;policy_data&#34;],&#34;description&#34;: &#34;Confirm the expected rule data keys have been provided in the expected format. The keys are `supported_vcs` and `supported_digests`.&#34;,&#34;title&#34;: &#34;Rule data provided&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_version_controlled.materials_format_okay&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Confirm at least one entry in the predicate.materials array of the attestation contains the expected attributes: uri and digest.sha1.&#34;,&#34;title&#34;: &#34;Materials have uri and digest&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_version_controlled.materials_include_git_sha&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Ensure that each entry in the predicate.materials array with a SHA-1 digest includes a valid Git commit SHA.&#34;,&#34;title&#34;: &#34;Materials include git commit shas&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_version_controlled.materials_uri_is_git_repo&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Ensure each entry in the predicate.materials array with a SHA-1 digest includes a valid Git URI.&#34;,&#34;title&#34;: &#34;Material uri is a git repo&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;tasks.pipeline_has_tasks&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;slsa3&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Ensure that at least one Task is present in the PipelineRun attestation.&#34;,&#34;title&#34;: &#34;Pipeline run includes at least one task&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;tasks.successful_pipeline_tasks&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;slsa3&#34;],&#34;depends_on&#34;: [&#34;tasks.pipeline_has_tasks&#34;],&#34;description&#34;: &#34;Ensure that all of the Tasks in the Pipeline completed successfully. Note that skipped Tasks are not taken into account and do not influence the outcome.&#34;,&#34;title&#34;: &#34;Successful pipeline tasks&#34;}}],&#34;success&#34;: true,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;&#34;,&#34;sig&#34;: &#34;MEQCIBq18yWVAorXyPPujnxOZ8mHF27hiJQ6EAno4Tjv33YSAiAcU67ZBZRjdijTh/A/83Fk9Ixw85yDTJBi/oDjYPGgMA==&#34;}],&#34;attestations&#34;: [{&#34;type&#34;: &#34;https://in-toto.io/Statement/v0.1&#34;,&#34;predicateType&#34;: &#34;https://slsa.dev/provenance/v0.2&#34;,&#34;predicateBuildType&#34;: &#34;tekton.dev/v1/PipelineRun&#34;,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;SHA256:IhiN7gY+Z3uSSd7tmj6w5Zfhqafzdhm3DZjIvGc6iYY&#34;,&#34;sig&#34;: &#34;MEUCIB3dH/CuxExH77jGOhngRyCwsNeug1KyBLQKKWqW0qF/AiEAw8EQ0dR5hgbJ/tlxqAA33VypQMBitTw6kMhgcR8Z/kM=&#34;}]}]},{&#34;name&#34;: &#34;-sha256:c100497badd3edd2f02b294411b511396e71caf701f4df45db448e6cdbc686b0-amd64&#34;,&#34;containerImage&#34;: &#34;quay.io/konflux-ci/ec-golden-image@sha256:c100497badd3edd2f02b294411b511396e71caf701f4df45db448e6cdbc686b0&#34;,&#34;source&#34;: {},&#34;successes&#34;: [{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;attestation_type.known_attestation_type&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;slsa3&#34;],&#xA;&#34;depends_on&#34;: [&#34;attestation_type.pipelinerun_attestation_found&#34;],&#34;description&#34;: &#34;Confirm the attestation found for the image has a known attestation type.&#34;,&#34;title&#34;: &#34;Known attestation type found&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;attestation_type.pipelinerun_attestation_found&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;slsa3&#34;],&#34;description&#34;: &#34;Confirm at least one PipelineRun attestation is present.&#34;,&#34;title&#34;: &#34;PipelineRun attestation found&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.signature_check&#34;,&#34;description&#34;: &#34;The attestation signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Attestation signature check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.syntax_check&#34;,&#34;description&#34;: &#34;The attestation has correct syntax.&#34;,&#34;title&#34;: &#34;Attestation syntax check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.image.signature_check&#34;,&#34;description&#34;: &#34;The image signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Image signature check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_build_service.allowed_builder_ids_provided&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;policy_data&#34;],&#34;description&#34;: &#34;Confirm the `allowed_builder_ids` rule data was provided, since it is required by the policy rules in this package.&#34;,&#34;title&#34;: &#34;Allowed builder IDs provided&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_build_service.slsa_builder_id_accepted&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the attestation attribute predicate.builder.id is set to one of the values in the `allowed_builder_ids` rule data, e.g. \&#34;https://tekton.dev/chains/v2\&#34;.&#34;,&#34;title&#34;: &#34;SLSA Builder ID is known and accepted&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_build_service.slsa_builder_id_found&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the attestation attribute predicate.builder.id is set.&#34;,&#34;title&#34;: &#34;SLSA Builder ID found&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_scripted_build.build_script_used&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the predicate.buildConfig.tasks.steps attribute for the task responsible for building and pushing the image is not empty.&#34;,&#34;title&#34;: &#34;Build task contains steps&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_scripted_build.build_task_image_results_found&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Confirm that a build task exists and it has the expected IMAGE_DIGEST and IMAGE_URL task results.&#34;,&#34;title&#34;: &#34;Build task set image digest and url task results&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_scripted_build.subject_build_task_matches&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify the subject of the attestations matches the IMAGE_DIGEST and IMAGE_URL values from the build task.&#34;,&#34;title&#34;: &#34;Provenance subject matches build task image result&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_provenance_available.allowed_predicate_types_provided&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;policy_data&#34;],&#34;description&#34;: &#34;Confirm the `allowed_predicate_types` rule data was provided, since it is required by the policy rules in this package.&#34;,&#34;title&#34;: &#34;Allowed predicate types provided&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_provenance_available.attestation_predicate_type_accepted&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the predicateType field of the attestation indicates the in-toto SLSA Provenance format was used to attest the PipelineRun.&#34;,&#34;title&#34;: &#34;Expected attestation predicate type found&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_correlated.attested_source_code_reference&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Attestation contains source reference.&#34;,&#34;title&#34;: &#34;Source reference&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_correlated.expected_source_code_reference&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the provided source code reference is the one being attested.&#34;,&#34;title&#34;: &#34;Expected source code reference&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_correlated.rule_data_provided&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;policy_data&#34;],&#34;description&#34;: &#34;Confirm the expected rule data keys have been provided in the expected format. The keys are `supported_vcs` and `supported_digests`.&#34;,&#34;title&#34;: &#34;Rule data provided&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_version_controlled.materials_format_okay&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Confirm at least one entry in the predicate.materials array of the attestation contains the expected attributes: uri and digest.sha1.&#34;,&#34;title&#34;: &#34;Materials have uri and digest&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_version_controlled.materials_include_git_sha&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Ensure that each entry in the predicate.materials array with a SHA-1 digest includes a valid Git commit SHA.&#34;,&#34;title&#34;: &#34;Materials include git commit shas&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_version_controlled.materials_uri_is_git_repo&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Ensure each entry in the predicate.materials array with a SHA-1 digest includes a valid Git URI.&#34;,&#34;title&#34;: &#34;Material uri is a git repo&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;tasks.pipeline_has_tasks&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;slsa3&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Ensure that at least one Task is present in the PipelineRun attestation.&#34;,&#34;title&#34;: &#34;Pipeline run includes at least one task&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;tasks.successful_pipeline_tasks&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;slsa3&#34;],&#34;depends_on&#34;: [&#34;tasks.pipeline_has_tasks&#34;],&#34;description&#34;: &#34;Ensure that all of the Tasks in the Pipeline completed successfully. Note that skipped Tasks are not taken into account and do not influence the outcome.&#34;,&#34;title&#34;: &#34;Successful pipeline tasks&#34;}}],&#34;success&#34;: true,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;&#34;,&#34;sig&#34;: &#34;MEQCIHxTtFk2bdTapnn7KctPkokRxcv93bMICQzKn39JKl0LAiBCxnJjATuj6BTcqLlA8wMoi6veCojTO4/4C5LttuGMHA==&#34;},{&#34;keyid&#34;: &#34;&#34;,&#34;sig&#34;: &#34;MEYCIQC+dYCC62hMKwiuaN96kH3W0IDnI3Q0dORmRturzbbB4wIhAMZtr0VklbfgVlU56eO49dlwq8pKtye2zerYiC8NazW4&#34;}],&#34;attestations&#34;: [{&#34;type&#34;: &#34;https://in-toto.io/Statement/v0.1&#34;,&#34;predicateType&#34;: &#34;https://slsa.dev/provenance/v0.2&#34;,&#34;predicateBuildType&#34;: &#34;tekton.dev/v1/PipelineRun&#34;,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;SHA256:IhiN7gY+Z3uSSd7tmj6w5Zfhqafzdhm3DZjIvGc6iYY&#34;,&#34;sig&#34;: &#34;MEUCIB3dH/CuxExH77jGOhngRyCwsNeug1KyBLQKKWqW0qF/AiEAw8EQ0dR5hgbJ/tlxqAA33VypQMBitTw6kMhgcR8Z/kM=&#34;}]}]},{&#34;name&#34;: &#34;-sha256:9024c5db8db1fa036f7c56020829f0e239db7b660d5e5f6439af84ab66489d63-arm64&#34;,&#34;containerImage&#34;: &#34;quay.io/konflux-ci/ec-golden-image@sha256:9024c5db8db1fa036f7c56020829f0e239db7b660d5e5f6439af84ab66489d63&#34;,&#34;source&#34;: {},&#34;successes&#34;: [{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;attestation_type.known_attestation_type&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;slsa3&#34;],&#34;depends_on&#34;: [&#34;attestation_type.pipelinerun_attestation_found&#34;],&#34;description&#34;: &#34;Confirm the attestation found for the image has a known attestation type.&#34;,&#34;title&#34;: &#34;Known attestation type found&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#xA;&#34;metadata&#34;: {&#34;code&#34;: &#34;attestation_type.pipelinerun_attestation_found&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;slsa3&#34;],&#34;description&#34;: &#34;Confirm at least one PipelineRun attestation is present.&#34;,&#34;title&#34;: &#34;PipelineRun attestation found&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.signature_check&#34;,&#34;description&#34;: &#34;The attestation signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Attestation signature check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.syntax_check&#34;,&#34;description&#34;: &#34;The attestation has correct syntax.&#34;,&#34;title&#34;: &#34;Attestation syntax check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.image.signature_check&#34;,&#34;description&#34;: &#34;The image signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Image signature check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_build_service.allowed_builder_ids_provided&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;policy_data&#34;],&#34;description&#34;: &#34;Confirm the `allowed_builder_ids` rule data was provided, since it is required by the policy rules in this package.&#34;,&#34;title&#34;: &#34;Allowed builder IDs provided&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_build_service.slsa_builder_id_accepted&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the attestation attribute predicate.builder.id is set to one of the values in the `allowed_builder_ids` rule data, e.g. \&#34;https://tekton.dev/chains/v2\&#34;.&#34;,&#34;title&#34;: &#34;SLSA Builder ID is known and accepted&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_build_service.slsa_builder_id_found&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the attestation attribute predicate.builder.id is set.&#34;,&#34;title&#34;: &#34;SLSA Builder ID found&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_scripted_build.build_script_used&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the predicate.buildConfig.tasks.steps attribute for the task responsible for building and pushing the image is not empty.&#34;,&#34;title&#34;: &#34;Build task contains steps&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_scripted_build.build_task_image_results_found&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Confirm that a build task exists and it has the expected IMAGE_DIGEST and IMAGE_URL task results.&#34;,&#34;title&#34;: &#34;Build task set image digest and url task results&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_scripted_build.subject_build_task_matches&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify the subject of the attestations matches the IMAGE_DIGEST and IMAGE_URL values from the build task.&#34;,&#34;title&#34;: &#34;Provenance subject matches build task image result&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_provenance_available.allowed_predicate_types_provided&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;policy_data&#34;],&#34;description&#34;: &#34;Confirm the `allowed_predicate_types` rule data was provided, since it is required by the policy rules in this package.&#34;,&#34;title&#34;: &#34;Allowed predicate types provided&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_provenance_available.attestation_predicate_type_accepted&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the predicateType field of the attestation indicates the in-toto SLSA Provenance format was used to attest the PipelineRun.&#34;,&#34;title&#34;: &#34;Expected attestation predicate type found&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_correlated.attested_source_code_reference&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Attestation contains source reference.&#34;,&#34;title&#34;: &#34;Source reference&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_correlated.expected_source_code_reference&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the provided source code reference is the one being attested.&#34;,&#34;title&#34;: &#34;Expected source code reference&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_correlated.rule_data_provided&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;policy_data&#34;],&#34;description&#34;: &#34;Confirm the expected rule data keys have been provided in the expected format. The keys are `supported_vcs` and `supported_digests`.&#34;,&#34;title&#34;: &#34;Rule data provided&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_version_controlled.materials_format_okay&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Confirm at least one entry in the predicate.materials array of the attestation contains the expected attributes: uri and digest.sha1.&#34;,&#34;title&#34;: &#34;Materials have uri and digest&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_version_controlled.materials_include_git_sha&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Ensure that each entry in the predicate.materials array with a SHA-1 digest includes a valid Git commit SHA.&#34;,&#34;title&#34;: &#34;Materials include git commit shas&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_version_controlled.materials_uri_is_git_repo&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Ensure each entry in the predicate.materials array with a SHA-1 digest includes a valid Git URI.&#34;,&#34;title&#34;: &#34;Material uri is a git repo&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;tasks.pipeline_has_tasks&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;slsa3&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Ensure that at least one Task is present in the PipelineRun attestation.&#34;,&#34;title&#34;: &#34;Pipeline run includes at least one task&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;tasks.successful_pipeline_tasks&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;slsa3&#34;],&#34;depends_on&#34;: [&#34;tasks.pipeline_has_tasks&#34;],&#34;description&#34;: &#34;Ensure that all of the Tasks in the Pipeline completed successfully. Note that skipped Tasks are not taken into account and do not influence the outcome.&#34;,&#34;title&#34;: &#34;Successful pipeline tasks&#34;}}],&#34;success&#34;: true,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;&#34;,&#34;sig&#34;: &#34;MEQCIFQ78YKKqW5FcHcpAdeQwKgDS/Mo7tWGNvEsIaFU+8gaAiBaGO5O2kkl2eEedoP4ZiBaS720B45IeoIObcy+IgqRyQ==&#34;},{&#34;keyid&#34;: &#34;&#34;,&#34;sig&#34;: &#34;MEQCIHYpELtYjBZyeFW0mhT81Ko6wYTTi+Kr1iwU+pPtxOxeAiB6BJKk+Tmh9gdvkDL2snwVXBsjmPwd0rUaPseGWVHzCQ==&#34;}],&#34;attestations&#34;: [{&#34;type&#34;: &#34;https://in-toto.io/Statement/v0.1&#34;,&#34;predicateType&#34;: &#34;https://slsa.dev/provenance/v0.2&#34;,&#34;predicateBuildType&#34;: &#34;tekton.dev/v1/PipelineRun&#34;,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;SHA256:IhiN7gY+Z3uSSd7tmj6w5Zfhqafzdhm3DZjIvGc6iYY&#34;,&#34;sig&#34;: &#34;MEUCIB3dH/CuxExH77jGOhngRyCwsNeug1KyBLQKKWqW0qF/AiEAw8EQ0dR5hgbJ/tlxqAA33VypQMBitTw6kMhgcR8Z/kM=&#34;}]}]},{&#34;name&#34;: &#34;&#34;,&#34;containerImage&#34;: &#34;quay.io/konflux-ci/ec-golden-image@sha256:304040ca1911aa4d911bd7c6d6d07193c57dc49dbc43e63828b42ab204fb1b25&#34;,&#34;source&#34;: {},&#34;successes&#34;: [{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;attestation_type.known_attestation_type&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;slsa3&#34;],&#34;depends_on&#34;: [&#34;attestation_type.pipelinerun_attestation_found&#34;],&#34;description&#34;: &#34;Confirm the attestation found for the image has a known attestation type.&#34;,&#34;title&#34;: &#34;Known attestation type found&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;attestation_type.pipelinerun_attestation_found&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;slsa3&#34;],&#34;description&#34;: &#34;Confirm at least one PipelineRun attestation is present.&#34;,&#34;title&#34;: &#34;PipelineRun attestation found&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#xA;&#34;code&#34;: &#34;builtin.attestation.signature_check&#34;,&#34;description&#34;: &#34;The attestation signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Attestation signature check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.syntax_check&#34;,&#34;description&#34;: &#34;The attestation has correct syntax.&#34;,&#34;title&#34;: &#34;Attestation syntax check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.image.signature_check&#34;,&#34;description&#34;: &#34;The image signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Image signature check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_build_service.allowed_builder_ids_provided&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;policy_data&#34;],&#34;description&#34;: &#34;Confirm the `allowed_builder_ids` rule data was provided, since it is required by the policy rules in this package.&#34;,&#34;title&#34;: &#34;Allowed builder IDs provided&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_build_service.slsa_builder_id_accepted&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the attestation attribute predicate.builder.id is set to one of the values in the `allowed_builder_ids` rule data, e.g. \&#34;https://tekton.dev/chains/v2\&#34;.&#34;,&#34;title&#34;: &#34;SLSA Builder ID is known and accepted&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_build_service.slsa_builder_id_found&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the attestation attribute predicate.builder.id is set.&#34;,&#34;title&#34;: &#34;SLSA Builder ID found&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_scripted_build.build_script_used&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the predicate.buildConfig.tasks.steps attribute for the task responsible for building and pushing the image is not empty.&#34;,&#34;title&#34;: &#34;Build task contains steps&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_scripted_build.build_task_image_results_found&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Confirm that a build task exists and it has the expected IMAGE_DIGEST and IMAGE_URL task results.&#34;,&#34;title&#34;: &#34;Build task set image digest and url task results&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_build_scripted_build.subject_build_task_matches&#34;,&#34;collections&#34;: [&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify the subject of the attestations matches the IMAGE_DIGEST and IMAGE_URL values from the build task.&#34;,&#34;title&#34;: &#34;Provenance subject matches build task image result&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_provenance_available.allowed_predicate_types_provided&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;policy_data&#34;],&#34;description&#34;: &#34;Confirm the `allowed_predicate_types` rule data was provided, since it is required by the policy rules in this package.&#34;,&#34;title&#34;: &#34;Allowed predicate types provided&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_provenance_available.attestation_predicate_type_accepted&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the predicateType field of the attestation indicates the in-toto SLSA Provenance format was used to attest the PipelineRun.&#34;,&#34;title&#34;: &#34;Expected attestation predicate type found&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_correlated.attested_source_code_reference&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Attestation contains source reference.&#34;,&#34;title&#34;: &#34;Source reference&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_correlated.expected_source_code_reference&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Verify that the provided source code reference is the one being attested.&#34;,&#34;title&#34;: &#34;Expected source code reference&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_correlated.rule_data_provided&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;policy_data&#34;],&#34;description&#34;: &#34;Confirm the expected rule data keys have been provided in the expected format. The keys are `supported_vcs` and `supported_digests`.&#34;,&#34;title&#34;: &#34;Rule data provided&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_version_controlled.materials_format_okay&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Confirm at least one entry in the predicate.materials array of the attestation contains the expected attributes: uri and digest.sha1.&#34;,&#34;title&#34;: &#34;Materials have uri and digest&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_version_controlled.materials_include_git_sha&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Ensure that each entry in the predicate.materials array with a SHA-1 digest includes a valid Git commit SHA.&#34;,&#34;title&#34;: &#34;Materials include git commit shas&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;slsa_source_version_controlled.materials_uri_is_git_repo&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;slsa3&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Ensure each entry in the predicate.materials array with a SHA-1 digest includes a valid Git URI.&#34;,&#34;title&#34;: &#34;Material uri is a git repo&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;tasks.pipeline_has_tasks&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;slsa3&#34;],&#34;depends_on&#34;: [&#34;attestation_type.known_attestation_type&#34;],&#34;description&#34;: &#34;Ensure that at least one Task is present in the PipelineRun attestation.&#34;,&#34;title&#34;: &#34;Pipeline run includes at least one task&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;tasks.successful_pipeline_tasks&#34;,&#34;collections&#34;: [&#34;minimal&#34;,&#34;redhat&#34;,&#34;redhat_rpms&#34;,&#34;slsa3&#34;],&#34;depends_on&#34;: [&#34;tasks.pipeline_has_tasks&#34;],&#34;description&#34;: &#34;Ensure that all of the Tasks in the Pipeline completed successfully. Note that skipped Tasks are not taken into account and do not influence the outcome.&#34;,&#34;title&#34;: &#34;Successful pipeline tasks&#34;}}],&#34;success&#34;: true,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;&#34;,&#34;sig&#34;: &#34;MEUCIQD86lmOqCovYZDPKm0XxxsLgDQcFIFAv+QZxrFSHmCvQAIgTd1I005ox8MfABqsAen6PZEyg2MCEQNBCx1NLS3V0JQ=&#34;}],&#34;attestations&#34;: [{&#34;type&#34;: &#34;https://in-toto.io/Statement/v0.1&#34;,&#34;predicateType&#34;: &#34;https://slsa.dev/provenance/v0.2&#34;,&#34;predicateBuildType&#34;: &#34;tekton.dev/v1beta1/TaskRun&#34;,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;SHA256:IhiN7gY+Z3uSSd7tmj6w5Zfhqafzdhm3DZjIvGc6iYY&#34;,&#34;sig&#34;: &#34;MEUCIQDcgZIwEkLFqD7U9HrobgEC8Jo7wm+xJ5AoyO3qg+aj8QIgb9xDpjYGRMmpVk+QATeVKlHonzBiu51HtT3J+lQXPXc=&#34;}]},{&#34;type&#34;: &#34;https://in-toto.io/Statement/v0.1&#34;,&#34;predicateType&#34;: &#34;https://slsa.dev/provenance/v0.2&#34;,&#34;predicateBuildType&#34;: &#34;tekton.dev/v1beta1/PipelineRun&#34;,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;SHA256:IhiN7gY+Z3uSSd7tmj6w5Zfhqafzdhm3DZjIvGc6iYY&#34;,&#34;sig&#34;: &#34;MEYCIQDKSihaAR/zAhJhR5GCqleDvfUUtvRw61vk0YeTBAnOSQIhAKa09B4yEfaSJronmWBFbu5cVPNxm17CMl/PElEz1POa&#34;}]}]}],&#34;key&#34;: &#34;-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEZP/0htjhVt2y0ohjgtIIgICOtQtA\nnaYJRuLprwIv6FDhZ5yFjYUEtsmoNcW7rx2KM6FOXGsCX3BNc7qhHELT+g==\n-----END PUBLIC KEY-----\n&#34;,&#34;policy&#34;: {&#34;name&#34;: &#34;Default&#34;,&#34;description&#34;: &#34;Includes rules for levels 1, 2 &amp; 3 of SLSA v0.1. This is the default config used for new Konflux applications. Source: https://github.com/conforma/config/blob/main/default/policy.yaml&#34;,&#34;sources&#34;: [{&#34;name&#34;: &#34;Default&#34;,&#34;policy&#34;: [&#34;oci::quay.io/enterprise-contract/ec-release-policy:konflux@sha256:59c6b95c02295edb7928ef187571d26d426993fd5aae0236a03c832afbd6072a&#34;],&#34;data&#34;: [&#34;git::github.com/release-engineering/rhtap-ec-policy//data?ref=67018469815ee9f81e47cfb54dae39d71ed5f389&#34;,&#34;oci::quay.io/konflux-ci/tekton-catalog/data-acceptable-bundles:latest@sha256:c75d0123e83efa6c182b6510c35982b48201143ce74a9a388680a0ee1aa4affb&#34;,&#xA;&#34;oci::quay.io/konflux-ci/konflux-vanguard/data-acceptable-bundles:latest@sha256:0b31c7bc77a7463a1bc52f3d3625ef0e0e75443da7fd2de8005d7885282138ea&#34;,&#34;oci::quay.io/konflux-ci/integration-service-catalog/data-acceptable-bundles:latest@sha256:7b00455045ea3873a72caeb1e7ac7d036bd53963a26409891a4cc9d0d242b9fc&#34;],&#34;config&#34;: {&#34;exclude&#34;: [&#34;slsa_source_correlated.source_code_reference_provided&#34;],&#34;include&#34;: [&#34;@slsa3&#34;]}}],&#34;publicKey&#34;: &#34;k8s://chains-e2e-vgkz/golden-image-public-keyujfewetwbn&#34;},&#34;ec-version&#34;: &#34;v0.9.25&#34;,&#34;effective-time&#34;: &#34;2026-05-09T03:09:06.29175514Z&#34;}----- END -----&#xA;&lt; Exit [It] verifies ec validate accepts a list of image references - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:301 @ 05/09/26 03:09:17.734 (18.095s)&#xA;&gt; Enter [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 03:09:17.734&#xA;&lt; Exit [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 03:09:17.734 (0s)&#xA;</system-err>
          </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="passed" time="33.103606679">
              <system-err>&gt; Enter [BeforeEach] verify-enterprise-contract task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:154 @ 05/09/26 03:09:17.736&#xA;&lt; Exit [BeforeEach] verify-enterprise-contract task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:154 @ 05/09/26 03:09:17.748 (13ms)&#xA;&gt; Enter [It] verifies redhat products pass the redhat policy rule collection before release  - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:345 @ 05/09/26 03:09:17.749&#xA;Update public key to verify golden images&#xA;Creating Pipeline &#34;verify-enterprise-contract-run-q5jgz&#34;&#xA;Waiting for pipeline &#34;verify-enterprise-contract-run-q5jgz&#34; to finish&#xA;&lt; Exit [It] verifies redhat products pass the redhat policy rule collection before release  - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:345 @ 05/09/26 03:09:50.839 (33.09s)&#xA;&gt; Enter [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 03:09:50.839&#xA;&lt; Exit [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 03:09:50.839 (0s)&#xA;</system-err>
          </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="passed" time="15.189169458">
              <system-err>&gt; Enter [BeforeEach] verify-enterprise-contract task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:154 @ 05/09/26 03:09:50.84&#xA;&lt; Exit [BeforeEach] verify-enterprise-contract task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:154 @ 05/09/26 03:09:50.858 (19ms)&#xA;&gt; Enter [It] verifies the release policy: Task are trusted - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:382 @ 05/09/26 03:09:50.858&#xA;Update public key to verify golden images&#xA;Creating Pipeline &#34;verify-enterprise-contract-run-2whpz&#34;&#xA;Waiting for pipeline &#34;verify-enterprise-contract-run-2whpz&#34; to finish&#xA;*** Logs from pod &#39;verify-enterprise-contract-5fb0371886d918523daf5de3ac0116e8-pod&#39;, container &#39;step-report-json&#39;:&#xA;----- START -----{&#34;success&#34;: false,&#34;components&#34;: [{&#34;name&#34;: &#34;&#34;,&#34;containerImage&#34;: &#34;quay.io/konflux-ci/ec-golden-image@sha256:304040ca1911aa4d911bd7c6d6d07193c57dc49dbc43e63828b42ab204fb1b25&#34;,&#34;source&#34;: {},&#34;violations&#34;: [{&#34;msg&#34;: &#34;PipelineTask \&#34;build-container\&#34; uses an untrusted task reference: oci://quay.io/redhat-appstudio-tekton-catalog/task-buildah:0.1@sha256:c3712257615d206ef40013bf1c5c681670fc8f7fd6aac9fa4c86f7afeff627ef. Please upgrade the task version to: sha256:73628c0497b9d1fb068dffb997cf7bea57ed6dfa04e892abf1d6fc7f6828050a&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.trusted&#34;,&#34;collections&#34;: [&#34;redhat&#34;],&#34;description&#34;: &#34;Check the trust of the Tekton Tasks used in the build Pipeline. There are two modes in which trust is verified. The first mode is used if Trusted Artifacts are enabled. In this case, a chain of trust is established for all the Tasks involved in creating an artifact. If the chain contains an untrusted Task, then a violation is emitted. The second mode is used as a fallback when Trusted Artifacts are not enabled. In this case, **all** Tasks in the build Pipeline must be trusted. To exclude this rule add \&#34;trusted_task.trusted:buildah\&#34; to the `exclude` section of the policy configuration.&#34;,&#34;solution&#34;: &#34;If using Trusted Artifacts, be sure every Task in the build Pipeline responsible for producing a Trusted Artifact is trusted. Otherwise, ensure **all** Tasks in the build Pipeline are trusted. Note that trust is eventually revoked from Tasks when newer versions are made available.&#34;,&#34;term&#34;: &#34;buildah&#34;,&#34;title&#34;: &#34;Tasks are trusted&#34;}},{&#34;msg&#34;: &#34;PipelineTask \&#34;clair-scan\&#34; uses an untrusted task reference: oci://quay.io/redhat-appstudio-tekton-catalog/task-clair-scan:0.1@sha256:fba8170329ab00b864ee7d16e0358df4c4386880e10894fd7bbbb1457112477b. Please upgrade the task version to: sha256:d3af2290595378de7f8bc73b54aa7a5fac793090e2cef4f1822d31e18a64761f&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.trusted&#34;,&#34;collections&#34;: [&#34;redhat&#34;],&#34;description&#34;: &#34;Check the trust of the Tekton Tasks used in the build Pipeline. There are two modes in which trust is verified. The first mode is used if Trusted Artifacts are enabled. In this case, a chain of trust is established for all the Tasks involved in creating an artifact. If the chain contains an untrusted Task, then a violation is emitted. The second mode is used as a fallback when Trusted Artifacts are not enabled. In this case, **all** Tasks in the build Pipeline must be trusted. To exclude this rule add \&#34;trusted_task.trusted:clair-scan\&#34; to the `exclude` section of the policy configuration.&#34;,&#34;solution&#34;: &#34;If using Trusted Artifacts, be sure every Task in the build Pipeline responsible for producing a Trusted Artifact is trusted. Otherwise, ensure **all** Tasks in the build Pipeline are trusted. Note that trust is eventually revoked from Tasks when newer versions are made available.&#34;,&#34;term&#34;: &#34;clair-scan&#34;,&#34;title&#34;: &#34;Tasks are trusted&#34;}},{&#34;msg&#34;: &#34;PipelineTask \&#34;clamav-scan\&#34; uses an untrusted task reference: oci://quay.io/redhat-appstudio-tekton-catalog/task-clamav-scan:0.1@sha256:28b425322aa84f988c6c4f8d503787b3fb301668b2ad6728846b8f8c45ba012b. Please upgrade the task version to: sha256:1b186d53eeab12f0ae1b7aa333e9cf2b2c9dcc9751f5e940ca935a168bba5a7d&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.trusted&#34;,&#34;collections&#34;: [&#34;redhat&#34;],&#34;description&#34;: &#34;Check the trust of the Tekton Tasks used in the build Pipeline. There are two modes in which trust is verified. The first mode is used if Trusted Artifacts are enabled. In this case, a chain of trust is established for all the Tasks involved in creating an artifact. If the chain contains an untrusted Task, then a violation is emitted. The second mode is used as a fallback when Trusted Artifacts are not enabled. In this case, **all** Tasks in the build Pipeline must be trusted. To exclude this rule add \&#34;trusted_task.trusted:clamav-scan\&#34; to the `exclude` section of the policy configuration.&#34;,&#34;solution&#34;: &#34;If using Trusted Artifacts, be sure every Task in the build Pipeline responsible for producing a Trusted Artifact is trusted. Otherwise, ensure **all** Tasks in the build Pipeline are trusted. Note that trust is eventually revoked from Tasks when newer versions are made available.&#34;,&#34;term&#34;: &#34;clamav-scan&#34;,&#34;title&#34;: &#34;Tasks are trusted&#34;}},{&#34;msg&#34;: &#34;PipelineTask \&#34;deprecated-base-image-check\&#34; uses an untrusted task reference: oci://quay.io/redhat-appstudio-tekton-catalog/task-deprecated-image-check:0.1@sha256:28d724dd6f6c365b2a839d9e52baac91559fd78c160774769c1ec724301f78d4. Please upgrade the task version to: sha256:409efc4464663225f96518776b3811c31ea4e988a18493a3114eedf01e0a0a17&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.trusted&#34;,&#34;collections&#34;: [&#34;redhat&#34;],&#34;description&#34;: &#34;Check the trust of the Tekton Tasks used in the build Pipeline. There are two modes in which trust is verified. The first mode is used if Trusted Artifacts are enabled. In this case, a chain of trust is established for all the Tasks involved in creating an artifact. If the chain contains an untrusted Task, then a violation is emitted. The second mode is used as a fallback when Trusted Artifacts are not enabled. In this case, **all** Tasks in the build Pipeline must be trusted. To exclude this rule add \&#34;trusted_task.trusted:deprecated-image-check\&#34; to the `exclude` section of the policy configuration.&#34;,&#34;solution&#34;: &#34;If using Trusted Artifacts, be sure every Task in the build Pipeline responsible for producing a Trusted Artifact is trusted. Otherwise, ensure **all** Tasks in the build Pipeline are trusted. Note that trust is eventually revoked from Tasks when newer versions are made available.&#34;,&#34;term&#34;: &#34;deprecated-image-check&#34;,&#34;title&#34;: &#34;Tasks are trusted&#34;}},{&#34;msg&#34;: &#34;PipelineTask \&#34;clone-repository\&#34; uses an untrusted task reference: oci://quay.io/redhat-appstudio-tekton-catalog/task-git-clone:0.1@sha256:f4e37778cba00296606ddfbc1c58181330899cafcaa1ee41c75a7cf8bed312f0. Please upgrade the task version to: sha256:2175fdd1ab932727d7a539ef260f32a127a004c61257f974ffaf23863763de9b&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.trusted&#34;,&#34;collections&#34;: [&#34;redhat&#34;],&#34;description&#34;: &#34;Check the trust of the Tekton Tasks used in the build Pipeline. There are two modes in which trust is verified. The first mode is used if Trusted Artifacts are enabled. In this case, a chain of trust is established for all the Tasks involved in creating an artifact. If the chain contains an untrusted Task, then a violation is emitted. The second mode is used as a fallback when Trusted Artifacts are not enabled. In this case, **all** Tasks in the build Pipeline must be trusted. To exclude this rule add \&#34;trusted_task.trusted:git-clone\&#34; to the `exclude` section of the policy configuration.&#34;,&#34;solution&#34;: &#34;If using Trusted Artifacts, be sure every Task in the build Pipeline responsible for producing a Trusted Artifact is trusted. Otherwise, ensure **all** Tasks in the build Pipeline are trusted. Note that trust is eventually revoked from Tasks when newer versions are made available.&#34;,&#34;term&#34;: &#34;git-clone&#34;,&#34;title&#34;: &#34;Tasks are trusted&#34;}},{&#34;msg&#34;: &#34;PipelineTask \&#34;init\&#34; uses an untrusted task reference: oci://quay.io/redhat-appstudio-tekton-catalog/task-init:0.1@sha256:5ce77110e2a49407a69a7922042dc0859f7e8f5f75dc0cd0bcc2d17860469bdb. Please upgrade the task version to: sha256:60e0a74b7f4b1166cb62672d6b6f262b4284b20ade9157a387b4a52283ccada8&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.trusted&#34;,&#34;collections&#34;: [&#34;redhat&#34;],&#34;description&#34;: &#34;Check the trust of the Tekton Tasks used in the build Pipeline. There are two modes in which trust is verified. The first mode is used if Trusted Artifacts are enabled. In this case, a chain of trust is established for all the Tasks involved in creating an artifact. If the chain contains an untrusted Task, then a violation is emitted. The second mode is used as a fallback when Trusted Artifacts are not enabled. In this case, **all** Tasks in the build Pipeline must be trusted. To exclude this rule add \&#34;trusted_task.trusted:init\&#34; to the `exclude` section of the policy configuration.&#34;,&#xA;&#34;solution&#34;: &#34;If using Trusted Artifacts, be sure every Task in the build Pipeline responsible for producing a Trusted Artifact is trusted. Otherwise, ensure **all** Tasks in the build Pipeline are trusted. Note that trust is eventually revoked from Tasks when newer versions are made available.&#34;,&#34;term&#34;: &#34;init&#34;,&#34;title&#34;: &#34;Tasks are trusted&#34;}},{&#34;msg&#34;: &#34;PipelineTask \&#34;sanity-inspect-image\&#34; uses an untrusted task reference: oci://quay.io/redhat-appstudio-tekton-catalog/task-sanity-inspect-image:0.1@sha256:fd4efd9d12eea3a8d47532c4226e685618845d0ba95abb98e008020243d96301. Please upgrade the task version to: sha256:b9ad0ed56be21c9e3c8e2e636275f92d887e57681c718cd36f117eb6fa547824&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.trusted&#34;,&#34;collections&#34;: [&#34;redhat&#34;],&#34;description&#34;: &#34;Check the trust of the Tekton Tasks used in the build Pipeline. There are two modes in which trust is verified. The first mode is used if Trusted Artifacts are enabled. In this case, a chain of trust is established for all the Tasks involved in creating an artifact. If the chain contains an untrusted Task, then a violation is emitted. The second mode is used as a fallback when Trusted Artifacts are not enabled. In this case, **all** Tasks in the build Pipeline must be trusted. To exclude this rule add \&#34;trusted_task.trusted:sanity-inspect-image\&#34; to the `exclude` section of the policy configuration.&#34;,&#34;solution&#34;: &#34;If using Trusted Artifacts, be sure every Task in the build Pipeline responsible for producing a Trusted Artifact is trusted. Otherwise, ensure **all** Tasks in the build Pipeline are trusted. Note that trust is eventually revoked from Tasks when newer versions are made available.&#34;,&#34;term&#34;: &#34;sanity-inspect-image&#34;,&#34;title&#34;: &#34;Tasks are trusted&#34;}},{&#34;msg&#34;: &#34;PipelineTask \&#34;sanity-label-check\&#34; uses an untrusted task reference: oci://quay.io/redhat-appstudio-tekton-catalog/task-sanity-label-check:0.1@sha256:534770bf7a7c10277ab5f9c1e7b766abbffb343cc864dd9545aecc5278257dc3. Please upgrade the task version to: sha256:dd49667be76c81264a7fb28e3b43f72c527507e5691720c6262575255cb60689&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.trusted&#34;,&#34;collections&#34;: [&#34;redhat&#34;],&#34;description&#34;: &#34;Check the trust of the Tekton Tasks used in the build Pipeline. There are two modes in which trust is verified. The first mode is used if Trusted Artifacts are enabled. In this case, a chain of trust is established for all the Tasks involved in creating an artifact. If the chain contains an untrusted Task, then a violation is emitted. The second mode is used as a fallback when Trusted Artifacts are not enabled. In this case, **all** Tasks in the build Pipeline must be trusted. To exclude this rule add \&#34;trusted_task.trusted:sanity-label-check\&#34; to the `exclude` section of the policy configuration.&#34;,&#34;solution&#34;: &#34;If using Trusted Artifacts, be sure every Task in the build Pipeline responsible for producing a Trusted Artifact is trusted. Otherwise, ensure **all** Tasks in the build Pipeline are trusted. Note that trust is eventually revoked from Tasks when newer versions are made available.&#34;,&#34;term&#34;: &#34;sanity-label-check&#34;,&#34;title&#34;: &#34;Tasks are trusted&#34;}},{&#34;msg&#34;: &#34;PipelineTask \&#34;sanity-optional-label-check\&#34; uses an untrusted task reference: oci://quay.io/redhat-appstudio-tekton-catalog/task-sanity-label-check:0.1@sha256:534770bf7a7c10277ab5f9c1e7b766abbffb343cc864dd9545aecc5278257dc3. Please upgrade the task version to: sha256:dd49667be76c81264a7fb28e3b43f72c527507e5691720c6262575255cb60689&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.trusted&#34;,&#34;collections&#34;: [&#34;redhat&#34;],&#34;description&#34;: &#34;Check the trust of the Tekton Tasks used in the build Pipeline. There are two modes in which trust is verified. The first mode is used if Trusted Artifacts are enabled. In this case, a chain of trust is established for all the Tasks involved in creating an artifact. If the chain contains an untrusted Task, then a violation is emitted. The second mode is used as a fallback when Trusted Artifacts are not enabled. In this case, **all** Tasks in the build Pipeline must be trusted. To exclude this rule add \&#34;trusted_task.trusted:sanity-label-check\&#34; to the `exclude` section of the policy configuration.&#34;,&#34;solution&#34;: &#34;If using Trusted Artifacts, be sure every Task in the build Pipeline responsible for producing a Trusted Artifact is trusted. Otherwise, ensure **all** Tasks in the build Pipeline are trusted. Note that trust is eventually revoked from Tasks when newer versions are made available.&#34;,&#34;term&#34;: &#34;sanity-label-check&#34;,&#34;title&#34;: &#34;Tasks are trusted&#34;}},{&#34;msg&#34;: &#34;PipelineTask \&#34;sbom-json-check\&#34; uses an untrusted task reference: oci://quay.io/redhat-appstudio-tekton-catalog/task-sbom-json-check:0.1@sha256:ce6a0932da9b41080108284d1366fc2de8374fca5137500138e16ad9e04610c6. Please upgrade the task version to: sha256:32a7b681f947179b4df11f2e9f05f27478001247e519fa0b1a211cbf9562a205&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.trusted&#34;,&#34;collections&#34;: [&#34;redhat&#34;],&#34;description&#34;: &#34;Check the trust of the Tekton Tasks used in the build Pipeline. There are two modes in which trust is verified. The first mode is used if Trusted Artifacts are enabled. In this case, a chain of trust is established for all the Tasks involved in creating an artifact. If the chain contains an untrusted Task, then a violation is emitted. The second mode is used as a fallback when Trusted Artifacts are not enabled. In this case, **all** Tasks in the build Pipeline must be trusted. To exclude this rule add \&#34;trusted_task.trusted:sbom-json-check\&#34; to the `exclude` section of the policy configuration.&#34;,&#34;solution&#34;: &#34;If using Trusted Artifacts, be sure every Task in the build Pipeline responsible for producing a Trusted Artifact is trusted. Otherwise, ensure **all** Tasks in the build Pipeline are trusted. Note that trust is eventually revoked from Tasks when newer versions are made available.&#34;,&#34;term&#34;: &#34;sbom-json-check&#34;,&#34;title&#34;: &#34;Tasks are trusted&#34;}},{&#34;msg&#34;: &#34;PipelineTask \&#34;show-summary\&#34; uses an untrusted task reference: oci://quay.io/redhat-appstudio-tekton-catalog/task-summary:0.1@sha256:c0f66b28c338426774e34a8d4a00349fbab798b19df5841a95727148d5ef3c65. Please upgrade the task version to: sha256:4d7a2201ce4cb6dca8a48f4d9d4e02d5d3b57ef8eb99009675f1a34f2923ae49&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.trusted&#34;,&#34;collections&#34;: [&#34;redhat&#34;],&#34;description&#34;: &#34;Check the trust of the Tekton Tasks used in the build Pipeline. There are two modes in which trust is verified. The first mode is used if Trusted Artifacts are enabled. In this case, a chain of trust is established for all the Tasks involved in creating an artifact. If the chain contains an untrusted Task, then a violation is emitted. The second mode is used as a fallback when Trusted Artifacts are not enabled. In this case, **all** Tasks in the build Pipeline must be trusted. To exclude this rule add \&#34;trusted_task.trusted:summary\&#34; to the `exclude` section of the policy configuration.&#34;,&#34;solution&#34;: &#34;If using Trusted Artifacts, be sure every Task in the build Pipeline responsible for producing a Trusted Artifact is trusted. Otherwise, ensure **all** Tasks in the build Pipeline are trusted. Note that trust is eventually revoked from Tasks when newer versions are made available.&#34;,&#34;term&#34;: &#34;summary&#34;,&#34;title&#34;: &#34;Tasks are trusted&#34;}}],&#34;successes&#34;: [{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.signature_check&#34;,&#34;description&#34;: &#34;The attestation signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Attestation signature check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.syntax_check&#34;,&#34;description&#34;: &#34;The attestation has correct syntax.&#34;,&#34;title&#34;: &#34;Attestation syntax check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.image.signature_check&#34;,&#34;description&#34;: &#34;The image signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Image signature check passed&#34;}}],&#34;success&#34;: false,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;&#34;,&#34;sig&#34;: &#34;MEUCIQD86lmOqCovYZDPKm0XxxsLgDQcFIFAv+QZxrFSHmCvQAIgTd1I005ox8MfABqsAen6PZEyg2MCEQNBCx1NLS3V0JQ=&#34;}],&#34;attestations&#34;: [{&#xA;&#34;type&#34;: &#34;https://in-toto.io/Statement/v0.1&#34;,&#34;predicateType&#34;: &#34;https://slsa.dev/provenance/v0.2&#34;,&#34;predicateBuildType&#34;: &#34;tekton.dev/v1beta1/TaskRun&#34;,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;SHA256:IhiN7gY+Z3uSSd7tmj6w5Zfhqafzdhm3DZjIvGc6iYY&#34;,&#34;sig&#34;: &#34;MEUCIQDcgZIwEkLFqD7U9HrobgEC8Jo7wm+xJ5AoyO3qg+aj8QIgb9xDpjYGRMmpVk+QATeVKlHonzBiu51HtT3J+lQXPXc=&#34;}]},{&#34;type&#34;: &#34;https://in-toto.io/Statement/v0.1&#34;,&#34;predicateType&#34;: &#34;https://slsa.dev/provenance/v0.2&#34;,&#34;predicateBuildType&#34;: &#34;tekton.dev/v1beta1/PipelineRun&#34;,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;SHA256:IhiN7gY+Z3uSSd7tmj6w5Zfhqafzdhm3DZjIvGc6iYY&#34;,&#34;sig&#34;: &#34;MEYCIQDKSihaAR/zAhJhR5GCqleDvfUUtvRw61vk0YeTBAnOSQIhAKa09B4yEfaSJronmWBFbu5cVPNxm17CMl/PElEz1POa&#34;}]}]}],&#34;key&#34;: &#34;-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEZP/0htjhVt2y0ohjgtIIgICOtQtA\nnaYJRuLprwIv6FDhZ5yFjYUEtsmoNcW7rx2KM6FOXGsCX3BNc7qhHELT+g==\n-----END PUBLIC KEY-----\n&#34;,&#34;policy&#34;: {&#34;name&#34;: &#34;Default&#34;,&#34;description&#34;: &#34;Includes rules for levels 1, 2 &amp; 3 of SLSA v0.1. This is the default config used for new Konflux applications. Source: https://github.com/conforma/config/blob/main/default/policy.yaml&#34;,&#34;sources&#34;: [{&#34;name&#34;: &#34;Default&#34;,&#34;policy&#34;: [&#34;oci::quay.io/enterprise-contract/ec-release-policy:konflux@sha256:59c6b95c02295edb7928ef187571d26d426993fd5aae0236a03c832afbd6072a&#34;],&#34;data&#34;: [&#34;git::github.com/release-engineering/rhtap-ec-policy//data?ref=67018469815ee9f81e47cfb54dae39d71ed5f389&#34;,&#34;oci::quay.io/konflux-ci/tekton-catalog/data-acceptable-bundles:latest@sha256:c75d0123e83efa6c182b6510c35982b48201143ce74a9a388680a0ee1aa4affb&#34;,&#34;oci::quay.io/konflux-ci/konflux-vanguard/data-acceptable-bundles:latest@sha256:0b31c7bc77a7463a1bc52f3d3625ef0e0e75443da7fd2de8005d7885282138ea&#34;,&#34;oci::quay.io/konflux-ci/integration-service-catalog/data-acceptable-bundles:latest@sha256:7b00455045ea3873a72caeb1e7ac7d036bd53963a26409891a4cc9d0d242b9fc&#34;],&#34;config&#34;: {&#34;include&#34;: [&#34;trusted_task.trusted&#34;]}}],&#34;publicKey&#34;: &#34;k8s://chains-e2e-vgkz/golden-image-public-keyjpfvpdmssh&#34;},&#34;ec-version&#34;: &#34;v0.9.25&#34;,&#34;effective-time&#34;: &#34;2026-05-09T03:09:57.818257257Z&#34;}----- END -----&#xA;&lt; Exit [It] verifies the release policy: Task are trusted - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:382 @ 05/09/26 03:10:06.028 (15.17s)&#xA;&gt; Enter [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 03:10:06.029&#xA;&lt; Exit [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 03:10:06.029 (0s)&#xA;</system-err>
          </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="passed" time="15.127874143">
              <system-err>&gt; Enter [BeforeEach] verify-enterprise-contract task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:154 @ 05/09/26 03:10:06.029&#xA;&lt; Exit [BeforeEach] verify-enterprise-contract task - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:154 @ 05/09/26 03:10:06.046 (17ms)&#xA;&gt; Enter [It] verifies the release policy: Task references are pinned - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:422 @ 05/09/26 03:10:06.046&#xA;Update public &lt;key to verify unpinned task image&#xA;Creating Pipeline &#34;verify-enterprise-contract-run-sc45g&#34;&#xA;Waiting for pipeline &#34;verify-enterprise-contract-run-sc45g&#34; to finish&#xA;*** Logs from pod &#39;verify-enterprise-contract-3ce59b0778a24d6c5ad066e8b3d9445d-pod&#39;, container &#39;step-report-json&#39;:&#xA;----- START -----{&#34;success&#34;: true,&#34;components&#34;: [{&#34;name&#34;: &#34;&#34;,&#34;containerImage&#34;: &#34;quay.io/redhat-appstudio-qe/enterprise-contract-tests@sha256:c1a2330b0117c4ccd642ba95539a499ae54f0282b124f0514ee57b274d674f10&#34;,&#34;source&#34;: {},&#34;warnings&#34;: [{&#34;msg&#34;: &#34;Pipeline task \&#34;build-container\&#34; uses an unpinned task reference, oci://quay.io/redhat-appstudio/appstudio-tasks:8be37c13984bc3f8af4d6314d87b1ec5e494b6ca-1@&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.pinned&#34;,&#34;collections&#34;: [&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;description&#34;: &#34;Check if all Tekton Tasks use a Task definition by a pinned reference. When using the git resolver, a commit ID is expected for the revision parameter. When using the bundles resolver, the bundle parameter is expected to include an image reference with a digest.&#34;,&#34;solution&#34;: &#34;Update the Pipeline definition so that all Task references have a pinned value as mentioned in the description.&#34;,&#34;term&#34;: &#34;buildah&#34;,&#34;title&#34;: &#34;Task references are pinned&#34;}},{&#34;msg&#34;: &#34;Pipeline task \&#34;clamav-scan\&#34; uses an unpinned task reference, oci://quay.io/redhat-appstudio/appstudio-tasks:8be37c13984bc3f8af4d6314d87b1ec5e494b6ca-1@&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.pinned&#34;,&#34;collections&#34;: [&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;description&#34;: &#34;Check if all Tekton Tasks use a Task definition by a pinned reference. When using the git resolver, a commit ID is expected for the revision parameter. When using the bundles resolver, the bundle parameter is expected to include an image reference with a digest.&#34;,&#34;solution&#34;: &#34;Update the Pipeline definition so that all Task references have a pinned value as mentioned in the description.&#34;,&#34;term&#34;: &#34;clamav-scan&#34;,&#34;title&#34;: &#34;Task references are pinned&#34;}},{&#34;msg&#34;: &#34;Pipeline task \&#34;appstudio-configure-build\&#34; uses an unpinned task reference, oci://quay.io/redhat-appstudio/appstudio-tasks:8be37c13984bc3f8af4d6314d87b1ec5e494b6ca-1@&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.pinned&#34;,&#34;collections&#34;: [&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;description&#34;: &#34;Check if all Tekton Tasks use a Task definition by a pinned reference. When using the git resolver, a commit ID is expected for the revision parameter. When using the bundles resolver, the bundle parameter is expected to include an image reference with a digest.&#34;,&#34;solution&#34;: &#34;Update the Pipeline definition so that all Task references have a pinned value as mentioned in the description.&#34;,&#34;term&#34;: &#34;configure-build&#34;,&#34;title&#34;: &#34;Task references are pinned&#34;}},{&#34;msg&#34;: &#34;Pipeline task \&#34;conftest-clair\&#34; uses an unpinned task reference, oci://quay.io/redhat-appstudio/appstudio-tasks:8be37c13984bc3f8af4d6314d87b1ec5e494b6ca-1@&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.pinned&#34;,&#34;collections&#34;: [&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;description&#34;: &#34;Check if all Tekton Tasks use a Task definition by a pinned reference. When using the git resolver, a commit ID is expected for the revision parameter. When using the bundles resolver, the bundle parameter is expected to include an image reference with a digest.&#34;,&#34;solution&#34;: &#34;Update the Pipeline definition so that all Task references have a pinned value as mentioned in the description.&#34;,&#34;term&#34;: &#34;conftest-clair&#34;,&#34;title&#34;: &#34;Task references are pinned&#34;}},{&#34;msg&#34;: &#34;Pipeline task \&#34;deprecated-base-image-check\&#34; uses an unpinned task reference, oci://quay.io/redhat-appstudio/appstudio-tasks:8be37c13984bc3f8af4d6314d87b1ec5e494b6ca-1@&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.pinned&#34;,&#34;collections&#34;: [&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;description&#34;: &#34;Check if all Tekton Tasks use a Task definition by a pinned reference. When using the git resolver, a commit ID is expected for the revision parameter. When using the bundles resolver, the bundle parameter is expected to include an image reference with a digest.&#34;,&#34;solution&#34;: &#34;Update the Pipeline definition so that all Task references have a pinned value as mentioned in the description.&#34;,&#34;term&#34;: &#34;deprecated-image-check&#34;,&#34;title&#34;: &#34;Task references are pinned&#34;}},{&#34;msg&#34;: &#34;Pipeline task \&#34;get-clair-results\&#34; uses an unpinned task reference, oci://quay.io/redhat-appstudio/appstudio-tasks:8be37c13984bc3f8af4d6314d87b1ec5e494b6ca-1@&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.pinned&#34;,&#34;collections&#34;: [&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;description&#34;: &#34;Check if all Tekton Tasks use a Task definition by a pinned reference. When using the git resolver, a commit ID is expected for the revision parameter. When using the bundles resolver, the bundle parameter is expected to include an image reference with a digest.&#34;,&#34;solution&#34;: &#34;Update the Pipeline definition so that all Task references have a pinned value as mentioned in the description.&#34;,&#34;term&#34;: &#34;get-clair-scan&#34;,&#34;title&#34;: &#34;Task references are pinned&#34;}},{&#34;msg&#34;: &#34;Pipeline task \&#34;clone-repository\&#34; uses an unpinned task reference, oci://quay.io/redhat-appstudio/appstudio-tasks:8be37c13984bc3f8af4d6314d87b1ec5e494b6ca-1@&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.pinned&#34;,&#34;collections&#34;: [&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;description&#34;: &#34;Check if all Tekton Tasks use a Task definition by a pinned reference. When using the git resolver, a commit ID is expected for the revision parameter. When using the bundles resolver, the bundle parameter is expected to include an image reference with a digest.&#34;,&#34;solution&#34;: &#34;Update the Pipeline definition so that all Task references have a pinned value as mentioned in the description.&#34;,&#34;term&#34;: &#34;git-clone&#34;,&#34;title&#34;: &#34;Task references are pinned&#34;}},{&#34;msg&#34;: &#34;Pipeline task \&#34;hacbs-test-evaluation\&#34; uses an unpinned task reference, oci://quay.io/redhat-appstudio/appstudio-tasks:8be37c13984bc3f8af4d6314d87b1ec5e494b6ca-1@&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.pinned&#34;,&#34;collections&#34;: [&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;description&#34;: &#34;Check if all Tekton Tasks use a Task definition by a pinned reference. When using the git resolver, a commit ID is expected for the revision parameter. When using the bundles resolver, the bundle parameter is expected to include an image reference with a digest.&#34;,&#34;solution&#34;: &#34;Update the Pipeline definition so that all Task references have a pinned value as mentioned in the description.&#34;,&#34;term&#34;: &#34;hacbs-test-evaluation&#34;,&#34;title&#34;: &#34;Task references are pinned&#34;}},{&#34;msg&#34;: &#34;Pipeline task \&#34;appstudio-init\&#34; uses an unpinned task reference, oci://quay.io/redhat-appstudio/appstudio-tasks:8be37c13984bc3f8af4d6314d87b1ec5e494b6ca-1@&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.pinned&#34;,&#34;collections&#34;: [&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;description&#34;: &#34;Check if all Tekton Tasks use a Task definition by a pinned reference. When using the git resolver, a commit ID is expected for the revision parameter. When using the bundles resolver, the bundle parameter is expected to include an image reference with a digest.&#34;,&#34;solution&#34;: &#34;Update the Pipeline definition so that all Task references have a pinned value as mentioned in the description.&#34;,&#34;term&#34;: &#34;init&#34;,&#34;title&#34;: &#34;Task references are pinned&#34;}},{&#34;msg&#34;: &#34;Pipeline task \&#34;sanity-inspect-image\&#34; uses an unpinned task reference, oci://quay.io/redhat-appstudio/appstudio-tasks:8be37c13984bc3f8af4d6314d87b1ec5e494b6ca-2@&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.pinned&#34;,&#34;collections&#34;: [&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;description&#34;: &#34;Check if all Tekton Tasks use a Task definition by a pinned reference. When using the git resolver, a commit ID is expected for the revision parameter. When using the bundles resolver, the bundle parameter is expected to include an image reference with a digest.&#34;,&#34;solution&#34;: &#34;Update the Pipeline definition so that all Task references have a pinned value as mentioned in the description.&#34;,&#34;term&#34;: &#34;sanity-inspect-image&#34;,&#34;title&#34;: &#34;Task references are pinned&#34;}},{&#34;msg&#34;: &#34;Pipeline task \&#34;sanity-label-check\&#34; uses an unpinned task reference, oci://quay.io/redhat-appstudio/appstudio-tasks:8be37c13984bc3f8af4d6314d87b1ec5e494b6ca-2@&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.pinned&#34;,&#34;collections&#34;: [&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;description&#34;: &#34;Check if all Tekton Tasks use a Task definition by a pinned reference. When using the git resolver, a commit ID is expected for the revision parameter. When using the bundles resolver, the bundle parameter is expected to include an image reference with a digest.&#34;,&#xA;&#34;solution&#34;: &#34;Update the Pipeline definition so that all Task references have a pinned value as mentioned in the description.&#34;,&#34;term&#34;: &#34;sanity-label-check&#34;,&#34;title&#34;: &#34;Task references are pinned&#34;}},{&#34;msg&#34;: &#34;Pipeline task \&#34;sanity-optional-label-check\&#34; uses an unpinned task reference, oci://quay.io/redhat-appstudio/appstudio-tasks:8be37c13984bc3f8af4d6314d87b1ec5e494b6ca-2@&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.pinned&#34;,&#34;collections&#34;: [&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;description&#34;: &#34;Check if all Tekton Tasks use a Task definition by a pinned reference. When using the git resolver, a commit ID is expected for the revision parameter. When using the bundles resolver, the bundle parameter is expected to include an image reference with a digest.&#34;,&#34;solution&#34;: &#34;Update the Pipeline definition so that all Task references have a pinned value as mentioned in the description.&#34;,&#34;term&#34;: &#34;sanity-label-check&#34;,&#34;title&#34;: &#34;Task references are pinned&#34;}},{&#34;msg&#34;: &#34;Pipeline task \&#34;sast-go\&#34; uses an unpinned task reference, oci://quay.io/redhat-appstudio/appstudio-tasks:8be37c13984bc3f8af4d6314d87b1ec5e494b6ca-2@&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.pinned&#34;,&#34;collections&#34;: [&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;description&#34;: &#34;Check if all Tekton Tasks use a Task definition by a pinned reference. When using the git resolver, a commit ID is expected for the revision parameter. When using the bundles resolver, the bundle parameter is expected to include an image reference with a digest.&#34;,&#34;solution&#34;: &#34;Update the Pipeline definition so that all Task references have a pinned value as mentioned in the description.&#34;,&#34;term&#34;: &#34;sast-go&#34;,&#34;title&#34;: &#34;Task references are pinned&#34;}},{&#34;msg&#34;: &#34;Pipeline task \&#34;sast-java-sec-check\&#34; uses an unpinned task reference, oci://quay.io/redhat-appstudio/appstudio-tasks:8be37c13984bc3f8af4d6314d87b1ec5e494b6ca-2@&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.pinned&#34;,&#34;collections&#34;: [&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;description&#34;: &#34;Check if all Tekton Tasks use a Task definition by a pinned reference. When using the git resolver, a commit ID is expected for the revision parameter. When using the bundles resolver, the bundle parameter is expected to include an image reference with a digest.&#34;,&#34;solution&#34;: &#34;Update the Pipeline definition so that all Task references have a pinned value as mentioned in the description.&#34;,&#34;term&#34;: &#34;sast-java-sec-check&#34;,&#34;title&#34;: &#34;Task references are pinned&#34;}},{&#34;msg&#34;: &#34;Pipeline task \&#34;sast-snyk-check\&#34; uses an unpinned task reference, oci://quay.io/redhat-appstudio/appstudio-tasks:8be37c13984bc3f8af4d6314d87b1ec5e494b6ca-2@&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.pinned&#34;,&#34;collections&#34;: [&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;description&#34;: &#34;Check if all Tekton Tasks use a Task definition by a pinned reference. When using the git resolver, a commit ID is expected for the revision parameter. When using the bundles resolver, the bundle parameter is expected to include an image reference with a digest.&#34;,&#34;solution&#34;: &#34;Update the Pipeline definition so that all Task references have a pinned value as mentioned in the description.&#34;,&#34;term&#34;: &#34;sast-snyk-check&#34;,&#34;title&#34;: &#34;Task references are pinned&#34;}},{&#34;msg&#34;: &#34;Pipeline task \&#34;show-summary\&#34; uses an unpinned task reference, oci://quay.io/redhat-appstudio/appstudio-tasks:8be37c13984bc3f8af4d6314d87b1ec5e494b6ca-2@&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;trusted_task.pinned&#34;,&#34;collections&#34;: [&#34;redhat&#34;,&#34;redhat_rpms&#34;],&#34;description&#34;: &#34;Check if all Tekton Tasks use a Task definition by a pinned reference. When using the git resolver, a commit ID is expected for the revision parameter. When using the bundles resolver, the bundle parameter is expected to include an image reference with a digest.&#34;,&#34;solution&#34;: &#34;Update the Pipeline definition so that all Task references have a pinned value as mentioned in the description.&#34;,&#34;term&#34;: &#34;summary&#34;,&#34;title&#34;: &#34;Task references are pinned&#34;}}],&#34;successes&#34;: [{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.signature_check&#34;,&#34;description&#34;: &#34;The attestation signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Attestation signature check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.attestation.syntax_check&#34;,&#34;description&#34;: &#34;The attestation has correct syntax.&#34;,&#34;title&#34;: &#34;Attestation syntax check passed&#34;}},{&#34;msg&#34;: &#34;Pass&#34;,&#34;metadata&#34;: {&#34;code&#34;: &#34;builtin.image.signature_check&#34;,&#34;description&#34;: &#34;The image signature matches available signing materials.&#34;,&#34;title&#34;: &#34;Image signature check passed&#34;}}],&#34;success&#34;: true,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;&#34;,&#34;sig&#34;: &#34;MEYCIQD0M+eFk8KPeOHvC6GNIQkaJGZvtOvvDqBvzi+qYgiS2gIhAP7stpq7Nl9vpF4tjqLC7/gr6t5yXc9Y353Btfe3DcEM&#34;},{&#34;keyid&#34;: &#34;&#34;,&#34;sig&#34;: &#34;MEUCIDkj9PKADlbayhD4DIUm5SRw2pCzSTeak1dJHAZOyQyQAiEApp4BQneeSKSbKbojFEzeJbVTPGBQrA7QnTzTblnU7nE=&#34;}],&#34;attestations&#34;: [{&#34;type&#34;: &#34;https://in-toto.io/Statement/v0.1&#34;,&#34;predicateType&#34;: &#34;https://slsa.dev/provenance/v0.2&#34;,&#34;predicateBuildType&#34;: &#34;https://tekton.dev/attestations/chains@v2&#34;,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;SHA256:w1ABTR6Lt6NlJapY8sIR8F2BvXZ6qn2q+GrC+jWwpqE&#34;,&#34;sig&#34;: &#34;MEQCICXkO7VwYxRHIYd+EbSeIvN+tKMyM4YSZkbUewMSefclAiBCoWnkdF5X4z6rY2YnOlwF5NrrPJh4f/tIvGJe1E3HIQ==&#34;}]},{&#34;type&#34;: &#34;https://in-toto.io/Statement/v0.1&#34;,&#34;predicateType&#34;: &#34;https://slsa.dev/provenance/v0.2&#34;,&#34;predicateBuildType&#34;: &#34;https://tekton.dev/attestations/chains@v2&#34;,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;SHA256:w1ABTR6Lt6NlJapY8sIR8F2BvXZ6qn2q+GrC+jWwpqE&#34;,&#34;sig&#34;: &#34;MEUCIQCmcnxF+boyOwR1RSLnZHUJgGtuQ5y0pm+hBjAhyb9TOwIgTtn/WYNIDWeW9WEALawsVBBtcsdeG91wuwIHpYo2zpc=&#34;}]},{&#34;type&#34;: &#34;https://in-toto.io/Statement/v0.1&#34;,&#34;predicateType&#34;: &#34;https://slsa.dev/provenance/v0.2&#34;,&#34;predicateBuildType&#34;: &#34;https://tekton.dev/attestations/chains/pipelinerun@v2&#34;,&#34;signatures&#34;: [{&#34;keyid&#34;: &#34;SHA256:w1ABTR6Lt6NlJapY8sIR8F2BvXZ6qn2q+GrC+jWwpqE&#34;,&#34;sig&#34;: &#34;MEUCIQCrK8Zvo5I45A0j/gvxmsJV30nb6/iQxQVeOMhELH964AIgXm12BtB+JHO5YWoFZAAAR+yMrpgeNBvn5vvVLYoYpHA=&#34;}]}]}],&#34;key&#34;: &#34;-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEPfwkY/ru2JRd6FSqIp7lT3gzjaEC\nEAg+paWtlme2KNcostCsmIbwz+bc2aFV+AxCOpRjRpp3vYrbS5KhkmgC1Q==\n-----END PUBLIC KEY-----\n&#34;,&#34;policy&#34;: {&#34;name&#34;: &#34;Default&#34;,&#34;description&#34;: &#34;Includes rules for levels 1, 2 &amp; 3 of SLSA v0.1. This is the default config used for new Konflux applications. Source: https://github.com/conforma/config/blob/main/default/policy.yaml&#34;,&#34;sources&#34;: [{&#34;name&#34;: &#34;Default&#34;,&#34;policy&#34;: [&#34;oci::quay.io/enterprise-contract/ec-release-policy:konflux@sha256:59c6b95c02295edb7928ef187571d26d426993fd5aae0236a03c832afbd6072a&#34;],&#34;data&#34;: [&#34;git::github.com/release-engineering/rhtap-ec-policy//data?ref=67018469815ee9f81e47cfb54dae39d71ed5f389&#34;,&#34;oci::quay.io/konflux-ci/tekton-catalog/data-acceptable-bundles:latest@sha256:c75d0123e83efa6c182b6510c35982b48201143ce74a9a388680a0ee1aa4affb&#34;,&#34;oci::quay.io/konflux-ci/konflux-vanguard/data-acceptable-bundles:latest@sha256:0b31c7bc77a7463a1bc52f3d3625ef0e0e75443da7fd2de8005d7885282138ea&#34;,&#34;oci::quay.io/konflux-ci/integration-service-catalog/data-acceptable-bundles:latest@sha256:7b00455045ea3873a72caeb1e7ac7d036bd53963a26409891a4cc9d0d242b9fc&#34;],&#34;config&#34;: {&#34;include&#34;: [&#34;trusted_task.pinned&#34;]}}],&#34;publicKey&#34;: &#34;k8s://chains-e2e-vgkz/unpinned-task-bundle-public-keykmfntlkytm&#34;},&#34;ec-version&#34;: &#34;v0.9.25&#34;,&#34;effective-time&#34;: &#34;2026-05-09T03:10:12.98771793Z&#34;}----- END -----&#xA;&lt; Exit [It] verifies the release policy: Task references are pinned - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:422 @ 05/09/26 03:10:21.157 (15.11s)&#xA;&gt; Enter [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 03:10:21.157&#xA;&lt; Exit [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/enterprise-contract/contract.go:29 @ 05/09/26 03:10:21.157 (0s)&#xA;</system-err>
          </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] [konflux-demo-suite] Maven project - Default build creates an application [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="passed" time="49.38111165">
              <system-err>&gt; Enter [BeforeAll] Maven project - Default build - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:84 @ 05/09/26 02:56:33.321&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo BeforeAll: initializing framework for appappMaven project - Default build&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo BeforeAll: namespacesuserNamespacekonflux-pdximanagedNamespacekonflux-pdxi-managed&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo BeforeAll: component configcomponentNamekonflux-demo-component-oztepacBranchNamekonflux-konflux-demo-component-oztecomponentRepositoryNamehacbs-test-project-konflux-demo&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo BeforeAll: creating release configmanagedNamespacekonflux-pdxi-manageduserNamespacekonflux-pdxi&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo createReleaseConfig: creating managed namespacemanagedNamespacekonflux-pdxi-managed&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo createReleaseConfig: creating release-service-accountmanagedNamespacekonflux-pdxi-managed&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo createReleaseConfig: finishedmanagedNamespacekonflux-pdxi-manageduserNamespacekonflux-pdxi&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo BeforeAll: created and linked release-catalog-trusted-artifacts-quay-secretmanagedNamespacekonflux-pdxi-managed&#34;&#xA;created and linked release-catalog-trusted-artifacts-quay-secret in namespace &#34;konflux-pdxi-managed&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo BeforeAll: setup completeappMaven project - Default buildcomponentNamekonflux-demo-component-ozte&#34;&#xA;&lt; Exit [BeforeAll] Maven project - Default build - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:84 @ 05/09/26 02:57:22.558 (49.237s)&#xA;&gt; Enter [It] creates an application - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:189 @ 05/09/26 02:57:22.558&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: creating applicationapplicationNamekonflux-demo-appnamespacekonflux-pdxi&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: application createdapplicationNamekonflux-demo-app&#34;&#xA;&lt; Exit [It] creates an application - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:189 @ 05/09/26 02:57:22.702 (144ms)&#xA;</system-err>
          </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="passed" time="0.259247698">
              <system-err>&gt; Enter [It] creates an IntegrationTestScenario for the app - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:202 @ 05/09/26 02:57:22.702&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: creating IntegrationTestScenarioapplicationNamekonflux-demo-appnamespacekonflux-pdxi&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: IntegrationTestScenario createdscenariomy-integration-test-sjij&#34;&#xA;&lt; Exit [It] creates an IntegrationTestScenario for the app - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:202 @ 05/09/26 02:57:22.962 (259ms)&#xA;</system-err>
          </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="passed" time="0.592208708">
              <system-err>&gt; Enter [It] creates new branch for the build - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:218 @ 05/09/26 02:57:22.962&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: creating branch for buildrepohacbs-test-project-konflux-demobranchbase-rdcrcufrommain&#34;&#xA;&lt; Exit [It] creates new branch for the build - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:218 @ 05/09/26 02:57:23.554 (592ms)&#xA;</system-err>
          </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="passed" time="30.063349321">
              <system-err>&gt; Enter [It] creates component konflux-demo-component (private: false) from git source https://github.com/redhat-appstudio-qe/hacbs-test-project-konflux-demo - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:233 @ 05/09/26 02:57:23.555&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: creating componentcomponentNamekonflux-demo-component-ozteapplicationNamekonflux-demo-appnamespacekonflux-pdxirevisionbase-rdcrcu&#34;&#xA;Image repository for component konflux-demo-component-ozte in namespace konflux-pdxi do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component konflux-demo-component-ozte in namespace konflux-pdxi do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: component createdcomponentNamekonflux-demo-component-ozte&#34;&#xA;&lt; Exit [It] creates component konflux-demo-component (private: false) from git source https://github.com/redhat-appstudio-qe/hacbs-test-project-konflux-demo - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:233 @ 05/09/26 02:57:53.618 (30.063s)&#xA;</system-err>
          </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="passed" time="80.108634419">
              <system-err>&gt; Enter [It] triggers creation of a PR in the sample repo - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:259 @ 05/09/26 02:57:53.619&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: waiting for PaC PRrepohacbs-test-project-konflux-demopacBranchNamekonflux-konflux-demo-component-ozte&#34;&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-ozte (found 12 PRs)&#34; &#34;error&#34;=null&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: PaC PR createdprNumber29725prSHA00e0525d6f925b212b0e4826aa883be2d029258b&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: waiting for pull-request PipelineRun to appear (will delete it)componentkonflux-demo-component-ozteprSHA00e0525d6f925b212b0e4826aa883be2d029258b&#34;&#xA;PipelineRun not found yet for component konflux-pdxi/konflux-demo-component-ozte prSHA 00e0525d6f925b212b0e4826aa883be2d029258b: no pipelinerun found for component konflux-demo-component-ozte&#xA;&lt; Exit [It] triggers creation of a PR in the sample repo - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:259 @ 05/09/26 02:59:13.727 (1m20.108s)&#xA;</system-err>
          </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="passed" time="0.022207626">
              <system-err>&gt; Enter [It] verifies component build status - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:297 @ 05/09/26 02:59:13.728&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: verifying component build status (PaC enabled)componentkonflux-demo-component-oztenamespacekonflux-pdxi&#34;&#xA;state: enabled&#xA;mergeUrl: https://github.com/redhat-appstudio-qe/hacbs-test-project-konflux-demo/pull/29725&#xA;errId: 0&#xA;errMessage: &#xA;configurationTime: Sat, 09 May 2026 02:58:52 UTC&#xA;&lt; Exit [It] verifies component build status - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:297 @ 05/09/26 02:59:13.75 (22ms)&#xA;</system-err>
          </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="passed" time="21.643964417">
              <system-err>&gt; Enter [It] should eventually lead to triggering a &#39;push&#39; event type PipelineRun after merging the PaC init branch  - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:335 @ 05/09/26 02:59:13.751&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: merging PaC PRrepohacbs-test-project-konflux-demoprNumber29725&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: PaC PR mergedheadSHAdf4b85d07e462aad02e527c127a0811c02c4ca24&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: waiting for push PipelineRun to startcomponentkonflux-demo-component-ozteheadSHAdf4b85d07e462aad02e527c127a0811c02c4ca24&#34;&#xA;PipelineRun has not been created yet for component konflux-pdxi/konflux-demo-component-ozte&#xA;&#34;msg&#34;=&#34;Konflux demo: GetComponentPipelineRun failed: no pipelinerun found for component konflux-demo-component-ozte&#34; &#34;error&#34;=null&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: push PipelineRun startedpipelineRunkonflux-demo-component-ozte-on-push-tc6sl&#34;&#xA;&lt; Exit [It] should eventually lead to triggering a &#39;push&#39; event type PipelineRun after merging the PaC init branch  - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:335 @ 05/09/26 02:59:35.395 (21.644s)&#xA;</system-err>
          </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="passed" time="0.000232516">
              <system-err>&gt; Enter [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:369 @ 05/09/26 02:59:35.396&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: checking build PipelineRun has no snapshot annotationpipelineRunkonflux-demo-component-ozte-on-push-tc6sl&#34;&#xA;&lt; Exit [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:369 @ 05/09/26 02:59:35.396 (0s)&#xA;</system-err>
          </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="passed" time="480.015713116">
              <system-err>&gt; Enter [It] should eventually complete successfully - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:373 @ 05/09/26 02:59:35.396&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: waiting for build PipelineRun to finishpipelineRunkonflux-demo-component-ozte-on-push-tc6slcomponentkonflux-demo-component-ozteheadSHAdf4b85d07e462aad02e527c127a0811c02c4ca24&#34;&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl found for Component konflux-pdxi/konflux-demo-component-ozte&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-tc6sl reason: Completed&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: build PipelineRun finishedpipelineRunkonflux-demo-component-ozte-on-push-tc6slheadSHAdf4b85d07e462aad02e527c127a0811c02c4ca24&#34;&#xA;&lt; Exit [It] should eventually complete successfully - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:373 @ 05/09/26 03:07:35.412 (8m0.016s)&#xA;</system-err>
          </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="passed" time="0.528782056">
              <system-err>&gt; Enter [It] should validate Tekton TaskRun test results successfully - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:389 @ 05/09/26 03:07:35.416&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: validating build PipelineRun TaskRun test resultscomponentkonflux-demo-component-ozteheadSHAdf4b85d07e462aad02e527c127a0811c02c4ca24&#34;&#xA;&lt; Exit [It] should validate Tekton TaskRun test results successfully - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:389 @ 05/09/26 03:07:35.944 (529ms)&#xA;</system-err>
          </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="passed" time="0.026306025">
              <system-err>&gt; Enter [It] should validate that the build pipelineRun is signed - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:403 @ 05/09/26 03:07:35.945&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: validating build PipelineRun is signedcomponentkonflux-demo-component-ozte&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: build PipelineRun is signedpipelineRunkonflux-demo-component-ozte-on-push-tc6sl&#34;&#xA;&lt; Exit [It] should validate that the build pipelineRun is signed - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:403 @ 05/09/26 03:07:35.971 (26ms)&#xA;</system-err>
          </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="passed" time="0.014155429">
              <system-err>&gt; Enter [It] should find the related Snapshot CR - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:419 @ 05/09/26 03:07:35.972&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: waiting for Snapshot CRpipelineRunkonflux-demo-component-ozte-on-push-tc6slnamespacekonflux-pdxi&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: Snapshot foundsnapshotkonflux-demo-app-20260509-025918-000&#34;&#xA;&lt; Exit [It] should find the related Snapshot CR - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:419 @ 05/09/26 03:07:35.986 (14ms)&#xA;</system-err>
          </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="passed" time="0.089791396">
              <system-err>&gt; Enter [It] should validate that the build pipelineRun is annotated with the name of the Snapshot - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:432 @ 05/09/26 03:07:35.986&#xA;&lt; Exit [It] should validate that the build pipelineRun is annotated with the name of the Snapshot - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:432 @ 05/09/26 03:07:36.076 (90ms)&#xA;</system-err>
          </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="passed" time="0.094522913">
              <system-err>&gt; Enter [It] should find the related Integration Test PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:441 @ 05/09/26 03:07:36.077&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: waiting for Integration Test PipelineRunscenariomy-integration-test-sjijsnapshotkonflux-demo-app-20260509-025918-000&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: Integration Test PipelineRun foundpipelineRunmy-integration-test-sjij-klqmv&#34;&#xA;&lt; Exit [It] should find the related Integration Test PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:441 @ 05/09/26 03:07:36.171 (94ms)&#xA;</system-err>
          </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="passed" time="220.424631263">
              <system-err>&gt; Enter [It] should eventually succeed - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:462 @ 05/09/26 03:07:36.172&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: triggering PaC build retriggercomponentkonflux-demo-component-ozte&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: waiting for retriggered PipelineRun to appearcomponentkonflux-demo-component-ozte&#34;&#xA;PipelineRun is not been retriggered yet for the component konflux-pdxi/konflux-demo-component-ozte&#xA;&#34;msg&#34;=&#34;Konflux demo: GetComponentPipelineRunWithType (incoming) failed: no pipelinerun found for component konflux-demo-component-ozte&#34; &#34;error&#34;=null&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: waiting for retriggered build PipelineRun to finishpipelineRunkonflux-demo-component-ozte-on-push-rsvwn&#34;&#xA;PipelineRun konflux-demo-component-ozte-on-push-rsvwn found for Component konflux-pdxi/konflux-demo-component-ozte&#xA;PipelineRun konflux-demo-component-ozte-on-push-rsvwn reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-rsvwn reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-rsvwn reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-rsvwn reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-rsvwn reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-rsvwn reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-rsvwn reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-rsvwn reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-rsvwn reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-rsvwn reason: Running&#xA;PipelineRun konflux-demo-component-ozte-on-push-rsvwn reason: Completed&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: retriggered build PipelineRun finishedpipelineRunkonflux-demo-component-ozte-on-push-rsvwn&#34;&#xA;&lt; Exit [It] should eventually succeed - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:462 @ 05/09/26 03:11:16.597 (3m40.424s)&#xA;</system-err>
          </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="passed" time="0.081411943">
              <system-err>&gt; Enter [It] should eventually complete successfully - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:493 @ 05/09/26 03:11:16.597&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: waiting for Integration pipeline to finishscenariomy-integration-test-sjijsnapshotkonflux-demo-app-20260509-025918-000&#34;&#xA;PipelineRun my-integration-test-sjij-klqmv reason: Succeeded&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: Integration pipeline finishedsnapshotkonflux-demo-app-20260509-025918-000&#34;&#xA;&lt; Exit [It] should eventually complete successfully - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:493 @ 05/09/26 03:11:16.679 (81ms)&#xA;</system-err>
          </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="passed" time="0.067860551">
              <system-err>&gt; Enter [It] should lead to Snapshot CR being marked as passed - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:505 @ 05/09/26 03:11:16.679&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: waiting for Snapshot to be marked as passedpipelineRunkonflux-demo-component-ozte-on-push-tc6sl&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: Snapshot marked as passedsnapshotkonflux-demo-app-20260509-025918-000&#34;&#xA;&lt; Exit [It] should lead to Snapshot CR being marked as passed - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:505 @ 05/09/26 03:11:16.747 (68ms)&#xA;</system-err>
          </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="passed" time="0.14987742">
              <system-err>&gt; Enter [It] should trigger creation of Release CR - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:518 @ 05/09/26 03:11:16.748&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: waiting for Release CRsnapshotkonflux-demo-app-20260509-025918-000namespacekonflux-pdxi&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: Release CR createdreleasekonflux-demo-app-20260509-025918-000-df4b85d-q6v9j&#34;&#xA;&lt; Exit [It] should trigger creation of Release CR - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:518 @ 05/09/26 03:11:16.897 (150ms)&#xA;</system-err>
          </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="passed" time="0.137011265">
              <system-err>&gt; Enter [It] triggers creation of Release PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:533 @ 05/09/26 03:11:16.898&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: waiting for Release PipelineRun to startreleasekonflux-demo-app-20260509-025918-000-df4b85d-q6v9jmanagedNamespacekonflux-pdxi-managed&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: Release PipelineRun startedpipelineRunmanaged-blm2d&#34;&#xA;&lt; Exit [It] triggers creation of Release PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:533 @ 05/09/26 03:11:17.035 (137ms)&#xA;</system-err>
          </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="passed" time="0.085429242">
              <system-err>&gt; Enter [It] should eventually succeed - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:552 @ 05/09/26 03:11:17.035&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: waiting for Release PipelineRun to completereleasekonflux-demo-app-20260509-025918-000-df4b85d-q6v9jmanagedNamespacekonflux-pdxi-managed&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: Release PipelineRun succeededreleasekonflux-demo-app-20260509-025918-000-df4b85d-q6v9j&#34;&#xA;&lt; Exit [It] should eventually succeed - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:552 @ 05/09/26 03:11:17.121 (85ms)&#xA;</system-err>
          </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="passed" time="90.11036382">
              <system-err>&gt; Enter [It] should lead to Release CR being marked as succeeded - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:578 @ 05/09/26 03:11:17.121&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: waiting for Release CR to be marked as releasedreleasekonflux-demo-app-20260509-025918-000-df4b85d-q6v9jnamespacekonflux-pdxi&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: Release CR marked as succeededreleasekonflux-demo-app-20260509-025918-000-df4b85d-q6v9j&#34;&#xA;&lt; Exit [It] should lead to Release CR being marked as succeeded - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:578 @ 05/09/26 03:11:17.236 (114ms)&#xA;&gt; Enter [AfterAll] Maven project - Default build - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:154 @ 05/09/26 03:11:17.236&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo AfterAll: cleaning up namespacesuserNamespacekonflux-pdximanagedNamespacekonflux-pdxi-managed&#34;&#xA;&#34;msg&#34;=&#34;Konflux demo AfterAll: failed to delete GitHub ref konflux-konflux-demo-component-ozte in repo hacbs-test-project-konflux-demo: DELETE https://api.github.com/repos/redhat-appstudio-qe/hacbs-test-project-konflux-demo/git/refs/heads/konflux-konflux-demo-component-ozte: 422 Reference does not exist []&#34; &#34;error&#34;=null&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo AfterAll: cleanup finishedcomponentRepositoryNamehacbs-test-project-konflux-demo&#34;&#xA;&lt; Exit [AfterAll] Maven project - Default build - /tmp/tmp.CNj1aJY7Z5/tests/konflux-demo/konflux-demo.go:154 @ 05/09/26 03:12:47.231 (1m29.996s)&#xA;</system-err>
          </testcase>
          <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="100.670006635">
              <system-err>&gt; Enter [BeforeAll] with happy path for general flow of Integration service - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:52 @ 05/09/26 02:56:33.413&#xA;Image repository for component test-component-pac-gsbtxh in namespace integration1-bkbp 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.CNj1aJY7Z5/tests/integration-service/integration.go:52 @ 05/09/26 02:57:14.063 (40.65s)&#xA;&gt; Enter [It] triggers a build PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:85 @ 05/09/26 02:57:14.064&#xA;no pipelinerun found for component test-component-pac-gsbtxh (application: integ-app-ulue, namespace: integration1-bkbp)no pipelinerun found for component test-component-pac-gsbtxh (application: integ-app-ulue, namespace: integration1-bkbp)no pipelinerun found for component test-component-pac-gsbtxh (application: integ-app-ulue, namespace: integration1-bkbp)&#xA;&lt; Exit [It] triggers a build PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:85 @ 05/09/26 02:58:14.082 (1m0.019s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 02:58:14.083&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 02:58:14.083 (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.093833362">
              <system-err>&gt; Enter [It] verifies if the build PipelineRun contains the finalizer - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:90 @ 05/09/26 02:58:14.083&#xA;&lt; Exit [It] verifies if the build PipelineRun contains the finalizer - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:90 @ 05/09/26 02:58:14.177 (94ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 02:58:14.177&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 02:58:14.177 (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="580.087197288">
              <system-err>&gt; Enter [It] waits for build PipelineRun to succeed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:101 @ 05/09/26 02:58:14.177&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr found for Component integration1-bkbp/test-component-pac-gsbtxh&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: ResolvingTaskRef&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun test-component-pac-gsbtxh-on-pull-request-crjkr reason: Running&#xA;PipelineRun my-integration-test-mlug-pn6ll reason: ResolvingPipelineRef&#xA;PipelineRun my-integration-test-mlug-pn6ll reason: Succeeded&#xA;&lt; Exit [It] waits for build PipelineRun to succeed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:101 @ 05/09/26 03:07:54.264 (9m40.087s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.264&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.264 (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.272961706">
              <system-err>&gt; Enter [It] should have a related PaC init PR created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:107 @ 05/09/26 03:07:54.265&#xA;&lt; Exit [It] should have a related PaC init PR created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:107 @ 05/09/26 03:07:54.537 (272ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.538&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.538 (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.059602335">
              <system-err>&gt; Enter [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:128 @ 05/09/26 03:07:54.538&#xA;&lt; Exit [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:128 @ 05/09/26 03:07:54.598 (59ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.598&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.598 (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.009907555">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:132 @ 05/09/26 03:07:54.598&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:132 @ 05/09/26 03:07:54.608 (10ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.608&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.608 (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.037582575">
              <system-err>&gt; Enter [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:137 @ 05/09/26 03:07:54.609&#xA;&lt; Exit [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:137 @ 05/09/26 03:07:54.646 (37ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.646&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.646 (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.01643774">
              <system-err>&gt; Enter [It] verifies that the finalizer has been removed from the build pipelinerun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:141 @ 05/09/26 03:07:54.647&#xA;&lt; Exit [It] verifies that the finalizer has been removed from the build pipelinerun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:141 @ 05/09/26 03:07:54.663 (16ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.663&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.663 (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.075605484">
              <system-err>&gt; Enter [It] checks if all of the integrationPipelineRuns passed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:154 @ 05/09/26 03:07:54.663&#xA;Integration test scenario my-integration-test-mlug is found&#xA;PipelineRun my-integration-test-mlug-pn6ll reason: Succeeded&#xA;&lt; Exit [It] checks if all of the integrationPipelineRuns passed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:154 @ 05/09/26 03:07:54.738 (75ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.739&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.739 (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.008860607">
              <system-err>&gt; Enter [It] checks if the passed status of integration test is reported in the Snapshot - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:158 @ 05/09/26 03:07:54.739&#xA;&lt; Exit [It] checks if the passed status of integration test is reported in the Snapshot - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:158 @ 05/09/26 03:07:54.748 (8ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.748&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.748 (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.007055379">
              <system-err>&gt; Enter [It] checks if the skipped integration test is absent from the Snapshot&#39;s status annotation - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:173 @ 05/09/26 03:07:54.749&#xA;&lt; Exit [It] checks if the skipped integration test is absent from the Snapshot&#39;s status annotation - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:173 @ 05/09/26 03:07:54.755 (7ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.755&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.755 (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.069080669">
              <system-err>&gt; Enter [It] checks if the finalizer was removed from all of the related Integration pipelineRuns - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:183 @ 05/09/26 03:07:54.756&#xA;Integration test scenario my-integration-test-mlug is found&#xA;&lt; Exit [It] checks if the finalizer was removed from all of the related Integration pipelineRuns - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:183 @ 05/09/26 03:07:54.825 (68ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.825&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.825 (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.113053535">
              <system-err>&gt; Enter [It] creates a ReleasePlan - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:188 @ 05/09/26 03:07:54.826&#xA;IntegrationTestScenario my-integration-test-mlug is found&#xA;IntegrationTestScenario skipped-its is found&#xA;&lt; Exit [It] creates a ReleasePlan - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:188 @ 05/09/26 03:07:54.938 (112ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.938&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.939 (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.028700268">
              <system-err>&gt; Enter [It] creates an snapshot of push event - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:198 @ 05/09/26 03:07:54.939&#xA;&lt; Exit [It] creates an snapshot of push event - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:198 @ 05/09/26 03:07:54.968 (28ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.968&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.968 (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.017959861">
              <system-err>&gt; Enter [It] checks if the global candidate is updated after push event - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:205 @ 05/09/26 03:07:54.968&#xA;&lt; Exit [It] checks if the global candidate is updated after push event - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:205 @ 05/09/26 03:07:54.986 (18ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.986&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:07:54.986 (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="40.064055365">
              <system-err>&gt; Enter [It] checks if all of the integrationPipelineRuns created by push event passed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:218 @ 05/09/26 03:07:54.987&#xA;Integration test scenario my-integration-test-mlug is found&#xA;PipelineRun has not been created yet for test scenario %s and snapshot %s/%s my-integration-test-mlug integration1-bkbp snapshot-sample-ihke&#xA;PipelineRun my-integration-test-mlug-8j5cw reason: Running&#xA;PipelineRun my-integration-test-mlug-8j5cw reason: Succeeded&#xA;&lt; Exit [It] checks if all of the integrationPipelineRuns created by push event passed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:218 @ 05/09/26 03:08:35.051 (40.064s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:08:35.051&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:08:35.051 (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="3.841586354">
              <system-err>&gt; Enter [It] checks if a Release is created successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:222 @ 05/09/26 03:08:35.051&#xA;&lt; Exit [It] checks if a Release is created successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:222 @ 05/09/26 03:08:35.065 (14ms)&#xA;&gt; Enter [AfterAll] with happy path for general flow of Integration service - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:68 @ 05/09/26 03:08:35.066&#xA;&lt; Exit [AfterAll] with happy path for general flow of Integration service - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:68 @ 05/09/26 03:08:38.893 (3.827s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:08:38.893&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:08:38.893 (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="332.526270461">
              <system-err>&gt; Enter [BeforeAll] with an integration test fail - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:234 @ 05/09/26 03:08:38.893&#xA;&lt; Exit [BeforeAll] with an integration test fail - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:234 @ 05/09/26 03:08:51.38 (12.487s)&#xA;&gt; Enter [It] triggers a build PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:266 @ 05/09/26 03:08:51.381&#xA;no pipelinerun found for component test-component-pac-qbmncf (application: integ-app-zbro, namespace: integration2-vvvi)PipelineRun test-component-pac-qbmncf-on-pull-request-n7jnx found for Component integration2-vvvi/test-component-pac-qbmncf&#xA;PipelineRun test-component-pac-qbmncf-on-pull-request-n7jnx reason: Running&#xA;PipelineRun test-component-pac-qbmncf-on-pull-request-n7jnx reason: Running&#xA;PipelineRun test-component-pac-qbmncf-on-pull-request-n7jnx reason: Running&#xA;PipelineRun test-component-pac-qbmncf-on-pull-request-n7jnx reason: Running&#xA;PipelineRun test-component-pac-qbmncf-on-pull-request-n7jnx reason: Running&#xA;PipelineRun test-component-pac-qbmncf-on-pull-request-n7jnx reason: Running&#xA;PipelineRun test-component-pac-qbmncf-on-pull-request-n7jnx reason: Running&#xA;PipelineRun test-component-pac-qbmncf-on-pull-request-n7jnx reason: Running&#xA;PipelineRun test-component-pac-qbmncf-on-pull-request-n7jnx reason: Running&#xA;PipelineRun test-component-pac-qbmncf-on-pull-request-n7jnx reason: Running&#xA;PipelineRun test-component-pac-qbmncf-on-pull-request-n7jnx reason: Running&#xA;PipelineRun my-integration-test-vday-xh4j6 reason: Running&#xA;PipelineRun my-integration-test-vday-xh4j6 reason: Running&#xA;PipelineRun my-integration-test-vday-xh4j6 reason: Running&#xA;PipelineRun my-integration-test-vday-xh4j6 reason: Running&#xA;PipelineRun my-integration-test-vday-xh4j6 reason: Succeeded&#xA;&lt; Exit [It] triggers a build PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:266 @ 05/09/26 03:14:11.419 (5m20.039s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.42&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.42 (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.279692299">
              <system-err>&gt; Enter [It] should have a related PaC init PR created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:273 @ 05/09/26 03:14:11.42&#xA;&lt; Exit [It] should have a related PaC init PR created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:273 @ 05/09/26 03:14:11.7 (279ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.7&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.7 (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.017060825">
              <system-err>&gt; Enter [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:292 @ 05/09/26 03:14:11.7&#xA;&lt; Exit [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:292 @ 05/09/26 03:14:11.717 (17ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.717&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.717 (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.005450606">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:296 @ 05/09/26 03:14:11.718&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:296 @ 05/09/26 03:14:11.723 (5ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.723&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.723 (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.016577072">
              <system-err>&gt; Enter [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:301 @ 05/09/26 03:14:11.723&#xA;&lt; Exit [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:301 @ 05/09/26 03:14:11.74 (16ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.74&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.74 (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="0.0100886">
              <system-err>&gt; Enter [It] checks if all of the integrationPipelineRuns finished - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:305 @ 05/09/26 03:14:11.74&#xA;Integration test scenario my-integration-test-vday is found&#xA;PipelineRun my-integration-test-vday-xh4j6 reason: Succeeded&#xA;&lt; Exit [It] checks if all of the integrationPipelineRuns finished - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:305 @ 05/09/26 03:14:11.75 (10ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.75&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.75 (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.005876867">
              <system-err>&gt; Enter [It] checks if the failed status of integration test is reported in the Snapshot - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:309 @ 05/09/26 03:14:11.751&#xA;&lt; Exit [It] checks if the failed status of integration test is reported in the Snapshot - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:309 @ 05/09/26 03:14:11.756 (6ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.756&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.756 (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.005628401">
              <system-err>&gt; Enter [It] checks if the skipped integration test is absent from the Snapshot&#39;s status annotation - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:324 @ 05/09/26 03:14:11.757&#xA;&lt; Exit [It] checks if the skipped integration test is absent from the Snapshot&#39;s status annotation - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:324 @ 05/09/26 03:14:11.762 (5ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.762&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.762 (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.005303851">
              <system-err>&gt; Enter [It] checks if snapshot is marked as failed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:334 @ 05/09/26 03:14:11.763&#xA;&lt; Exit [It] checks if snapshot is marked as failed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:334 @ 05/09/26 03:14:11.768 (5ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.768&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.768 (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.009216636">
              <system-err>&gt; Enter [It] checks if the finalizer was removed from all of the related Integration pipelineRuns - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:340 @ 05/09/26 03:14:11.768&#xA;Integration test scenario my-integration-test-vday is found&#xA;&lt; Exit [It] checks if the finalizer was removed from all of the related Integration pipelineRuns - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:340 @ 05/09/26 03:14:11.777 (9ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.777&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.777 (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.045172217">
              <system-err>&gt; Enter [It] creates a new IntegrationTestScenario - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:344 @ 05/09/26 03:14:11.778&#xA;&lt; Exit [It] creates a new IntegrationTestScenario - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:344 @ 05/09/26 03:14:11.823 (45ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.823&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.823 (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.020354284">
              <system-err>&gt; Enter [It] updates the Snapshot with the re-run label for the new scenario - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:349 @ 05/09/26 03:14:11.823&#xA;&lt; Exit [It] updates the Snapshot with the re-run label for the new scenario - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:349 @ 05/09/26 03:14:11.843 (20ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.843&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:11.843 (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.016584434">
              <system-err>&gt; Enter [It] checks if the new integration pipelineRun started - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:358 @ 05/09/26 03:14:11.844&#xA;PipelineRun has not been created yet for test scenario %s and snapshot %s/%s my-integration-test-dgcp integration2-vvvi integ-app-zbro-20260509-030902-000&#xA;&lt; Exit [It] checks if the new integration pipelineRun started - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:358 @ 05/09/26 03:14:31.86 (20.016s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:31.86&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:31.86 (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.005902727">
              <system-err>&gt; Enter [It] checks if the re-run label was removed from the Snapshot - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:364 @ 05/09/26 03:14:31.861&#xA;&lt; Exit [It] checks if the re-run label was removed from the Snapshot - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:364 @ 05/09/26 03:14:31.866 (6ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:31.866&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:31.866 (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="20.021701067">
              <system-err>&gt; Enter [It] checks if all integration pipelineRuns finished successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:378 @ 05/09/26 03:14:31.867&#xA;Integration test scenario my-integration-test-dgcp is found&#xA;PipelineRun my-integration-test-dgcp-cql2d reason: Running&#xA;PipelineRun my-integration-test-dgcp-cql2d reason: Succeeded&#xA;Integration test scenario my-integration-test-vday is found&#xA;PipelineRun my-integration-test-vday-xh4j6 reason: Succeeded&#xA;&lt; Exit [It] checks if all integration pipelineRuns finished successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:378 @ 05/09/26 03:14:51.888 (20.021s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:51.889&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:51.889 (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.092264779">
              <system-err>&gt; Enter [It] checks if the name of the re-triggered pipelinerun is reported in the Snapshot - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:382 @ 05/09/26 03:14:51.889&#xA;&lt; Exit [It] checks if the name of the re-triggered pipelinerun is reported in the Snapshot - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:382 @ 05/09/26 03:14:51.981 (92ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:51.981&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:51.981 (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.006295718">
              <system-err>&gt; Enter [It] checks if snapshot is still marked as failed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:399 @ 05/09/26 03:14:51.982&#xA;&lt; Exit [It] checks if snapshot is still marked as failed - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:399 @ 05/09/26 03:14:51.988 (6ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:51.988&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:51.988 (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.015230668">
              <system-err>&gt; Enter [It] creates an snapshot of push event - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:406 @ 05/09/26 03:14:51.988&#xA;&lt; Exit [It] creates an snapshot of push event - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:406 @ 05/09/26 03:14:52.003 (15ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:52.003&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:52.003 (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="3.607879804">
              <system-err>&gt; Enter [It] checks no Release CRs are created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:413 @ 05/09/26 03:14:52.004&#xA;&lt; Exit [It] checks no Release CRs are created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:413 @ 05/09/26 03:14:52.009 (5ms)&#xA;&gt; Enter [AfterAll] with an integration test fail - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:250 @ 05/09/26 03:14:52.009&#xA;&lt; Exit [AfterAll] with an integration test fail - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:250 @ 05/09/26 03:14:55.611 (3.603s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:55.612&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/integration.go:49 @ 05/09/26 03:14:55.612 (0s)&#xA;</system-err>
          </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="passed" time="98.298567947">
              <system-err>&gt; Enter [BeforeAll] component update with renovate - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:72 @ 05/09/26 02:56:33.314&#xA;ReleaseAdmissionPlan data: {&#34;Mapping&#34;:{&#34;Components&#34;:[{&#34;Name&#34;:&#34;gh-multi-component-parent-eexq&#34;,&#34;Repository&#34;:&#34;quay.io/redhat-appstudio-qe/release-repository&#34;}]}}&#xA;&lt; Exit [BeforeAll] component update with renovate - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:72 @ 05/09/26 02:57:21.255 (47.94s)&#xA;&gt; Enter [It] creates component with nudges - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:235 @ 05/09/26 02:57:21.255&#xA;Image repository for component gh-multi-component-child-eexq in namespace build-e2e-ikpq do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component gh-multi-component-child-eexq in namespace build-e2e-ikpq do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component gh-multi-component-parent-eexq in namespace build-e2e-ikpq do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [It] creates component with nudges - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:235 @ 05/09/26 02:58:11.612 (50.357s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 02:58:11.612&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 02:58:11.612 (0s)&#xA;</system-err>
          </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="passed" time="80.071066864">
              <system-err>&gt; Enter [It] triggers a PipelineRun for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:259 @ 05/09/26 02:58:11.613&#xA;PipelineRun has not been created yet for the component build-e2e-ikpq/gh-multi-component-parent-eexq&#xA;PipelineRun has not been created yet for the component build-e2e-ikpq/gh-multi-component-parent-eexq&#xA;PipelineRun has not been created yet for the component build-e2e-ikpq/gh-multi-component-parent-eexq&#xA;PipelineRun has not been created yet for the component build-e2e-ikpq/gh-multi-component-parent-eexq&#xA;&lt; Exit [It] triggers a PipelineRun for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:259 @ 05/09/26 02:59:31.684 (1m20.071s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 02:59:31.684&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 02:59:31.684 (0s)&#xA;</system-err>
          </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="passed" time="500.030394021">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:274 @ 05/09/26 02:59:31.685&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs found for Component build-e2e-ikpq/gh-multi-component-parent-eexq&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-pull-request-vtmgs reason: Succeeded&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:274 @ 05/09/26 03:07:51.715 (8m20.03s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:07:51.715&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:07:51.715 (0s)&#xA;</system-err>
          </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="passed" time="0.012196487">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for child component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:285 @ 05/09/26 03:07:51.716&#xA;PipelineRun gh-multi-component-child-eexq-on-pull-request-8lb7d found for Component build-e2e-ikpq/gh-multi-component-child-eexq&#xA;PipelineRun gh-multi-component-child-eexq-on-pull-request-8lb7d reason: Succeeded&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for child component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:285 @ 05/09/26 03:07:51.728 (12ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:07:51.728&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:07:51.728 (0s)&#xA;</system-err>
          </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="passed" time="0.204892153">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for child component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:289 @ 05/09/26 03:07:51.728&#xA;&lt; Exit [It] should lead to a PaC PR creation for child component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:289 @ 05/09/26 03:07:51.933 (204ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:07:51.933&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:07:51.933 (0s)&#xA;</system-err>
          </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="passed" time="1.905077512">
              <system-err>&gt; Enter [It] Merging the PaC PR should be successful for child component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:307 @ 05/09/26 03:07:51.934&#xA;merged result sha: 2cf10ea52fedaf9ad4813d8d912cf6cd137cee4f for PR #1&#xA;&lt; Exit [It] Merging the PaC PR should be successful for child component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:307 @ 05/09/26 03:07:53.838 (1.904s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:07:53.839&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:07:53.839 (0s)&#xA;</system-err>
          </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="passed" time="5.34888951">
              <system-err>&gt; Enter [It] create dockerfile and yaml manifest that references build and distribution repositories - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:318 @ 05/09/26 03:07:53.84&#xA;&lt; Exit [It] create dockerfile and yaml manifest that references build and distribution repositories - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:318 @ 05/09/26 03:07:59.188 (5.348s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:07:59.188&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:07:59.188 (0s)&#xA;</system-err>
          </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="passed" time="0.153134421">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:358 @ 05/09/26 03:07:59.189&#xA;&lt; Exit [It] should lead to a PaC PR creation for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:358 @ 05/09/26 03:07:59.341 (152ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:07:59.342&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:07:59.342 (0s)&#xA;</system-err>
          </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="passed" time="1.658501306">
              <system-err>&gt; Enter [It] Merging the PaC PR should be successful for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:375 @ 05/09/26 03:07:59.343&#xA;merged result sha: b8a27e5d6b270ad83d617f9eb6b5d37b3c17d2b9 for PR #1&#xA;&lt; Exit [It] Merging the PaC PR should be successful for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:375 @ 05/09/26 03:08:01 (1.658s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:08:01.001&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:08:01.001 (0s)&#xA;</system-err>
          </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="passed" time="25.07719572">
              <system-err>&gt; Enter [It] PR merge triggers PAC PipelineRun for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:385 @ 05/09/26 03:08:01.002&#xA;Push PipelineRun has not been created yet for the component build-e2e-ikpq/gh-multi-component-parent-eexq&#xA;&lt; Exit [It] PR merge triggers PAC PipelineRun for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:385 @ 05/09/26 03:08:26.078 (25.077s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:08:26.079&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:08:26.079 (0s)&#xA;</system-err>
          </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="passed" time="300.290991346">
              <system-err>&gt; Enter [It] PAC PipelineRun for parent component  is successful - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:401 @ 05/09/26 03:08:26.079&#xA;PipelineRun gh-multi-component-parent-eexq-on-push-ktttg found for Component build-e2e-ikpq/gh-multi-component-parent-eexq&#xA;PipelineRun gh-multi-component-parent-eexq-on-push-ktttg reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-push-ktttg reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-push-ktttg reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-push-ktttg reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-push-ktttg reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-push-ktttg reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-push-ktttg reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-push-ktttg reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-push-ktttg reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-push-ktttg reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-push-ktttg reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-push-ktttg reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-push-ktttg reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-push-ktttg reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-push-ktttg reason: Running&#xA;PipelineRun gh-multi-component-parent-eexq-on-push-ktttg reason: Succeeded&#xA;&lt; Exit [It] PAC PipelineRun for parent component  is successful - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:401 @ 05/09/26 03:13:26.37 (5m0.291s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:13:26.37&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:13:26.37 (0s)&#xA;</system-err>
          </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="passed" time="121.56370012">
              <system-err>&gt; Enter [It] should lead to a nudge PR creation for child component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:412 @ 05/09/26 03:13:26.37&#xA;&lt; Exit [It] should lead to a nudge PR creation for child component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:412 @ 05/09/26 03:15:27.934 (2m1.563s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:15:27.934&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:15:27.934 (0s)&#xA;</system-err>
          </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="passed" time="1.6351341879999999">
              <system-err>&gt; Enter [It] merging the PR should be successful for child component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:429 @ 05/09/26 03:15:27.935&#xA;merged result sha: 285ab5dba00bad37c1bc475b8991b8a678274a14 for PR #3&#xA;&lt; Exit [It] merging the PR should be successful for child component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:429 @ 05/09/26 03:15:29.569 (1.635s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:15:29.569&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:15:29.57 (0s)&#xA;</system-err>
          </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="passed" time="25.315651745">
              <system-err>&gt; Enter [It] Verify the nudge updated the contents - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:440 @ 05/09/26 03:15:29.57&#xA;Verifying Dockerfile.tmp updated to sha sha256:e035af6439c0af5580d8614cd01cb1d51f0457963879ab4b72d7e09d78ef0821content: FROM quay.io/redhat-appstudio-qe/build-e2e-ikpq/gh-multi-component-parent-eexq@sha256:e035af6439c0af5580d8614cd01cb1d51f0457963879ab4b72d7e09d78ef0821&#xA;RUN echo hello&#xA;&#xA;&lt; Exit [It] Verify the nudge updated the contents - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:440 @ 05/09/26 03:15:29.756 (186ms)&#xA;&gt; Enter [AfterAll] component update with renovate - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:214 @ 05/09/26 03:15:29.756&#xA;&lt; Exit [AfterAll] component update with renovate - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:214 @ 05/09/26 03:15:54.885 (25.129s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:15:54.886&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:15:54.886 (0s)&#xA;</system-err>
          </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="passed" time="94.105532622">
              <system-err>&gt; Enter [BeforeAll] component update with renovate - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:72 @ 05/09/26 02:56:33.315&#xA;ReleaseAdmissionPlan data: {&#34;Mapping&#34;:{&#34;Components&#34;:[{&#34;Name&#34;:&#34;gl-multi-component-parent-dmnp&#34;,&#34;Repository&#34;:&#34;quay.io/redhat-appstudio-qe/release-repository&#34;}]}}&#xA;&lt; Exit [BeforeAll] component update with renovate - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:72 @ 05/09/26 02:57:17.228 (43.914s)&#xA;&gt; Enter [It] creates component with nudges - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:235 @ 05/09/26 02:57:17.228&#xA;Image repository for component gl-multi-component-child-dmnp in namespace build-e2e-fpvm do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component gl-multi-component-child-dmnp in namespace build-e2e-fpvm do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component gl-multi-component-parent-dmnp in namespace build-e2e-fpvm do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component gl-multi-component-parent-dmnp in namespace build-e2e-fpvm do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [It] creates component with nudges - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:235 @ 05/09/26 02:58:07.42 (50.191s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 02:58:07.42&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 02:58:07.42 (0s)&#xA;</system-err>
          </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="passed" time="120.126858611">
              <system-err>&gt; Enter [It] triggers a PipelineRun for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:259 @ 05/09/26 02:58:07.421&#xA;PipelineRun has not been created yet for the component build-e2e-fpvm/gl-multi-component-parent-dmnp&#xA;PipelineRun has not been created yet for the component build-e2e-fpvm/gl-multi-component-parent-dmnp&#xA;PipelineRun has not been created yet for the component build-e2e-fpvm/gl-multi-component-parent-dmnp&#xA;PipelineRun has not been created yet for the component build-e2e-fpvm/gl-multi-component-parent-dmnp&#xA;PipelineRun has not been created yet for the component build-e2e-fpvm/gl-multi-component-parent-dmnp&#xA;PipelineRun has not been created yet for the component build-e2e-fpvm/gl-multi-component-parent-dmnp&#xA;&lt; Exit [It] triggers a PipelineRun for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:259 @ 05/09/26 03:00:07.547 (2m0.127s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:00:07.547&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:00:07.547 (0s)&#xA;</system-err>
          </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="passed" time="660.015405277">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:274 @ 05/09/26 03:00:07.548&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg found for Component build-e2e-fpvm/gl-multi-component-parent-dmnp&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-pull-request-lldqg reason: Succeeded&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:274 @ 05/09/26 03:11:07.563 (11m0.015s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:11:07.563&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:11:07.563 (0s)&#xA;</system-err>
          </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="passed" time="0.029294212">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for child component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:285 @ 05/09/26 03:11:07.564&#xA;PipelineRun gl-multi-component-child-dmnp-on-pull-request-smp5z found for Component build-e2e-fpvm/gl-multi-component-child-dmnp&#xA;PipelineRun gl-multi-component-child-dmnp-on-pull-request-smp5z reason: Succeeded&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for child component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:285 @ 05/09/26 03:11:07.593 (29ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:11:07.593&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:11:07.593 (0s)&#xA;</system-err>
          </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="passed" time="0.237476445">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for child component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:289 @ 05/09/26 03:11:07.593&#xA;&lt; Exit [It] should lead to a PaC PR creation for child component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:289 @ 05/09/26 03:11:07.83 (237ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:11:07.83&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:11:07.831 (0s)&#xA;</system-err>
          </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="passed" time="1.521303095">
              <system-err>&gt; Enter [It] Merging the PaC PR should be successful for child component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:307 @ 05/09/26 03:11:07.831&#xA;merged result sha: c96868272b0941269d4f299be068d3db5c98c284 for PR #1&#xA;&lt; Exit [It] Merging the PaC PR should be successful for child component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:307 @ 05/09/26 03:11:09.352 (1.521s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:11:09.352&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:11:09.352 (0s)&#xA;</system-err>
          </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="passed" time="65.006407003">
              <system-err>&gt; Enter [It] create dockerfile and yaml manifest that references build and distribution repositories - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:318 @ 05/09/26 03:11:09.353&#xA;&lt; Exit [It] create dockerfile and yaml manifest that references build and distribution repositories - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:318 @ 05/09/26 03:12:14.359 (1m5.006s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:12:14.359&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:12:14.359 (0s)&#xA;</system-err>
          </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="passed" time="0.217922608">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:358 @ 05/09/26 03:12:14.36&#xA;&lt; Exit [It] should lead to a PaC PR creation for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:358 @ 05/09/26 03:12:14.577 (217ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:12:14.577&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:12:14.577 (0s)&#xA;</system-err>
          </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="passed" time="1.136678282">
              <system-err>&gt; Enter [It] Merging the PaC PR should be successful for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:375 @ 05/09/26 03:12:14.578&#xA;merged result sha: ede26083e0350ab8793c05cda11619001bde48e2 for PR #1&#xA;&lt; Exit [It] Merging the PaC PR should be successful for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:375 @ 05/09/26 03:12:15.714 (1.136s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:12:15.715&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:12:15.715 (0s)&#xA;</system-err>
          </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="passed" time="20.020661821">
              <system-err>&gt; Enter [It] PR merge triggers PAC PipelineRun for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:385 @ 05/09/26 03:12:15.715&#xA;Push PipelineRun has not been created yet for the component build-e2e-fpvm/gl-multi-component-parent-dmnp&#xA;&lt; Exit [It] PR merge triggers PAC PipelineRun for parent component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:385 @ 05/09/26 03:12:35.735 (20.02s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:12:35.736&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:12:35.736 (0s)&#xA;</system-err>
          </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="passed" time="280.015665117">
              <system-err>&gt; Enter [It] PAC PipelineRun for parent component  is successful - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:401 @ 05/09/26 03:12:35.736&#xA;PipelineRun gl-multi-component-parent-dmnp-on-push-9g5k2 found for Component build-e2e-fpvm/gl-multi-component-parent-dmnp&#xA;PipelineRun gl-multi-component-parent-dmnp-on-push-9g5k2 reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-push-9g5k2 reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-push-9g5k2 reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-push-9g5k2 reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-push-9g5k2 reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-push-9g5k2 reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-push-9g5k2 reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-push-9g5k2 reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-push-9g5k2 reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-push-9g5k2 reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-push-9g5k2 reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-push-9g5k2 reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-push-9g5k2 reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-push-9g5k2 reason: Running&#xA;PipelineRun gl-multi-component-parent-dmnp-on-push-9g5k2 reason: Succeeded&#xA;&lt; Exit [It] PAC PipelineRun for parent component  is successful - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:401 @ 05/09/26 03:17:15.752 (4m40.015s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:17:15.752&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:17:15.752 (0s)&#xA;</system-err>
          </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="passed" time="10.312387815">
              <system-err>&gt; Enter [It] should lead to a nudge PR creation for child component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:412 @ 05/09/26 03:17:15.752&#xA;&lt; Exit [It] should lead to a nudge PR creation for child component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:412 @ 05/09/26 03:17:26.064 (10.312s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:17:26.065&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:17:26.065 (0s)&#xA;</system-err>
          </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="passed" time="1.304798161">
              <system-err>&gt; Enter [It] merging the PR should be successful for child component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:429 @ 05/09/26 03:17:26.065&#xA;merged result sha: 4403f4dc87857a1bb3e49c88804b1cba0b9fec4a for PR #3&#xA;&lt; Exit [It] merging the PR should be successful for child component  - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:429 @ 05/09/26 03:17:27.37 (1.304s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:17:27.37&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:17:27.37 (0s)&#xA;</system-err>
          </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="passed" time="22.476139273">
              <system-err>&gt; Enter [It] Verify the nudge updated the contents - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:440 @ 05/09/26 03:17:27.371&#xA;Verifying Dockerfile.tmp updated to sha sha256:ffe86f03557569b964d9c407d4b192e8cedf2271964f01ac8039abadfbdb332dcontent: FROM quay.io/redhat-appstudio-qe/build-e2e-fpvm/gl-multi-component-parent-dmnp@sha256:ffe86f03557569b964d9c407d4b192e8cedf2271964f01ac8039abadfbdb332d&#xA;RUN echo hello&#xA;&#xA;&lt; Exit [It] Verify the nudge updated the contents - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:440 @ 05/09/26 03:17:27.697 (326ms)&#xA;&gt; Enter [AfterAll] component update with renovate - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:214 @ 05/09/26 03:17:27.697&#xA;&lt; Exit [AfterAll] component update with renovate - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:214 @ 05/09/26 03:17:49.846 (22.149s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:17:49.846&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/renovate.go:28 @ 05/09/26 03:17:49.847 (0s)&#xA;</system-err>
          </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 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="passed" time="112.589273783">
              <system-err>&gt; Enter [BeforeAll] PaC component build - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:54 @ 05/09/26 02:56:33.42&#xA;&lt; Exit [BeforeAll] PaC component build - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:54 @ 05/09/26 02:56:53.098 (19.677s)&#xA;&gt; Enter [BeforeAll] when a new component without specified branch is created and with visibility private - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:117 @ 05/09/26 02:56:53.098&#xA;Image repository for component gh-test-custom-default-opspis in namespace build-e2e-abfa do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component gh-test-custom-default-opspis in namespace build-e2e-abfa do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component gh-test-custom-default-opspis in namespace build-e2e-abfa 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 without specified branch is created and with visibility private - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:117 @ 05/09/26 02:57:24.425 (31.327s)&#xA;&gt; Enter [It] correctly targets the default branch (that is not named &#39;main&#39;) with PaC - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:136 @ 05/09/26 02:57:24.425&#xA;&lt; Exit [It] correctly targets the default branch (that is not named &#39;main&#39;) with PaC - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:136 @ 05/09/26 02:58:26.009 (1m1.584s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:26.009&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:26.009 (0s)&#xA;</system-err>
          </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="passed" time="0.011281763">
              <system-err>&gt; Enter [It] workspace parameter is set correctly in PaC repository CR - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:153 @ 05/09/26 02:58:26.01&#xA;&lt; Exit [It] workspace parameter is set correctly in PaC repository CR - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:153 @ 05/09/26 02:58:26.021 (11ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:26.021&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:26.021 (0s)&#xA;</system-err>
          </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="passed" time="20.03036361">
              <system-err>&gt; Enter [It] triggers a PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:176 @ 05/09/26 02:58:26.022&#xA;PipelineRun has not been created yet for the component build-e2e-abfa/gh-test-custom-branch-cqjobe&#xA;&lt; Exit [It] triggers a PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:176 @ 05/09/26 02:58:46.052 (20.03s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:46.052&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:46.052 (0s)&#xA;</system-err>
          </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="passed" time="0.000320388">
              <system-err>&gt; Enter [It] build pipeline uses the correct serviceAccount - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:191 @ 05/09/26 02:58:46.052&#xA;&lt; Exit [It] build pipeline uses the correct serviceAccount - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:191 @ 05/09/26 02:58:46.052 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:46.053&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:46.053 (0s)&#xA;</system-err>
          </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="passed" time="0.023785836">
              <system-err>&gt; Enter [It] component build status is set correctly - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:195 @ 05/09/26 02:58:46.053&#xA;build status annotation value: {&#34;pac&#34;:{&#34;state&#34;:&#34;enabled&#34;,&#34;merge-url&#34;:&#34;https://github.com/redhat-appstudio-qe/devfile-sample-hello-world-sdlgxd/pull/1&#34;,&#34;configuration-time&#34;:&#34;Sat, 09 May 2026 02:58:25 UTC&#34;},&#34;message&#34;:&#34;done&#34;}&#xA;state: enabled&#xA;mergeUrl: https://github.com/redhat-appstudio-qe/devfile-sample-hello-world-sdlgxd/pull/1&#xA;errId: 0&#xA;errMessage: &#xA;configurationTime: Sat, 09 May 2026 02:58:25 UTC&#xA;&lt; Exit [It] component build status is set correctly - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:195 @ 05/09/26 02:58:46.076 (24ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:46.077&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:46.077 (0s)&#xA;</system-err>
          </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="passed" time="1.017159639">
              <system-err>&gt; Enter [It] image repo and robot account created successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:225 @ 05/09/26 02:58:46.077&#xA;&lt; Exit [It] image repo and robot account created successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:225 @ 05/09/26 02:58:47.094 (1.017s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:47.094&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:47.094 (0s)&#xA;</system-err>
          </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="passed" time="0.277995775">
              <system-err>&gt; Enter [It] created image repo is private - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:243 @ 05/09/26 02:58:47.095&#xA;&lt; Exit [It] created image repo is private - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:243 @ 05/09/26 02:58:47.372 (278ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:47.372&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:47.373 (0s)&#xA;</system-err>
          </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="passed" time="21.095957926">
              <system-err>&gt; Enter [It] a related PipelineRun should be deleted after deleting the component - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:249 @ 05/09/26 02:58:47.373&#xA;&lt; Exit [It] a related PipelineRun should be deleted after deleting the component - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:249 @ 05/09/26 02:59:08.469 (21.095s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:08.469&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:08.469 (0s)&#xA;</system-err>
          </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="passed" time="0.155659081">
              <system-err>&gt; Enter [It] PR branch should not exist in the repo - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:265 @ 05/09/26 02:59:08.47&#xA;&lt; Exit [It] PR branch should not exist in the repo - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:265 @ 05/09/26 02:59:08.625 (155ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:08.625&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:08.625 (0s)&#xA;</system-err>
          </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="passed" time="0.88414493">
              <system-err>&gt; Enter [It] related image repo and the robot account should be deleted after deleting the component - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:278 @ 05/09/26 02:59:08.626&#xA;&lt; Exit [It] related image repo and the robot account should be deleted after deleting the component - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:278 @ 05/09/26 02:59:09.51 (884ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:09.51&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:09.51 (0s)&#xA;</system-err>
          </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="passed" time="70.088517321">
              <system-err>&gt; Enter [BeforeAll] when a new Component with specified custom branch is created - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:306 @ 05/09/26 02:59:09.51&#xA;&lt; Exit [BeforeAll] when a new Component with specified custom branch is created - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:306 @ 05/09/26 02:59:19.545 (10.035s)&#xA;&gt; Enter [It] triggers a PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:332 @ 05/09/26 02:59:19.546&#xA;PipelineRun has not been created yet for the component build-e2e-abfa/gh-test-custom-branch-cqjobe&#xA;PipelineRun has not been created yet for the component build-e2e-abfa/gh-test-custom-branch-cqjobe&#xA;PipelineRun has not been created yet for the component build-e2e-abfa/gh-test-custom-branch-cqjobe&#xA;&lt; Exit [It] triggers a PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:332 @ 05/09/26 03:00:19.599 (1m0.053s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:00:19.599&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:00:19.599 (0s)&#xA;</system-err>
          </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="passed" time="0.222573042">
              <system-err>&gt; Enter [It] should lead to a PaC init PR creation - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:347 @ 05/09/26 03:00:19.6&#xA;&lt; Exit [It] should lead to a PaC init PR creation - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:347 @ 05/09/26 03:00:19.822 (222ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:00:19.822&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:00:19.822 (0s)&#xA;</system-err>
          </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="passed" time="640.019404459">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:365 @ 05/09/26 03:00:19.823&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb found for Component build-e2e-abfa/gh-test-custom-branch-cqjobe&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-stsfb reason: Succeeded&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:365 @ 05/09/26 03:10:59.842 (10m40.019s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:10:59.842&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:10:59.842 (0s)&#xA;</system-err>
          </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="passed" time="0.912485946">
              <system-err>&gt; Enter [It] image repo and robot account created successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:371 @ 05/09/26 03:10:59.843&#xA;&lt; Exit [It] image repo and robot account created successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:371 @ 05/09/26 03:11:00.755 (912ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:11:00.755&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:11:00.755 (0s)&#xA;</system-err>
          </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="passed" time="0.282849654">
              <system-err>&gt; Enter [It] created image repo is public - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:390 @ 05/09/26 03:11:00.756&#xA;&lt; Exit [It] created image repo is public - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:390 @ 05/09/26 03:11:01.038 (282ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:11:01.038&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:11:01.038 (0s)&#xA;</system-err>
          </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="passed" time="0.693198315">
              <system-err>&gt; Enter [It] image tag is updated successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:396 @ 05/09/26 03:11:01.039&#xA;Image tag quay.io/redhat-appstudio-qe/build-e2e-abfa/gh-test-custom-branch-cqjobe:on-pr-95555d41f5769e5bc7f928ce401b477fdbdab26e successfully found in Quay&#xA;&lt; Exit [It] image tag is updated successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:396 @ 05/09/26 03:11:01.732 (693ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:11:01.732&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:11:01.732 (0s)&#xA;</system-err>
          </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="passed" time="0.261695385">
              <system-err>&gt; Enter [It] should ensure pruning labels are set - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:425 @ 05/09/26 03:11:01.733&#xA;&lt; Exit [It] should ensure pruning labels are set - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:425 @ 05/09/26 03:11:01.994 (261ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:11:01.994&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:11:01.994 (0s)&#xA;</system-err>
          </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="passed" time="0.458720267">
              <system-err>&gt; Enter [It] eventually leads to the PipelineRun status report at Checks tab - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:439 @ 05/09/26 03:11:01.995&#xA;&lt; Exit [It] eventually leads to the PipelineRun status report at Checks tab - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:439 @ 05/09/26 03:11:02.392 (397ms)&#xA;&gt; Enter [AfterAll] when a new Component with specified custom branch is created - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:324 @ 05/09/26 03:11:02.392&#xA;&lt; Exit [AfterAll] when a new Component with specified custom branch is created - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:324 @ 05/09/26 03:11:02.453 (61ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:11:02.453&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:11:02.453 (0s)&#xA;</system-err>
          </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="passed" time="20.721705277">
              <system-err>&gt; Enter [BeforeAll] when the PaC init branch is updated - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:454 @ 05/09/26 03:11:02.454&#xA;created file sha: 6545b178bef2bb6524c41e3c7ec33c2d8008fc6a&#xA;&lt; Exit [BeforeAll] when the PaC init branch is updated - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:454 @ 05/09/26 03:11:03.15 (696ms)&#xA;&gt; Enter [It] eventually leads to triggering another PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:464 @ 05/09/26 03:11:03.15&#xA;PipelineRun has not been created yet for the component build-e2e-abfa/gh-test-custom-branch-cqjobe&#xA;&lt; Exit [It] eventually leads to triggering another PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:464 @ 05/09/26 03:11:23.175 (20.025s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:11:23.176&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:11:23.176 (0s)&#xA;</system-err>
          </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="passed" time="0.178843658">
              <system-err>&gt; Enter [It] should lead to a PaC init PR update - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:479 @ 05/09/26 03:11:23.176&#xA;&lt; Exit [It] should lead to a PaC init PR update - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:479 @ 05/09/26 03:11:23.355 (178ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:11:23.355&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:11:23.355 (0s)&#xA;</system-err>
          </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="passed" time="420.017751536">
              <system-err>&gt; Enter [It] PipelineRun should eventually finish - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:498 @ 05/09/26 03:11:23.355&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr found for Component build-e2e-abfa/gh-test-custom-branch-cqjobe&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-pull-request-xgjfr reason: Succeeded&#xA;&lt; Exit [It] PipelineRun should eventually finish - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:498 @ 05/09/26 03:18:23.373 (7m0.017s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:18:23.373&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:18:23.373 (0s)&#xA;</system-err>
          </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="passed" time="0.38207532">
              <system-err>&gt; Enter [It] eventually leads to another update of a PR about the PipelineRun status report at Checks tab - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:504 @ 05/09/26 03:18:23.374&#xA;&lt; Exit [It] eventually leads to another update of a PR about the PipelineRun status report at Checks tab - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:504 @ 05/09/26 03:18:23.755 (382ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:18:23.756&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:18:23.756 (0s)&#xA;</system-err>
          </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="passed" time="21.58676094">
              <system-err>&gt; Enter [BeforeAll] when the PaC init branch is merged - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:520 @ 05/09/26 03:18:23.756&#xA;merged result sha: d2f8eb79909f6969d2986708eaa5303cf56d44b7&#xA;&lt; Exit [BeforeAll] when the PaC init branch is merged - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:520 @ 05/09/26 03:18:25.318 (1.562s)&#xA;&gt; Enter [It] eventually leads to triggering another PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:530 @ 05/09/26 03:18:25.319&#xA;PipelineRun has not been created yet for the component build-e2e-abfa/gh-test-custom-branch-cqjobe&#xA;&lt; Exit [It] eventually leads to triggering another PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:530 @ 05/09/26 03:18:45.343 (20.024s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:18:45.343&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:18:45.343 (0s)&#xA;</system-err>
          </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="passed" time="260.015046829">
              <system-err>&gt; Enter [It] pipelineRun should eventually finish - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:546 @ 05/09/26 03:18:45.344&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-push-bzxs4 found for Component build-e2e-abfa/gh-test-custom-branch-cqjobe&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-push-bzxs4 reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-push-bzxs4 reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-push-bzxs4 reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-push-bzxs4 reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-push-bzxs4 reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-push-bzxs4 reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-push-bzxs4 reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-push-bzxs4 reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-push-bzxs4 reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-push-bzxs4 reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-push-bzxs4 reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-push-bzxs4 reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-push-bzxs4 reason: Running&#xA;PipelineRun gh-test-custom-branch-cqjobe-on-push-bzxs4 reason: Succeeded&#xA;&lt; Exit [It] pipelineRun should eventually finish - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:546 @ 05/09/26 03:23:05.358 (4m20.015s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:23:05.358&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:23:05.358 (0s)&#xA;</system-err>
          </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="passed" time="0.367259086">
              <system-err>&gt; Enter [It] does not have expiration set - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:552 @ 05/09/26 03:23:05.359&#xA;&lt; Exit [It] does not have expiration set - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:552 @ 05/09/26 03:23:05.726 (367ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:23:05.726&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:23:05.726 (0s)&#xA;</system-err>
          </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="passed" time="120.394691315">
              <system-err>&gt; Enter [It] After updating image visibility to private, it should not trigger another PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:564 @ 05/09/26 03:23:05.727&#xA;waiting for one minute and expecting to not trigger a PipelineRun&#xA;&lt; Exit [It] After updating image visibility to private, it should not trigger another PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:564 @ 05/09/26 03:25:06.121 (2m0.394s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:25:06.121&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:25:06.122 (0s)&#xA;</system-err>
          </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="passed" time="0.276573588">
              <system-err>&gt; Enter [It] image repo is updated to private - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:595 @ 05/09/26 03:25:06.122&#xA;&lt; Exit [It] image repo is updated to private - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:595 @ 05/09/26 03:25:06.398 (276ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:25:06.399&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:25:06.399 (0s)&#xA;</system-err>
          </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 related image repo and robot accounts deleted [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="7.214791294">
              <system-err>&gt; Enter [BeforeAll] when the component is removed - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:649 @ 05/09/26 03:25:06.4&#xA;&lt; Exit [BeforeAll] when the component is removed - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:649 @ 05/09/26 03:25:07.426 (1.026s)&#xA;&gt; Enter [It] related image repo and robot accounts deleted - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:661 @ 05/09/26 03:25:07.426&#xA;&lt; Exit [It] related image repo and robot accounts deleted - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:661 @ 05/09/26 03:25:13.614 (6.188s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:25:13.614&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:25:13.614 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the component is removed purge PR is created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="1.749210624">
              <system-err>&gt; Enter [It] purge PR is created successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:679 @ 05/09/26 03:25:13.615&#xA;Found purge PR with id: 3&#xA;&lt; Exit [It] purge PR is created successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:679 @ 05/09/26 03:25:13.826 (211ms)&#xA;&gt; Enter [AfterAll] PaC component build - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:101 @ 05/09/26 03:25:13.826&#xA;&lt; Exit [AfterAll] PaC component build - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:101 @ 05/09/26 03:25:15.364 (1.537s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:25:15.364&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:25:15.364 (0s)&#xA;</system-err>
          </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="passed" time="129.427575096">
              <system-err>&gt; Enter [BeforeAll] PaC component build - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:54 @ 05/09/26 02:56:33.422&#xA;&lt; Exit [BeforeAll] PaC component build - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:54 @ 05/09/26 02:57:16.193 (42.77s)&#xA;&gt; Enter [BeforeAll] when a new component without specified branch is created and with visibility private - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:117 @ 05/09/26 02:57:16.193&#xA;Image repository for component gl-test-custom-default-cxecoc in namespace build-e2e-llyw 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 without specified branch is created and with visibility private - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:117 @ 05/09/26 02:57:36.243 (20.05s)&#xA;&gt; Enter [It] correctly targets the default branch (that is not named &#39;main&#39;) with PaC - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:136 @ 05/09/26 02:57:36.243&#xA;&lt; Exit [It] correctly targets the default branch (that is not named &#39;main&#39;) with PaC - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:136 @ 05/09/26 02:58:42.849 (1m6.606s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:42.85&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:42.85 (0s)&#xA;</system-err>
          </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="passed" time="0.030574477">
              <system-err>&gt; Enter [It] workspace parameter is set correctly in PaC repository CR - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:153 @ 05/09/26 02:58:42.85&#xA;&lt; Exit [It] workspace parameter is set correctly in PaC repository CR - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:153 @ 05/09/26 02:58:42.881 (30ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:42.881&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:42.881 (0s)&#xA;</system-err>
          </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="passed" time="20.05327516">
              <system-err>&gt; Enter [It] triggers a PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:176 @ 05/09/26 02:58:42.881&#xA;&lt; Exit [It] triggers a PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:176 @ 05/09/26 02:59:02.934 (20.053s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:02.934&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:02.934 (0s)&#xA;</system-err>
          </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="passed" time="0.000312878">
              <system-err>&gt; Enter [It] build pipeline uses the correct serviceAccount - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:191 @ 05/09/26 02:59:02.935&#xA;&lt; Exit [It] build pipeline uses the correct serviceAccount - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:191 @ 05/09/26 02:59:02.935 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:02.935&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:02.935 (0s)&#xA;</system-err>
          </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="passed" time="0.01603359">
              <system-err>&gt; Enter [It] component build status is set correctly - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:195 @ 05/09/26 02:59:02.936&#xA;build status annotation value: {&#34;pac&#34;:{&#34;state&#34;:&#34;enabled&#34;,&#34;merge-url&#34;:&#34;https://gitlab.com/konflux-qe/devfile-sample-hello-world-kughbe/-/merge_requests/1&#34;,&#34;configuration-time&#34;:&#34;Sat, 09 May 2026 02:58:38 UTC&#34;},&#34;message&#34;:&#34;done&#34;}&#xA;state: enabled&#xA;mergeUrl: https://gitlab.com/konflux-qe/devfile-sample-hello-world-kughbe/-/merge_requests/1&#xA;errId: 0&#xA;errMessage: &#xA;configurationTime: Sat, 09 May 2026 02:58:38 UTC&#xA;&lt; Exit [It] component build status is set correctly - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:195 @ 05/09/26 02:59:02.951 (16ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:02.952&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:02.952 (0s)&#xA;</system-err>
          </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="passed" time="0.897201781">
              <system-err>&gt; Enter [It] image repo and robot account created successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:225 @ 05/09/26 02:59:02.952&#xA;&lt; Exit [It] image repo and robot account created successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:225 @ 05/09/26 02:59:03.849 (897ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:03.849&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:03.849 (0s)&#xA;</system-err>
          </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="passed" time="0.276512978">
              <system-err>&gt; Enter [It] created image repo is private - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:243 @ 05/09/26 02:59:03.85&#xA;&lt; Exit [It] created image repo is private - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:243 @ 05/09/26 02:59:04.126 (276ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:04.126&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:04.126 (0s)&#xA;</system-err>
          </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="passed" time="8.050154031">
              <system-err>&gt; Enter [It] a related PipelineRun should be deleted after deleting the component - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:249 @ 05/09/26 02:59:04.127&#xA;&lt; Exit [It] a related PipelineRun should be deleted after deleting the component - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:249 @ 05/09/26 02:59:12.176 (8.05s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:12.177&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:12.177 (0s)&#xA;</system-err>
          </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="passed" time="1.326818783">
              <system-err>&gt; Enter [It] PR branch should not exist in the repo - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:265 @ 05/09/26 02:59:12.177&#xA;&lt; Exit [It] PR branch should not exist in the repo - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:265 @ 05/09/26 02:59:13.504 (1.326s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:13.504&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:13.504 (0s)&#xA;</system-err>
          </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="passed" time="2.133291737">
              <system-err>&gt; Enter [It] related image repo and the robot account should be deleted after deleting the component - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:278 @ 05/09/26 02:59:13.504&#xA;&lt; Exit [It] related image repo and the robot account should be deleted after deleting the component - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:278 @ 05/09/26 02:59:15.637 (2.133s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:15.638&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:59:15.638 (0s)&#xA;</system-err>
          </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="passed" time="70.083969352">
              <system-err>&gt; Enter [BeforeAll] when a new Component with specified custom branch is created - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:306 @ 05/09/26 02:59:15.638&#xA;&lt; Exit [BeforeAll] when a new Component with specified custom branch is created - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:306 @ 05/09/26 02:59:25.677 (10.039s)&#xA;&gt; Enter [It] triggers a PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:332 @ 05/09/26 02:59:25.677&#xA;PipelineRun has not been created yet for the component build-e2e-llyw/gl-test-custom-branch-wyomnt&#xA;PipelineRun has not been created yet for the component build-e2e-llyw/gl-test-custom-branch-wyomnt&#xA;PipelineRun has not been created yet for the component build-e2e-llyw/gl-test-custom-branch-wyomnt&#xA;&lt; Exit [It] triggers a PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:332 @ 05/09/26 03:00:25.722 (1m0.045s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:00:25.722&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:00:25.722 (0s)&#xA;</system-err>
          </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="passed" time="0.199789909">
              <system-err>&gt; Enter [It] should lead to a PaC init PR creation - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:347 @ 05/09/26 03:00:25.723&#xA;&lt; Exit [It] should lead to a PaC init PR creation - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:347 @ 05/09/26 03:00:25.922 (199ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:00:25.922&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:00:25.922 (0s)&#xA;</system-err>
          </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="passed" time="811.145806136">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:365 @ 05/09/26 03:00:25.923&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk found for Component build-e2e-llyw/gl-test-custom-branch-wyomnt&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-ntvqk reason: Failed&#xA;attempt 1/3: PipelineRun &#34;gl-test-custom-branch-wyomnt-on-pull-request-ntvqk&#34; failed: &#xA; pod: gl-test-custom-branch-wyomnt-on-pull-request-ntvqk-init-pod | init container: prepare&#xA;2026/05/09 03:00:31 Entrypoint initialization&#xA;&#xA;pod: gl-test-custom-branch-wyomnt-on-pull-request-ntvqk-init-pod | container step-init: &#xA;time=&#34;2026-05-09T03:00:34Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-05-09T03:00:34Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-05-09T03:00:34Z&#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-05-09T03:00:34Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-05-09T03:00:34Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-05-09T03:00:34Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-05-09T03:00:35Z&#34; level=info msg=&#34;Cache proxy is disabled via param&#34;&#xA;time=&#34;2026-05-09T03:00:35Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-05-09T03:00:35Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;New PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk found after retrigger for component build-e2e-llyw/gl-test-custom-branch-wyomnt&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk found for Component build-e2e-llyw/gl-test-custom-branch-wyomnt&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk reason: ResolvingTaskRef&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-vlltk reason: Succeeded&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:365 @ 05/09/26 03:13:57.068 (13m31.145s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:13:57.068&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:13:57.068 (0s)&#xA;</system-err>
          </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="passed" time="0.862445639">
              <system-err>&gt; Enter [It] image repo and robot account created successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:371 @ 05/09/26 03:13:57.069&#xA;&lt; Exit [It] image repo and robot account created successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:371 @ 05/09/26 03:13:57.931 (862ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:13:57.931&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:13:57.931 (0s)&#xA;</system-err>
          </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="passed" time="0.276076872">
              <system-err>&gt; Enter [It] created image repo is public - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:390 @ 05/09/26 03:13:57.932&#xA;&lt; Exit [It] created image repo is public - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:390 @ 05/09/26 03:13:58.207 (276ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:13:58.208&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:13:58.208 (0s)&#xA;</system-err>
          </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="passed" time="0.349048213">
              <system-err>&gt; Enter [It] image tag is updated successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:396 @ 05/09/26 03:13:58.208&#xA;Image tag quay.io/redhat-appstudio-qe/build-e2e-llyw/gl-test-custom-branch-wyomnt:on-pr-03a4e1d1f460670b63b5a4d3282c6ce0af8b6f83 successfully found in Quay&#xA;&lt; Exit [It] image tag is updated successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:396 @ 05/09/26 03:13:58.557 (349ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:13:58.557&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:13:58.557 (0s)&#xA;</system-err>
          </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="passed" time="0.376586668">
              <system-err>&gt; Enter [It] should ensure pruning labels are set - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:425 @ 05/09/26 03:13:58.558&#xA;&lt; Exit [It] should ensure pruning labels are set - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:425 @ 05/09/26 03:13:58.934 (376ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:13:58.934&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:13:58.934 (0s)&#xA;</system-err>
          </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="passed" time="0.460841452">
              <system-err>&gt; Enter [It] eventually leads to the PipelineRun status report at Checks tab - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:439 @ 05/09/26 03:13:58.935&#xA;&lt; Exit [It] eventually leads to the PipelineRun status report at Checks tab - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:439 @ 05/09/26 03:13:59.26 (325ms)&#xA;&gt; Enter [AfterAll] when a new Component with specified custom branch is created - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:324 @ 05/09/26 03:13:59.26&#xA;&lt; Exit [AfterAll] when a new Component with specified custom branch is created - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:324 @ 05/09/26 03:13:59.395 (135ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:13:59.395&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:13:59.396 (0s)&#xA;</system-err>
          </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="passed" time="20.800823129">
              <system-err>&gt; Enter [BeforeAll] when the PaC init branch is updated - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:454 @ 05/09/26 03:13:59.396&#xA;created file sha: 271c2d3ef1c0d44d774cf45da21e8145ed8ae4cc&#xA;&lt; Exit [BeforeAll] when the PaC init branch is updated - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:454 @ 05/09/26 03:14:00.175 (779ms)&#xA;&gt; Enter [It] eventually leads to triggering another PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:464 @ 05/09/26 03:14:00.176&#xA;PipelineRun has not been created yet for the component build-e2e-llyw/gl-test-custom-branch-wyomnt&#xA;&lt; Exit [It] eventually leads to triggering another PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:464 @ 05/09/26 03:14:20.197 (20.021s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:14:20.197&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:14:20.197 (0s)&#xA;</system-err>
          </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="passed" time="0.252923385">
              <system-err>&gt; Enter [It] should lead to a PaC init PR update - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:479 @ 05/09/26 03:14:20.197&#xA;&lt; Exit [It] should lead to a PaC init PR update - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:479 @ 05/09/26 03:14:20.45 (253ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:14:20.45&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:14:20.45 (0s)&#xA;</system-err>
          </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="passed" time="320.017194086">
              <system-err>&gt; Enter [It] PipelineRun should eventually finish - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:498 @ 05/09/26 03:14:20.451&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-nwhwp found for Component build-e2e-llyw/gl-test-custom-branch-wyomnt&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-nwhwp reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-nwhwp reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-nwhwp reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-nwhwp reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-nwhwp reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-nwhwp reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-nwhwp reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-nwhwp reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-nwhwp reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-nwhwp reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-nwhwp reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-nwhwp reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-nwhwp reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-nwhwp reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-nwhwp reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-nwhwp reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-pull-request-nwhwp reason: Succeeded&#xA;&lt; Exit [It] PipelineRun should eventually finish - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:498 @ 05/09/26 03:19:40.468 (5m20.017s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:19:40.468&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:19:40.468 (0s)&#xA;</system-err>
          </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="passed" time="0.329624928">
              <system-err>&gt; Enter [It] eventually leads to another update of a PR about the PipelineRun status report at Checks tab - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:504 @ 05/09/26 03:19:40.468&#xA;&lt; Exit [It] eventually leads to another update of a PR about the PipelineRun status report at Checks tab - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:504 @ 05/09/26 03:19:40.798 (329ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:19:40.798&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:19:40.798 (0s)&#xA;</system-err>
          </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="passed" time="41.254490831">
              <system-err>&gt; Enter [BeforeAll] when the PaC init branch is merged - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:520 @ 05/09/26 03:19:40.798&#xA;merged result sha: f040df5cb04c0f14471469169bd254a7952490ec&#xA;&lt; Exit [BeforeAll] when the PaC init branch is merged - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:520 @ 05/09/26 03:19:42.026 (1.228s)&#xA;&gt; Enter [It] eventually leads to triggering another PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:530 @ 05/09/26 03:19:42.027&#xA;PipelineRun has not been created yet for the component build-e2e-llyw/gl-test-custom-branch-wyomnt&#xA;PipelineRun has not been created yet for the component build-e2e-llyw/gl-test-custom-branch-wyomnt&#xA;&lt; Exit [It] eventually leads to triggering another PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:530 @ 05/09/26 03:20:22.053 (40.026s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:20:22.053&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:20:22.053 (0s)&#xA;</system-err>
          </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="passed" time="260.012920644">
              <system-err>&gt; Enter [It] pipelineRun should eventually finish - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:546 @ 05/09/26 03:20:22.053&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-push-zl56d found for Component build-e2e-llyw/gl-test-custom-branch-wyomnt&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-push-zl56d reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-push-zl56d reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-push-zl56d reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-push-zl56d reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-push-zl56d reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-push-zl56d reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-push-zl56d reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-push-zl56d reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-push-zl56d reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-push-zl56d reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-push-zl56d reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-push-zl56d reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-push-zl56d reason: Running&#xA;PipelineRun gl-test-custom-branch-wyomnt-on-push-zl56d reason: Succeeded&#xA;&lt; Exit [It] pipelineRun should eventually finish - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:546 @ 05/09/26 03:24:42.066 (4m20.013s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:24:42.066&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:24:42.066 (0s)&#xA;</system-err>
          </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="passed" time="0.302384205">
              <system-err>&gt; Enter [It] does not have expiration set - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:552 @ 05/09/26 03:24:42.067&#xA;&lt; Exit [It] does not have expiration set - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:552 @ 05/09/26 03:24:42.369 (302ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:24:42.369&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:24:42.369 (0s)&#xA;</system-err>
          </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="passed" time="120.581866773">
              <system-err>&gt; Enter [It] After updating image visibility to private, it should not trigger another PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:564 @ 05/09/26 03:24:42.369&#xA;waiting for one minute and expecting to not trigger a PipelineRun&#xA;&lt; Exit [It] After updating image visibility to private, it should not trigger another PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:564 @ 05/09/26 03:26:42.951 (2m0.581s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:26:42.951&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:26:42.951 (0s)&#xA;</system-err>
          </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="passed" time="0.28979783">
              <system-err>&gt; Enter [It] image repo is updated to private - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:595 @ 05/09/26 03:26:42.952&#xA;&lt; Exit [It] image repo is updated to private - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:595 @ 05/09/26 03:26:43.241 (289ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:26:43.241&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:26:43.241 (0s)&#xA;</system-err>
          </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 related image repo and robot accounts deleted [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="7.155097468">
              <system-err>&gt; Enter [BeforeAll] when the component is removed - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:649 @ 05/09/26 03:26:43.242&#xA;&lt; Exit [BeforeAll] when the component is removed - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:649 @ 05/09/26 03:26:44.267 (1.025s)&#xA;&gt; Enter [It] related image repo and robot accounts deleted - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:661 @ 05/09/26 03:26:44.267&#xA;&lt; Exit [It] related image repo and robot accounts deleted - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:661 @ 05/09/26 03:26:50.397 (6.129s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:26:50.397&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:26:50.397 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the component is removed purge PR is created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="2.308195294">
              <system-err>&gt; Enter [It] purge PR is created successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:679 @ 05/09/26 03:26:50.398&#xA;Found purge PR with id: 3&#xA;&lt; Exit [It] purge PR is created successfully - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:679 @ 05/09/26 03:26:50.624 (226ms)&#xA;&gt; Enter [AfterAll] PaC component build - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:101 @ 05/09/26 03:26:50.624&#xA;&lt; Exit [AfterAll] PaC component build - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:101 @ 05/09/26 03:26:52.706 (2.082s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:26:52.706&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:26:52.706 (0s)&#xA;</system-err>
          </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="passed" time="110.301830541">
              <system-err>&gt; Enter [BeforeAll] PaC component build - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:54 @ 05/09/26 02:56:33.417&#xA;&lt; Exit [BeforeAll] PaC component build - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:54 @ 05/09/26 02:56:50.651 (17.234s)&#xA;&gt; Enter [BeforeAll] when a new component without specified branch is created and with visibility private - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:117 @ 05/09/26 02:56:50.651&#xA;Image repository for component fj-test-custom-default-rkvqco in namespace build-e2e-afjm do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component fj-test-custom-default-rkvqco in namespace build-e2e-afjm 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 without specified branch is created and with visibility private - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:117 @ 05/09/26 02:57:21.047 (30.396s)&#xA;&gt; Enter [It] correctly targets the default branch (that is not named &#39;main&#39;) with PaC - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:136 @ 05/09/26 02:57:21.047&#xA;&lt; Exit [It] correctly targets the default branch (that is not named &#39;main&#39;) with PaC - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:136 @ 05/09/26 02:58:23.718 (1m2.671s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:23.719&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:23.719 (0s)&#xA;</system-err>
          </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="passed" time="0.035635084">
              <system-err>&gt; Enter [It] workspace parameter is set correctly in PaC repository CR - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:153 @ 05/09/26 02:58:23.719&#xA;&lt; Exit [It] workspace parameter is set correctly in PaC repository CR - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:153 @ 05/09/26 02:58:23.754 (35ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:23.755&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 02:58:23.755 (0s)&#xA;</system-err>
          </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="failed" time="1800.270434347">
              <failure message="Timed out after 1800.000s.&#xA;timed out when waiting for the PipelineRun to start for the component fj-test-custom-branch-ecubwp/build-e2e-afjm&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc001480380&gt;: &#xA;    no pipelinerun found for component fj-test-custom-default-rkvqco&#xA;    {&#xA;        s: &#34;no pipelinerun found for component fj-test-custom-default-rkvqco&#34;,&#xA;    }" type="failed">[FAILED] Timed out after 1800.000s.&#xA;timed out when waiting for the PipelineRun to start for the component fj-test-custom-branch-ecubwp/build-e2e-afjm&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc001480380&gt;: &#xA;    no pipelinerun found for component fj-test-custom-default-rkvqco&#xA;    {&#xA;        s: &#34;no pipelinerun found for component fj-test-custom-default-rkvqco&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:188 @ 05/09/26 03:28:23.756&#xA;</failure>
              <system-err>&gt; Enter [It] triggers a PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:176 @ 05/09/26 02:58:23.755&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;PipelineRun has not been created yet for the component build-e2e-afjm/fj-test-custom-branch-ecubwp&#xA;[FAILED] Timed out after 1800.000s.&#xA;timed out when waiting for the PipelineRun to start for the component fj-test-custom-branch-ecubwp/build-e2e-afjm&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc001480380&gt;: &#xA;    no pipelinerun found for component fj-test-custom-default-rkvqco&#xA;    {&#xA;        s: &#34;no pipelinerun found for component fj-test-custom-default-rkvqco&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:188 @ 05/09/26 03:28:23.756&#xA;&lt; Exit [It] triggers a PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:176 @ 05/09/26 03:28:23.756 (30m0.001s)&#xA;&gt; Enter [AfterAll] PaC component build - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:101 @ 05/09/26 03:28:23.756&#xA;&lt; Exit [AfterAll] PaC component build - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:101 @ 05/09/26 03:28:23.756 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:28:23.756&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:28 @ 05/09/26 03:28:24.026 (269ms)&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:191 @ 05/09/26 03:28:24.026&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:195 @ 05/09/26 03:28:24.027&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:225 @ 05/09/26 03:28:24.027&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:243 @ 05/09/26 03:28:24.027&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:249 @ 05/09/26 03:28:24.027&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:265 @ 05/09/26 03:28:24.028&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:278 @ 05/09/26 03:28:24.028&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:332 @ 05/09/26 03:28:24.028&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:347 @ 05/09/26 03:28:24.028&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:365 @ 05/09/26 03:28:24.028&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:371 @ 05/09/26 03:28:24.029&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:390 @ 05/09/26 03:28:24.029&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:396 @ 05/09/26 03:28:24.029&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:425 @ 05/09/26 03:28:24.029&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:439 @ 05/09/26 03:28:24.029&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:464 @ 05/09/26 03:28:24.03&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:479 @ 05/09/26 03:28:24.03&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:498 @ 05/09/26 03:28:24.03&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:504 @ 05/09/26 03:28:24.03&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:530 @ 05/09/26 03:28:24.03&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:546 @ 05/09/26 03:28:24.03&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:552 @ 05/09/26 03:28:24.031&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:564 @ 05/09/26 03:28:24.031&#xA;</system-err>
          </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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:595 @ 05/09/26 03:28:24.031&#xA;</system-err>
          </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 related image repo and robot accounts deleted [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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:661 @ 05/09/26 03:28:24.032&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the component is removed purge PR is 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 - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.CNj1aJY7Z5/tests/build/pac_build.go:679 @ 05/09/26 03:28:24.032&#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="57.292569594">
              <system-err>&gt; Enter [BeforeAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:60 @ 05/09/26 02:56:33.416&#xA;Successfully acquired repository lock for namespace group-aokw&#xA;&lt; Exit [BeforeAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:60 @ 05/09/26 02:57:00.571 (27.155s)&#xA;&gt; Enter [It] creates the Component A successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:205 @ 05/09/26 02:57:00.571&#xA;Image repository for component go-component-wzvrbm in namespace group-aokw 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-wzvrbm in namespace group-aokw 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.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:205 @ 05/09/26 02:57:30.708 (30.137s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 02:57:30.708&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 02:57:30.708 (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="80.097885437">
              <system-err>&gt; Enter [It] triggers a Build PipelineRun for componentA go-component - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:213 @ 05/09/26 02:57:30.709&#xA;Build PipelineRun has not been created yet for the componentA group-aokw/go-component-wzvrbm&#xA;Build PipelineRun has not been created yet for the componentA group-aokw/go-component-wzvrbm&#xA;Build PipelineRun has not been created yet for the componentA group-aokw/go-component-wzvrbm&#xA;Build PipelineRun has not been created yet for the componentA group-aokw/go-component-wzvrbm&#xA;&lt; Exit [It] triggers a Build PipelineRun for componentA go-component - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:213 @ 05/09/26 02:58:50.807 (1m20.098s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 02:58:50.807&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 02:58:50.807 (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.000249297">
              <system-err>&gt; Enter [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:227 @ 05/09/26 02:58:50.807&#xA;&lt; Exit [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:227 @ 05/09/26 02:58:50.807 (0s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 02:58:50.807&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 02:58:50.807 (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="565.804600061">
              <system-err>&gt; Enter [It] should lead to build PipelineRunA finishing successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:231 @ 05/09/26 02:58:50.808&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn found for Component group-aokw/go-component-wzvrbm&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Running&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Completed&#xA;&lt; Exit [It] should lead to build PipelineRunA finishing successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:231 @ 05/09/26 03:08:16.612 (9m25.804s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:08:16.612&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:08:16.612 (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="1.38788368">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for componentA go-component - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:236 @ 05/09/26 03:08:16.617&#xA;&lt; Exit [It] should lead to a PaC PR creation for componentA go-component - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:236 @ 05/09/26 03:08:18.004 (1.387s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:08:18.004&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:08:18.004 (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.295428549">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:258 @ 05/09/26 03:08:18.005&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:258 @ 05/09/26 03:08:18.3 (295ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:08:18.3&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:08:18.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 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.234560648">
              <system-err>&gt; Enter [It] should find the related Integration PipelineRuns - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:263 @ 05/09/26 03:08:18.301&#xA;&lt; Exit [It] should find the related Integration PipelineRuns - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:263 @ 05/09/26 03:08:18.535 (234ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:08:18.535&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:08:18.535 (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.011067274">
              <system-err>&gt; Enter [It] integration pipeline should end up with success - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:270 @ 05/09/26 03:08:18.536&#xA;PipelineRun integration-resolver-pipelinerun-fzlxj reason: Running&#xA;PipelineRun integration-resolver-pipelinerun-fzlxj reason: Succeeded&#xA;&lt; Exit [It] integration pipeline should end up with success - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:270 @ 05/09/26 03:08:38.547 (20.011s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:08:38.547&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:08:38.547 (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.804422516">
              <system-err>&gt; Enter [It] should merge the init PaC PR successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:277 @ 05/09/26 03:08:38.547&#xA;merged result sha: 77f1bdc3668fbd8e9adbadd6c10a9e8983200169 for PR #21844&#xA;&lt; Exit [It] should merge the init PaC PR successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:277 @ 05/09/26 03:08:40.351 (1.804s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:08:40.352&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:08:40.352 (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.169485192">
              <system-err>&gt; Enter [It] creates the Component B successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:296 @ 05/09/26 03:08:40.352&#xA;Image repository for component python-component-xssyak in namespace group-aokw 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.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:296 @ 05/09/26 03:08:50.521 (10.169s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:08:50.521&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:08:50.522 (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.027983976">
              <system-err>&gt; Enter [It] triggers a Build PipelineRun for component python-component - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:304 @ 05/09/26 03:08:50.523&#xA;Build PipelineRun has not been created yet for the componentB group-aokw/python-component-xssyak&#xA;&lt; Exit [It] triggers a Build PipelineRun for component python-component - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:304 @ 05/09/26 03:09:10.55 (20.027s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:09:10.55&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:09:10.55 (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.000280267">
              <system-err>&gt; Enter [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:318 @ 05/09/26 03:09:10.551&#xA;&lt; Exit [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:318 @ 05/09/26 03:09:10.551 (0s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:09:10.551&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:09:10.551 (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="340.021137643">
              <system-err>&gt; Enter [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:322 @ 05/09/26 03:09:10.552&#xA;PipelineRun python-component-xssyak-on-pull-request-m9pmf found for Component group-aokw/python-component-xssyak&#xA;PipelineRun python-component-xssyak-on-pull-request-m9pmf reason: Running&#xA;PipelineRun python-component-xssyak-on-pull-request-m9pmf reason: Running&#xA;PipelineRun python-component-xssyak-on-pull-request-m9pmf reason: Running&#xA;PipelineRun python-component-xssyak-on-pull-request-m9pmf reason: Running&#xA;PipelineRun python-component-xssyak-on-pull-request-m9pmf reason: Running&#xA;PipelineRun python-component-xssyak-on-pull-request-m9pmf reason: Running&#xA;PipelineRun python-component-xssyak-on-pull-request-m9pmf reason: Running&#xA;PipelineRun python-component-xssyak-on-pull-request-m9pmf reason: Running&#xA;PipelineRun python-component-xssyak-on-pull-request-m9pmf reason: Running&#xA;PipelineRun python-component-xssyak-on-pull-request-m9pmf reason: Running&#xA;PipelineRun python-component-xssyak-on-pull-request-m9pmf reason: Running&#xA;PipelineRun python-component-xssyak-on-pull-request-m9pmf reason: Running&#xA;PipelineRun python-component-xssyak-on-pull-request-m9pmf reason: Running&#xA;PipelineRun python-component-xssyak-on-pull-request-m9pmf reason: Running&#xA;PipelineRun python-component-xssyak-on-pull-request-m9pmf reason: Running&#xA;PipelineRun python-component-xssyak-on-pull-request-m9pmf reason: Running&#xA;PipelineRun python-component-xssyak-on-pull-request-m9pmf reason: Running&#xA;PipelineRun integration-resolver-pipelinerun-x72q2 reason: Succeeded&#xA;&lt; Exit [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:322 @ 05/09/26 03:14:50.572 (5m40.021s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:14:50.573&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:14:50.573 (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.359956883">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for component python-component - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:327 @ 05/09/26 03:14:50.573&#xA;&lt; Exit [It] should lead to a PaC PR creation for component python-component - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:327 @ 05/09/26 03:14:50.933 (360ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:14:50.933&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:14:50.933 (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.007435429">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:349 @ 05/09/26 03:14:50.933&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:349 @ 05/09/26 03:14:50.941 (7ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:14:50.941&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:14:50.941 (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.007387867">
              <system-err>&gt; Enter [It] should find the related Integration PipelineRuns - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:354 @ 05/09/26 03:14:50.941&#xA;&lt; Exit [It] should find the related Integration PipelineRuns - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:354 @ 05/09/26 03:14:50.948 (7ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:14:50.948&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:14:50.948 (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.006860163">
              <system-err>&gt; Enter [It] integration pipeline should end up with success - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:361 @ 05/09/26 03:14:50.949&#xA;PipelineRun integration-resolver-pipelinerun-x72q2 reason: Succeeded&#xA;&lt; Exit [It] integration pipeline should end up with success - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:361 @ 05/09/26 03:14:50.955 (7ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:14:50.955&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:14:50.955 (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.669320014">
              <system-err>&gt; Enter [It] should merge the init PaC PR successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:368 @ 05/09/26 03:14:50.956&#xA;merged result sha: 10b90491cf301adabfa3689eb00904b612e8dca3 for PR #21846&#xA;&lt; Exit [It] should merge the init PaC PR successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:368 @ 05/09/26 03:14:52.625 (1.669s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:14:52.625&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:14:52.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 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.025937803">
              <system-err>&gt; Enter [It] creates the Component C successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:387 @ 05/09/26 03:14:52.626&#xA;&lt; Exit [It] creates the Component C successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:387 @ 05/09/26 03:15:02.651 (10.026s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:15:02.651&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:15:02.651 (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.025578479">
              <system-err>&gt; Enter [It] triggers a Build PipelineRun for componentC konflux-test-integration-clone - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:395 @ 05/09/26 03:15:02.652&#xA;Build PipelineRun has not been created yet for the componentC group-aokw/konflux-test-integration-clone-tajmuq&#xA;&lt; Exit [It] triggers a Build PipelineRun for componentC konflux-test-integration-clone - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:395 @ 05/09/26 03:15:22.677 (20.025s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:15:22.677&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:15:22.677 (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.000322589">
              <system-err>&gt; Enter [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:409 @ 05/09/26 03:15:22.678&#xA;&lt; Exit [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:409 @ 05/09/26 03:15:22.678 (0s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:15:22.678&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:15:22.678 (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.018698736">
              <system-err>&gt; Enter [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:413 @ 05/09/26 03:15:22.678&#xA;PipelineRun konflux-test-integration-clone-tajmuq-on-pull-request-5zm8k found for Component group-aokw/konflux-test-integration-clone-tajmuq&#xA;PipelineRun konflux-test-integration-clone-tajmuq-on-pull-request-5zm8k reason: Running&#xA;PipelineRun konflux-test-integration-clone-tajmuq-on-pull-request-5zm8k reason: Running&#xA;PipelineRun konflux-test-integration-clone-tajmuq-on-pull-request-5zm8k reason: Running&#xA;PipelineRun konflux-test-integration-clone-tajmuq-on-pull-request-5zm8k reason: Running&#xA;PipelineRun konflux-test-integration-clone-tajmuq-on-pull-request-5zm8k reason: Running&#xA;PipelineRun konflux-test-integration-clone-tajmuq-on-pull-request-5zm8k reason: Running&#xA;PipelineRun konflux-test-integration-clone-tajmuq-on-pull-request-5zm8k reason: Running&#xA;PipelineRun konflux-test-integration-clone-tajmuq-on-pull-request-5zm8k reason: Running&#xA;PipelineRun konflux-test-integration-clone-tajmuq-on-pull-request-5zm8k reason: Running&#xA;PipelineRun integration-resolver-pipelinerun-crx4b reason: Running&#xA;PipelineRun integration-resolver-pipelinerun-crx4b reason: Succeeded&#xA;&lt; Exit [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:413 @ 05/09/26 03:18:42.697 (3m20.018s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:18:42.697&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:18:42.697 (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.355602835">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for componentC konflux-test-integration-clone - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:418 @ 05/09/26 03:18:42.698&#xA;&lt; Exit [It] should lead to a PaC PR creation for componentC konflux-test-integration-clone - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:418 @ 05/09/26 03:18:43.053 (355ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:18:43.053&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:18:43.053 (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.00821514">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:440 @ 05/09/26 03:18:43.054&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:440 @ 05/09/26 03:18:43.061 (8ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:18:43.062&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:18:43.062 (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.008415115">
              <system-err>&gt; Enter [It] should find the related Integration PipelineRuns - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:445 @ 05/09/26 03:18:43.062&#xA;&lt; Exit [It] should find the related Integration PipelineRuns - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:445 @ 05/09/26 03:18:43.07 (8ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:18:43.07&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:18:43.07 (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.006781841">
              <system-err>&gt; Enter [It] integration pipeline should end up with success - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:452 @ 05/09/26 03:18:43.071&#xA;PipelineRun integration-resolver-pipelinerun-crx4b reason: Succeeded&#xA;&lt; Exit [It] integration pipeline should end up with success - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:452 @ 05/09/26 03:18:43.077 (7ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:18:43.077&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:18:43.077 (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.45757383">
              <system-err>&gt; Enter [It] should merge the init PaC PR successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:459 @ 05/09/26 03:18:43.078&#xA;merged result sha: fd73b51f156644b967451be2573c9aa77d9305ec for PR #9195&#xA;&lt; Exit [It] should merge the init PaC PR successfully - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:459 @ 05/09/26 03:18:44.535 (1.457s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:18:44.535&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:18:44.535 (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.441616546">
              <system-err>&gt; Enter [It] should make change to the root folder - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:479 @ 05/09/26 03:18:44.536&#xA;PR #21848 got created with sha 92123bb9389ed41f5e1d7bd9091c8a0f54fea51a&#xA;&lt; Exit [It] should make change to the root folder - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:479 @ 05/09/26 03:18:46.977 (2.441s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:18:46.977&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:18:46.977 (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="1.9507263670000001">
              <system-err>&gt; Enter [It] should make change to the multiple-repo - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:497 @ 05/09/26 03:18:46.978&#xA;PR #9196 got created with sha 532a6dad9d22b2faed89bf8bb680382d42e20e46&#xA;&lt; Exit [It] should make change to the multiple-repo - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:497 @ 05/09/26 03:18:48.928 (1.95s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:18:48.928&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:18:48.928 (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.112205824">
              <system-err>&gt; Enter [It] wait for the last components build to finish - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:513 @ 05/09/26 03:18:48.929&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn found for Component group-aokw/go-component-wzvrbm&#xA;PipelineRun go-component-wzvrbm-on-pull-request-s4jdn reason: Completed&#xA;PipelineRun integration-resolver-pipelinerun-x72q2 found for Component group-aokw/python-component-xssyak&#xA;PipelineRun integration-resolver-pipelinerun-x72q2 reason: Succeeded&#xA;PipelineRun integration-resolver-pipelinerun-crx4b found for Component group-aokw/konflux-test-integration-clone-tajmuq&#xA;PipelineRun integration-resolver-pipelinerun-crx4b reason: Succeeded&#xA;&lt; Exit [It] wait for the last components build to finish - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:513 @ 05/09/26 03:18:49.041 (112ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:18:49.041&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:18:49.041 (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.008440956">
              <system-err>&gt; Enter [It] wait for all component snapshots to be created with proper PR group annotations - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:521 @ 05/09/26 03:18:49.041&#xA;Component snapshot integ-app-kjbe-20260509-025835-000 has PR group annotation: konflux-go-component-wzvrbm&#xA;Component snapshot integ-app-kjbe-20260509-030851-000 is missing PR group annotation&#xA;Component snapshot integ-app-kjbe-20260509-030859-000 has PR group annotation: konflux-python-component-xssyak&#xA;Component snapshot integ-app-kjbe-20260509-031506-000 has PR group annotation: konflux-konflux-test-integration-clone-tajmuq&#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.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:521 @ 05/09/26 03:18:49.049 (8ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:18:49.05&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:18:49.05 (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="360.610963429">
              <system-err>&gt; Enter [It] get all group snapshots and check if pr-group annotation contains all components - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:556 @ 05/09/26 03:18:49.05&#xA;Attempting to find group snapshots for application integ-app-kjbe in namespace group-aokw&#xA;Found 4 component snapshots:&#xA;PR Groups found: map[konflux-go-component-wzvrbm:1 konflux-konflux-test-integration-clone-tajmuq:1 konflux-python-component-xssyak: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-kjbe in namespace group-aokw&#xA;Found 4 component snapshots:&#xA;PR Groups found: map[konflux-go-component-wzvrbm:1 konflux-konflux-test-integration-clone-tajmuq:1 konflux-python-component-xssyak: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-kjbe in namespace group-aokw&#xA;Found 5 component snapshots:&#xA;PR Groups found: map[konflux-go-component-wzvrbm:1 konflux-konflux-test-integration-clone-tajmuq:1 konflux-python-component-xssyak: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-kjbe in namespace group-aokw&#xA;Found 5 component snapshots:&#xA;PR Groups found: map[konflux-go-component-wzvrbm:1 konflux-konflux-test-integration-clone-tajmuq:1 konflux-python-component-xssyak: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-kjbe in namespace group-aokw&#xA;Found 5 component snapshots:&#xA;PR Groups found: map[konflux-go-component-wzvrbm:1 konflux-konflux-test-integration-clone-tajmuq:1 konflux-python-component-xssyak: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-kjbe in namespace group-aokw&#xA;Found 5 component snapshots:&#xA;PR Groups found: map[konflux-go-component-wzvrbm:1 konflux-konflux-test-integration-clone-tajmuq:1 konflux-python-component-xssyak: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-kjbe in namespace group-aokw&#xA;Found 5 component snapshots:&#xA;PR Groups found: map[konflux-go-component-wzvrbm:1 konflux-konflux-test-integration-clone-tajmuq:1 konflux-python-component-xssyak: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-kjbe in namespace group-aokw&#xA;Found 7 component snapshots:&#xA;PR Groups found: map[konflux-go-component-wzvrbm:1 konflux-konflux-test-integration-clone-tajmuq:1 konflux-python-component-xssyak:1 pr-branch-vulzvf: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-kjbe in namespace group-aokw&#xA;Found 7 component snapshots:&#xA;PR Groups found: map[konflux-go-component-wzvrbm:1 konflux-konflux-test-integration-clone-tajmuq:1 konflux-python-component-xssyak:1 pr-branch-vulzvf: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-kjbe in namespace group-aokw&#xA;Found 7 component snapshots:&#xA;PR Groups found: map[konflux-go-component-wzvrbm:1 konflux-konflux-test-integration-clone-tajmuq:1 konflux-python-component-xssyak:1 pr-branch-vulzvf: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-kjbe in namespace group-aokw&#xA;Found 7 component snapshots:&#xA;PR Groups found: map[konflux-go-component-wzvrbm:1 konflux-konflux-test-integration-clone-tajmuq:1 konflux-python-component-xssyak:1 pr-branch-vulzvf: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-kjbe in namespace group-aokw&#xA;Found 8 component snapshots:&#xA;PR Groups found: map[konflux-go-component-wzvrbm:1 konflux-konflux-test-integration-clone-tajmuq:1 konflux-python-component-xssyak:1 pr-branch-vulzvf:2]&#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-kjbe in namespace group-aokw&#xA;Found 9 component snapshots:&#xA;PR Groups found: map[konflux-go-component-wzvrbm:1 konflux-konflux-test-integration-clone-tajmuq:1 konflux-python-component-xssyak:1 pr-branch-vulzvf:3]&#xA;Found 1 group snapshots!&#xA;  Group Snapshot 0: integ-app-kjbe-20260509-032448-902 (type: group)&#xA;    Group Test Info: [{&#34;namespace&#34;:&#34;group-aokw&#34;,&#34;component&#34;:&#34;go-component-wzvrbm&#34;,&#34;buildPipelineRun&#34;:&#34;go-component-wzvrbm-on-pull-request-hlsxs&#34;,&#34;snapshot&#34;:&#34;integ-app-kjbe-20260509-031851-000-q9&#34;,&#34;repoUrl&#34;:&#34;https://github.com/redhat-appstudio-qe/group-snapshot-multi-component&#34;,&#34;pullRequestNumber&#34;:&#34;21848&#34;},{&#34;namespace&#34;:&#34;group-aokw&#34;,&#34;component&#34;:&#34;python-component-xssyak&#34;,&#34;buildPipelineRun&#34;:&#34;python-component-xssyak-on-pull-request-rttzn&#34;,&#34;snapshot&#34;:&#34;integ-app-kjbe-20260509-031851-000&#34;,&#34;repoUrl&#34;:&#34;https://github.com/redhat-appstudio-qe/group-snapshot-multi-component&#34;,&#34;pullRequestNumber&#34;:&#34;21848&#34;},{&#34;namespace&#34;:&#34;group-aokw&#34;,&#34;component&#34;:&#34;konflux-test-integration-clone-tajmuq&#34;,&#34;buildPipelineRun&#34;:&#34;konflux-test-integration-clone-tajmuq-on-pull-request-h9sg7&#34;,&#34;snapshot&#34;:&#34;integ-app-kjbe-20260509-031852-000&#34;,&#34;repoUrl&#34;:&#34;https://github.com/redhat-appstudio-qe/konflux-test-integration-clone&#34;,&#34;pullRequestNumber&#34;:&#34;9196&#34;}]&#xA;Validating group test info annotation: [{&#34;namespace&#34;:&#34;group-aokw&#34;,&#34;component&#34;:&#34;go-component-wzvrbm&#34;,&#34;buildPipelineRun&#34;:&#34;go-component-wzvrbm-on-pull-request-hlsxs&#34;,&#34;snapshot&#34;:&#34;integ-app-kjbe-20260509-031851-000-q9&#34;,&#34;repoUrl&#34;:&#34;https://github.com/redhat-appstudio-qe/group-snapshot-multi-component&#34;,&#34;pullRequestNumber&#34;:&#34;21848&#34;},{&#34;namespace&#34;:&#34;group-aokw&#34;,&#34;component&#34;:&#34;python-component-xssyak&#34;,&#34;buildPipelineRun&#34;:&#34;python-component-xssyak-on-pull-request-rttzn&#34;,&#34;snapshot&#34;:&#34;integ-app-kjbe-20260509-031851-000&#34;,&#34;repoUrl&#34;:&#34;https://github.com/redhat-appstudio-qe/group-snapshot-multi-component&#34;,&#34;pullRequestNumber&#34;:&#34;21848&#34;},{&#34;namespace&#34;:&#34;group-aokw&#34;,&#34;component&#34;:&#34;konflux-test-integration-clone-tajmuq&#34;,&#34;buildPipelineRun&#34;:&#34;konflux-test-integration-clone-tajmuq-on-pull-request-h9sg7&#34;,&#34;snapshot&#34;:&#34;integ-app-kjbe-20260509-031852-000&#34;,&#34;repoUrl&#34;:&#34;https://github.com/redhat-appstudio-qe/konflux-test-integration-clone&#34;,&#34;pullRequestNumber&#34;:&#34;9196&#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.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:556 @ 05/09/26 03:24:49.66 (6m0.61s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:24:49.661&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:24:49.661 (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.052797728">
              <system-err>&gt; Enter [It] make sure that group snapshot contains last build pipelinerun for each component - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:635 @ 05/09/26 03:24:49.661&#xA;&lt; Exit [It] make sure that group snapshot contains last build pipelinerun for each component - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:635 @ 05/09/26 03:24:49.714 (52ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:24:49.714&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:24:49.714 (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.662006476">
              <system-err>&gt; Enter [It] make change to the multiple-repo to trigger a new cycle of testing - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:648 @ 05/09/26 03:24:49.715&#xA;&lt; Exit [It] make change to the multiple-repo to trigger a new cycle of testing - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:648 @ 05/09/26 03:24:50.376 (662ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:24:50.376&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:24:50.376 (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.123063102">
              <system-err>&gt; Enter [It] wait for the components A and B build to finish - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:654 @ 05/09/26 03:24:50.377&#xA;Waiting for build pipelineRun to be created for app group-aokw/integ-app-kjbe, sha: 0ea2e72692bbd54011502c48a3102738fa2ddbc9&#xA;PipelineRun go-component-wzvrbm-on-pull-request-hlsxs found for Component group-aokw/go-component-wzvrbm&#xA;PipelineRun go-component-wzvrbm-on-pull-request-hlsxs reason: Completed&#xA;PipelineRun integration-resolver-pipelinerun-2w4lk found for Component group-aokw/python-component-xssyak&#xA;PipelineRun integration-resolver-pipelinerun-2w4lk reason: Succeeded&#xA;&lt; Exit [It] wait for the components A and B build to finish - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:654 @ 05/09/26 03:24:50.5 (123ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:24:50.5&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:24:50.5 (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="360.338028485">
              <system-err>&gt; Enter [It] get all component snapshots for component A and check if older snapshot has been cancelled - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:663 @ 05/09/26 03:24:50.501&#xA;&lt; Exit [It] get all component snapshots for component A and check if older snapshot has been cancelled - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:663 @ 05/09/26 03:30:50.838 (6m0.338s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:30:50.839&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:30:50.839 (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.098853924">
              <system-err>&gt; Enter [It] get all group snapshots and check if older group snapshot is cancelled - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:690 @ 05/09/26 03:30:50.839&#xA;&lt; Exit [It] get all group snapshots and check if older group snapshot is cancelled - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:690 @ 05/09/26 03:30:50.938 (99ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:30:50.938&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:30:50.938 (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.218211034">
              <system-err>&gt; Enter [It] verifies that ResolutionRequest is deleted after pipeline resolution - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:720 @ 05/09/26 03:30:50.939&#xA;&lt; Exit [It] verifies that ResolutionRequest is deleted after pipeline resolution - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:720 @ 05/09/26 03:30:51.156 (218ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:30:51.157&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:30:51.157 (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.226349811">
              <system-err>&gt; Enter [It] verifies that no orphaned ResolutionRequests remain in namespace after test completion - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:740 @ 05/09/26 03:30:51.157&#xA;&lt; Exit [It] verifies that no orphaned ResolutionRequests remain in namespace after test completion - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:740 @ 05/09/26 03:30:51.383 (226ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:30:51.383&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:30:51.384 (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="25.661419486">
              <system-err>&gt; Enter [BeforeAll] when IntegrationTestScenario reference to task as pipelinerun resolution - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:775 @ 05/09/26 03:30:51.384&#xA;&lt; Exit [BeforeAll] when IntegrationTestScenario reference to task as pipelinerun resolution - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:775 @ 05/09/26 03:30:51.43 (46ms)&#xA;&gt; Enter [It] trigger pipelinerun for invalid integrationTestScenario by annotating snapshot and verify failing to create integration pipelinerun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:780 @ 05/09/26 03:30:51.431&#xA;&lt; Exit [It] trigger pipelinerun for invalid integrationTestScenario by annotating snapshot and verify failing to create integration pipelinerun - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:780 @ 05/09/26 03:31:11.494 (20.064s)&#xA;&gt; Enter [AfterAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:149 @ 05/09/26 03:31:11.494&#xA;&lt; Exit [AfterAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:149 @ 05/09/26 03:31:17.045 (5.551s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:31:17.045&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.CNj1aJY7Z5/tests/integration-service/group-snapshots-tests.go:50 @ 05/09/26 03:31:17.045 (0s)&#xA;</system-err>
          </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="passed" time="17.550084772">
              <system-err>&gt; Enter [BeforeAll] test pac with multiple components using same repository - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:40 @ 05/09/26 02:56:33.414&#xA;&lt; Exit [BeforeAll] test pac with multiple components using same repository - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:40 @ 05/09/26 02:56:40.831 (7.418s)&#xA;&gt; Enter [It] creates component with context directory go-component - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:106 @ 05/09/26 02:56:40.832&#xA;&lt; Exit [It] creates component with context directory go-component - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:106 @ 05/09/26 02:56:50.963 (10.131s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 02:56:50.963&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 02:56:50.963 (0s)&#xA;</system-err>
          </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-hqvhoy [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="passed" time="80.143254675">
              <system-err>&gt; Enter [It] triggers a PipelineRun for component go-component-hqvhoy - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:125 @ 05/09/26 02:56:50.964&#xA;PipelineRun has not been created yet for the component build-e2e-xedv/go-component-hqvhoy&#xA;PipelineRun has not been created yet for the component build-e2e-xedv/go-component-hqvhoy&#xA;PipelineRun has not been created yet for the component build-e2e-xedv/go-component-hqvhoy&#xA;PipelineRun has not been created yet for the component build-e2e-xedv/go-component-hqvhoy&#xA;&lt; Exit [It] triggers a PipelineRun for component go-component-hqvhoy - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:125 @ 05/09/26 02:58:11.107 (1m20.143s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 02:58:11.107&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 02:58:11.107 (0s)&#xA;</system-err>
          </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-hqvhoy [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="passed" time="0.405995676">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for component go-component-hqvhoy - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:140 @ 05/09/26 02:58:11.108&#xA;&lt; Exit [It] should lead to a PaC PR creation for component go-component-hqvhoy - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:140 @ 05/09/26 02:58:11.514 (406ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 02:58:11.514&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 02:58:11.514 (0s)&#xA;</system-err>
          </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-hqvhoy [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="passed" time="2990.777586799">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for component go-component-hqvhoy - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:159 @ 05/09/26 02:58:11.515&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r found for Component build-e2e-xedv/go-component-hqvhoy&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-h6d5r reason: Running&#xA;attempt 1/3: PipelineRun &#34;go-component-hqvhoy-on-pull-request-h6d5r&#34; failed: context deadline exceededNew PipelineRun go-component-hqvhoy-on-pull-request-khb5b found after retrigger for component build-e2e-xedv/go-component-hqvhoy&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b found for Component build-e2e-xedv/go-component-hqvhoy&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Running&#xA;PipelineRun go-component-hqvhoy-on-pull-request-khb5b reason: Succeeded&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for component go-component-hqvhoy - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:159 @ 05/09/26 03:48:02.292 (49m50.777s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:48:02.292&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:48:02.292 (0s)&#xA;</system-err>
          </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="passed" time="1.6743471680000002">
              <system-err>&gt; Enter [It] merging the PR should be successful - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:164 @ 05/09/26 03:48:02.293&#xA;merged result sha: b1ecac61687fe15abad7e01937bf0998f6232e2d for PR #33070&#xA;&lt; Exit [It] merging the PR should be successful - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:164 @ 05/09/26 03:48:03.966 (1.674s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:48:03.967&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:48:03.967 (0s)&#xA;</system-err>
          </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="passed" time="20.041988009">
              <system-err>&gt; Enter [It] leads to triggering on push PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:174 @ 05/09/26 03:48:03.968&#xA;Push PipelineRun has not been created yet for the component build-e2e-xedv/go-component-hqvhoy&#xA;&lt; Exit [It] leads to triggering on push PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:174 @ 05/09/26 03:48:24.009 (20.042s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:48:24.009&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:48:24.009 (0s)&#xA;</system-err>
          </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="passed" time="10.044360971">
              <system-err>&gt; Enter [It] creates component with context directory python-component - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:106 @ 05/09/26 03:48:24.01&#xA;&lt; Exit [It] creates component with context directory python-component - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:106 @ 05/09/26 03:48:34.054 (10.044s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:48:34.054&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:48:34.054 (0s)&#xA;</system-err>
          </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-hwtuss [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="passed" time="20.024062279">
              <system-err>&gt; Enter [It] triggers a PipelineRun for component python-component-hwtuss - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:125 @ 05/09/26 03:48:34.055&#xA;PipelineRun has not been created yet for the component build-e2e-xedv/python-component-hwtuss&#xA;&lt; Exit [It] triggers a PipelineRun for component python-component-hwtuss - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:125 @ 05/09/26 03:48:54.078 (20.024s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:48:54.079&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:48:54.079 (0s)&#xA;</system-err>
          </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-hwtuss [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="passed" time="0.349982144">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for component python-component-hwtuss - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:140 @ 05/09/26 03:48:54.079&#xA;&lt; Exit [It] should lead to a PaC PR creation for component python-component-hwtuss - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:140 @ 05/09/26 03:48:54.429 (350ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:48:54.429&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:48:54.429 (0s)&#xA;</system-err>
          </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-hwtuss [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="passed" time="380.032638324">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for component python-component-hwtuss - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:159 @ 05/09/26 03:48:54.429&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm found for Component build-e2e-xedv/python-component-hwtuss&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm reason: Running&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm reason: Running&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm reason: Running&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm reason: Running&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm reason: Running&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm reason: Running&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm reason: Running&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm reason: Running&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm reason: Running&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm reason: Running&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm reason: Running&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm reason: Running&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm reason: Running&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm reason: Running&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm reason: Running&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm reason: Running&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm reason: Running&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm reason: Running&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm reason: Running&#xA;PipelineRun python-component-hwtuss-on-pull-request-bxwnm reason: Succeeded&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for component python-component-hwtuss - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:159 @ 05/09/26 03:55:14.462 (6m20.032s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:55:14.462&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:55:14.462 (0s)&#xA;</system-err>
          </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="passed" time="1.6086989090000001">
              <system-err>&gt; Enter [It] merging the PR should be successful - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:164 @ 05/09/26 03:55:14.463&#xA;merged result sha: 35bea8153c6901bf635944150220ebefcf28b1f2 for PR #33075&#xA;&lt; Exit [It] merging the PR should be successful - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:164 @ 05/09/26 03:55:16.071 (1.608s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:55:16.071&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:55:16.071 (0s)&#xA;</system-err>
          </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="passed" time="20.025060727">
              <system-err>&gt; Enter [It] leads to triggering on push PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:174 @ 05/09/26 03:55:16.072&#xA;Push PipelineRun has not been created yet for the component build-e2e-xedv/python-component-hwtuss&#xA;&lt; Exit [It] leads to triggering on push PipelineRun - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:174 @ 05/09/26 03:55:36.097 (20.025s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:55:36.097&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:55:36.097 (0s)&#xA;</system-err>
          </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="passed" time="2.4626979430000002">
              <system-err>&gt; Enter [It] only one component is changed - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:190 @ 05/09/26 03:55:36.097&#xA;PR #33076 got created with sha 191ad9e90fd734fb847091ca551c94fcf5deb9f4&#xA;&lt; Exit [It] only one component is changed - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:190 @ 05/09/26 03:55:38.56 (2.462s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:55:38.56&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:55:38.56 (0s)&#xA;</system-err>
          </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="passed" time="20.025405638">
              <system-err>&gt; Enter [It] only related pipelinerun should be triggered - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:205 @ 05/09/26 03:55:38.56&#xA;on pull PiplelineRun has not been created yet for the PR&#xA;&lt; Exit [It] only related pipelinerun should be triggered - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:205 @ 05/09/26 03:55:58.586 (20.025s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:55:58.586&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:55:58.586 (0s)&#xA;</system-err>
          </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="passed" time="19.862298629">
              <system-err>&gt; Enter [BeforeAll] when a components is created with same git url in different namespace - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:223 @ 05/09/26 03:55:58.586&#xA;&lt; Exit [BeforeAll] when a components is created with same git url in different namespace - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:223 @ 05/09/26 03:56:10.272 (11.686s)&#xA;&gt; Enter [It] should fail to configure PaC for the component - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:264 @ 05/09/26 03:56:10.272&#xA;build status annotation value: {&#34;pac&#34;:{&#34;state&#34;:&#34;error&#34;,&#34;error-id&#34;:53,&#34;error-message&#34;:&#34;53: Git repository is already handled by Pipelines as Code&#34;},&#34;message&#34;:&#34;done&#34;}&#xA;build status: &amp;{State:error MergeUrl: ConfigurationTime: ErrorInfo:{ErrId:53 ErrMessage:53: Git repository is already handled by Pipelines as Code}}&#xA;&lt; Exit [It] should fail to configure PaC for the component - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:264 @ 05/09/26 03:56:10.284 (12ms)&#xA;&gt; Enter [AfterAll] when a components is created with same git url in different namespace - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:253 @ 05/09/26 03:56:10.284&#xA;&lt; Exit [AfterAll] when a components is created with same git url in different namespace - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:253 @ 05/09/26 03:56:12.324 (2.039s)&#xA;&gt; Enter [AfterAll] test pac with multiple components using same repository - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:68 @ 05/09/26 03:56:12.324&#xA;&lt; Exit [AfterAll] test pac with multiple components using same repository - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:68 @ 05/09/26 03:56:18.448 (6.124s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:56:18.448&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.CNj1aJY7Z5/tests/build/multi_component.go:28 @ 05/09/26 03:56:18.448 (0s)&#xA;</system-err>
          </testcase>
      </testsuite>
  </testsuites>