<?xml version="1.0" encoding="UTF-8"?>
  <testsuites tests="461" disabled="326" errors="1" failures="12" time="5264.94583465">
      <testsuite name="Red Hat App Studio E2E tests" package="/tmp/tmp.DGYK2mBrx2/cmd" tests="461" disabled="88" skipped="238" errors="1" failures="12" time="5264.94583465" timestamp="2026-04-21T07:58:43">
          <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="RandomSeed" value="1776757242"></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 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="108.655691081">
              <system-err>&gt; Enter [BeforeAll] PaC component build - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:54 @ 04/21/26 07:58:44.172&#xA;&lt; Exit [BeforeAll] PaC component build - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:54 @ 04/21/26 07:59:30.29 (46.119s)&#xA;&gt; Enter [BeforeAll] when a new component without specified branch is created and with visibility private - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:117 @ 04/21/26 07:59:30.291&#xA;Image repository for component fj-test-custom-default-dgsuox in namespace build-e2e-zugn 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.DGYK2mBrx2/tests/build/pac_build.go:117 @ 04/21/26 07:59:44.185 (13.895s)&#xA;&gt; Enter [It] correctly targets the default branch (that is not named &#39;main&#39;) with PaC - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:136 @ 04/21/26 07:59:44.186&#xA;&lt; Exit [It] correctly targets the default branch (that is not named &#39;main&#39;) with PaC - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:136 @ 04/21/26 08:00:32.827 (48.641s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:32.827&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:32.827 (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.015815701">
              <system-err>&gt; Enter [It] workspace parameter is set correctly in PaC repository CR - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:153 @ 04/21/26 08:00:32.828&#xA;&lt; Exit [It] workspace parameter is set correctly in PaC repository CR - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:153 @ 04/21/26 08:00:32.843 (16ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:32.843&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:32.843 (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="passed" time="20.02538472">
              <system-err>&gt; Enter [It] triggers a PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:176 @ 04/21/26 08:00:32.844&#xA;PipelineRun has not been created yet for the component build-e2e-zugn/fj-test-custom-branch-csvtba&#xA;&lt; Exit [It] triggers a PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:176 @ 04/21/26 08:00:52.869 (20.025s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:52.869&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:52.869 (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 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="passed" time="0.000321408">
              <system-err>&gt; Enter [It] build pipeline uses the correct serviceAccount - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:191 @ 04/21/26 08:00:52.87&#xA;&lt; Exit [It] build pipeline uses the correct serviceAccount - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:191 @ 04/21/26 08:00:52.87 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:52.87&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:52.87 (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 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="passed" time="0.006675538">
              <system-err>&gt; Enter [It] component build status is set correctly - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:195 @ 04/21/26 08:00:52.87&#xA;build status annotation value: {&#34;pac&#34;:{&#34;state&#34;:&#34;enabled&#34;,&#34;merge-url&#34;:&#34;https://codeberg.org/konflux-qe/devfile-sample-hello-world-mloshv/pulls/1&#34;,&#34;configuration-time&#34;:&#34;Tue, 21 Apr 2026 08:00:32 UTC&#34;},&#34;message&#34;:&#34;done&#34;}&#xA;state: enabled&#xA;mergeUrl: https://codeberg.org/konflux-qe/devfile-sample-hello-world-mloshv/pulls/1&#xA;errId: 0&#xA;errMessage: &#xA;configurationTime: Tue, 21 Apr 2026 08:00:32 UTC&#xA;&lt; Exit [It] component build status is set correctly - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:195 @ 04/21/26 08:00:52.877 (6ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:52.877&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:52.877 (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 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="passed" time="1.744482003">
              <system-err>&gt; Enter [It] image repo and robot account created successfully - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:225 @ 04/21/26 08:00:52.877&#xA;&lt; Exit [It] image repo and robot account created successfully - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:225 @ 04/21/26 08:00:54.621 (1.744s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:54.622&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:54.622 (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 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="passed" time="0.280110005">
              <system-err>&gt; Enter [It] created image repo is private - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:243 @ 04/21/26 08:00:54.622&#xA;&lt; Exit [It] created image repo is private - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:243 @ 04/21/26 08:00:54.902 (280ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:54.902&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:54.902 (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 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="passed" time="15.046293561">
              <system-err>&gt; Enter [It] a related PipelineRun should be deleted after deleting the component - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:249 @ 04/21/26 08:00:54.903&#xA;&lt; Exit [It] a related PipelineRun should be deleted after deleting the component - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:249 @ 04/21/26 08:01:09.949 (15.046s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:01:09.949&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:01:09.949 (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 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="passed" time="0.919231262">
              <system-err>&gt; Enter [It] PR branch should not exist in the repo - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:265 @ 04/21/26 08:01:09.95&#xA;&lt; Exit [It] PR branch should not exist in the repo - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:265 @ 04/21/26 08:01:10.868 (919ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:01:10.869&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:01:10.869 (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 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="passed" time="0.946806766">
              <system-err>&gt; Enter [It] related image repo and the robot account should be deleted after deleting the component - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:278 @ 04/21/26 08:01:10.869&#xA;&lt; Exit [It] related image repo and the robot account should be deleted after deleting the component - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:278 @ 04/21/26 08:01:11.816 (946ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:01:11.816&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:01:11.816 (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 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="passed" time="220.197773985">
              <system-err>&gt; Enter [BeforeAll] when a new Component with specified custom branch is created - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:306 @ 04/21/26 08:01:11.817&#xA;Image repository for component fj-test-custom-branch-csvtba in namespace build-e2e-zugn 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.DGYK2mBrx2/tests/build/pac_build.go:306 @ 04/21/26 08:01:31.845 (20.028s)&#xA;&gt; Enter [It] triggers a PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:332 @ 04/21/26 08:01:31.845&#xA;PipelineRun has not been created yet for the component build-e2e-zugn/fj-test-custom-branch-csvtba&#xA;PipelineRun has not been created yet for the component build-e2e-zugn/fj-test-custom-branch-csvtba&#xA;PipelineRun has not been created yet for the component build-e2e-zugn/fj-test-custom-branch-csvtba&#xA;PipelineRun has not been created yet for the component build-e2e-zugn/fj-test-custom-branch-csvtba&#xA;PipelineRun has not been created yet for the component build-e2e-zugn/fj-test-custom-branch-csvtba&#xA;PipelineRun has not been created yet for the component build-e2e-zugn/fj-test-custom-branch-csvtba&#xA;PipelineRun has not been created yet for the component build-e2e-zugn/fj-test-custom-branch-csvtba&#xA;PipelineRun has not been created yet for the component build-e2e-zugn/fj-test-custom-branch-csvtba&#xA;PipelineRun has not been created yet for the component build-e2e-zugn/fj-test-custom-branch-csvtba&#xA;PipelineRun has not been created yet for the component build-e2e-zugn/fj-test-custom-branch-csvtba&#xA;&lt; Exit [It] triggers a PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:332 @ 04/21/26 08:04:52.014 (3m20.169s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:04:52.015&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:04:52.015 (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 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="passed" time="1.8059854419999999">
              <system-err>&gt; Enter [It] should lead to a PaC init PR creation - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:347 @ 04/21/26 08:04:52.015&#xA;&lt; Exit [It] should lead to a PaC init PR creation - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:347 @ 04/21/26 08:04:53.821 (1.806s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:04:53.821&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:04:53.821 (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 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="passed" time="380.01515918">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:365 @ 04/21/26 08:04:53.822&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz found for Component build-e2e-zugn/fj-test-custom-branch-csvtba&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-z6xqz reason: Succeeded&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:365 @ 04/21/26 08:11:13.836 (6m20.015s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:13.837&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:13.837 (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 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="passed" time="1.060987971">
              <system-err>&gt; Enter [It] image repo and robot account created successfully - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:371 @ 04/21/26 08:11:13.837&#xA;&lt; Exit [It] image repo and robot account created successfully - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:371 @ 04/21/26 08:11:14.898 (1.06s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:14.898&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:14.898 (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 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="passed" time="0.334014481">
              <system-err>&gt; Enter [It] created image repo is public - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:390 @ 04/21/26 08:11:14.899&#xA;&lt; Exit [It] created image repo is public - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:390 @ 04/21/26 08:11:15.232 (333ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:15.233&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:15.233 (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 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="passed" time="0.354339118">
              <system-err>&gt; Enter [It] image tag is updated successfully - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:396 @ 04/21/26 08:11:15.233&#xA;Image tag quay.io/redhat-appstudio-qe/build-e2e-zugn/fj-test-custom-branch-csvtba:on-pr-3c9efebec4033041f4425d0748ae8de9bf41e133 successfully found in Quay&#xA;&lt; Exit [It] image tag is updated successfully - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:396 @ 04/21/26 08:11:15.587 (354ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:15.587&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:15.588 (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 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="passed" time="0.48429095">
              <system-err>&gt; Enter [It] should ensure pruning labels are set - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:425 @ 04/21/26 08:11:15.588&#xA;&lt; Exit [It] should ensure pruning labels are set - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:425 @ 04/21/26 08:11:16.072 (484ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:16.072&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:16.072 (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 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="passed" time="11.105932062">
              <system-err>&gt; Enter [It] eventually leads to the PipelineRun status report at Checks tab - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:439 @ 04/21/26 08:11:16.073&#xA;&lt; Exit [It] eventually leads to the PipelineRun status report at Checks tab - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:439 @ 04/21/26 08:11:16.073 (0s)&#xA;&gt; Enter [AfterAll] when a new Component with specified custom branch is created - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:324 @ 04/21/26 08:11:16.073&#xA;&lt; Exit [AfterAll] when a new Component with specified custom branch is created - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:324 @ 04/21/26 08:11:27.178 (11.105s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:27.179&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:27.179 (0s)&#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="passed" time="49.639721459">
              <system-err>&gt; Enter [BeforeAll] when the PaC init branch is updated - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:454 @ 04/21/26 08:11:27.179&#xA;created file sha: 7ea33f1ffff63bf9f49283571ca7ecfcde50f30d&#xA;&lt; Exit [BeforeAll] when the PaC init branch is updated - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:454 @ 04/21/26 08:11:36.777 (9.598s)&#xA;&gt; Enter [It] eventually leads to triggering another PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:464 @ 04/21/26 08:11:36.777&#xA;PipelineRun has not been created yet for the component build-e2e-zugn/fj-test-custom-branch-csvtba&#xA;PipelineRun has not been created yet for the component build-e2e-zugn/fj-test-custom-branch-csvtba&#xA;&lt; Exit [It] eventually leads to triggering another PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:464 @ 04/21/26 08:12:16.818 (40.041s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:12:16.819&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:12:16.819 (0s)&#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="passed" time="1.2532154119999999">
              <system-err>&gt; Enter [It] should lead to a PaC init PR update - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:479 @ 04/21/26 08:12:16.819&#xA;&lt; Exit [It] should lead to a PaC init PR update - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:479 @ 04/21/26 08:12:18.072 (1.253s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:12:18.072&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:12:18.072 (0s)&#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="passed" time="260.021032386">
              <system-err>&gt; Enter [It] PipelineRun should eventually finish - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:498 @ 04/21/26 08:12:18.073&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-nc2xm found for Component build-e2e-zugn/fj-test-custom-branch-csvtba&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-nc2xm reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-nc2xm reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-nc2xm reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-nc2xm reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-nc2xm reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-nc2xm reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-nc2xm reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-nc2xm reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-nc2xm reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-nc2xm reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-nc2xm reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-nc2xm reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-nc2xm reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-pull-request-nc2xm reason: Succeeded&#xA;&lt; Exit [It] PipelineRun should eventually finish - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:498 @ 04/21/26 08:16:38.093 (4m20.021s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:16:38.094&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:16:38.094 (0s)&#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="passed" time="0.000267307">
              <system-err>&gt; Enter [It] eventually leads to another update of a PR about the PipelineRun status report at Checks tab - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:504 @ 04/21/26 08:16:38.094&#xA;&lt; Exit [It] eventually leads to another update of a PR about the PipelineRun status report at Checks tab - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:504 @ 04/21/26 08:16:38.094 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:16:38.094&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:16:38.094 (0s)&#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="passed" time="39.672771187">
              <system-err>&gt; Enter [BeforeAll] when the PaC init branch is merged - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:520 @ 04/21/26 08:16:38.095&#xA;merged result sha: 849d56ebe6a9acf366855b71c3368cb98e512d34&#xA;&lt; Exit [BeforeAll] when the PaC init branch is merged - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:520 @ 04/21/26 08:16:57.735 (19.64s)&#xA;&gt; Enter [It] eventually leads to triggering another PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:530 @ 04/21/26 08:16:57.735&#xA;&lt; Exit [It] eventually leads to triggering another PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:530 @ 04/21/26 08:17:17.767 (20.032s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:17:17.767&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:17:17.767 (0s)&#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="passed" time="260.020180471">
              <system-err>&gt; Enter [It] pipelineRun should eventually finish - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:546 @ 04/21/26 08:17:17.768&#xA;PipelineRun fj-test-custom-branch-csvtba-on-push-5t8cf found for Component build-e2e-zugn/fj-test-custom-branch-csvtba&#xA;PipelineRun fj-test-custom-branch-csvtba-on-push-5t8cf reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-push-5t8cf reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-push-5t8cf reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-push-5t8cf reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-push-5t8cf reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-push-5t8cf reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-push-5t8cf reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-push-5t8cf reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-push-5t8cf reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-push-5t8cf reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-push-5t8cf reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-push-5t8cf reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-push-5t8cf reason: Running&#xA;PipelineRun fj-test-custom-branch-csvtba-on-push-5t8cf reason: Succeeded&#xA;&lt; Exit [It] pipelineRun should eventually finish - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:546 @ 04/21/26 08:21:37.788 (4m20.02s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:21:37.788&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:21:37.788 (0s)&#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="passed" time="0.433504046">
              <system-err>&gt; Enter [It] does not have expiration set - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:552 @ 04/21/26 08:21:37.788&#xA;&lt; Exit [It] does not have expiration set - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:552 @ 04/21/26 08:21:38.222 (433ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:21:38.222&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:21:38.222 (0s)&#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="passed" time="120.349020702">
              <system-err>&gt; Enter [It] After updating image visibility to private, it should not trigger another PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:564 @ 04/21/26 08:21:38.222&#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.DGYK2mBrx2/tests/build/pac_build.go:564 @ 04/21/26 08:23:38.571 (2m0.349s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:23:38.571&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:23:38.571 (0s)&#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="passed" time="0.287467513">
              <system-err>&gt; Enter [It] image repo is updated to private - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:595 @ 04/21/26 08:23:38.572&#xA;&lt; Exit [It] image repo is updated to private - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:595 @ 04/21/26 08:23:38.859 (287ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:23:38.859&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:23:38.859 (0s)&#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 and recreated (with the same name in the same namespace) should no longer lead to a creation of a PaC PR [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="107.723755139">
              <system-err>&gt; Enter [BeforeAll] when the component is removed and recreated (with the same name in the same namespace) - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:650 @ 04/21/26 08:23:38.86&#xA;&lt; Exit [BeforeAll] when the component is removed and recreated (with the same name in the same namespace) - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:650 @ 04/21/26 08:23:43.676 (4.815s)&#xA;&gt; Enter [BeforeAll] when the component is removed and recreated (with the same name in the same namespace) - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:679 @ 04/21/26 08:23:43.676&#xA;&lt; Exit [BeforeAll] when the component is removed and recreated (with the same name in the same namespace) - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:679 @ 04/21/26 08:23:53.71 (10.034s)&#xA;&gt; Enter [It] should no longer lead to a creation of a PaC PR - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:715 @ 04/21/26 08:23:53.711&#xA;&lt; Exit [It] should no longer lead to a creation of a PaC PR - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:715 @ 04/21/26 08:24:05.406 (11.695s)&#xA;&gt; Enter [AfterAll] when the component is removed and recreated (with the same name in the same namespace) - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:697 @ 04/21/26 08:24:05.406&#xA;Found purge PR with id: 3&#xA;&lt; Exit [AfterAll] when the component is removed and recreated (with the same name in the same namespace) - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:697 @ 04/21/26 08:24:33.783 (28.376s)&#xA;&gt; Enter [AfterAll] PaC component build - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:101 @ 04/21/26 08:24:33.783&#xA;&lt; Exit [AfterAll] PaC component build - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:101 @ 04/21/26 08:25:26.584 (52.801s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:25:26.584&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:25:26.584 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when creating tenants and running initial pipelines should create both tenants concurrently [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="passed" time="7.191707175">
              <system-err>&gt; Enter [BeforeAll] [disaster-recovery DR Same-Version Backup/Restore] - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:33 @ 04/21/26 08:38:53.371&#xA;STEP: Validating OADP operator health: pods running in openshift-adp - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:38 @ 04/21/26 08:38:54.992&#xA;STEP: Validating Velero readiness: deployment has ready replicas - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:38 @ 04/21/26 08:38:54.998&#xA;STEP: Validating BSL availability: at least one BackupStorageLocation is Available - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:38 @ 04/21/26 08:38:55.002&#xA;STEP: Validating GitHub repo is reachable: https://github.com/redhat-appstudio-qe/DR_test_MathWizz - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:38 @ 04/21/26 08:38:55.019&#xA;STEP: Validating repo structure: 3 component Dockerfiles exist - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:38 @ 04/21/26 08:38:55.019&#xA;&lt; Exit [BeforeAll] [disaster-recovery DR Same-Version Backup/Restore] - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:33 @ 04/21/26 08:38:55.39 (2.019s)&#xA;&gt; Enter [It] should create both tenants concurrently - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:43 @ 04/21/26 08:38:55.39&#xA;STEP: Creating tenant namespace dr-test-moshekipod-same-version-dr - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:38:55.39&#xA;STEP: Creating tenant namespace dr-test-kokohazamar-same-version-dr - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:38:55.39&#xA;STEP: Creating Application kokohazamar-same-version-dr in namespace dr-test-kokohazamar-same-version-dr - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:38:56.437&#xA;STEP: Creating Application moshekipod-same-version-dr in namespace dr-test-moshekipod-same-version-dr - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:38:56.441&#xA;STEP: Creating Component mathwizz-web-server in namespace dr-test-moshekipod-same-version-dr - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:38:56.701&#xA;STEP: Creating Component mathwizz-web-server in namespace dr-test-kokohazamar-same-version-dr - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:38:56.701&#xA;STEP: Creating Component mathwizz-history-worker in namespace dr-test-moshekipod-same-version-dr - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:38:56.957&#xA;STEP: Creating Component mathwizz-history-worker in namespace dr-test-kokohazamar-same-version-dr - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:38:56.957&#xA;STEP: Creating Component mathwizz-frontend in namespace dr-test-kokohazamar-same-version-dr - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:38:57.197&#xA;STEP: Creating Component mathwizz-frontend in namespace dr-test-moshekipod-same-version-dr - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:38:57.258&#xA;STEP: Creating managed namespace dr-test-kokohazamar-same-version-dr-managed for release pipelines - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:38:57.402&#xA;STEP: Creating managed namespace dr-test-moshekipod-same-version-dr-managed for release pipelines - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:38:57.453&#xA;STEP: Creating release pipeline ServiceAccount release-service-account in managed namespace dr-test-kokohazamar-same-version-dr-managed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:38:59.806&#xA;STEP: Creating release pipeline RoleBinding in managed namespace dr-test-kokohazamar-same-version-dr-managed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:38:59.832&#xA;STEP: Creating release pipeline ServiceAccount release-service-account in managed namespace dr-test-moshekipod-same-version-dr-managed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:38:59.854&#xA;STEP: Creating release pipeline RoleBinding in managed namespace dr-test-moshekipod-same-version-dr-managed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:38:59.894&#xA;STEP: Creating registry auth secrets in managed namespace dr-test-kokohazamar-same-version-dr-managed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:38:59.908&#xA;STEP: Linking Quay auth secret to release SA in managed namespace dr-test-kokohazamar-same-version-dr-managed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:38:59.968&#xA;STEP: Creating cosign signing secret in managed namespace dr-test-kokohazamar-same-version-dr-managed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:38:59.995&#xA;STEP: Creating registry auth secrets in managed namespace dr-test-moshekipod-same-version-dr-managed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:39:00.001&#xA;STEP: Linking Quay auth secret to release SA in managed namespace dr-test-moshekipod-same-version-dr-managed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:39:00.028&#xA;STEP: Getting default Enterprise Contract policy from enterprise-contract-service namespace - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:39:00.028&#xA;STEP: Creating cosign signing secret in managed namespace dr-test-moshekipod-same-version-dr-managed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:39:00.049&#xA;STEP: Creating Enterprise Contract policy dr-ec-policy in managed namespace dr-test-kokohazamar-same-version-dr-managed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:39:00.057&#xA;STEP: Creating ReleasePlan dr-releaseplan in tenant namespace dr-test-kokohazamar-same-version-dr - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:39:00.083&#xA;STEP: Getting default Enterprise Contract policy from enterprise-contract-service namespace - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:39:00.093&#xA;STEP: Creating Enterprise Contract policy dr-ec-policy in managed namespace dr-test-moshekipod-same-version-dr-managed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:39:00.107&#xA;STEP: Creating ReleasePlan dr-releaseplan in tenant namespace dr-test-moshekipod-same-version-dr - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:39:00.123&#xA;STEP: Creating ReleasePlanAdmission dr-releaseplanadmission in managed namespace dr-test-moshekipod-same-version-dr-managed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:39:00.221&#xA;STEP: Creating ReleasePlanAdmission dr-releaseplanadmission in managed namespace dr-test-kokohazamar-same-version-dr-managed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:39:00.223&#xA;STEP: Creating release PVC dr-release-pvc in managed namespace dr-test-kokohazamar-same-version-dr-managed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:39:00.37&#xA;STEP: Creating release PVC dr-release-pvc in managed namespace dr-test-moshekipod-same-version-dr-managed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:39:00.384&#xA;STEP: Creating secrets access Role in managed namespace dr-test-moshekipod-same-version-dr-managed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:39:00.421&#xA;STEP: Creating secrets access Role in managed namespace dr-test-kokohazamar-same-version-dr-managed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:39:00.435&#xA;STEP: Creating secrets access RoleBinding in managed namespace dr-test-moshekipod-same-version-dr-managed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:39:00.445&#xA;STEP: Creating secrets access RoleBinding in managed namespace dr-test-kokohazamar-same-version-dr-managed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:50 @ 04/21/26 08:39:00.452&#xA;&lt; Exit [It] should create both tenants concurrently - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:43 @ 04/21/26 08:39:00.562 (5.172s)&#xA;&gt; Enter [AfterEach] [disaster-recovery DR Same-Version Backup/Restore] - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:29 @ 04/21/26 08:39:00.562&#xA;&lt; Exit [AfterEach] [disaster-recovery DR Same-Version Backup/Restore] - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:29 @ 04/21/26 08:39:00.562 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when creating tenants and running initial pipelines should wait for all build PipelineRuns to succeed [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="timedout" time="2847.945254861">
              <failure message="A suite timeout occurred" type="timedout">[TIMEDOUT] A suite timeout occurred&#xA;In [It] at: /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:56 @ 04/21/26 09:26:28.238&#xA;&#xA;This is the Progress Report generated when the suite timeout occurred:&#xA;  [disaster-recovery DR Same-Version Backup/Restore] when creating tenants and running initial pipelines should wait for all build PipelineRuns to succeed (Spec Runtime: 47m27.676s)&#xA;    /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:56&#xA;    In [It] (Node Runtime: 47m27.676s)&#xA;      /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:56&#xA;      At [By Step] Waiting for 3 release PipelineRuns in dr-test-kokohazamar-same-version-dr-managed (base: 0) (Step Runtime: 17m27.674s)&#xA;        /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:57&#xA;&#xA;      Spec Goroutine&#xA;      goroutine 775 [select, 2 minutes]&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc000631c00, {0x497b9a8, 0xc0016414c0}, 0x1, {0xc0020c07c0, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.0/internal/async_assertion.go:558&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc000631c00, {0x497b9a8, 0xc0016414c0}, {0xc0020c07c0, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.0/internal/async_assertion.go:145&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForSucceededPRCount(0xc001ceec00, {0x409b9e4, 0x2b}, {0x0, 0x0}, {0x0, 0x0}, 0x3, 0x34630b8a000, 0x45d964b800)&#xA;          /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/tenant_application_lifecycle.go:104&#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(0xc001ceec00, {0xc000b31300, 0x2, 0xc0001a0ea0?}, 0x0, 0x0)&#xA;          /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/tenant_application_lifecycle.go:184&#xA;            | &#x9;By(fmt.Sprintf(&#34;Waiting for %d release PipelineRuns in %s (base: %d)&#34;,&#xA;            | &#x9;&#x9;expected, t.ManagedNamespace, releaseBase))&#xA;            &gt; &#x9;waitForSucceededPRCount(fw, t.ManagedNamespace, &#34;&#34;, &#34;&#34;, expected,&#xA;            | &#x9;&#x9;ReleaseChainTimeout, ReleaseChainPoll)&#xA;            | }&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.init.func2.2.2()&#xA;          /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:57&#xA;            | &#xA;            | &#x9;It(&#34;should wait for all build PipelineRuns to succeed&#34;, func() {&#xA;            &gt; &#x9;&#x9;waitForPipelineChains(fw, svTenants, nil, nil)&#xA;            | &#x9;})&#xA;            | })&#xA;        github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x0?, 0x0?})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.27.4/internal/node.go:524&#xA;        github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3()&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.27.4/internal/suite.go:945&#xA;        github.com/onsi/ginkgo/v2/internal.(*Suite).runNode in goroutine 123&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.27.4/internal/suite.go:910&#xA;&#xA;There were additional failures detected after the initial failure. These are visible in the timeline&#xA;</failure>
              <system-err>&gt; Enter [It] should wait for all build PipelineRuns to succeed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:56 @ 04/21/26 08:39:00.563&#xA;STEP: Waiting for per-component build → test chains across all tenants - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:57 @ 04/21/26 08:39:00.563&#xA;STEP: Waiting for build PipelineRun for mathwizz-frontend in dr-test-moshekipod-same-version-dr (base: 0) - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/tenant_application_lifecycle.go:163 @ 04/21/26 08:39:00.563&#xA;STEP: Waiting for build PipelineRun for mathwizz-frontend in dr-test-kokohazamar-same-version-dr (base: 0) - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/tenant_application_lifecycle.go:163 @ 04/21/26 08:39:00.563&#xA;STEP: Waiting for build PipelineRun for mathwizz-web-server in dr-test-kokohazamar-same-version-dr (base: 0) - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/tenant_application_lifecycle.go:163 @ 04/21/26 08:39:00.563&#xA;STEP: Waiting for build PipelineRun for mathwizz-web-server in dr-test-moshekipod-same-version-dr (base: 0) - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/tenant_application_lifecycle.go:163 @ 04/21/26 08:39:00.563&#xA;STEP: Waiting for build PipelineRun for mathwizz-history-worker in dr-test-kokohazamar-same-version-dr (base: 0) - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/tenant_application_lifecycle.go:163 @ 04/21/26 08:39:00.563&#xA;STEP: Waiting for build PipelineRun for mathwizz-history-worker in dr-test-moshekipod-same-version-dr (base: 0) - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/tenant_application_lifecycle.go:163 @ 04/21/26 08:39:00.563&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded&#xA;STEP: Waiting for 3 release PipelineRuns in dr-test-kokohazamar-same-version-dr-managed (base: 0) - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:57 @ 04/21/26 09:09:00.564&#xA;namespace dr-test-kokohazamar-same-version-dr-managed: 0/3 release PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr-managed: 0/3 release PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr-managed: 0/3 release PipelineRuns succeeded&#xA;namespace dr-test-kokohazamar-same-version-dr-managed: 0/3 release PipelineRuns succeeded&#xA;[TIMEDOUT] A suite timeout occurred&#xA;In [It] at: /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:56 @ 04/21/26 09:26:28.238&#xA;&#xA;This is the Progress Report generated when the suite timeout occurred:&#xA;  [disaster-recovery DR Same-Version Backup/Restore] when creating tenants and running initial pipelines should wait for all build PipelineRuns to succeed (Spec Runtime: 47m27.676s)&#xA;    /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:56&#xA;    In [It] (Node Runtime: 47m27.676s)&#xA;      /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:56&#xA;      At [By Step] Waiting for 3 release PipelineRuns in dr-test-kokohazamar-same-version-dr-managed (base: 0) (Step Runtime: 17m27.674s)&#xA;        /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:57&#xA;&#xA;      Spec Goroutine&#xA;      goroutine 775 [select, 2 minutes]&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc000631c00, {0x497b9a8, 0xc0016414c0}, 0x1, {0xc0020c07c0, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.0/internal/async_assertion.go:558&#xA;        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc000631c00, {0x497b9a8, 0xc0016414c0}, {0xc0020c07c0, 0x4, 0x4})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/gomega@v1.39.0/internal/async_assertion.go:145&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.waitForSucceededPRCount(0xc001ceec00, {0x409b9e4, 0x2b}, {0x0, 0x0}, {0x0, 0x0}, 0x3, 0x34630b8a000, 0x45d964b800)&#xA;          /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/tenant_application_lifecycle.go:104&#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(0xc001ceec00, {0xc000b31300, 0x2, 0xc0001a0ea0?}, 0x0, 0x0)&#xA;          /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/tenant_application_lifecycle.go:184&#xA;            | &#x9;By(fmt.Sprintf(&#34;Waiting for %d release PipelineRuns in %s (base: %d)&#34;,&#xA;            | &#x9;&#x9;expected, t.ManagedNamespace, releaseBase))&#xA;            &gt; &#x9;waitForSucceededPRCount(fw, t.ManagedNamespace, &#34;&#34;, &#34;&#34;, expected,&#xA;            | &#x9;&#x9;ReleaseChainTimeout, ReleaseChainPoll)&#xA;            | }&#xA;      &gt; github.com/konflux-ci/e2e-tests/tests/disaster-recovery.init.func2.2.2()&#xA;          /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:57&#xA;            | &#xA;            | &#x9;It(&#34;should wait for all build PipelineRuns to succeed&#34;, func() {&#xA;            &gt; &#x9;&#x9;waitForPipelineChains(fw, svTenants, nil, nil)&#xA;            | &#x9;})&#xA;            | })&#xA;        github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x0?, 0x0?})&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.27.4/internal/node.go:524&#xA;        github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3()&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.27.4/internal/suite.go:945&#xA;        github.com/onsi/ginkgo/v2/internal.(*Suite).runNode in goroutine 123&#xA;          /opt/app-root/src/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.27.4/internal/suite.go:910&#xA;&lt; Exit [It] should wait for all build PipelineRuns to succeed - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:56 @ 04/21/26 09:26:28.239 (47m27.676s)&#xA;&gt; Enter [AfterEach] [disaster-recovery DR Same-Version Backup/Restore] - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:29 @ 04/21/26 09:26:28.239&#xA;[FAILED] Timed out after 1800.001s.&#xA;expected 1 successful build PipelineRuns in namespace dr-test-moshekipod-same-version-dr&#xA;Expected&#xA;    &lt;int&gt;: 0&#xA;to equal&#xA;    &lt;int&gt;: 1&#xA;In [AfterEach] at: /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/tenant_application_lifecycle.go:165 @ 04/21/26 09:26:28.486&#xA;&lt; Exit [AfterEach] [disaster-recovery DR Same-Version Backup/Restore] - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:29 @ 04/21/26 09:26:28.486 (247ms)&#xA;&gt; Enter [AfterAll] [disaster-recovery DR Same-Version Backup/Restore] - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:119 @ 04/21/26 09:26:28.487&#xA;STEP: Collecting Velero pod information - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:121 @ 04/21/26 09:26:28.487&#xA;Velero pod: node-agent-gcrv7 | Phase: Running | Ready: true&#xA;Velero pod: node-agent-jh8s7 | Phase: Running | Ready: true&#xA;Velero pod: node-agent-jv5vq | Phase: Running | Ready: true&#xA;Velero pod: velero-5498cfc4db-8q745 | Phase: Running | Ready: true&#xA;STEP: Collecting Backup CR status for tenant &#34;dr-test-kokohazamar-same-version-dr&#34; - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:121 @ 04/21/26 09:26:28.492&#xA;WARNING: could not get Backup CR &#34;backup-kokohazamar-same-version-dr&#34;: backups.velero.io &#34;backup-kokohazamar-same-version-dr&#34; not found&#xA;STEP: Collecting Restore CR status for tenant &#34;dr-test-kokohazamar-same-version-dr&#34; - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:121 @ 04/21/26 09:26:28.496&#xA;WARNING: could not get Restore CR &#34;restore-backup-kokohazamar-same-version-dr&#34;: restores.velero.io &#34;restore-backup-kokohazamar-same-version-dr&#34; not found&#xA;STEP: Collecting Backup CR status for tenant &#34;dr-test-moshekipod-same-version-dr&#34; - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:121 @ 04/21/26 09:26:28.501&#xA;WARNING: could not get Backup CR &#34;backup-moshekipod-same-version-dr&#34;: backups.velero.io &#34;backup-moshekipod-same-version-dr&#34; not found&#xA;STEP: Collecting Restore CR status for tenant &#34;dr-test-moshekipod-same-version-dr&#34; - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:121 @ 04/21/26 09:26:28.504&#xA;WARNING: could not get Restore CR &#34;restore-backup-moshekipod-same-version-dr&#34;: restores.velero.io &#34;restore-backup-moshekipod-same-version-dr&#34; not found&#xA;&lt; Exit [AfterAll] [disaster-recovery DR Same-Version Backup/Restore] - /tmp/tmp.DGYK2mBrx2/tests/disaster-recovery/dr_same_version.go:119 @ 04/21/26 09:26:28.508 (22ms)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when backing up tenant data should create backup CRs for both tenants concurrently [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when simulating disaster by deleting namespaces should delete both tenant namespaces [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when restoring from backup should restore tenant-1 (KokoHazamar) via velero CLI method [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when restoring from backup should restore tenant-2 (MosheKipod) via oc command method [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when performing post-restore recovery should rotate SA tokens on both tenants [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when verifying restored tenants should confirm structural integrity of both tenants [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when verifying restored tenants should confirm functional pipeline execution after restore [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when creating tenants on the old Konflux version should create both tenants concurrently [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when creating tenants on the old Konflux version should wait for all build PipelineRuns to succeed [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when backing up tenant data before upgrade should create backup CRs for both tenants concurrently [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when simulating disaster by deleting namespaces should delete both tenant namespaces [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when upgrading Konflux to the new version should upgrade the cluster and verify Velero survived [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when restoring tenants from backup on the new Konflux version should restore tenant-1 (KokoHazamar) via velero CLI method [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when restoring tenants from backup on the new Konflux version should restore tenant-2 (MosheKipod) via oc command method [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when performing post-restore recovery should rotate SA tokens on both tenants [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when verifying restored tenants should confirm structural integrity of both tenants [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when verifying restored tenants should confirm functional pipeline execution after restore [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for 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] [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="79.017388309">
              <system-err>&gt; Enter [BeforeAll] test build annotations - /tmp/tmp.DGYK2mBrx2/tests/build/annotations.go:35 @ 04/21/26 07:58:44.16&#xA;&lt; Exit [BeforeAll] test build annotations - /tmp/tmp.DGYK2mBrx2/tests/build/annotations.go:35 @ 04/21/26 07:58:49.434 (5.274s)&#xA;&gt; Enter [BeforeAll] when component is created with invalid build request annotations - /tmp/tmp.DGYK2mBrx2/tests/build/annotations.go:69 @ 04/21/26 07:58:49.435&#xA;Image repository for component test-annotations-wrkham in namespace build-e2e-tova 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.DGYK2mBrx2/tests/build/annotations.go:69 @ 04/21/26 07:59:01.13 (11.695s)&#xA;&gt; Enter [It] handles invalid request annotation - /tmp/tmp.DGYK2mBrx2/tests/build/annotations.go:89 @ 04/21/26 07:59:01.13&#xA;build status annotation value: {&#34;message&#34;:&#34;unexpected build request: foo&#34;}&#xA;&lt; Exit [It] handles invalid request annotation - /tmp/tmp.DGYK2mBrx2/tests/build/annotations.go:89 @ 04/21/26 08:00:01.138 (1m0.008s)&#xA;&gt; Enter [AfterAll] test build annotations - /tmp/tmp.DGYK2mBrx2/tests/build/annotations.go:51 @ 04/21/26 08:00:01.138&#xA;&lt; Exit [AfterAll] test build annotations - /tmp/tmp.DGYK2mBrx2/tests/build/annotations.go:51 @ 04/21/26 08:00:03.176 (2.038s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/annotations.go:24 @ 04/21/26 08:00:03.177&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/annotations.go:24 @ 04/21/26 08:00:03.177 (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-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] [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="90.191394307">
              <system-err>&gt; Enter [BeforeAll] [release-service-suite [RELEASE-2136] Release CR fails when block-releases true in ReleasePlanAdmission.] - /tmp/tmp.DGYK2mBrx2/tests/release/service/block_releases_release_plan_admission.go:34 @ 04/21/26 07:58:44.067&#xA;&lt; Exit [BeforeAll] [release-service-suite [RELEASE-2136] Release CR fails when block-releases true in ReleasePlanAdmission.] - /tmp/tmp.DGYK2mBrx2/tests/release/service/block_releases_release_plan_admission.go:34 @ 04/21/26 07:59:37.886 (53.819s)&#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.DGYK2mBrx2/tests/release/service/block_releases_release_plan_admission.go:69 @ 04/21/26 07:59:37.886&#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.DGYK2mBrx2/tests/release/service/block_releases_release_plan_admission.go:69 @ 04/21/26 07:59:38.153 (267ms)&#xA;&gt; Enter [AfterEach] [release-service-suite [RELEASE-2136] Release CR fails when block-releases true in ReleasePlanAdmission.] - /tmp/tmp.DGYK2mBrx2/tests/release/service/block_releases_release_plan_admission.go:32 @ 04/21/26 07:59:38.153&#xA;&lt; Exit [AfterEach] [release-service-suite [RELEASE-2136] Release CR fails when block-releases true in ReleasePlanAdmission.] - /tmp/tmp.DGYK2mBrx2/tests/release/service/block_releases_release_plan_admission.go:32 @ 04/21/26 07:59:38.153 (0s)&#xA;&gt; Enter [AfterAll] [release-service-suite [RELEASE-2136] Release CR fails when block-releases true in ReleasePlanAdmission.] - /tmp/tmp.DGYK2mBrx2/tests/release/service/block_releases_release_plan_admission.go:61 @ 04/21/26 07:59:38.153&#xA;&lt; Exit [AfterAll] [release-service-suite [RELEASE-2136] Release CR fails when block-releases true in ReleasePlanAdmission.] - /tmp/tmp.DGYK2mBrx2/tests/release/service/block_releases_release_plan_admission.go:61 @ 04/21/26 08:00:14.259 (36.106s)&#xA;</system-err>
          </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="58.794235514">
              <system-err>&gt; Enter [BeforeAll] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] - /tmp/tmp.DGYK2mBrx2/tests/release/service/missing_release_plan_and_admission.go:34 @ 04/21/26 07:58:44.171&#xA;&lt; Exit [BeforeAll] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] - /tmp/tmp.DGYK2mBrx2/tests/release/service/missing_release_plan_and_admission.go:34 @ 04/21/26 07:59:42.824 (58.653s)&#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.DGYK2mBrx2/tests/release/service/missing_release_plan_and_admission.go:66 @ 04/21/26 07:59:42.824&#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.DGYK2mBrx2/tests/release/service/missing_release_plan_and_admission.go:66 @ 04/21/26 07:59:42.965 (141ms)&#xA;&gt; Enter [AfterEach] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] - /tmp/tmp.DGYK2mBrx2/tests/release/service/missing_release_plan_and_admission.go:32 @ 04/21/26 07:59:42.965&#xA;&lt; Exit [AfterEach] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] - /tmp/tmp.DGYK2mBrx2/tests/release/service/missing_release_plan_and_admission.go:32 @ 04/21/26 07:59:42.965 (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="41.133564523">
              <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.DGYK2mBrx2/tests/release/service/missing_release_plan_and_admission.go:76 @ 04/21/26 07:59:42.966&#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.DGYK2mBrx2/tests/release/service/missing_release_plan_and_admission.go:76 @ 04/21/26 07:59:42.994 (28ms)&#xA;&gt; Enter [AfterEach] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] - /tmp/tmp.DGYK2mBrx2/tests/release/service/missing_release_plan_and_admission.go:32 @ 04/21/26 07:59:42.994&#xA;&lt; Exit [AfterEach] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] - /tmp/tmp.DGYK2mBrx2/tests/release/service/missing_release_plan_and_admission.go:32 @ 04/21/26 07:59:42.994 (0s)&#xA;&gt; Enter [AfterAll] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] - /tmp/tmp.DGYK2mBrx2/tests/release/service/missing_release_plan_and_admission.go:58 @ 04/21/26 07:59:42.994&#xA;&lt; Exit [AfterAll] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] - /tmp/tmp.DGYK2mBrx2/tests/release/service/missing_release_plan_and_admission.go:58 @ 04/21/26 08:00:24.099 (41.105s)&#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] [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="50.085333001">
              <system-err>&gt; Enter [BeforeAll] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:32 @ 04/21/26 07:58:44.066&#xA;&lt; Exit [BeforeAll] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:32 @ 04/21/26 07:59:24.958 (40.892s)&#xA;&gt; Enter [It] verifies that the ReleasePlan CR is unmatched in the beginning - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:57 @ 04/21/26 07:59:24.958&#xA;&lt; Exit [It] verifies that the ReleasePlan CR is unmatched in the beginning - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:57 @ 04/21/26 07:59:34.151 (9.193s)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:34.151&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:34.152 (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="2.822956932">
              <system-err>&gt; Enter [It] Creates ReleasePlanAdmission CR in corresponding managed namespace - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:72 @ 04/21/26 07:59:34.152&#xA;&lt; Exit [It] Creates ReleasePlanAdmission CR in corresponding managed namespace - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:72 @ 04/21/26 07:59:36.975 (2.823s)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:36.975&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:36.975 (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.376912375">
              <system-err>&gt; Enter [It] verifies that the ReleasePlan CR is set to matched - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:85 @ 04/21/26 07:59:36.975&#xA;&lt; Exit [It] verifies that the ReleasePlan CR is set to matched - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:85 @ 04/21/26 07:59:37.352 (376ms)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:37.352&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:37.352 (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.261126127">
              <system-err>&gt; Enter [It] verifies that the ReleasePlanAdmission CR is set to matched - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:105 @ 04/21/26 07:59:37.353&#xA;&lt; Exit [It] verifies that the ReleasePlanAdmission CR is set to matched - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:105 @ 04/21/26 07:59:37.613 (261ms)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:37.614&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:37.614 (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.203550687">
              <system-err>&gt; Enter [It] Creates a manual release ReleasePlan CR in devNamespace - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:123 @ 04/21/26 07:59:37.614&#xA;&lt; Exit [It] Creates a manual release ReleasePlan CR in devNamespace - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:123 @ 04/21/26 07:59:37.817 (203ms)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:37.818&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:37.818 (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.137641043">
              <system-err>&gt; Enter [It] verifies that the second ReleasePlan CR is set to matched - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:129 @ 04/21/26 07:59:37.818&#xA;&lt; Exit [It] verifies that the second ReleasePlan CR is set to matched - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:129 @ 04/21/26 07:59:37.955 (137ms)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:37.955&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:37.956 (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.046551186">
              <system-err>&gt; Enter [It] verifies that the ReleasePlanAdmission CR has two matched ReleasePlan CRs - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:150 @ 04/21/26 07:59:37.956&#xA;&lt; Exit [It] verifies that the ReleasePlanAdmission CR has two matched ReleasePlan CRs - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:150 @ 04/21/26 07:59:38.002 (46ms)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:38.002&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:38.002 (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.149377396">
              <system-err>&gt; Enter [It] deletes one ReleasePlan CR - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:171 @ 04/21/26 07:59:38.003&#xA;&lt; Exit [It] deletes one ReleasePlan CR - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:171 @ 04/21/26 07:59:38.152 (149ms)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:38.152&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:38.152 (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.042872117">
              <system-err>&gt; Enter [It] verifies that the ReleasePlanAdmission CR has only one matching ReleasePlan - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:177 @ 04/21/26 07:59:38.153&#xA;&lt; Exit [It] verifies that the ReleasePlanAdmission CR has only one matching ReleasePlan - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:177 @ 04/21/26 07:59:38.195 (42ms)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:38.195&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:38.195 (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.097124649">
              <system-err>&gt; Enter [It] deletes the ReleasePlanAdmission CR - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:198 @ 04/21/26 07:59:38.196&#xA;&lt; Exit [It] deletes the ReleasePlanAdmission CR - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:198 @ 04/21/26 07:59:38.293 (97ms)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:38.293&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:38.293 (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="18.524867048">
              <system-err>&gt; Enter [It] verifies that the ReleasePlan CR has no matched ReleasePlanAdmission - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:204 @ 04/21/26 07:59:38.293&#xA;&lt; Exit [It] verifies that the ReleasePlan CR has no matched ReleasePlanAdmission - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:204 @ 04/21/26 07:59:38.486 (193ms)&#xA;&gt; Enter [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:38.486&#xA;&lt; Exit [AfterEach] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:30 @ 04/21/26 07:59:38.486 (0s)&#xA;&gt; Enter [AfterAll] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:48 @ 04/21/26 07:59:38.487&#xA;&lt; Exit [AfterAll] [release-service-suite ReleasePlan and ReleasePlanAdmission match] - /tmp/tmp.DGYK2mBrx2/tests/release/service/release_plan_and_admission_matched.go:48 @ 04/21/26 07:59:56.818 (18.332s)&#xA;</system-err>
          </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="1.755521117">
              <system-err>&gt; Enter [BeforeAll] [release-service-suite Release service tenant pipeline] - /tmp/tmp.DGYK2mBrx2/tests/release/service/tenant_pipelines.go:41 @ 04/21/26 07:59:56.819&#xA;snapshotPush.Name: %s snapshot-sample-hxyn&#xA;&lt; Exit [BeforeAll] [release-service-suite Release service tenant pipeline] - /tmp/tmp.DGYK2mBrx2/tests/release/service/tenant_pipelines.go:41 @ 04/21/26 07:59:58.457 (1.637s)&#xA;&gt; Enter [It] verifies that a Release CR should have been created in the dev namespace - /tmp/tmp.DGYK2mBrx2/tests/release/service/tenant_pipelines.go:110 @ 04/21/26 07:59:58.457&#xA;&lt; Exit [It] verifies that a Release CR should have been created in the dev namespace - /tmp/tmp.DGYK2mBrx2/tests/release/service/tenant_pipelines.go:110 @ 04/21/26 07:59:58.574 (118ms)&#xA;&gt; Enter [AfterEach] [release-service-suite Release service tenant pipeline] - /tmp/tmp.DGYK2mBrx2/tests/release/service/tenant_pipelines.go:28 @ 04/21/26 07:59:58.575&#xA;&lt; Exit [AfterEach] [release-service-suite Release service tenant pipeline] - /tmp/tmp.DGYK2mBrx2/tests/release/service/tenant_pipelines.go:28 @ 04/21/26 07:59:58.575 (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.009809563">
              <system-err>&gt; Enter [It] verifies that Tenant PipelineRun is triggered - /tmp/tmp.DGYK2mBrx2/tests/release/service/tenant_pipelines.go:117 @ 04/21/26 07:59:58.575&#xA;PipelineRun has not been created yet for release %s/%s tenant-dev-kxog snapshot-sample-hxyn-dkwzk&#xA;PipelineRun tenant-p7wx7 reason: Running&#xA;PipelineRun tenant-p7wx7 reason: Succeeded&#xA;&lt; Exit [It] verifies that Tenant PipelineRun is triggered - /tmp/tmp.DGYK2mBrx2/tests/release/service/tenant_pipelines.go:117 @ 04/21/26 08:00:38.584 (40.01s)&#xA;&gt; Enter [AfterEach] [release-service-suite Release service tenant pipeline] - /tmp/tmp.DGYK2mBrx2/tests/release/service/tenant_pipelines.go:28 @ 04/21/26 08:00:38.585&#xA;&lt; Exit [AfterEach] [release-service-suite Release service tenant pipeline] - /tmp/tmp.DGYK2mBrx2/tests/release/service/tenant_pipelines.go:28 @ 04/21/26 08:00:38.585 (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="56.03526936">
              <system-err>&gt; Enter [It] verifies that a Release is marked as succeeded. - /tmp/tmp.DGYK2mBrx2/tests/release/service/tenant_pipelines.go:121 @ 04/21/26 08:00:38.585&#xA;&lt; Exit [It] verifies that a Release is marked as succeeded. - /tmp/tmp.DGYK2mBrx2/tests/release/service/tenant_pipelines.go:121 @ 04/21/26 08:00:38.592 (6ms)&#xA;&gt; Enter [AfterEach] [release-service-suite Release service tenant pipeline] - /tmp/tmp.DGYK2mBrx2/tests/release/service/tenant_pipelines.go:28 @ 04/21/26 08:00:38.592&#xA;&lt; Exit [AfterEach] [release-service-suite Release service tenant pipeline] - /tmp/tmp.DGYK2mBrx2/tests/release/service/tenant_pipelines.go:28 @ 04/21/26 08:00:38.592 (0s)&#xA;&gt; Enter [AfterAll] [release-service-suite Release service tenant pipeline] - /tmp/tmp.DGYK2mBrx2/tests/release/service/tenant_pipelines.go:102 @ 04/21/26 08:00:38.592&#xA;&lt; Exit [AfterAll] [release-service-suite Release service tenant pipeline] - /tmp/tmp.DGYK2mBrx2/tests/release/service/tenant_pipelines.go:102 @ 04/21/26 08:01:34.62 (56.028s)&#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="59.215543628">
              <system-err>&gt; Enter [BeforeAll] [release-service-suite Release service happy path] - /tmp/tmp.DGYK2mBrx2/tests/release/service/happy_path.go:42 @ 04/21/26 07:58:43.863&#xA;snapshotPush.Name: %s snapshot-sample-mrzc&#xA;&lt; Exit [BeforeAll] [release-service-suite Release service happy path] - /tmp/tmp.DGYK2mBrx2/tests/release/service/happy_path.go:42 @ 04/21/26 07:59:42.953 (59.09s)&#xA;&gt; Enter [It] verifies that a Release CR should have been created in the dev namespace - /tmp/tmp.DGYK2mBrx2/tests/release/service/happy_path.go:151 @ 04/21/26 07:59:42.954&#xA;&lt; Exit [It] verifies that a Release CR should have been created in the dev namespace - /tmp/tmp.DGYK2mBrx2/tests/release/service/happy_path.go:151 @ 04/21/26 07:59:43.078 (125ms)&#xA;&gt; Enter [AfterEach] [release-service-suite Release service happy path] - /tmp/tmp.DGYK2mBrx2/tests/release/service/happy_path.go:27 @ 04/21/26 07:59:43.079&#xA;&lt; Exit [AfterEach] [release-service-suite Release service happy path] - /tmp/tmp.DGYK2mBrx2/tests/release/service/happy_path.go:27 @ 04/21/26 07:59:43.079 (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="100.013938493">
              <system-err>&gt; Enter [It] verifies that Release PipelineRun is triggered - /tmp/tmp.DGYK2mBrx2/tests/release/service/happy_path.go:158 @ 04/21/26 07:59:43.079&#xA;PipelineRun has not been created yet for release %s/%s happy-path-zvxj snapshot-sample-mrzc-kv8tx&#xA;PipelineRun managed-5gmcx reason: PipelineRunPending&#xA;PipelineRun managed-5gmcx reason: Running&#xA;PipelineRun managed-5gmcx reason: Running&#xA;PipelineRun managed-5gmcx reason: Running&#xA;PipelineRun managed-5gmcx reason: Succeeded&#xA;&lt; Exit [It] verifies that Release PipelineRun is triggered - /tmp/tmp.DGYK2mBrx2/tests/release/service/happy_path.go:158 @ 04/21/26 08:01:23.093 (1m40.014s)&#xA;&gt; Enter [AfterEach] [release-service-suite Release service happy path] - /tmp/tmp.DGYK2mBrx2/tests/release/service/happy_path.go:27 @ 04/21/26 08:01:23.093&#xA;&lt; Exit [AfterEach] [release-service-suite Release service happy path] - /tmp/tmp.DGYK2mBrx2/tests/release/service/happy_path.go:27 @ 04/21/26 08:01:23.093 (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.022701535">
              <system-err>&gt; Enter [It] verifies that Enterprise Contract Task has succeeded in the Release PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/release/service/happy_path.go:162 @ 04/21/26 08:01:23.093&#xA;the status of the verify-conforma TaskRun on the release pipeline is: [{Succeeded True  {2026-04-21 08:01:21 +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.DGYK2mBrx2/tests/release/service/happy_path.go:162 @ 04/21/26 08:01:23.116 (22ms)&#xA;&gt; Enter [AfterEach] [release-service-suite Release service happy path] - /tmp/tmp.DGYK2mBrx2/tests/release/service/happy_path.go:27 @ 04/21/26 08:01:23.116&#xA;&lt; Exit [AfterEach] [release-service-suite Release service happy path] - /tmp/tmp.DGYK2mBrx2/tests/release/service/happy_path.go:27 @ 04/21/26 08:01:23.116 (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="83.096816335">
              <system-err>&gt; Enter [It] verifies that a Release is marked as succeeded. - /tmp/tmp.DGYK2mBrx2/tests/release/service/happy_path.go:174 @ 04/21/26 08:01:23.116&#xA;&lt; Exit [It] verifies that a Release is marked as succeeded. - /tmp/tmp.DGYK2mBrx2/tests/release/service/happy_path.go:174 @ 04/21/26 08:01:23.13 (13ms)&#xA;&gt; Enter [AfterEach] [release-service-suite Release service happy path] - /tmp/tmp.DGYK2mBrx2/tests/release/service/happy_path.go:27 @ 04/21/26 08:01:23.13&#xA;&lt; Exit [AfterEach] [release-service-suite Release service happy path] - /tmp/tmp.DGYK2mBrx2/tests/release/service/happy_path.go:27 @ 04/21/26 08:01:23.13 (0s)&#xA;&gt; Enter [AfterAll] [release-service-suite Release service happy path] - /tmp/tmp.DGYK2mBrx2/tests/release/service/happy_path.go:142 @ 04/21/26 08:01:23.131&#xA;&lt; Exit [AfterAll] [release-service-suite Release service happy path] - /tmp/tmp.DGYK2mBrx2/tests/release/service/happy_path.go:142 @ 04/21/26 08:02:46.213 (1m23.083s)&#xA;</system-err>
          </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.534365179">
              <system-err>&gt; Enter [BeforeAll] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/enterprise-contract/contract.go:31 @ 04/21/26 07:58:43.861&#xA;&lt; Exit [BeforeAll] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/enterprise-contract/contract.go:31 @ 04/21/26 07:58:46.279 (2.418s)&#xA;&gt; Enter [It] verifies if the chains controller is running - /tmp/tmp.DGYK2mBrx2/tests/enterprise-contract/contract.go:43 @ 04/21/26 07:58:46.279&#xA;&lt; Exit [It] verifies if the chains controller is running - /tmp/tmp.DGYK2mBrx2/tests/enterprise-contract/contract.go:43 @ 04/21/26 07:58:46.395 (115ms)&#xA;&gt; Enter [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/enterprise-contract/contract.go:29 @ 04/21/26 07:58:46.395&#xA;&lt; Exit [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/enterprise-contract/contract.go:29 @ 04/21/26 07:58:46.395 (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.023584971">
              <system-err>&gt; Enter [It] verifies the signing secret is present - /tmp/tmp.DGYK2mBrx2/tests/enterprise-contract/contract.go:48 @ 04/21/26 07:58:46.395&#xA;&lt; Exit [It] verifies the signing secret is present - /tmp/tmp.DGYK2mBrx2/tests/enterprise-contract/contract.go:48 @ 04/21/26 07:58:46.419 (23ms)&#xA;&gt; Enter [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/enterprise-contract/contract.go:29 @ 04/21/26 07:58:46.419&#xA;&lt; Exit [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/enterprise-contract/contract.go:29 @ 04/21/26 07:58:46.419 (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="failed" time="245.447704299">
              <failure message="Unexpected error:&#xA;    &lt;*errors.errorString | 0xc00098e300&gt;: &#xA;    result &#34;IMAGE_DIGEST&#34; not found in TaskRuns of PipelineRun chains-e2e-kapa/buildah-demo-ntudtkngsn&#xA;    {&#xA;        s: &#34;result \&#34;IMAGE_DIGEST\&#34; not found in TaskRuns of PipelineRun chains-e2e-kapa/buildah-demo-ntudtkngsn&#34;,&#xA;    }&#xA;occurred" type="failed">[FAILED] Unexpected error:&#xA;    &lt;*errors.errorString | 0xc00098e300&gt;: &#xA;    result &#34;IMAGE_DIGEST&#34; not found in TaskRuns of PipelineRun chains-e2e-kapa/buildah-demo-ntudtkngsn&#xA;    {&#xA;        s: &#34;result \&#34;IMAGE_DIGEST\&#34; not found in TaskRuns of PipelineRun chains-e2e-kapa/buildah-demo-ntudtkngsn&#34;,&#xA;    }&#xA;occurred&#xA;In [BeforeAll] at: /tmp/tmp.DGYK2mBrx2/tests/enterprise-contract/contract.go:104 @ 04/21/26 08:02:51.564&#xA;</failure>
              <system-err>&gt; Enter [BeforeAll] test creating and signing an image and task - /tmp/tmp.DGYK2mBrx2/tests/enterprise-contract/contract.go:73 @ 04/21/26 07:58:46.42&#xA;Creating Pipeline &#34;buildah-demo-ntudtkngsn&#34;&#xA;Waiting for pipeline &#34;buildah-demo-ntudtkngsn&#34; to finish&#xA;The pipeline named &#34;buildah-demo-ntudtkngsn&#34; in namespace &#34;chains-e2e-kapa&#34; succeeded&#xA;[FAILED] Unexpected error:&#xA;    &lt;*errors.errorString | 0xc00098e300&gt;: &#xA;    result &#34;IMAGE_DIGEST&#34; not found in TaskRuns of PipelineRun chains-e2e-kapa/buildah-demo-ntudtkngsn&#xA;    {&#xA;        s: &#34;result \&#34;IMAGE_DIGEST\&#34; not found in TaskRuns of PipelineRun chains-e2e-kapa/buildah-demo-ntudtkngsn&#34;,&#xA;    }&#xA;occurred&#xA;In [BeforeAll] at: /tmp/tmp.DGYK2mBrx2/tests/enterprise-contract/contract.go:104 @ 04/21/26 08:02:51.564&#xA;&lt; Exit [BeforeAll] test creating and signing an image and task - /tmp/tmp.DGYK2mBrx2/tests/enterprise-contract/contract.go:73 @ 04/21/26 08:02:51.564 (4m5.145s)&#xA;&gt; Enter [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/enterprise-contract/contract.go:29 @ 04/21/26 08:02:51.564&#xA;&lt; Exit [AfterEach] [enterprise-contract-suite Conforma E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/enterprise-contract/contract.go:29 @ 04/21/26 08:02:51.867 (303ms)&#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="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.DGYK2mBrx2/tests/enterprise-contract/contract.go:177 @ 04/21/26 08:02:51.868&#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="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.DGYK2mBrx2/tests/enterprise-contract/contract.go:197 @ 04/21/26 08:02:51.868&#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="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.DGYK2mBrx2/tests/enterprise-contract/contract.go:225 @ 04/21/26 08:02:51.868&#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="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.DGYK2mBrx2/tests/enterprise-contract/contract.go:251 @ 04/21/26 08:02:51.868&#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="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.DGYK2mBrx2/tests/enterprise-contract/contract.go:279 @ 04/21/26 08:02:51.868&#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="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.DGYK2mBrx2/tests/enterprise-contract/contract.go:301 @ 04/21/26 08:02:51.869&#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="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.DGYK2mBrx2/tests/enterprise-contract/contract.go:345 @ 04/21/26 08:02:51.869&#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="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.DGYK2mBrx2/tests/enterprise-contract/contract.go:382 @ 04/21/26 08:02:51.869&#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="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.DGYK2mBrx2/tests/enterprise-contract/contract.go:422 @ 04/21/26 08:02:51.869&#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] [upgrade-suite Create users and check their state] Verify AppStudioProvisionedUser [upgrade-verify]" classname="Red Hat App Studio E2E tests" status="panicked" time="7.578581623">
              <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 @ 04/21/26 07:58:51.749&#xA;&#xA;runtime error: invalid memory address or nil pointer dereference&#xA;&#xA;Full Stack Trace&#xA;  k8s.io/apimachinery/pkg/util/runtime.handleCrash({0x4996d58, 0xc0007a9500}, {0x3855fc0, 0x6ebb8e0}, {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({0x4996d58, 0xc0007a9500}, {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({0x3855fc0?, 0x6ebb8e0?})&#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.DGYK2mBrx2/pkg/sandbox/sandbox.go:319 +0x35&#xA;  github.com/konflux-ci/e2e-tests/pkg/utils.WaitUntilWithInterval.func1({0xc0007a9601?, 0xc0001a1c18?})&#xA;  &#x9;/tmp/tmp.DGYK2mBrx2/pkg/utils/util.go:129 +0x13&#xA;  k8s.io/apimachinery/pkg/util/wait.loopConditionUntilContext.func1({0x4996d58?, 0xc0007a9500?}, 0x4996d58?)&#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({0x4996d58, 0xc0007a9500}, {0x4980da8, 0xc000ba1100}, 0x1, 0x0, 0xc00145dd90)&#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({0x4996c08?, 0x6f7e800?}, 0xee6b2800, 0x41d765?, 0x1, 0xc0001a1d90)&#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?, 0xc0001a1dd8?, 0x1?)&#xA;  &#x9;/tmp/tmp.DGYK2mBrx2/pkg/utils/util.go:129 +0x45&#xA;  github.com/konflux-ci/e2e-tests/pkg/sandbox.(*SandboxController).CheckUserCreatedWithSignUp(0x40054df?, {0x40054df?, 0x4001a69?}, 0x8?)&#xA;  &#x9;/tmp/tmp.DGYK2mBrx2/pkg/sandbox/sandbox.go:318 +0x72&#xA;  github.com/konflux-ci/e2e-tests/pkg/sandbox.(*SandboxController).CheckUserCreated(0x0, {0x40054df, 0x9})&#xA;  &#x9;/tmp/tmp.DGYK2mBrx2/pkg/sandbox/sandbox.go:314 +0x4b&#xA;  github.com/konflux-ci/e2e-tests/tests/upgrade/verify.VerifyAppStudioProvisionedUser(0xf?)&#xA;  &#x9;/tmp/tmp.DGYK2mBrx2/tests/upgrade/verify/verifyUsers.go:14 +0x25&#xA;  github.com/konflux-ci/e2e-tests/tests/upgrade.init.func1.2()&#xA;  &#x9;/tmp/tmp.DGYK2mBrx2/tests/upgrade/verifyWorkload.go:21 +0x1a&#xA;</error>
              <system-err>&gt; Enter [BeforeAll] [upgrade-suite Create users and check their state] - /tmp/tmp.DGYK2mBrx2/tests/upgrade/verifyWorkload.go:16 @ 04/21/26 07:58:44.17&#xA;&lt; Exit [BeforeAll] [upgrade-suite Create users and check their state] - /tmp/tmp.DGYK2mBrx2/tests/upgrade/verifyWorkload.go:16 @ 04/21/26 07:58:51.748 (7.578s)&#xA;&gt; Enter [It] Verify AppStudioProvisionedUser - /tmp/tmp.DGYK2mBrx2/tests/upgrade/verifyWorkload.go:20 @ 04/21/26 07:58:51.748&#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 55 [running]:\nk8s.io/apimachinery/pkg/util/runtime.logPanic({0x4996cb0, 0xc00098e0f0}, {0x3855fc0, 0x6ebb8e0})\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({0x4996d58, 0xc0007a9500}, {0x3855fc0, 0x6ebb8e0}, {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({0x4996d58, 0xc0007a9500}, {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({0x3855fc0?, 0x6ebb8e0?})\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.DGYK2mBrx2/pkg/sandbox/sandbox.go:319 +0x35\ngithub.com/konflux-ci/e2e-tests/pkg/utils.WaitUntilWithInterval.func1({0xc0007a9601?, 0xc0001a1c18?})\n\t/tmp/tmp.DGYK2mBrx2/pkg/utils/util.go:129 +0x13\nk8s.io/apimachinery/pkg/util/wait.loopConditionUntilContext.func1({0x4996d58?, 0xc0007a9500?}, 0x4996d58?)\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({0x4996d58, 0xc0007a9500}, {0x4980da8, 0xc000ba1100}, 0x1, 0x0, 0xc0001a1d90)\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({0x4996c08?, 0x6f7e800?}, 0xee6b2800, 0x41d765?, 0x1, 0xc0001a1d90)\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?, 0xc0001a1dd8?, 0x1?)\n\t/tmp/tmp.DGYK2mBrx2/pkg/utils/util.go:129 +0x45\ngithub.com/konflux-ci/e2e-tests/pkg/sandbox.(*SandboxController).CheckUserCreatedWithSignUp(0x40054df?, {0x40054df?, 0x4001a69?}, 0x8?)\n\t/tmp/tmp.DGYK2mBrx2/pkg/sandbox/sandbox.go:318 +0x72\ngithub.com/konflux-ci/e2e-tests/pkg/sandbox.(*SandboxController).CheckUserCreated(0x0, {0x40054df, 0x9})\n\t/tmp/tmp.DGYK2mBrx2/pkg/sandbox/sandbox.go:314 +0x4b\ngithub.com/konflux-ci/e2e-tests/tests/upgrade/verify.VerifyAppStudioProvisionedUser(0xf?)\n\t/tmp/tmp.DGYK2mBrx2/tests/upgrade/verify/verifyUsers.go:14 +0x25\ngithub.com/konflux-ci/e2e-tests/tests/upgrade.init.func1.2()\n\t/tmp/tmp.DGYK2mBrx2/tests/upgrade/verifyWorkload.go:21 +0x1a\ngithub.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x414928?, 0xc000d8c3d8?})\n\t/opt/app-root/src/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.27.4/internal/node.go:524 +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.27.4/internal/suite.go:945 +0x393\ncreated by github.com/onsi/ginkgo/v2/internal.(*Suite).runNode in goroutine 123\n\t/opt/app-root/src/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.27.4/internal/suite.go:910 +0xd50\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 @ 04/21/26 07:58:51.749&#xA;&#xA;runtime error: invalid memory address or nil pointer dereference&#xA;&#xA;Full Stack Trace&#xA;  k8s.io/apimachinery/pkg/util/runtime.handleCrash({0x4996d58, 0xc0007a9500}, {0x3855fc0, 0x6ebb8e0}, {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({0x4996d58, 0xc0007a9500}, {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({0x3855fc0?, 0x6ebb8e0?})&#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.DGYK2mBrx2/pkg/sandbox/sandbox.go:319 +0x35&#xA;  github.com/konflux-ci/e2e-tests/pkg/utils.WaitUntilWithInterval.func1({0xc0007a9601?, 0xc0001a1c18?})&#xA;  &#x9;/tmp/tmp.DGYK2mBrx2/pkg/utils/util.go:129 +0x13&#xA;  k8s.io/apimachinery/pkg/util/wait.loopConditionUntilContext.func1({0x4996d58?, 0xc0007a9500?}, 0x4996d58?)&#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({0x4996d58, 0xc0007a9500}, {0x4980da8, 0xc000ba1100}, 0x1, 0x0, 0xc00145dd90)&#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({0x4996c08?, 0x6f7e800?}, 0xee6b2800, 0x41d765?, 0x1, 0xc0001a1d90)&#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?, 0xc0001a1dd8?, 0x1?)&#xA;  &#x9;/tmp/tmp.DGYK2mBrx2/pkg/utils/util.go:129 +0x45&#xA;  github.com/konflux-ci/e2e-tests/pkg/sandbox.(*SandboxController).CheckUserCreatedWithSignUp(0x40054df?, {0x40054df?, 0x4001a69?}, 0x8?)&#xA;  &#x9;/tmp/tmp.DGYK2mBrx2/pkg/sandbox/sandbox.go:318 +0x72&#xA;  github.com/konflux-ci/e2e-tests/pkg/sandbox.(*SandboxController).CheckUserCreated(0x0, {0x40054df, 0x9})&#xA;  &#x9;/tmp/tmp.DGYK2mBrx2/pkg/sandbox/sandbox.go:314 +0x4b&#xA;  github.com/konflux-ci/e2e-tests/tests/upgrade/verify.VerifyAppStudioProvisionedUser(0xf?)&#xA;  &#x9;/tmp/tmp.DGYK2mBrx2/tests/upgrade/verify/verifyUsers.go:14 +0x25&#xA;  github.com/konflux-ci/e2e-tests/tests/upgrade.init.func1.2()&#xA;  &#x9;/tmp/tmp.DGYK2mBrx2/tests/upgrade/verifyWorkload.go:21 +0x1a&#xA;&lt; Exit [It] Verify AppStudioProvisionedUser - /tmp/tmp.DGYK2mBrx2/tests/upgrade/verifyWorkload.go:20 @ 04/21/26 07:58:51.749 (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.DGYK2mBrx2/tests/upgrade/verifyWorkload.go:24 @ 04/21/26 07:58:51.749&#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.DGYK2mBrx2/tests/upgrade/verifyWorkload.go:28 @ 04/21/26 07:58:51.75&#xA;</system-err>
          </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="55.368786288">
              <system-err>&gt; Enter [BeforeAll] test build secret lookup - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:32 @ 04/21/26 07:58:51.75&#xA;&lt; Exit [BeforeAll] test build secret lookup - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:32 @ 04/21/26 07:59:25.365 (33.615s)&#xA;&gt; Enter [BeforeAll] when two secrets are created - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:100 @ 04/21/26 07:59:25.365&#xA;&lt; Exit [BeforeAll] when two secrets are created - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:100 @ 04/21/26 07:59:34.885 (9.52s)&#xA;&gt; Enter [It] creates first component - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:123 @ 04/21/26 07:59:34.885&#xA;Image repository for component component-one-hojl in namespace build-e2e-ljjs do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [It] creates first component - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:123 @ 04/21/26 07:59:47.119 (12.234s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:25 @ 04/21/26 07:59:47.119&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:25 @ 04/21/26 07:59:47.119 (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="20.032500714">
              <system-err>&gt; Enter [It] creates second component - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:140 @ 04/21/26 07:59:47.119&#xA;Image repository for component component-two-akad in namespace build-e2e-ljjs 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-akad in namespace build-e2e-ljjs 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.DGYK2mBrx2/tests/build/secret_lookup.go:140 @ 04/21/26 08:00:07.151 (20.032s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:25 @ 04/21/26 08:00:07.152&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:25 @ 04/21/26 08:00:07.152 (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="35.089068339">
              <system-err>&gt; Enter [It] check first component annotation has errors - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:158 @ 04/21/26 08:00:07.152&#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;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.DGYK2mBrx2/tests/build/secret_lookup.go:158 @ 04/21/26 08:00:42.241 (35.089s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:25 @ 04/21/26 08:00:42.241&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:25 @ 04/21/26 08:00:42.241 (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.038064392">
              <system-err>&gt; Enter [It] triggered PipelineRun is for component  - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:178 @ 04/21/26 08:00:42.242&#xA;PipelineRun has not been created yet for the component build-e2e-ljjs/component-two-akad&#xA;PipelineRun has not been created yet for the component build-e2e-ljjs/component-two-akad&#xA;&lt; Exit [It] triggered PipelineRun is for component  - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:178 @ 04/21/26 08:01:22.279 (40.038s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:25 @ 04/21/26 08:01:22.28&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:25 @ 04/21/26 08:01:22.28 (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="157.256648851">
              <system-err>&gt; Enter [It] check only one pipelinerun should be triggered - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:193 @ 04/21/26 08:01:22.28&#xA;&lt; Exit [It] check only one pipelinerun should be triggered - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:193 @ 04/21/26 08:03:22.281 (2m0s)&#xA;&gt; Enter [AfterAll] test build secret lookup - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:61 @ 04/21/26 08:03:22.281&#xA;&lt; Exit [AfterAll] test build secret lookup - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:61 @ 04/21/26 08:03:59.536 (37.255s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:25 @ 04/21/26 08:03:59.537&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/secret_lookup.go:25 @ 04/21/26 08:03:59.537 (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] [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] [konflux-demo-suite] Maven project - Default build creates an application [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="passed" time="53.746137301">
              <system-err>&gt; Enter [BeforeAll] Maven project - Default build - /tmp/tmp.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:84 @ 04/21/26 07:58:44.068&#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-kqbwmanagedNamespacekonflux-kqbw-managed&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo BeforeAll: component configcomponentNamekonflux-demo-component-pocupacBranchNamekonflux-konflux-demo-component-pocucomponentRepositoryNamehacbs-test-project-konflux-demo&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo BeforeAll: creating release configmanagedNamespacekonflux-kqbw-manageduserNamespacekonflux-kqbw&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo createReleaseConfig: creating managed namespacemanagedNamespacekonflux-kqbw-managed&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo createReleaseConfig: creating release-service-accountmanagedNamespacekonflux-kqbw-managed&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo createReleaseConfig: finishedmanagedNamespacekonflux-kqbw-manageduserNamespacekonflux-kqbw&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo BeforeAll: created and linked release-catalog-trusted-artifacts-quay-secretmanagedNamespacekonflux-kqbw-managed&#34;&#xA;created and linked release-catalog-trusted-artifacts-quay-secret in namespace &#34;konflux-kqbw-managed&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo BeforeAll: setup completeappMaven project - Default buildcomponentNamekonflux-demo-component-pocu&#34;&#xA;&lt; Exit [BeforeAll] Maven project - Default build - /tmp/tmp.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:84 @ 04/21/26 07:59:37.398 (53.33s)&#xA;&gt; Enter [It] creates an application - /tmp/tmp.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:189 @ 04/21/26 07:59:37.398&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: creating applicationapplicationNamekonflux-demo-appnamespacekonflux-kqbw&#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.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:189 @ 04/21/26 07:59:37.814 (416ms)&#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.208955181">
              <system-err>&gt; Enter [It] creates an IntegrationTestScenario for the app - /tmp/tmp.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:202 @ 04/21/26 07:59:37.815&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: creating IntegrationTestScenarioapplicationNamekonflux-demo-appnamespacekonflux-kqbw&#34;&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: IntegrationTestScenario createdscenariomy-integration-test-mnwf&#34;&#xA;&lt; Exit [It] creates an IntegrationTestScenario for the app - /tmp/tmp.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:202 @ 04/21/26 07:59:38.024 (209ms)&#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.663946835">
              <system-err>&gt; Enter [It] creates new branch for the build - /tmp/tmp.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:218 @ 04/21/26 07:59:38.025&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: creating branch for buildrepohacbs-test-project-konflux-demobranchbase-kfwpgrfrommain&#34;&#xA;&lt; Exit [It] creates new branch for the build - /tmp/tmp.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:218 @ 04/21/26 07:59:38.688 (664ms)&#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="20.162319852">
              <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.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:233 @ 04/21/26 07:59:38.689&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: creating componentcomponentNamekonflux-demo-component-pocuapplicationNamekonflux-demo-appnamespacekonflux-kqbwrevisionbase-kfwpgr&#34;&#xA;Image repository for component konflux-demo-component-pocu in namespace konflux-kqbw 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-pocu&#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.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:233 @ 04/21/26 07:59:58.851 (20.162s)&#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="failed" time="350.720667371">
              <failure message="Timed out after 300.000s.&#xA;timed out when waiting for `pull-request` event type PaC PipelineRun to be present in the user namespace &#34;konflux-kqbw&#34; for component &#34;konflux-demo-component-pocu&#34; with a label pointing to &#34;konflux-demo-app&#34;&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc0006b88b0&gt;: &#xA;    no pipelinerun found for component konflux-demo-component-pocu&#xA;    {&#xA;        s: &#34;no pipelinerun found for component konflux-demo-component-pocu&#34;,&#xA;    }" type="failed">[FAILED] Timed out after 300.000s.&#xA;timed out when waiting for `pull-request` event type PaC PipelineRun to be present in the user namespace &#34;konflux-kqbw&#34; for component &#34;konflux-demo-component-pocu&#34; with a label pointing to &#34;konflux-demo-app&#34;&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc0006b88b0&gt;: &#xA;    no pipelinerun found for component konflux-demo-component-pocu&#xA;    {&#xA;        s: &#34;no pipelinerun found for component konflux-demo-component-pocu&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:294 @ 04/21/26 08:05:49.572&#xA;</failure>
              <system-err>&gt; Enter [It] triggers creation of a PR in the sample repo - /tmp/tmp.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:259 @ 04/21/26 07:59:58.852&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: waiting for PaC PRrepohacbs-test-project-konflux-demopacBranchNamekonflux-konflux-demo-component-pocu&#34;&#xA;&#34;msg&#34;=&#34;Konflux demo: could not get the expected PaC branch name konflux-konflux-demo-component-pocu (found 29 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-pocu (found 29 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-pocu (found 29 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-pocu (found 29 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-pocu (found 29 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-pocu (found 29 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-pocu (found 29 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-pocu (found 29 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-pocu (found 29 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-pocu (found 29 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-pocu (found 29 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-pocu (found 29 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-pocu (found 29 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-pocu (found 29 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-pocu (found 29 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-pocu (found 29 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-pocu (found 29 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-pocu (found 29 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-pocu (found 29 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-pocu (found 29 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-pocu (found 29 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-pocu (found 29 PRs)&#34; &#34;error&#34;=null&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;Konflux demo: PaC PR createdprNumber29114prSHA489ef624b8776207c937b7711e79e6a79c693c0a&#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-pocuprSHA489ef624b8776207c937b7711e79e6a79c693c0a&#34;&#xA;PipelineRun not found yet for component konflux-kqbw/konflux-demo-component-pocu prSHA 489ef624b8776207c937b7711e79e6a79c693c0a: no pipelinerun found for component konflux-demo-component-pocu&#xA;PipelineRun not found yet for component konflux-kqbw/konflux-demo-component-pocu prSHA 489ef624b8776207c937b7711e79e6a79c693c0a: no pipelinerun found for component konflux-demo-component-pocu&#xA;PipelineRun not found yet for component konflux-kqbw/konflux-demo-component-pocu prSHA 489ef624b8776207c937b7711e79e6a79c693c0a: no pipelinerun found for component konflux-demo-component-pocu&#xA;PipelineRun not found yet for component konflux-kqbw/konflux-demo-component-pocu prSHA 489ef624b8776207c937b7711e79e6a79c693c0a: no pipelinerun found for component konflux-demo-component-pocu&#xA;PipelineRun not found yet for component konflux-kqbw/konflux-demo-component-pocu prSHA 489ef624b8776207c937b7711e79e6a79c693c0a: no pipelinerun found for component konflux-demo-component-pocu&#xA;PipelineRun not found yet for component konflux-kqbw/konflux-demo-component-pocu prSHA 489ef624b8776207c937b7711e79e6a79c693c0a: no pipelinerun found for component konflux-demo-component-pocu&#xA;PipelineRun not found yet for component konflux-kqbw/konflux-demo-component-pocu prSHA 489ef624b8776207c937b7711e79e6a79c693c0a: no pipelinerun found for component konflux-demo-component-pocu&#xA;PipelineRun not found yet for component konflux-kqbw/konflux-demo-component-pocu prSHA 489ef624b8776207c937b7711e79e6a79c693c0a: no pipelinerun found for component konflux-demo-component-pocu&#xA;PipelineRun not found yet for component konflux-kqbw/konflux-demo-component-pocu prSHA 489ef624b8776207c937b7711e79e6a79c693c0a: no pipelinerun found for component konflux-demo-component-pocu&#xA;PipelineRun not found yet for component konflux-kqbw/konflux-demo-component-pocu prSHA 489ef624b8776207c937b7711e79e6a79c693c0a: no pipelinerun found for component konflux-demo-component-pocu&#xA;PipelineRun not found yet for component konflux-kqbw/konflux-demo-component-pocu prSHA 489ef624b8776207c937b7711e79e6a79c693c0a: no pipelinerun found for component konflux-demo-component-pocu&#xA;PipelineRun not found yet for component konflux-kqbw/konflux-demo-component-pocu prSHA 489ef624b8776207c937b7711e79e6a79c693c0a: no pipelinerun found for component konflux-demo-component-pocu&#xA;PipelineRun not found yet for component konflux-kqbw/konflux-demo-component-pocu prSHA 489ef624b8776207c937b7711e79e6a79c693c0a: no pipelinerun found for component konflux-demo-component-pocu&#xA;PipelineRun not found yet for component konflux-kqbw/konflux-demo-component-pocu prSHA 489ef624b8776207c937b7711e79e6a79c693c0a: no pipelinerun found for component konflux-demo-component-pocu&#xA;PipelineRun not found yet for component konflux-kqbw/konflux-demo-component-pocu prSHA 489ef624b8776207c937b7711e79e6a79c693c0a: no pipelinerun found for component konflux-demo-component-pocu&#xA;[FAILED] Timed out after 300.000s.&#xA;timed out when waiting for `pull-request` event type PaC PipelineRun to be present in the user namespace &#34;konflux-kqbw&#34; for component &#34;konflux-demo-component-pocu&#34; with a label pointing to &#34;konflux-demo-app&#34;&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc0006b88b0&gt;: &#xA;    no pipelinerun found for component konflux-demo-component-pocu&#xA;    {&#xA;        s: &#34;no pipelinerun found for component konflux-demo-component-pocu&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:294 @ 04/21/26 08:05:49.572&#xA;&lt; Exit [It] triggers creation of a PR in the sample repo - /tmp/tmp.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:259 @ 04/21/26 08:05:49.572 (5m50.72s)&#xA;&gt; Enter [AfterAll] Maven project - Default build - /tmp/tmp.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:154 @ 04/21/26 08:05:49.572&#xA;&lt; Exit [AfterAll] Maven project - Default build - /tmp/tmp.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:154 @ 04/21/26 08:05:49.573 (0s)&#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="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.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:297 @ 04/21/26 08:05:49.573&#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="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.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:335 @ 04/21/26 08:05:49.573&#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="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.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:369 @ 04/21/26 08:05:49.574&#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="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.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:373 @ 04/21/26 08:05:49.574&#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="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.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:389 @ 04/21/26 08:05:49.574&#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="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.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:403 @ 04/21/26 08:05:49.574&#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="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.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:419 @ 04/21/26 08:05:49.574&#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="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.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:432 @ 04/21/26 08:05:49.575&#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="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.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:441 @ 04/21/26 08:05:49.575&#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="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.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:462 @ 04/21/26 08:05:49.575&#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="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.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:493 @ 04/21/26 08:05:49.575&#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="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.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:505 @ 04/21/26 08:05:49.575&#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="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.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:518 @ 04/21/26 08:05:49.576&#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="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.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:533 @ 04/21/26 08:05:49.576&#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="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.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:552 @ 04/21/26 08:05:49.576&#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="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.DGYK2mBrx2/tests/konflux-demo/konflux-demo.go:578 @ 04/21/26 08:05:49.576&#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 triggers a Build PipelineRun [integration-service, gitlab-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="71.122961045">
              <system-err>&gt; Enter [BeforeAll] Gitlab with status reporting of Integration tests in the assosiated merge request - /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:45 @ 04/21/26 07:58:44.164&#xA;&lt; Exit [BeforeAll] Gitlab with status reporting of Integration tests in the assosiated merge request - /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:45 @ 04/21/26 07:58:51.455 (7.292s)&#xA;&gt; Enter [BeforeAll] when a new Component with specified custom branch is created - /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:109 @ 04/21/26 07:58:51.456&#xA;&lt; Exit [BeforeAll] when a new Component with specified custom branch is created - /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:109 @ 04/21/26 07:59:03.659 (12.204s)&#xA;&gt; Enter [It] triggers a Build PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:130 @ 04/21/26 07:59:03.66&#xA;Build PipelineRun has not been created yet for the component gitlab-rep-flag/test-comp-pac-gitlab-nqglox&#xA;&lt; Exit [It] triggers a Build PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:130 @ 04/21/26 07:59:55.286 (51.627s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 07:59:55.286&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 07:59:55.287 (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.000558885">
              <system-err>&gt; Enter [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:144 @ 04/21/26 07:59:55.288&#xA;&lt; Exit [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:144 @ 04/21/26 07:59:55.288 (0s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 07:59:55.288&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 07:59:55.288 (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="failed" time="703.580296547">
              <failure message="Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc000893790&gt;: &#xA;    &#xA;     pod: test-comp-pac-gitlab-nqglox-on-pull-request-gkvds-init-pod | init container: prepare&#xA;    2026/04/21 08:07:20 Entrypoint initialization&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox-on-pull-request-gkvds-init-pod | container step-init: &#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai&#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;    &#xA;     pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | init container: prepare&#xA;    2026/04/21 08:10:01 Entrypoint initialization&#xA;    &#xA;     pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | init container: place-scripts&#xA;    2026/04/21 08:10:02 Decoded script /tekton/scripts/script-0-g5m28&#xA;    2026/04/21 08:10:02 Decoded script /tekton/scripts/script-1-qv5ww&#xA;    2026/04/21 08:10:02 Decoded script /tekton/scripts/script-2-t2hmp&#xA;    2026/04/21 08:10:02 Decoded script /tekton/scripts/script-3-9hrxc&#xA;    2026/04/21 08:10:02 Decoded script /tekton/scripts/script-4-26ww8&#xA;    2026/04/21 08:10:02 Decoded script /tekton/scripts/script-5-8rjgc&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-introspect: &#xA;    Artifact type will be determined by introspection.&#xA;    Checking the media type of the OCI artifact...&#xA;    [retry] executing: skopeo inspect --raw --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#xA;    The media type of the OCI artifact is application/vnd.docker.distribution.manifest.v2+json.&#xA;    Looking for image labels that indicate this might be an operator bundle...&#xA;    [retry] executing: skopeo inspect --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#xA;    Found 0 matching labels.&#xA;    Expecting 3 or more to identify this image as an operator bundle.&#xA;    Introspection concludes that this artifact is of type &#34;application&#34;.&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-generate-container-auth: &#xA;    Selecting auth for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#xA;    Using token for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox&#xA;    Auth json written to &#34;/auth/auth.json&#34;.&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-set-skip-for-bundles: &#xA;    2026/04/21 08:10:47 INFO Step was skipped due to when expressions were evaluated to false.&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-app-check: &#xA;    time=&#34;2026-04-21T08:10:48Z&#34; level=info msg=&#34;certification library version&#34; version=&#34;1.17.1 &lt;commit: f7de82ae1c76e6c10ea94967d6b6a66f96248cbe&gt;&#34;&#xA;    time=&#34;2026-04-21T08:10:48Z&#34; level=info msg=&#34;running checks for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734 for platform amd64&#34;&#xA;    time=&#34;2026-04-21T08:10:48Z&#34; level=info msg=&#34;target image&#34; image=&#34;quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#34;&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;warning: licenses directory does not exist or all of its children are empty directories: error when checking for /licenses: stat /tmp/preflight-2625782039/fs/licenses: no such file or directory&#34; check=HasLicense&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=HasLicense result=FAILED&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=HasUniqueTag result=PASSED&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=LayerCountAcceptable result=PASSED&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=HasNoProhibitedPackages result=PASSED&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=HasRequiredLabel result=PASSED&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;USER 185 specified that is non-root&#34; check=RunAsNonRoot&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=RunAsNonRoot result=PASSED&#xA;    time=&#34;2026-04-21T08:11:05Z&#34; level=info msg=&#34;check completed&#34; check=HasModifiedFiles result=PASSED&#xA;    time=&#34;2026-04-21T08:11:12Z&#34; level=info msg=&#34;check completed&#34; check=BasedOnUbi result=PASSED&#xA;    time=&#34;2026-04-21T08:11:12Z&#34; level=info msg=&#34;This image&#39;s tag on-pr-cdc64b74622eaacc7ce5f90359269456f113f734 will be paired with digest sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760 once this image has been published in accordance with Red Hat Certification policy. You may then add or remove any supplemental tags through your Red Hat Connect portal as you see fit.&#34;&#xA;    {&#xA;        &#34;image&#34;: &#34;quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#34;,&#xA;        &#34;passed&#34;: false,&#xA;        &#34;test_library&#34;: {&#xA;            &#34;name&#34;: &#34;github.com/redhat-openshift-ecosystem/openshift-preflight&#34;,&#xA;            &#34;version&#34;: &#34;1.17.1&#34;,&#xA;            &#34;commit&#34;: &#34;f7de82ae1c76e6c10ea94967d6b6a66f96248cbe&#34;&#xA;        },&#xA;        &#34;results&#34;: {&#xA;            &#34;passed&#34;: [&#xA;                {&#xA;                    &#34;name&#34;: &#34;HasUniqueTag&#34;,&#xA;                    &#34;elapsed_time&#34;: 0,&#xA;                    &#34;description&#34;: &#34;Checking if container has a tag other than &#39;latest&#39;, so that the image can be uniquely identified.&#34;&#xA;                },&#xA;                {&#xA;                    &#34;name&#34;: &#34;LayerCountAcceptable&#34;,&#xA;                    &#34;elapsed_time&#34;: 0,&#xA;                    &#34;description&#34;: &#34;Checking if container has less than 40 layers.  Too many layers within the container images can degrade container performance.&#34;&#xA;                },&#xA;                {&#xA;                    &#34;name&#34;: &#34;HasNoProhibitedPackages&#34;,&#xA;                    &#34;elapsed_time&#34;: 38,&#xA;                    &#34;description&#34;: &#34;Checks to ensure that the image in use does not include prohibited packages, such as Red Hat Enterprise Linux (RHEL) kernel packages.&#34;&#xA;                },&#xA;                {&#xA;                    &#34;name&#34;: &#34;HasRequiredLabel&#34;,&#xA;                    &#34;elapsed_time&#34;: 0,&#xA;                    &#34;description&#34;: &#34;Checking if the required labels (name, vendor, version, release, summary, description, maintainer) are present in the container metadata&#34;&#xA;                },&#xA;                {&#xA;                    &#34;name&#34;: &#34;RunAsNonRoot&#34;,&#xA;                    &#34;elapsed_time&#34;: 0,&#xA;                    &#34;description&#34;: &#34;Checking if container runs as the root user because a container that does not specify a non-root user will fail the automatic certification, and will be subject to a manual review before the container can be approved for publication&#34;&#xA;                },&#xA;                {&#xA;                    &#34;name&#34;: &#34;HasModifiedFiles&#34;,&#xA;                    &#34;elapsed_time&#34;: 8668,&#xA;                    &#34;description&#34;: &#34;Checks that no files installed via RPM in the base Red Hat layer have been modified&#34;&#xA;                },&#xA;                {&#xA;                    &#34;name&#34;: &#34;BasedOnUbi&#34;,&#xA;                    &#34;elapsed_time&#34;: 7354,&#xA;                    &#34;description&#34;: &#34;Checking if the container&#39;s base image is based upon the Red Hat Universal Base Image (UBI)&#34;&#xA;                }&#xA;            ],&#xA;            &#34;failed&#34;: [&#xA;                {&#xA;                    &#34;name&#34;: &#34;HasLicense&#34;,&#xA;                    &#34;elapsed_time&#34;: 15,&#xA;                    &#34;description&#34;: &#34;Checking if terms and conditions applicable to the software including open source licensing information are present. The license must be at /licenses&#34;,&#xA;                    &#34;help&#34;: &#34;Check HasLicense encountered an error. Please review the preflight.log file for more information.&#34;,&#xA;                    &#34;suggestion&#34;: &#34;Create a directory named /licenses and include all relevant licensing and/or terms and conditions as text file(s) in that directory.&#34;,&#xA;                    &#34;knowledgebase_url&#34;: &#34;https://access.redhat.com/documentation/en-us/red_hat_software_certification/2024/html-single/red_hat_openshift_software_certification_policy_guide/index#assembly-requirements-for-container-images_openshift-sw-cert-policy-introduction&#34;,&#xA;                    &#34;check_url&#34;: &#34;https://access.redhat.com/documentation/en-us/red_hat_software_certification/2024/html-single/red_hat_openshift_software_certification_policy_guide/index#assembly-requirements-for-container-images_openshift-sw-cert-policy-introduction&#34;&#xA;                }&#xA;            ],&#xA;            &#34;errors&#34;: []&#xA;        }&#xA;    }&#xA;    time=&#34;2026-04-21T08:11:12Z&#34; level=info msg=&#34;Preflight result: FAILED&#34;&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-app-set-outcome: &#xA;    {&#34;result&#34;:&#34;FAILURE&#34;,&#34;timestamp&#34;:&#34;1776759072&#34;,&#34;note&#34;:&#34;Task preflight is a FAILURE: Refer to Tekton task logs for more information&#34;,&#34;successes&#34;:7,&#34;failures&#34;:1,&#34;warnings&#34;:0}[retry] executing: skopeo inspect --raw --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-final-outcome: &#xA;    + [[ ! -f /mount/konflux.results.json ]]&#xA;    + tee /tekton/steps/step-final-outcome/results/test-output&#xA;    {&#34;result&#34;:&#34;FAILURE&#34;,&#34;timestamp&#34;:&#34;1776759072&#34;,&#34;note&#34;:&#34;Task preflight is a FAILURE: Refer to Tekton task logs for more information&#34;,&#34;successes&#34;:7,&#34;failures&#34;:1,&#34;warnings&#34;:0}&#xA;     pod: test-comp-pac-gitlab-nqglox52a819651f560efef8a7fd4a3d045bb7-pod | init container: prepare&#xA;    2026/04/21 08:10:01 Entrypoint initialization&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox52a819651f560efef8a7fd4a3d045bb7-pod | container step-apply-additional-tags: &#xA;    time=&#34;2026-04-21T08:10:05Z&#34; level=info msg=&#34;[param] image-url: quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#34;&#xA;    time=&#34;2026-04-21T08:10:05Z&#34; level=info msg=&#34;[param] digest: sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760&#34;&#xA;    time=&#34;2026-04-21T08:10:05Z&#34; level=info msg=&#34;[param] tags-from-image-label: konflux.additional-tags&#34;&#xA;    time=&#34;2026-04-21T08:10:06Z&#34; level=warning msg=&#34;No tags given in &#39;konflux.additional-tags&#39; image label&#34;&#xA;    {&#34;tags&#34;:[]}&#xA;     pod: test-comp-pac-gitlab-nqglox53d62eb88415018600aa4813dd11fb26-pod | init container: prepare&#xA;    2026/04/21 08:10:02 Entrypoint initialization&#xA;    &#xA;     pod: test-comp-pac-gitlab-nqglox53d62eb88415018600aa4813dd11fb26-pod | init container: place-scripts&#xA;    2026/04/21 08:10:14 Decoded script /tekton/scripts/script-0-bzbgv&#xA;    2026/04/21 08:10:14 Decoded script /tekton/scripts/script-1-hxgf9&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox53d62eb88415018600aa4813dd11fb26-pod | container step-extract-and-scan-image: &#xA;    Starting clamd ...&#xA;    clamd is ready!&#xA;    Detecting artifact type for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox@sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760.&#xA;    Detected container image. Processing image manifests.&#xA;    Running &#34;oc image extract&#34; on image of arch amd64&#xA;    Scanning image for arch amd64. This operation may take a while.&#xA;    &#xA;    ----------- SCAN SUMMARY -----------&#xA;    Infected files: 0&#xA;    Time: 42.251 sec (0 m 42 s)&#xA;    Start Date: 2026:04:21 08:10:30&#xA;    End Date:   2026:04:21 08:11:13&#xA;    Executed-on: Scan was executed on clamsdcan version - ClamAV 1.4.3/27977/Mon Apr 20 06:26:26 2026 Database version: 27977&#xA;    [&#xA;    &#x9;{&#xA;    &#x9;&#x9;&#34;filename&#34;: &#34;/work/logs/clamscan-result-log-amd64.json&#34;,&#xA;    &#x9;&#x9;&#34;namespace&#34;: &#34;required_checks&#34;,&#xA;    &#x9;&#x9;&#34;successes&#34;: 2&#xA;    &#x9;}&#xA;    ]&#xA;    {&#34;timestamp&#34;:&#34;1776759073&#34;,&#34;namespace&#34;:&#34;required_checks&#34;,&#34;successes&#34;:2,&#34;failures&#34;:0,&#34;warnings&#34;:0,&#34;result&#34;:&#34;SUCCESS&#34;,&#34;note&#34;:&#34;All checks passed successfully&#34;}&#xA;    {&#34;timestamp&#34;:&#34;1776759073&#34;,&#34;namespace&#34;:&#34;required_checks&#34;,&#34;successes&#34;:2,&#34;failures&#34;:0,&#34;warnings&#34;:0,&#34;result&#34;:&#34;SUCCESS&#34;,&#34;note&#34;:&#34;All checks passed successfully&#34;}&#xA;    {&#34;timestamp&#34;:&#34;1776759073&#34;,&#34;namespace&#34;:&#34;required_checks&#34;,&#34;successes&#34;:2,&#34;failures&#34;:0,&#34;warnings&#34;:0,&#34;result&#34;:&#34;SUCCESS&#34;,&#34;note&#34;:&#34;All checks passed successfully&#34;}&#xA;    {&#34;image&#34;: {&#34;pullspec&#34;: &#34;quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#34;, &#34;digests&#34;: [&#34;sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760&#34;]}}&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox53d62eb88415018600aa4813dd11fb26-pod | container step-upload: &#xA;    Selecting auth&#xA;    Using token for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox&#xA;    Attaching to quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#xA;    Executing: oras attach --no-tty --registry-config /home/oras/auth.json --artifact-type application/vnd.clamav quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734@sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760 clamscan-result-amd64.log:text/vnd.clamav clamscan-ec-test-amd64.json:application/vnd.konflux.test_output+json&#xA;    Preparing clamscan-result-amd64.log&#xA;    Preparing clamscan-ec-test-amd64.json&#xA;    Exists    44136fa355b3 application/vnd.oci.empty.v1+json&#xA;    Uploading 6115c63e1844 clamscan-ec-test-amd64.json&#xA;    Uploading 669c731460fe clamscan-result-amd64.log&#xA;    Uploaded  6115c63e1844 clamscan-ec-test-amd64.json&#xA;    Uploaded  669c731460fe clamscan-result-amd64.log&#xA;    Uploading d84231f3b87c application/vnd.oci.image.manifest.v1+json&#xA;    Uploaded  d84231f3b87c application/vnd.oci.image.manifest.v1+json&#xA;    Attached to [registry] quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734@sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760&#xA;    Digest: sha256:d84231f3b87cad02abe05dd9d8ed577f5ed7cf8c240960a80a9557e857c50c8f&#xA;    &#xA;    {&#xA;        s: &#34;\n pod: test-comp-pac-gitlab-nqglox-on-pull-request-gkvds-init-pod | init container: prepare\n2026/04/21 08:07:20 Entrypoint initialization\n\npod: test-comp-pac-gitlab-nqglox-on-pull-request-gkvds-init-pod | container step-init: \ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;Using in-cluster config\&#34; logger=KubeClient\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;[param] enable: false\&#34;\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128\&#34;\ntime=\&#34;2026-04-21T08:07:22Z\&#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;\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;[param] http-proxy-result-path: /tekton/results/http-proxy\&#34;\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;[param] no-proxy-result-path: /tekton/results/no-proxy\&#34;\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;Cache proxy is disabled in param or in backend\&#34;\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;[result] HTTP PROXY: \&#34;\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;[result] NO PROXY: \&#34;\n\n pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | init container: prepare\n2026/04/21 08:10:01 Entrypoint initialization\n\n pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | init container: place-scripts\n2026/04/21 08:10:02 Decoded script /tekton/scripts/script-0-g5m28\n2026/04/21 08:10:02 Decoded script /tekton/scripts/script-1-qv5ww\n2026/04/21 08:10:02 Decoded script /tekton/scripts/script-2-t2hmp\n2026/04/21 08:10:02 Decoded script /tekton/scripts/script-3-9hrxc\n2026/04/21 08:10:02 Decoded script /tekton/scripts/script-4-26ww8\n2026/04/21 08:10:02 Decoded script /tekton/scripts/script-5-8rjgc\n\npod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-introspect: \nArtifact type will be determined by introspection.\nChecking the media type of the OCI artifact...\n[retry] executing: skopeo inspect --raw --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734\nThe media type of the OCI artifact is application/vnd.docker.distribution.manifest.v2+json.\nLooking for image labels that indicate this might be an operator bundle...\n[retry] executing: skopeo inspect --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734\nFound 0 matching labels.\nExpecting 3 or more to identify this image as an operator bundle.\nIntrospection concludes that this artifact is of type \&#34;application\&#34;.\n\npod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-generate-container-auth: \nSelecting auth for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734\nUsing token for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox\nAuth json written to \&#34;/auth/auth.json\&#34;.\n\npod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-set-skip-for-bundles: \n2026/04/21 08:10:47 INFO Step was skipped due to when expressions were evaluated to false.\n\npod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-app-check: \ntime=\&#34;2026-04-21T08:10:48Z\&#34; level=info msg=\&#34;certification library version\&#34; version=\&#34;1.17.1 &lt;commit: f7de82ae1c76e6c10ea94967d6b6a66f96248cbe&gt;\&#34;\ntime=\&#34;2026-04-21T08:10:48Z\&#34; level=info msg=\&#34;running checks for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734 for platform amd64\&#34;\ntime=\&#34;2026-04-21T08:10:48Z\&#34; level=info msg=\&#34;target image\&#34; ima...&#xA;&#xA;Gomega truncated this representation as it exceeds &#39;format.MaxLength&#39;.&#xA;Consider having the object provide a custom &#39;GomegaStringer&#39; representation&#xA;or adjust the parameters in Gomega&#39;s &#39;format&#39; package.&#xA;&#xA;Learn more here: https://onsi.github.io/gomega/#adjusting-output&#xA;" type="failed">[FAILED] Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc000893790&gt;: &#xA;    &#xA;     pod: test-comp-pac-gitlab-nqglox-on-pull-request-gkvds-init-pod | init container: prepare&#xA;    2026/04/21 08:07:20 Entrypoint initialization&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox-on-pull-request-gkvds-init-pod | container step-init: &#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai&#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;    &#xA;     pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | init container: prepare&#xA;    2026/04/21 08:10:01 Entrypoint initialization&#xA;    &#xA;     pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | init container: place-scripts&#xA;    2026/04/21 08:10:02 Decoded script /tekton/scripts/script-0-g5m28&#xA;    2026/04/21 08:10:02 Decoded script /tekton/scripts/script-1-qv5ww&#xA;    2026/04/21 08:10:02 Decoded script /tekton/scripts/script-2-t2hmp&#xA;    2026/04/21 08:10:02 Decoded script /tekton/scripts/script-3-9hrxc&#xA;    2026/04/21 08:10:02 Decoded script /tekton/scripts/script-4-26ww8&#xA;    2026/04/21 08:10:02 Decoded script /tekton/scripts/script-5-8rjgc&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-introspect: &#xA;    Artifact type will be determined by introspection.&#xA;    Checking the media type of the OCI artifact...&#xA;    [retry] executing: skopeo inspect --raw --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#xA;    The media type of the OCI artifact is application/vnd.docker.distribution.manifest.v2+json.&#xA;    Looking for image labels that indicate this might be an operator bundle...&#xA;    [retry] executing: skopeo inspect --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#xA;    Found 0 matching labels.&#xA;    Expecting 3 or more to identify this image as an operator bundle.&#xA;    Introspection concludes that this artifact is of type &#34;application&#34;.&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-generate-container-auth: &#xA;    Selecting auth for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#xA;    Using token for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox&#xA;    Auth json written to &#34;/auth/auth.json&#34;.&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-set-skip-for-bundles: &#xA;    2026/04/21 08:10:47 INFO Step was skipped due to when expressions were evaluated to false.&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-app-check: &#xA;    time=&#34;2026-04-21T08:10:48Z&#34; level=info msg=&#34;certification library version&#34; version=&#34;1.17.1 &lt;commit: f7de82ae1c76e6c10ea94967d6b6a66f96248cbe&gt;&#34;&#xA;    time=&#34;2026-04-21T08:10:48Z&#34; level=info msg=&#34;running checks for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734 for platform amd64&#34;&#xA;    time=&#34;2026-04-21T08:10:48Z&#34; level=info msg=&#34;target image&#34; image=&#34;quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#34;&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;warning: licenses directory does not exist or all of its children are empty directories: error when checking for /licenses: stat /tmp/preflight-2625782039/fs/licenses: no such file or directory&#34; check=HasLicense&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=HasLicense result=FAILED&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=HasUniqueTag result=PASSED&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=LayerCountAcceptable result=PASSED&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=HasNoProhibitedPackages result=PASSED&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=HasRequiredLabel result=PASSED&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;USER 185 specified that is non-root&#34; check=RunAsNonRoot&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=RunAsNonRoot result=PASSED&#xA;    time=&#34;2026-04-21T08:11:05Z&#34; level=info msg=&#34;check completed&#34; check=HasModifiedFiles result=PASSED&#xA;    time=&#34;2026-04-21T08:11:12Z&#34; level=info msg=&#34;check completed&#34; check=BasedOnUbi result=PASSED&#xA;    time=&#34;2026-04-21T08:11:12Z&#34; level=info msg=&#34;This image&#39;s tag on-pr-cdc64b74622eaacc7ce5f90359269456f113f734 will be paired with digest sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760 once this image has been published in accordance with Red Hat Certification policy. You may then add or remove any supplemental tags through your Red Hat Connect portal as you see fit.&#34;&#xA;    {&#xA;        &#34;image&#34;: &#34;quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#34;,&#xA;        &#34;passed&#34;: false,&#xA;        &#34;test_library&#34;: {&#xA;            &#34;name&#34;: &#34;github.com/redhat-openshift-ecosystem/openshift-preflight&#34;,&#xA;            &#34;version&#34;: &#34;1.17.1&#34;,&#xA;            &#34;commit&#34;: &#34;f7de82ae1c76e6c10ea94967d6b6a66f96248cbe&#34;&#xA;        },&#xA;        &#34;results&#34;: {&#xA;            &#34;passed&#34;: [&#xA;                {&#xA;                    &#34;name&#34;: &#34;HasUniqueTag&#34;,&#xA;                    &#34;elapsed_time&#34;: 0,&#xA;                    &#34;description&#34;: &#34;Checking if container has a tag other than &#39;latest&#39;, so that the image can be uniquely identified.&#34;&#xA;                },&#xA;                {&#xA;                    &#34;name&#34;: &#34;LayerCountAcceptable&#34;,&#xA;                    &#34;elapsed_time&#34;: 0,&#xA;                    &#34;description&#34;: &#34;Checking if container has less than 40 layers.  Too many layers within the container images can degrade container performance.&#34;&#xA;                },&#xA;                {&#xA;                    &#34;name&#34;: &#34;HasNoProhibitedPackages&#34;,&#xA;                    &#34;elapsed_time&#34;: 38,&#xA;                    &#34;description&#34;: &#34;Checks to ensure that the image in use does not include prohibited packages, such as Red Hat Enterprise Linux (RHEL) kernel packages.&#34;&#xA;                },&#xA;                {&#xA;                    &#34;name&#34;: &#34;HasRequiredLabel&#34;,&#xA;                    &#34;elapsed_time&#34;: 0,&#xA;                    &#34;description&#34;: &#34;Checking if the required labels (name, vendor, version, release, summary, description, maintainer) are present in the container metadata&#34;&#xA;                },&#xA;                {&#xA;                    &#34;name&#34;: &#34;RunAsNonRoot&#34;,&#xA;                    &#34;elapsed_time&#34;: 0,&#xA;                    &#34;description&#34;: &#34;Checking if container runs as the root user because a container that does not specify a non-root user will fail the automatic certification, and will be subject to a manual review before the container can be approved for publication&#34;&#xA;                },&#xA;                {&#xA;                    &#34;name&#34;: &#34;HasModifiedFiles&#34;,&#xA;                    &#34;elapsed_time&#34;: 8668,&#xA;                    &#34;description&#34;: &#34;Checks that no files installed via RPM in the base Red Hat layer have been modified&#34;&#xA;                },&#xA;                {&#xA;                    &#34;name&#34;: &#34;BasedOnUbi&#34;,&#xA;                    &#34;elapsed_time&#34;: 7354,&#xA;                    &#34;description&#34;: &#34;Checking if the container&#39;s base image is based upon the Red Hat Universal Base Image (UBI)&#34;&#xA;                }&#xA;            ],&#xA;            &#34;failed&#34;: [&#xA;                {&#xA;                    &#34;name&#34;: &#34;HasLicense&#34;,&#xA;                    &#34;elapsed_time&#34;: 15,&#xA;                    &#34;description&#34;: &#34;Checking if terms and conditions applicable to the software including open source licensing information are present. The license must be at /licenses&#34;,&#xA;                    &#34;help&#34;: &#34;Check HasLicense encountered an error. Please review the preflight.log file for more information.&#34;,&#xA;                    &#34;suggestion&#34;: &#34;Create a directory named /licenses and include all relevant licensing and/or terms and conditions as text file(s) in that directory.&#34;,&#xA;                    &#34;knowledgebase_url&#34;: &#34;https://access.redhat.com/documentation/en-us/red_hat_software_certification/2024/html-single/red_hat_openshift_software_certification_policy_guide/index#assembly-requirements-for-container-images_openshift-sw-cert-policy-introduction&#34;,&#xA;                    &#34;check_url&#34;: &#34;https://access.redhat.com/documentation/en-us/red_hat_software_certification/2024/html-single/red_hat_openshift_software_certification_policy_guide/index#assembly-requirements-for-container-images_openshift-sw-cert-policy-introduction&#34;&#xA;                }&#xA;            ],&#xA;            &#34;errors&#34;: []&#xA;        }&#xA;    }&#xA;    time=&#34;2026-04-21T08:11:12Z&#34; level=info msg=&#34;Preflight result: FAILED&#34;&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-app-set-outcome: &#xA;    {&#34;result&#34;:&#34;FAILURE&#34;,&#34;timestamp&#34;:&#34;1776759072&#34;,&#34;note&#34;:&#34;Task preflight is a FAILURE: Refer to Tekton task logs for more information&#34;,&#34;successes&#34;:7,&#34;failures&#34;:1,&#34;warnings&#34;:0}[retry] executing: skopeo inspect --raw --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-final-outcome: &#xA;    + [[ ! -f /mount/konflux.results.json ]]&#xA;    + tee /tekton/steps/step-final-outcome/results/test-output&#xA;    {&#34;result&#34;:&#34;FAILURE&#34;,&#34;timestamp&#34;:&#34;1776759072&#34;,&#34;note&#34;:&#34;Task preflight is a FAILURE: Refer to Tekton task logs for more information&#34;,&#34;successes&#34;:7,&#34;failures&#34;:1,&#34;warnings&#34;:0}&#xA;     pod: test-comp-pac-gitlab-nqglox52a819651f560efef8a7fd4a3d045bb7-pod | init container: prepare&#xA;    2026/04/21 08:10:01 Entrypoint initialization&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox52a819651f560efef8a7fd4a3d045bb7-pod | container step-apply-additional-tags: &#xA;    time=&#34;2026-04-21T08:10:05Z&#34; level=info msg=&#34;[param] image-url: quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#34;&#xA;    time=&#34;2026-04-21T08:10:05Z&#34; level=info msg=&#34;[param] digest: sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760&#34;&#xA;    time=&#34;2026-04-21T08:10:05Z&#34; level=info msg=&#34;[param] tags-from-image-label: konflux.additional-tags&#34;&#xA;    time=&#34;2026-04-21T08:10:06Z&#34; level=warning msg=&#34;No tags given in &#39;konflux.additional-tags&#39; image label&#34;&#xA;    {&#34;tags&#34;:[]}&#xA;     pod: test-comp-pac-gitlab-nqglox53d62eb88415018600aa4813dd11fb26-pod | init container: prepare&#xA;    2026/04/21 08:10:02 Entrypoint initialization&#xA;    &#xA;     pod: test-comp-pac-gitlab-nqglox53d62eb88415018600aa4813dd11fb26-pod | init container: place-scripts&#xA;    2026/04/21 08:10:14 Decoded script /tekton/scripts/script-0-bzbgv&#xA;    2026/04/21 08:10:14 Decoded script /tekton/scripts/script-1-hxgf9&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox53d62eb88415018600aa4813dd11fb26-pod | container step-extract-and-scan-image: &#xA;    Starting clamd ...&#xA;    clamd is ready!&#xA;    Detecting artifact type for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox@sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760.&#xA;    Detected container image. Processing image manifests.&#xA;    Running &#34;oc image extract&#34; on image of arch amd64&#xA;    Scanning image for arch amd64. This operation may take a while.&#xA;    &#xA;    ----------- SCAN SUMMARY -----------&#xA;    Infected files: 0&#xA;    Time: 42.251 sec (0 m 42 s)&#xA;    Start Date: 2026:04:21 08:10:30&#xA;    End Date:   2026:04:21 08:11:13&#xA;    Executed-on: Scan was executed on clamsdcan version - ClamAV 1.4.3/27977/Mon Apr 20 06:26:26 2026 Database version: 27977&#xA;    [&#xA;    &#x9;{&#xA;    &#x9;&#x9;&#34;filename&#34;: &#34;/work/logs/clamscan-result-log-amd64.json&#34;,&#xA;    &#x9;&#x9;&#34;namespace&#34;: &#34;required_checks&#34;,&#xA;    &#x9;&#x9;&#34;successes&#34;: 2&#xA;    &#x9;}&#xA;    ]&#xA;    {&#34;timestamp&#34;:&#34;1776759073&#34;,&#34;namespace&#34;:&#34;required_checks&#34;,&#34;successes&#34;:2,&#34;failures&#34;:0,&#34;warnings&#34;:0,&#34;result&#34;:&#34;SUCCESS&#34;,&#34;note&#34;:&#34;All checks passed successfully&#34;}&#xA;    {&#34;timestamp&#34;:&#34;1776759073&#34;,&#34;namespace&#34;:&#34;required_checks&#34;,&#34;successes&#34;:2,&#34;failures&#34;:0,&#34;warnings&#34;:0,&#34;result&#34;:&#34;SUCCESS&#34;,&#34;note&#34;:&#34;All checks passed successfully&#34;}&#xA;    {&#34;timestamp&#34;:&#34;1776759073&#34;,&#34;namespace&#34;:&#34;required_checks&#34;,&#34;successes&#34;:2,&#34;failures&#34;:0,&#34;warnings&#34;:0,&#34;result&#34;:&#34;SUCCESS&#34;,&#34;note&#34;:&#34;All checks passed successfully&#34;}&#xA;    {&#34;image&#34;: {&#34;pullspec&#34;: &#34;quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#34;, &#34;digests&#34;: [&#34;sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760&#34;]}}&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox53d62eb88415018600aa4813dd11fb26-pod | container step-upload: &#xA;    Selecting auth&#xA;    Using token for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox&#xA;    Attaching to quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#xA;    Executing: oras attach --no-tty --registry-config /home/oras/auth.json --artifact-type application/vnd.clamav quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734@sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760 clamscan-result-amd64.log:text/vnd.clamav clamscan-ec-test-amd64.json:application/vnd.konflux.test_output+json&#xA;    Preparing clamscan-result-amd64.log&#xA;    Preparing clamscan-ec-test-amd64.json&#xA;    Exists    44136fa355b3 application/vnd.oci.empty.v1+json&#xA;    Uploading 6115c63e1844 clamscan-ec-test-amd64.json&#xA;    Uploading 669c731460fe clamscan-result-amd64.log&#xA;    Uploaded  6115c63e1844 clamscan-ec-test-amd64.json&#xA;    Uploaded  669c731460fe clamscan-result-amd64.log&#xA;    Uploading d84231f3b87c application/vnd.oci.image.manifest.v1+json&#xA;    Uploaded  d84231f3b87c application/vnd.oci.image.manifest.v1+json&#xA;    Attached to [registry] quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734@sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760&#xA;    Digest: sha256:d84231f3b87cad02abe05dd9d8ed577f5ed7cf8c240960a80a9557e857c50c8f&#xA;    &#xA;    {&#xA;        s: &#34;\n pod: test-comp-pac-gitlab-nqglox-on-pull-request-gkvds-init-pod | init container: prepare\n2026/04/21 08:07:20 Entrypoint initialization\n\npod: test-comp-pac-gitlab-nqglox-on-pull-request-gkvds-init-pod | container step-init: \ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;Using in-cluster config\&#34; logger=KubeClient\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;[param] enable: false\&#34;\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128\&#34;\ntime=\&#34;2026-04-21T08:07:22Z\&#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;\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;[param] http-proxy-result-path: /tekton/results/http-proxy\&#34;\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;[param] no-proxy-result-path: /tekton/results/no-proxy\&#34;\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;Cache proxy is disabled in param or in backend\&#34;\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;[result] HTTP PROXY: \&#34;\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;[result] NO PROXY: \&#34;\n\n pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | init container: prepare\n2026/04/21 08:10:01 Entrypoint initialization\n\n pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | init container: place-scripts\n2026/04/21 08:10:02 Decoded script /tekton/scripts/script-0-g5m28\n2026/04/21 08:10:02 Decoded script /tekton/scripts/script-1-qv5ww\n2026/04/21 08:10:02 Decoded script /tekton/scripts/script-2-t2hmp\n2026/04/21 08:10:02 Decoded script /tekton/scripts/script-3-9hrxc\n2026/04/21 08:10:02 Decoded script /tekton/scripts/script-4-26ww8\n2026/04/21 08:10:02 Decoded script /tekton/scripts/script-5-8rjgc\n\npod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-introspect: \nArtifact type will be determined by introspection.\nChecking the media type of the OCI artifact...\n[retry] executing: skopeo inspect --raw --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734\nThe media type of the OCI artifact is application/vnd.docker.distribution.manifest.v2+json.\nLooking for image labels that indicate this might be an operator bundle...\n[retry] executing: skopeo inspect --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734\nFound 0 matching labels.\nExpecting 3 or more to identify this image as an operator bundle.\nIntrospection concludes that this artifact is of type \&#34;application\&#34;.\n\npod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-generate-container-auth: \nSelecting auth for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734\nUsing token for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox\nAuth json written to \&#34;/auth/auth.json\&#34;.\n\npod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-set-skip-for-bundles: \n2026/04/21 08:10:47 INFO Step was skipped due to when expressions were evaluated to false.\n\npod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-app-check: \ntime=\&#34;2026-04-21T08:10:48Z\&#34; level=info msg=\&#34;certification library version\&#34; version=\&#34;1.17.1 &lt;commit: f7de82ae1c76e6c10ea94967d6b6a66f96248cbe&gt;\&#34;\ntime=\&#34;2026-04-21T08:10:48Z\&#34; level=info msg=\&#34;running checks for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734 for platform amd64\&#34;\ntime=\&#34;2026-04-21T08:10:48Z\&#34; level=info msg=\&#34;target image\&#34; ima...&#xA;&#xA;Gomega truncated this representation as it exceeds &#39;format.MaxLength&#39;.&#xA;Consider having the object provide a custom &#39;GomegaStringer&#39; representation&#xA;or adjust the parameters in Gomega&#39;s &#39;format&#39; package.&#xA;&#xA;Learn more here: https://onsi.github.io/gomega/#adjusting-output&#xA;In [It] at: /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:150 @ 04/21/26 08:11:38.479&#xA;&#xA;There were additional failures detected after the initial failure. These are visible in the timeline&#xA;</failure>
              <system-err>&gt; Enter [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:148 @ 04/21/26 07:59:55.289&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-vv5k2 found for Component gitlab-rep-flag/test-comp-pac-gitlab-nqglox&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-vv5k2 reason: ResolvingTaskRef&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-vv5k2 reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-vv5k2 reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-vv5k2 reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-vv5k2 reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-vv5k2 reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-vv5k2 reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-vv5k2 reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-vv5k2 reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-vv5k2 reason: Failed&#xA;attempt 1/3: PipelineRun &#34;test-comp-pac-gitlab-nqglox-on-pull-request-vv5k2&#34; failed: &#xA; pod: test-comp-pac-gitlab-nqglox-on-pull-request-vv5k2-init-pod | init container: prepare&#xA;2026/04/21 08:00:01 Entrypoint initialization&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox-on-pull-request-vv5k2-init-pod | container step-init: &#xA;time=&#34;2026-04-21T08:00:21Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-21T08:00:21Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-21T08:00:21Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-21T08:00:21Z&#34; level=info msg=&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai&#34;&#xA;time=&#34;2026-04-21T08:00:21Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-21T08:00:21Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-21T08:00:21Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;time=&#34;2026-04-21T08:00:21Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-21T08:00:21Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;New PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-74qh6 found after retrigger for component gitlab-rep-flag/test-comp-pac-gitlab-nqglox&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-74qh6 found for Component gitlab-rep-flag/test-comp-pac-gitlab-nqglox&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-74qh6 reason: ResolvingTaskRef&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-74qh6 reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-74qh6 reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-74qh6 reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-74qh6 reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-74qh6 reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-74qh6 reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-74qh6 reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-74qh6 reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-74qh6 reason: PipelineRunStopping&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-74qh6 reason: PipelineRunStopping&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-74qh6 reason: PipelineRunStopping&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-74qh6 reason: Failed&#xA;an error happened during storing pipelineRun log gitlab-rep-flag:test-comp-pac-gitlab-nqglox-on-pull-request-74qh6: container &#34;step-get-vulnerabilities&#34; in pod &#34;test-comp-pac-gitlab-nqgloxced098dd6dcbb61cc0bb0f03280181e7-pod&#34; is waiting to start: PodInitializing&#xA;failed to get logs for PipelineRun gitlab-rep-flag:test-comp-pac-gitlab-nqglox-on-pull-request-74qh6: container &#34;step-get-vulnerabilities&#34; in pod &#34;test-comp-pac-gitlab-nqgloxced098dd6dcbb61cc0bb0f03280181e7-pod&#34; is waiting to start: PodInitializing&#xA;attempt 2/3: PipelineRun &#34;test-comp-pac-gitlab-nqglox-on-pull-request-74qh6&#34; failed: &#xA; pod: test-comp-pac-gitlab-nqglox-on-pull-request-74qh6-init-pod | init container: prepare&#xA;2026/04/21 08:03:09 Entrypoint initialization&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox-on-pull-request-74qh6-init-pod | container step-init: &#xA;time=&#34;2026-04-21T08:03:11Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-21T08:03:11Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-21T08:03:11Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-21T08:03:11Z&#34; level=info msg=&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai&#34;&#xA;time=&#34;2026-04-21T08:03:11Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-21T08:03:11Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-21T08:03:11Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;time=&#34;2026-04-21T08:03:11Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-21T08:03:11Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;&#xA; pod: test-comp-pac-gitlab-nqglox133c16bcc0b1ac1ace8237d1c3b679a8-pod | init container: prepare&#xA;2026/04/21 08:05:02 Entrypoint initialization&#xA;&#xA; pod: test-comp-pac-gitlab-nqglox133c16bcc0b1ac1ace8237d1c3b679a8-pod | init container: place-scripts&#xA;2026/04/21 08:05:03 Decoded script /tekton/scripts/script-0-22g5j&#xA;2026/04/21 08:05:03 Decoded script /tekton/scripts/script-1-94z4j&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox133c16bcc0b1ac1ace8237d1c3b679a8-pod | container step-extract-and-scan-image: &#xA;Starting clamd ...&#xA;clamd is ready!&#xA;Detecting artifact type for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox@sha256:a5ff6ade64007a1617b9a481a9b71388baac04ecf3738234506c5a84b8816603.&#xA;Detected container image. Processing image manifests.&#xA;Running &#34;oc image extract&#34; on image of arch amd64&#xA;Scanning image for arch amd64. This operation may take a while.&#xA;&#xA;----------- SCAN SUMMARY -----------&#xA;Infected files: 0&#xA;Time: 45.070 sec (0 m 45 s)&#xA;Start Date: 2026:04:21 08:05:50&#xA;End Date:   2026:04:21 08:06:35&#xA;Executed-on: Scan was executed on clamsdcan version - ClamAV 1.4.3/27977/Mon Apr 20 06:26:26 2026 Database version: 27977&#xA;[&#xA;&#x9;{&#xA;&#x9;&#x9;&#34;filename&#34;: &#34;/work/logs/clamscan-result-log-amd64.json&#34;,&#xA;&#x9;&#x9;&#34;namespace&#34;: &#34;required_checks&#34;,&#xA;&#x9;&#x9;&#34;successes&#34;: 2&#xA;&#x9;}&#xA;]&#xA;{&#34;timestamp&#34;:&#34;1776758795&#34;,&#34;namespace&#34;:&#34;required_checks&#34;,&#34;successes&#34;:2,&#34;failures&#34;:0,&#34;warnings&#34;:0,&#34;result&#34;:&#34;SUCCESS&#34;,&#34;note&#34;:&#34;All checks passed successfully&#34;}&#xA;{&#34;timestamp&#34;:&#34;1776758795&#34;,&#34;namespace&#34;:&#34;required_checks&#34;,&#34;successes&#34;:2,&#34;failures&#34;:0,&#34;warnings&#34;:0,&#34;result&#34;:&#34;SUCCESS&#34;,&#34;note&#34;:&#34;All checks passed successfully&#34;}&#xA;{&#34;timestamp&#34;:&#34;1776758795&#34;,&#34;namespace&#34;:&#34;required_checks&#34;,&#34;successes&#34;:2,&#34;failures&#34;:0,&#34;warnings&#34;:0,&#34;result&#34;:&#34;SUCCESS&#34;,&#34;note&#34;:&#34;All checks passed successfully&#34;}&#xA;{&#34;image&#34;: {&#34;pullspec&#34;: &#34;quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-991ae9c062842043ca3f26dc360f23bbfb5a58fc&#34;, &#34;digests&#34;: [&#34;sha256:a5ff6ade64007a1617b9a481a9b71388baac04ecf3738234506c5a84b8816603&#34;]}}&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox133c16bcc0b1ac1ace8237d1c3b679a8-pod | container step-upload: &#xA;Selecting auth&#xA;Using token for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox&#xA;Attaching to quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-991ae9c062842043ca3f26dc360f23bbfb5a58fc&#xA;Executing: oras attach --no-tty --registry-config /home/oras/auth.json --artifact-type application/vnd.clamav quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-991ae9c062842043ca3f26dc360f23bbfb5a58fc@sha256:a5ff6ade64007a1617b9a481a9b71388baac04ecf3738234506c5a84b8816603 clamscan-result-amd64.log:text/vnd.clamav clamscan-ec-test-amd64.json:application/vnd.konflux.test_output+json&#xA;Preparing clamscan-result-amd64.log&#xA;Preparing clamscan-ec-test-amd64.json&#xA;Uploading b7b61cd5a3c6 clamscan-ec-test-amd64.json&#xA;Exists    44136fa355b3 application/vnd.oci.empty.v1+json&#xA;Uploading 603639b7e383 clamscan-result-amd64.log&#xA;Uploaded  b7b61cd5a3c6 clamscan-ec-test-amd64.json&#xA;Uploaded  603639b7e383 clamscan-result-amd64.log&#xA;Uploading 9001e26a6387 application/vnd.oci.image.manifest.v1+json&#xA;Uploaded  9001e26a6387 application/vnd.oci.image.manifest.v1+json&#xA;Attached to [registry] quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-991ae9c062842043ca3f26dc360f23bbfb5a58fc@sha256:a5ff6ade64007a1617b9a481a9b71388baac04ecf3738234506c5a84b8816603&#xA;Digest: sha256:9001e26a6387bdee94426a34fd7eb0c2cc08b12ef92a3713e9bc10d370157757&#xA;&#xA; pod: test-comp-pac-gitlab-nqglox35800c29af22b68fe0ad24dd80020e3a-pod | init container: prepare&#xA;2026/04/21 08:05:02 Entrypoint initialization&#xA;&#xA; pod: test-comp-pac-gitlab-nqglox35800c29af22b68fe0ad24dd80020e3a-pod | init container: place-scripts&#xA;2026/04/21 08:05:02 Decoded script /tekton/scripts/script-0-wss2t&#xA;2026/04/21 08:05:02 Decoded script /tekton/scripts/script-1-l9msx&#xA;2026/04/21 08:05:02 Decoded script /tekton/scripts/script-2-pkk82&#xA;2026/04/21 08:05:02 Decoded script /tekton/scripts/script-3-8bgdc&#xA;2026/04/21 08:05:02 Decoded script /tekton/scripts/script-4-jr7d9&#xA;2026/04/21 08:05:02 Decoded script /tekton/scripts/script-5-w8bfj&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox35800c29af22b68fe0ad24dd80020e3a-pod | container step-introspect: &#xA;Artifact type will be determined by introspection.&#xA;Checking the media type of the OCI artifact...&#xA;[retry] executing: skopeo inspect --raw --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-991ae9c062842043ca3f26dc360f23bbfb5a58fc&#xA;The media type of the OCI artifact is application/vnd.docker.distribution.manifest.v2+json.&#xA;Looking for image labels that indicate this might be an operator bundle...&#xA;[retry] executing: skopeo inspect --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-991ae9c062842043ca3f26dc360f23bbfb5a58fc&#xA;Found 0 matching labels.&#xA;Expecting 3 or more to identify this image as an operator bundle.&#xA;Introspection concludes that this artifact is of type &#34;application&#34;.&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox35800c29af22b68fe0ad24dd80020e3a-pod | container step-generate-container-auth: &#xA;Selecting auth for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-991ae9c062842043ca3f26dc360f23bbfb5a58fc&#xA;Using token for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox&#xA;Auth json written to &#34;/auth/auth.json&#34;.&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox35800c29af22b68fe0ad24dd80020e3a-pod | container step-set-skip-for-bundles: &#xA;2026/04/21 08:05:31 INFO Step was skipped due to when expressions were evaluated to false.&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox35800c29af22b68fe0ad24dd80020e3a-pod | container step-app-check: &#xA;time=&#34;2026-04-21T08:05:31Z&#34; level=info msg=&#34;certification library version&#34; version=&#34;1.17.1 &lt;commit: f7de82ae1c76e6c10ea94967d6b6a66f96248cbe&gt;&#34;&#xA;time=&#34;2026-04-21T08:05:31Z&#34; level=info msg=&#34;running checks for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-991ae9c062842043ca3f26dc360f23bbfb5a58fc for platform amd64&#34;&#xA;time=&#34;2026-04-21T08:05:31Z&#34; level=info msg=&#34;target image&#34; image=&#34;quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-991ae9c062842043ca3f26dc360f23bbfb5a58fc&#34;&#xA;time=&#34;2026-04-21T08:05:40Z&#34; level=info msg=&#34;warning: licenses directory does not exist or all of its children are empty directories: error when checking for /licenses: stat /tmp/preflight-1446244437/fs/licenses: no such file or directory&#34; check=HasLicense&#xA;time=&#34;2026-04-21T08:05:40Z&#34; level=info msg=&#34;check completed&#34; check=HasLicense result=FAILED&#xA;time=&#34;2026-04-21T08:05:40Z&#34; level=info msg=&#34;check completed&#34; check=HasUniqueTag result=PASSED&#xA;time=&#34;2026-04-21T08:05:40Z&#34; level=info msg=&#34;check completed&#34; check=LayerCountAcceptable result=PASSED&#xA;time=&#34;2026-04-21T08:05:40Z&#34; level=info msg=&#34;check completed&#34; check=HasNoProhibitedPackages result=PASSED&#xA;time=&#34;2026-04-21T08:05:40Z&#34; level=info msg=&#34;check completed&#34; check=HasRequiredLabel result=PASSED&#xA;time=&#34;2026-04-21T08:05:40Z&#34; level=info msg=&#34;USER 185 specified that is non-root&#34; check=RunAsNonRoot&#xA;time=&#34;2026-04-21T08:05:40Z&#34; level=info msg=&#34;check completed&#34; check=RunAsNonRoot result=PASSED&#xA;time=&#34;2026-04-21T08:05:49Z&#34; level=info msg=&#34;check completed&#34; check=HasModifiedFiles result=PASSED&#xA;time=&#34;2026-04-21T08:05:49Z&#34; level=info msg=&#34;check completed&#34; check=BasedOnUbi result=PASSED&#xA;time=&#34;2026-04-21T08:05:49Z&#34; level=info msg=&#34;This image&#39;s tag on-pr-991ae9c062842043ca3f26dc360f23bbfb5a58fc will be paired with digest sha256:a5ff6ade64007a1617b9a481a9b71388baac04ecf3738234506c5a84b8816603 once this image has been published in accordance with Red Hat Certification policy. You may then add or remove any supplemental tags through your Red Hat Connect portal as you see fit.&#34;&#xA;{&#xA;    &#34;image&#34;: &#34;quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-991ae9c062842043ca3f26dc360f23bbfb5a58fc&#34;,&#xA;    &#34;passed&#34;: false,&#xA;    &#34;test_library&#34;: {&#xA;        &#34;name&#34;: &#34;github.com/redhat-openshift-ecosystem/openshift-preflight&#34;,&#xA;        &#34;version&#34;: &#34;1.17.1&#34;,&#xA;        &#34;commit&#34;: &#34;f7de82ae1c76e6c10ea94967d6b6a66f96248cbe&#34;&#xA;    },&#xA;    &#34;results&#34;: {&#xA;        &#34;passed&#34;: [&#xA;            {&#xA;                &#34;name&#34;: &#34;HasUniqueTag&#34;,&#xA;                &#34;elapsed_time&#34;: 0,&#xA;                &#34;description&#34;: &#34;Checking if container has a tag other than &#39;latest&#39;, so that the image can be uniquely identified.&#34;&#xA;            },&#xA;            {&#xA;                &#34;name&#34;: &#34;LayerCountAcceptable&#34;,&#xA;                &#34;elapsed_time&#34;: 0,&#xA;                &#34;description&#34;: &#34;Checking if container has less than 40 layers.  Too many layers within the container images can degrade container performance.&#34;&#xA;            },&#xA;            {&#xA;                &#34;name&#34;: &#34;HasNoProhibitedPackages&#34;,&#xA;                &#34;elapsed_time&#34;: 36,&#xA;                &#34;description&#34;: &#34;Checks to ensure that the image in use does not include prohibited packages, such as Red Hat Enterprise Linux (RHEL) kernel packages.&#34;&#xA;            },&#xA;            {&#xA;                &#34;name&#34;: &#34;HasRequiredLabel&#34;,&#xA;                &#34;elapsed_time&#34;: 0,&#xA;                &#34;description&#34;: &#34;Checking if the required labels (name, vendor, version, release, summary, description, maintainer) are present in the container metadata&#34;&#xA;            },&#xA;            {&#xA;                &#34;name&#34;: &#34;RunAsNonRoot&#34;,&#xA;                &#34;elapsed_time&#34;: 0,&#xA;                &#34;description&#34;: &#34;Checking if container runs as the root user because a container that does not specify a non-root user will fail the automatic certification, and will be subject to a manual review before the container can be approved for publication&#34;&#xA;            },&#xA;            {&#xA;                &#34;name&#34;: &#34;HasModifiedFiles&#34;,&#xA;                &#34;elapsed_time&#34;: 8541,&#xA;                &#34;description&#34;: &#34;Checks that no files installed via RPM in the base Red Hat layer have been modified&#34;&#xA;            },&#xA;            {&#xA;                &#34;name&#34;: &#34;BasedOnUbi&#34;,&#xA;                &#34;elapsed_time&#34;: 163,&#xA;                &#34;description&#34;: &#34;Checking if the container&#39;s base image is based upon the Red Hat Universal Base Image (UBI)&#34;&#xA;            }&#xA;        ],&#xA;        &#34;failed&#34;: [&#xA;            {&#xA;                &#34;name&#34;: &#34;HasLicense&#34;,&#xA;                &#34;elapsed_time&#34;: 0,&#xA;                &#34;description&#34;: &#34;Checking if terms and conditions applicable to the software including open source licensing information are present. The license must be at /licenses&#34;,&#xA;                &#34;help&#34;: &#34;Check HasLicense encountered an error. Please review the preflight.log file for more information.&#34;,&#xA;                &#34;suggestion&#34;: &#34;Create a directory named /licenses and include all relevant licensing and/or terms and conditions as text file(s) in that directory.&#34;,&#xA;                &#34;knowledgebase_url&#34;: &#34;https://access.redhat.com/documentation/en-us/red_hat_software_certification/2024/html-single/red_hat_openshift_software_certification_policy_guide/index#assembly-requirements-for-container-images_openshift-sw-cert-policy-introduction&#34;,&#xA;                &#34;check_url&#34;: &#34;https://access.redhat.com/documentation/en-us/red_hat_software_certification/2024/html-single/red_hat_openshift_software_certification_policy_guide/index#assembly-requirements-for-container-images_openshift-sw-cert-policy-introduction&#34;&#xA;            }&#xA;        ],&#xA;        &#34;errors&#34;: []&#xA;    }&#xA;}&#xA;time=&#34;2026-04-21T08:05:49Z&#34; level=info msg=&#34;Preflight result: FAILED&#34;&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox35800c29af22b68fe0ad24dd80020e3a-pod | container step-app-set-outcome: &#xA;{&#34;result&#34;:&#34;FAILURE&#34;,&#34;timestamp&#34;:&#34;1776758749&#34;,&#34;note&#34;:&#34;Task preflight is a FAILURE: Refer to Tekton task logs for more information&#34;,&#34;successes&#34;:7,&#34;failures&#34;:1,&#34;warnings&#34;:0}[retry] executing: skopeo inspect --raw --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-991ae9c062842043ca3f26dc360f23bbfb5a58fc&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox35800c29af22b68fe0ad24dd80020e3a-pod | container step-final-outcome: &#xA;+ [[ ! -f /mount/konflux.results.json ]]&#xA;+ tee /tekton/steps/step-final-outcome/results/test-output&#xA;{&#34;result&#34;:&#34;FAILURE&#34;,&#34;timestamp&#34;:&#34;1776758749&#34;,&#34;note&#34;:&#34;Task preflight is a FAILURE: Refer to Tekton task logs for more information&#34;,&#34;successes&#34;:7,&#34;failures&#34;:1,&#34;warnings&#34;:0}&#xA; pod: test-comp-pac-gitlab-nqglox4d7795f212d8167d3f539b1eb6d3f1ca-pod | init container: prepare&#xA;2026/04/21 08:05:03 Entrypoint initialization&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox4d7795f212d8167d3f539b1eb6d3f1ca-pod | container step-apply-additional-tags: &#xA;time=&#34;2026-04-21T08:05:30Z&#34; level=info msg=&#34;[param] image-url: quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-991ae9c062842043ca3f26dc360f23bbfb5a58fc&#34;&#xA;time=&#34;2026-04-21T08:05:30Z&#34; level=info msg=&#34;[param] digest: sha256:a5ff6ade64007a1617b9a481a9b71388baac04ecf3738234506c5a84b8816603&#34;&#xA;time=&#34;2026-04-21T08:05:30Z&#34; level=info msg=&#34;[param] tags-from-image-label: konflux.additional-tags&#34;&#xA;time=&#34;2026-04-21T08:05:31Z&#34; level=warning msg=&#34;No tags given in &#39;konflux.additional-tags&#39; image label&#34;&#xA;{&#34;tags&#34;:[]}&#xA; pod: test-comp-pac-gitlab-nqgloxced098dd6dcbb61cc0bb0f03280181e7-pod | init container: prepare&#xA;2026/04/21 08:05:02 Entrypoint initialization&#xA;&#xA; pod: test-comp-pac-gitlab-nqgloxced098dd6dcbb61cc0bb0f03280181e7-pod | init container: place-scripts&#xA;2026/04/21 08:05:27 Decoded script /tekton/scripts/script-0-h2mn5&#xA;2026/04/21 08:05:27 Decoded script /tekton/scripts/script-1-z4l64&#xA;2026/04/21 08:05:27 Decoded script /tekton/scripts/script-2-zsccr&#xA;2026/04/21 08:05:27 Decoded script /tekton/scripts/script-3-q54lp&#xA;&#xA;pod: test-comp-pac-gitlab-nqgloxced098dd6dcbb61cc0bb0f03280181e7-pod | container step-get-image-manifests: &#xA;&#xA;pod: test-comp-pac-gitlab-nqgloxced098dd6dcbb61cc0bb0f03280181e7-pod | container step-get-vulnerabilities: &#xA;New PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-gkvds found after retrigger for component gitlab-rep-flag/test-comp-pac-gitlab-nqglox&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-gkvds found for Component gitlab-rep-flag/test-comp-pac-gitlab-nqglox&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-gkvds reason: ResolvingTaskRef&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-gkvds reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-gkvds reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-gkvds reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-gkvds reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-gkvds reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-gkvds reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-gkvds reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-gkvds reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-gkvds reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-gkvds reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-gkvds reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-gkvds reason: Running&#xA;PipelineRun test-comp-pac-gitlab-nqglox-on-pull-request-gkvds reason: Failed&#xA;attempt 3/3: PipelineRun &#34;test-comp-pac-gitlab-nqglox-on-pull-request-gkvds&#34; failed: &#xA; pod: test-comp-pac-gitlab-nqglox-on-pull-request-gkvds-init-pod | init container: prepare&#xA;2026/04/21 08:07:20 Entrypoint initialization&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox-on-pull-request-gkvds-init-pod | container step-init: &#xA;time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai&#34;&#xA;time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;&#xA; pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | init container: prepare&#xA;2026/04/21 08:10:01 Entrypoint initialization&#xA;&#xA; pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | init container: place-scripts&#xA;2026/04/21 08:10:02 Decoded script /tekton/scripts/script-0-g5m28&#xA;2026/04/21 08:10:02 Decoded script /tekton/scripts/script-1-qv5ww&#xA;2026/04/21 08:10:02 Decoded script /tekton/scripts/script-2-t2hmp&#xA;2026/04/21 08:10:02 Decoded script /tekton/scripts/script-3-9hrxc&#xA;2026/04/21 08:10:02 Decoded script /tekton/scripts/script-4-26ww8&#xA;2026/04/21 08:10:02 Decoded script /tekton/scripts/script-5-8rjgc&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-introspect: &#xA;Artifact type will be determined by introspection.&#xA;Checking the media type of the OCI artifact...&#xA;[retry] executing: skopeo inspect --raw --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#xA;The media type of the OCI artifact is application/vnd.docker.distribution.manifest.v2+json.&#xA;Looking for image labels that indicate this might be an operator bundle...&#xA;[retry] executing: skopeo inspect --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#xA;Found 0 matching labels.&#xA;Expecting 3 or more to identify this image as an operator bundle.&#xA;Introspection concludes that this artifact is of type &#34;application&#34;.&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-generate-container-auth: &#xA;Selecting auth for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#xA;Using token for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox&#xA;Auth json written to &#34;/auth/auth.json&#34;.&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-set-skip-for-bundles: &#xA;2026/04/21 08:10:47 INFO Step was skipped due to when expressions were evaluated to false.&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-app-check: &#xA;time=&#34;2026-04-21T08:10:48Z&#34; level=info msg=&#34;certification library version&#34; version=&#34;1.17.1 &lt;commit: f7de82ae1c76e6c10ea94967d6b6a66f96248cbe&gt;&#34;&#xA;time=&#34;2026-04-21T08:10:48Z&#34; level=info msg=&#34;running checks for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734 for platform amd64&#34;&#xA;time=&#34;2026-04-21T08:10:48Z&#34; level=info msg=&#34;target image&#34; image=&#34;quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#34;&#xA;time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;warning: licenses directory does not exist or all of its children are empty directories: error when checking for /licenses: stat /tmp/preflight-2625782039/fs/licenses: no such file or directory&#34; check=HasLicense&#xA;time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=HasLicense result=FAILED&#xA;time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=HasUniqueTag result=PASSED&#xA;time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=LayerCountAcceptable result=PASSED&#xA;time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=HasNoProhibitedPackages result=PASSED&#xA;time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=HasRequiredLabel result=PASSED&#xA;time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;USER 185 specified that is non-root&#34; check=RunAsNonRoot&#xA;time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=RunAsNonRoot result=PASSED&#xA;time=&#34;2026-04-21T08:11:05Z&#34; level=info msg=&#34;check completed&#34; check=HasModifiedFiles result=PASSED&#xA;time=&#34;2026-04-21T08:11:12Z&#34; level=info msg=&#34;check completed&#34; check=BasedOnUbi result=PASSED&#xA;time=&#34;2026-04-21T08:11:12Z&#34; level=info msg=&#34;This image&#39;s tag on-pr-cdc64b74622eaacc7ce5f90359269456f113f734 will be paired with digest sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760 once this image has been published in accordance with Red Hat Certification policy. You may then add or remove any supplemental tags through your Red Hat Connect portal as you see fit.&#34;&#xA;{&#xA;    &#34;image&#34;: &#34;quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#34;,&#xA;    &#34;passed&#34;: false,&#xA;    &#34;test_library&#34;: {&#xA;        &#34;name&#34;: &#34;github.com/redhat-openshift-ecosystem/openshift-preflight&#34;,&#xA;        &#34;version&#34;: &#34;1.17.1&#34;,&#xA;        &#34;commit&#34;: &#34;f7de82ae1c76e6c10ea94967d6b6a66f96248cbe&#34;&#xA;    },&#xA;    &#34;results&#34;: {&#xA;        &#34;passed&#34;: [&#xA;            {&#xA;                &#34;name&#34;: &#34;HasUniqueTag&#34;,&#xA;                &#34;elapsed_time&#34;: 0,&#xA;                &#34;description&#34;: &#34;Checking if container has a tag other than &#39;latest&#39;, so that the image can be uniquely identified.&#34;&#xA;            },&#xA;            {&#xA;                &#34;name&#34;: &#34;LayerCountAcceptable&#34;,&#xA;                &#34;elapsed_time&#34;: 0,&#xA;                &#34;description&#34;: &#34;Checking if container has less than 40 layers.  Too many layers within the container images can degrade container performance.&#34;&#xA;            },&#xA;            {&#xA;                &#34;name&#34;: &#34;HasNoProhibitedPackages&#34;,&#xA;                &#34;elapsed_time&#34;: 38,&#xA;                &#34;description&#34;: &#34;Checks to ensure that the image in use does not include prohibited packages, such as Red Hat Enterprise Linux (RHEL) kernel packages.&#34;&#xA;            },&#xA;            {&#xA;                &#34;name&#34;: &#34;HasRequiredLabel&#34;,&#xA;                &#34;elapsed_time&#34;: 0,&#xA;                &#34;description&#34;: &#34;Checking if the required labels (name, vendor, version, release, summary, description, maintainer) are present in the container metadata&#34;&#xA;            },&#xA;            {&#xA;                &#34;name&#34;: &#34;RunAsNonRoot&#34;,&#xA;                &#34;elapsed_time&#34;: 0,&#xA;                &#34;description&#34;: &#34;Checking if container runs as the root user because a container that does not specify a non-root user will fail the automatic certification, and will be subject to a manual review before the container can be approved for publication&#34;&#xA;            },&#xA;            {&#xA;                &#34;name&#34;: &#34;HasModifiedFiles&#34;,&#xA;                &#34;elapsed_time&#34;: 8668,&#xA;                &#34;description&#34;: &#34;Checks that no files installed via RPM in the base Red Hat layer have been modified&#34;&#xA;            },&#xA;            {&#xA;                &#34;name&#34;: &#34;BasedOnUbi&#34;,&#xA;                &#34;elapsed_time&#34;: 7354,&#xA;                &#34;description&#34;: &#34;Checking if the container&#39;s base image is based upon the Red Hat Universal Base Image (UBI)&#34;&#xA;            }&#xA;        ],&#xA;        &#34;failed&#34;: [&#xA;            {&#xA;                &#34;name&#34;: &#34;HasLicense&#34;,&#xA;                &#34;elapsed_time&#34;: 15,&#xA;                &#34;description&#34;: &#34;Checking if terms and conditions applicable to the software including open source licensing information are present. The license must be at /licenses&#34;,&#xA;                &#34;help&#34;: &#34;Check HasLicense encountered an error. Please review the preflight.log file for more information.&#34;,&#xA;                &#34;suggestion&#34;: &#34;Create a directory named /licenses and include all relevant licensing and/or terms and conditions as text file(s) in that directory.&#34;,&#xA;                &#34;knowledgebase_url&#34;: &#34;https://access.redhat.com/documentation/en-us/red_hat_software_certification/2024/html-single/red_hat_openshift_software_certification_policy_guide/index#assembly-requirements-for-container-images_openshift-sw-cert-policy-introduction&#34;,&#xA;                &#34;check_url&#34;: &#34;https://access.redhat.com/documentation/en-us/red_hat_software_certification/2024/html-single/red_hat_openshift_software_certification_policy_guide/index#assembly-requirements-for-container-images_openshift-sw-cert-policy-introduction&#34;&#xA;            }&#xA;        ],&#xA;        &#34;errors&#34;: []&#xA;    }&#xA;}&#xA;time=&#34;2026-04-21T08:11:12Z&#34; level=info msg=&#34;Preflight result: FAILED&#34;&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-app-set-outcome: &#xA;{&#34;result&#34;:&#34;FAILURE&#34;,&#34;timestamp&#34;:&#34;1776759072&#34;,&#34;note&#34;:&#34;Task preflight is a FAILURE: Refer to Tekton task logs for more information&#34;,&#34;successes&#34;:7,&#34;failures&#34;:1,&#34;warnings&#34;:0}[retry] executing: skopeo inspect --raw --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-final-outcome: &#xA;+ [[ ! -f /mount/konflux.results.json ]]&#xA;+ tee /tekton/steps/step-final-outcome/results/test-output&#xA;{&#34;result&#34;:&#34;FAILURE&#34;,&#34;timestamp&#34;:&#34;1776759072&#34;,&#34;note&#34;:&#34;Task preflight is a FAILURE: Refer to Tekton task logs for more information&#34;,&#34;successes&#34;:7,&#34;failures&#34;:1,&#34;warnings&#34;:0}&#xA; pod: test-comp-pac-gitlab-nqglox52a819651f560efef8a7fd4a3d045bb7-pod | init container: prepare&#xA;2026/04/21 08:10:01 Entrypoint initialization&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox52a819651f560efef8a7fd4a3d045bb7-pod | container step-apply-additional-tags: &#xA;time=&#34;2026-04-21T08:10:05Z&#34; level=info msg=&#34;[param] image-url: quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#34;&#xA;time=&#34;2026-04-21T08:10:05Z&#34; level=info msg=&#34;[param] digest: sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760&#34;&#xA;time=&#34;2026-04-21T08:10:05Z&#34; level=info msg=&#34;[param] tags-from-image-label: konflux.additional-tags&#34;&#xA;time=&#34;2026-04-21T08:10:06Z&#34; level=warning msg=&#34;No tags given in &#39;konflux.additional-tags&#39; image label&#34;&#xA;{&#34;tags&#34;:[]}&#xA; pod: test-comp-pac-gitlab-nqglox53d62eb88415018600aa4813dd11fb26-pod | init container: prepare&#xA;2026/04/21 08:10:02 Entrypoint initialization&#xA;&#xA; pod: test-comp-pac-gitlab-nqglox53d62eb88415018600aa4813dd11fb26-pod | init container: place-scripts&#xA;2026/04/21 08:10:14 Decoded script /tekton/scripts/script-0-bzbgv&#xA;2026/04/21 08:10:14 Decoded script /tekton/scripts/script-1-hxgf9&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox53d62eb88415018600aa4813dd11fb26-pod | container step-extract-and-scan-image: &#xA;Starting clamd ...&#xA;clamd is ready!&#xA;Detecting artifact type for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox@sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760.&#xA;Detected container image. Processing image manifests.&#xA;Running &#34;oc image extract&#34; on image of arch amd64&#xA;Scanning image for arch amd64. This operation may take a while.&#xA;&#xA;----------- SCAN SUMMARY -----------&#xA;Infected files: 0&#xA;Time: 42.251 sec (0 m 42 s)&#xA;Start Date: 2026:04:21 08:10:30&#xA;End Date:   2026:04:21 08:11:13&#xA;Executed-on: Scan was executed on clamsdcan version - ClamAV 1.4.3/27977/Mon Apr 20 06:26:26 2026 Database version: 27977&#xA;[&#xA;&#x9;{&#xA;&#x9;&#x9;&#34;filename&#34;: &#34;/work/logs/clamscan-result-log-amd64.json&#34;,&#xA;&#x9;&#x9;&#34;namespace&#34;: &#34;required_checks&#34;,&#xA;&#x9;&#x9;&#34;successes&#34;: 2&#xA;&#x9;}&#xA;]&#xA;{&#34;timestamp&#34;:&#34;1776759073&#34;,&#34;namespace&#34;:&#34;required_checks&#34;,&#34;successes&#34;:2,&#34;failures&#34;:0,&#34;warnings&#34;:0,&#34;result&#34;:&#34;SUCCESS&#34;,&#34;note&#34;:&#34;All checks passed successfully&#34;}&#xA;{&#34;timestamp&#34;:&#34;1776759073&#34;,&#34;namespace&#34;:&#34;required_checks&#34;,&#34;successes&#34;:2,&#34;failures&#34;:0,&#34;warnings&#34;:0,&#34;result&#34;:&#34;SUCCESS&#34;,&#34;note&#34;:&#34;All checks passed successfully&#34;}&#xA;{&#34;timestamp&#34;:&#34;1776759073&#34;,&#34;namespace&#34;:&#34;required_checks&#34;,&#34;successes&#34;:2,&#34;failures&#34;:0,&#34;warnings&#34;:0,&#34;result&#34;:&#34;SUCCESS&#34;,&#34;note&#34;:&#34;All checks passed successfully&#34;}&#xA;{&#34;image&#34;: {&#34;pullspec&#34;: &#34;quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#34;, &#34;digests&#34;: [&#34;sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760&#34;]}}&#xA;&#xA;pod: test-comp-pac-gitlab-nqglox53d62eb88415018600aa4813dd11fb26-pod | container step-upload: &#xA;Selecting auth&#xA;Using token for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox&#xA;Attaching to quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#xA;Executing: oras attach --no-tty --registry-config /home/oras/auth.json --artifact-type application/vnd.clamav quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734@sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760 clamscan-result-amd64.log:text/vnd.clamav clamscan-ec-test-amd64.json:application/vnd.konflux.test_output+json&#xA;Preparing clamscan-result-amd64.log&#xA;Preparing clamscan-ec-test-amd64.json&#xA;Exists    44136fa355b3 application/vnd.oci.empty.v1+json&#xA;Uploading 6115c63e1844 clamscan-ec-test-amd64.json&#xA;Uploading 669c731460fe clamscan-result-amd64.log&#xA;Uploaded  6115c63e1844 clamscan-ec-test-amd64.json&#xA;Uploaded  669c731460fe clamscan-result-amd64.log&#xA;Uploading d84231f3b87c application/vnd.oci.image.manifest.v1+json&#xA;Uploaded  d84231f3b87c application/vnd.oci.image.manifest.v1+json&#xA;Attached to [registry] quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734@sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760&#xA;Digest: sha256:d84231f3b87cad02abe05dd9d8ed577f5ed7cf8c240960a80a9557e857c50c8f&#xA;[FAILED] Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc000893790&gt;: &#xA;    &#xA;     pod: test-comp-pac-gitlab-nqglox-on-pull-request-gkvds-init-pod | init container: prepare&#xA;    2026/04/21 08:07:20 Entrypoint initialization&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox-on-pull-request-gkvds-init-pod | container step-init: &#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai&#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;    time=&#34;2026-04-21T08:07:22Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;    &#xA;     pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | init container: prepare&#xA;    2026/04/21 08:10:01 Entrypoint initialization&#xA;    &#xA;     pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | init container: place-scripts&#xA;    2026/04/21 08:10:02 Decoded script /tekton/scripts/script-0-g5m28&#xA;    2026/04/21 08:10:02 Decoded script /tekton/scripts/script-1-qv5ww&#xA;    2026/04/21 08:10:02 Decoded script /tekton/scripts/script-2-t2hmp&#xA;    2026/04/21 08:10:02 Decoded script /tekton/scripts/script-3-9hrxc&#xA;    2026/04/21 08:10:02 Decoded script /tekton/scripts/script-4-26ww8&#xA;    2026/04/21 08:10:02 Decoded script /tekton/scripts/script-5-8rjgc&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-introspect: &#xA;    Artifact type will be determined by introspection.&#xA;    Checking the media type of the OCI artifact...&#xA;    [retry] executing: skopeo inspect --raw --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#xA;    The media type of the OCI artifact is application/vnd.docker.distribution.manifest.v2+json.&#xA;    Looking for image labels that indicate this might be an operator bundle...&#xA;    [retry] executing: skopeo inspect --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#xA;    Found 0 matching labels.&#xA;    Expecting 3 or more to identify this image as an operator bundle.&#xA;    Introspection concludes that this artifact is of type &#34;application&#34;.&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-generate-container-auth: &#xA;    Selecting auth for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#xA;    Using token for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox&#xA;    Auth json written to &#34;/auth/auth.json&#34;.&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-set-skip-for-bundles: &#xA;    2026/04/21 08:10:47 INFO Step was skipped due to when expressions were evaluated to false.&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-app-check: &#xA;    time=&#34;2026-04-21T08:10:48Z&#34; level=info msg=&#34;certification library version&#34; version=&#34;1.17.1 &lt;commit: f7de82ae1c76e6c10ea94967d6b6a66f96248cbe&gt;&#34;&#xA;    time=&#34;2026-04-21T08:10:48Z&#34; level=info msg=&#34;running checks for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734 for platform amd64&#34;&#xA;    time=&#34;2026-04-21T08:10:48Z&#34; level=info msg=&#34;target image&#34; image=&#34;quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#34;&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;warning: licenses directory does not exist or all of its children are empty directories: error when checking for /licenses: stat /tmp/preflight-2625782039/fs/licenses: no such file or directory&#34; check=HasLicense&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=HasLicense result=FAILED&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=HasUniqueTag result=PASSED&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=LayerCountAcceptable result=PASSED&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=HasNoProhibitedPackages result=PASSED&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=HasRequiredLabel result=PASSED&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;USER 185 specified that is non-root&#34; check=RunAsNonRoot&#xA;    time=&#34;2026-04-21T08:10:56Z&#34; level=info msg=&#34;check completed&#34; check=RunAsNonRoot result=PASSED&#xA;    time=&#34;2026-04-21T08:11:05Z&#34; level=info msg=&#34;check completed&#34; check=HasModifiedFiles result=PASSED&#xA;    time=&#34;2026-04-21T08:11:12Z&#34; level=info msg=&#34;check completed&#34; check=BasedOnUbi result=PASSED&#xA;    time=&#34;2026-04-21T08:11:12Z&#34; level=info msg=&#34;This image&#39;s tag on-pr-cdc64b74622eaacc7ce5f90359269456f113f734 will be paired with digest sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760 once this image has been published in accordance with Red Hat Certification policy. You may then add or remove any supplemental tags through your Red Hat Connect portal as you see fit.&#34;&#xA;    {&#xA;        &#34;image&#34;: &#34;quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#34;,&#xA;        &#34;passed&#34;: false,&#xA;        &#34;test_library&#34;: {&#xA;            &#34;name&#34;: &#34;github.com/redhat-openshift-ecosystem/openshift-preflight&#34;,&#xA;            &#34;version&#34;: &#34;1.17.1&#34;,&#xA;            &#34;commit&#34;: &#34;f7de82ae1c76e6c10ea94967d6b6a66f96248cbe&#34;&#xA;        },&#xA;        &#34;results&#34;: {&#xA;            &#34;passed&#34;: [&#xA;                {&#xA;                    &#34;name&#34;: &#34;HasUniqueTag&#34;,&#xA;                    &#34;elapsed_time&#34;: 0,&#xA;                    &#34;description&#34;: &#34;Checking if container has a tag other than &#39;latest&#39;, so that the image can be uniquely identified.&#34;&#xA;                },&#xA;                {&#xA;                    &#34;name&#34;: &#34;LayerCountAcceptable&#34;,&#xA;                    &#34;elapsed_time&#34;: 0,&#xA;                    &#34;description&#34;: &#34;Checking if container has less than 40 layers.  Too many layers within the container images can degrade container performance.&#34;&#xA;                },&#xA;                {&#xA;                    &#34;name&#34;: &#34;HasNoProhibitedPackages&#34;,&#xA;                    &#34;elapsed_time&#34;: 38,&#xA;                    &#34;description&#34;: &#34;Checks to ensure that the image in use does not include prohibited packages, such as Red Hat Enterprise Linux (RHEL) kernel packages.&#34;&#xA;                },&#xA;                {&#xA;                    &#34;name&#34;: &#34;HasRequiredLabel&#34;,&#xA;                    &#34;elapsed_time&#34;: 0,&#xA;                    &#34;description&#34;: &#34;Checking if the required labels (name, vendor, version, release, summary, description, maintainer) are present in the container metadata&#34;&#xA;                },&#xA;                {&#xA;                    &#34;name&#34;: &#34;RunAsNonRoot&#34;,&#xA;                    &#34;elapsed_time&#34;: 0,&#xA;                    &#34;description&#34;: &#34;Checking if container runs as the root user because a container that does not specify a non-root user will fail the automatic certification, and will be subject to a manual review before the container can be approved for publication&#34;&#xA;                },&#xA;                {&#xA;                    &#34;name&#34;: &#34;HasModifiedFiles&#34;,&#xA;                    &#34;elapsed_time&#34;: 8668,&#xA;                    &#34;description&#34;: &#34;Checks that no files installed via RPM in the base Red Hat layer have been modified&#34;&#xA;                },&#xA;                {&#xA;                    &#34;name&#34;: &#34;BasedOnUbi&#34;,&#xA;                    &#34;elapsed_time&#34;: 7354,&#xA;                    &#34;description&#34;: &#34;Checking if the container&#39;s base image is based upon the Red Hat Universal Base Image (UBI)&#34;&#xA;                }&#xA;            ],&#xA;            &#34;failed&#34;: [&#xA;                {&#xA;                    &#34;name&#34;: &#34;HasLicense&#34;,&#xA;                    &#34;elapsed_time&#34;: 15,&#xA;                    &#34;description&#34;: &#34;Checking if terms and conditions applicable to the software including open source licensing information are present. The license must be at /licenses&#34;,&#xA;                    &#34;help&#34;: &#34;Check HasLicense encountered an error. Please review the preflight.log file for more information.&#34;,&#xA;                    &#34;suggestion&#34;: &#34;Create a directory named /licenses and include all relevant licensing and/or terms and conditions as text file(s) in that directory.&#34;,&#xA;                    &#34;knowledgebase_url&#34;: &#34;https://access.redhat.com/documentation/en-us/red_hat_software_certification/2024/html-single/red_hat_openshift_software_certification_policy_guide/index#assembly-requirements-for-container-images_openshift-sw-cert-policy-introduction&#34;,&#xA;                    &#34;check_url&#34;: &#34;https://access.redhat.com/documentation/en-us/red_hat_software_certification/2024/html-single/red_hat_openshift_software_certification_policy_guide/index#assembly-requirements-for-container-images_openshift-sw-cert-policy-introduction&#34;&#xA;                }&#xA;            ],&#xA;            &#34;errors&#34;: []&#xA;        }&#xA;    }&#xA;    time=&#34;2026-04-21T08:11:12Z&#34; level=info msg=&#34;Preflight result: FAILED&#34;&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-app-set-outcome: &#xA;    {&#34;result&#34;:&#34;FAILURE&#34;,&#34;timestamp&#34;:&#34;1776759072&#34;,&#34;note&#34;:&#34;Task preflight is a FAILURE: Refer to Tekton task logs for more information&#34;,&#34;successes&#34;:7,&#34;failures&#34;:1,&#34;warnings&#34;:0}[retry] executing: skopeo inspect --raw --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-final-outcome: &#xA;    + [[ ! -f /mount/konflux.results.json ]]&#xA;    + tee /tekton/steps/step-final-outcome/results/test-output&#xA;    {&#34;result&#34;:&#34;FAILURE&#34;,&#34;timestamp&#34;:&#34;1776759072&#34;,&#34;note&#34;:&#34;Task preflight is a FAILURE: Refer to Tekton task logs for more information&#34;,&#34;successes&#34;:7,&#34;failures&#34;:1,&#34;warnings&#34;:0}&#xA;     pod: test-comp-pac-gitlab-nqglox52a819651f560efef8a7fd4a3d045bb7-pod | init container: prepare&#xA;    2026/04/21 08:10:01 Entrypoint initialization&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox52a819651f560efef8a7fd4a3d045bb7-pod | container step-apply-additional-tags: &#xA;    time=&#34;2026-04-21T08:10:05Z&#34; level=info msg=&#34;[param] image-url: quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#34;&#xA;    time=&#34;2026-04-21T08:10:05Z&#34; level=info msg=&#34;[param] digest: sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760&#34;&#xA;    time=&#34;2026-04-21T08:10:05Z&#34; level=info msg=&#34;[param] tags-from-image-label: konflux.additional-tags&#34;&#xA;    time=&#34;2026-04-21T08:10:06Z&#34; level=warning msg=&#34;No tags given in &#39;konflux.additional-tags&#39; image label&#34;&#xA;    {&#34;tags&#34;:[]}&#xA;     pod: test-comp-pac-gitlab-nqglox53d62eb88415018600aa4813dd11fb26-pod | init container: prepare&#xA;    2026/04/21 08:10:02 Entrypoint initialization&#xA;    &#xA;     pod: test-comp-pac-gitlab-nqglox53d62eb88415018600aa4813dd11fb26-pod | init container: place-scripts&#xA;    2026/04/21 08:10:14 Decoded script /tekton/scripts/script-0-bzbgv&#xA;    2026/04/21 08:10:14 Decoded script /tekton/scripts/script-1-hxgf9&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox53d62eb88415018600aa4813dd11fb26-pod | container step-extract-and-scan-image: &#xA;    Starting clamd ...&#xA;    clamd is ready!&#xA;    Detecting artifact type for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox@sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760.&#xA;    Detected container image. Processing image manifests.&#xA;    Running &#34;oc image extract&#34; on image of arch amd64&#xA;    Scanning image for arch amd64. This operation may take a while.&#xA;    &#xA;    ----------- SCAN SUMMARY -----------&#xA;    Infected files: 0&#xA;    Time: 42.251 sec (0 m 42 s)&#xA;    Start Date: 2026:04:21 08:10:30&#xA;    End Date:   2026:04:21 08:11:13&#xA;    Executed-on: Scan was executed on clamsdcan version - ClamAV 1.4.3/27977/Mon Apr 20 06:26:26 2026 Database version: 27977&#xA;    [&#xA;    &#x9;{&#xA;    &#x9;&#x9;&#34;filename&#34;: &#34;/work/logs/clamscan-result-log-amd64.json&#34;,&#xA;    &#x9;&#x9;&#34;namespace&#34;: &#34;required_checks&#34;,&#xA;    &#x9;&#x9;&#34;successes&#34;: 2&#xA;    &#x9;}&#xA;    ]&#xA;    {&#34;timestamp&#34;:&#34;1776759073&#34;,&#34;namespace&#34;:&#34;required_checks&#34;,&#34;successes&#34;:2,&#34;failures&#34;:0,&#34;warnings&#34;:0,&#34;result&#34;:&#34;SUCCESS&#34;,&#34;note&#34;:&#34;All checks passed successfully&#34;}&#xA;    {&#34;timestamp&#34;:&#34;1776759073&#34;,&#34;namespace&#34;:&#34;required_checks&#34;,&#34;successes&#34;:2,&#34;failures&#34;:0,&#34;warnings&#34;:0,&#34;result&#34;:&#34;SUCCESS&#34;,&#34;note&#34;:&#34;All checks passed successfully&#34;}&#xA;    {&#34;timestamp&#34;:&#34;1776759073&#34;,&#34;namespace&#34;:&#34;required_checks&#34;,&#34;successes&#34;:2,&#34;failures&#34;:0,&#34;warnings&#34;:0,&#34;result&#34;:&#34;SUCCESS&#34;,&#34;note&#34;:&#34;All checks passed successfully&#34;}&#xA;    {&#34;image&#34;: {&#34;pullspec&#34;: &#34;quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#34;, &#34;digests&#34;: [&#34;sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760&#34;]}}&#xA;    &#xA;    pod: test-comp-pac-gitlab-nqglox53d62eb88415018600aa4813dd11fb26-pod | container step-upload: &#xA;    Selecting auth&#xA;    Using token for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox&#xA;    Attaching to quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734&#xA;    Executing: oras attach --no-tty --registry-config /home/oras/auth.json --artifact-type application/vnd.clamav quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734@sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760 clamscan-result-amd64.log:text/vnd.clamav clamscan-ec-test-amd64.json:application/vnd.konflux.test_output+json&#xA;    Preparing clamscan-result-amd64.log&#xA;    Preparing clamscan-ec-test-amd64.json&#xA;    Exists    44136fa355b3 application/vnd.oci.empty.v1+json&#xA;    Uploading 6115c63e1844 clamscan-ec-test-amd64.json&#xA;    Uploading 669c731460fe clamscan-result-amd64.log&#xA;    Uploaded  6115c63e1844 clamscan-ec-test-amd64.json&#xA;    Uploaded  669c731460fe clamscan-result-amd64.log&#xA;    Uploading d84231f3b87c application/vnd.oci.image.manifest.v1+json&#xA;    Uploaded  d84231f3b87c application/vnd.oci.image.manifest.v1+json&#xA;    Attached to [registry] quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734@sha256:e85f168562b5e845007eccfa2172b356ea06e0fde5d0927a072319b33a894760&#xA;    Digest: sha256:d84231f3b87cad02abe05dd9d8ed577f5ed7cf8c240960a80a9557e857c50c8f&#xA;    &#xA;    {&#xA;        s: &#34;\n pod: test-comp-pac-gitlab-nqglox-on-pull-request-gkvds-init-pod | init container: prepare\n2026/04/21 08:07:20 Entrypoint initialization\n\npod: test-comp-pac-gitlab-nqglox-on-pull-request-gkvds-init-pod | container step-init: \ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;Using in-cluster config\&#34; logger=KubeClient\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;[param] enable: false\&#34;\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128\&#34;\ntime=\&#34;2026-04-21T08:07:22Z\&#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;\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;[param] http-proxy-result-path: /tekton/results/http-proxy\&#34;\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;[param] no-proxy-result-path: /tekton/results/no-proxy\&#34;\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;Cache proxy is disabled in param or in backend\&#34;\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;[result] HTTP PROXY: \&#34;\ntime=\&#34;2026-04-21T08:07:22Z\&#34; level=info msg=\&#34;[result] NO PROXY: \&#34;\n\n pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | init container: prepare\n2026/04/21 08:10:01 Entrypoint initialization\n\n pod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | init container: place-scripts\n2026/04/21 08:10:02 Decoded script /tekton/scripts/script-0-g5m28\n2026/04/21 08:10:02 Decoded script /tekton/scripts/script-1-qv5ww\n2026/04/21 08:10:02 Decoded script /tekton/scripts/script-2-t2hmp\n2026/04/21 08:10:02 Decoded script /tekton/scripts/script-3-9hrxc\n2026/04/21 08:10:02 Decoded script /tekton/scripts/script-4-26ww8\n2026/04/21 08:10:02 Decoded script /tekton/scripts/script-5-8rjgc\n\npod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-introspect: \nArtifact type will be determined by introspection.\nChecking the media type of the OCI artifact...\n[retry] executing: skopeo inspect --raw --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734\nThe media type of the OCI artifact is application/vnd.docker.distribution.manifest.v2+json.\nLooking for image labels that indicate this might be an operator bundle...\n[retry] executing: skopeo inspect --retry-times 3 docker://quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734\nFound 0 matching labels.\nExpecting 3 or more to identify this image as an operator bundle.\nIntrospection concludes that this artifact is of type \&#34;application\&#34;.\n\npod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-generate-container-auth: \nSelecting auth for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734\nUsing token for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox\nAuth json written to \&#34;/auth/auth.json\&#34;.\n\npod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-set-skip-for-bundles: \n2026/04/21 08:10:47 INFO Step was skipped due to when expressions were evaluated to false.\n\npod: test-comp-pac-gitlab-nqglox2b8471cdd39cb634fbb9e97558f54822-pod | container step-app-check: \ntime=\&#34;2026-04-21T08:10:48Z\&#34; level=info msg=\&#34;certification library version\&#34; version=\&#34;1.17.1 &lt;commit: f7de82ae1c76e6c10ea94967d6b6a66f96248cbe&gt;\&#34;\ntime=\&#34;2026-04-21T08:10:48Z\&#34; level=info msg=\&#34;running checks for quay.io/redhat-appstudio-qe/gitlab-rep-flag/test-comp-pac-gitlab-nqglox:on-pr-cdc64b74622eaacc7ce5f90359269456f113f734 for platform amd64\&#34;\ntime=\&#34;2026-04-21T08:10:48Z\&#34; level=info msg=\&#34;target image\&#34; ima...&#xA;&#xA;Gomega truncated this representation as it exceeds &#39;format.MaxLength&#39;.&#xA;Consider having the object provide a custom &#39;GomegaStringer&#39; representation&#xA;or adjust the parameters in Gomega&#39;s &#39;format&#39; package.&#xA;&#xA;Learn more here: https://onsi.github.io/gomega/#adjusting-output&#xA;In [It] at: /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:150 @ 04/21/26 08:11:38.479&#xA;&lt; Exit [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:148 @ 04/21/26 08:11:38.479 (11m43.19s)&#xA;&gt; Enter [AfterAll] Gitlab with status reporting of Integration tests in the assosiated merge request - /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:94 @ 04/21/26 08:11:38.479&#xA;[FAILED] Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc00269a0c0&gt;: &#xA;    failed to get MR of IID 0 in projectID konflux-qe/hacbs-test-project-integration, 404 Not Found&#xA;    {&#xA;        s: &#34;failed to get MR of IID 0 in projectID konflux-qe/hacbs-test-project-integration, 404 Not Found&#34;,&#xA;    }&#xA;In [AfterAll] at: /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:97 @ 04/21/26 08:11:38.665&#xA;&lt; Exit [AfterAll] Gitlab with status reporting of Integration tests in the assosiated merge request - /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:94 @ 04/21/26 08:11:38.665 (186ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 08:11:38.665&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 08:11:38.869 (204ms)&#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="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.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:153 @ 04/21/26 08:11:38.87&#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="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.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:172 @ 04/21/26 08:11:38.87&#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="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.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:179 @ 04/21/26 08:11:38.87&#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="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.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:183 @ 04/21/26 08:11:38.871&#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="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.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:188 @ 04/21/26 08:11:38.871&#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="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.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:194 @ 04/21/26 08:11:38.871&#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="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.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:207 @ 04/21/26 08:11:38.871&#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="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.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:212 @ 04/21/26 08:11:38.871&#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="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.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:229 @ 04/21/26 08:11:38.871&#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="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.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:233 @ 04/21/26 08:11:38.872&#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="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.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:250 @ 04/21/26 08:11:38.872&#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="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.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:254 @ 04/21/26 08:11:38.872&#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="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.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:278 @ 04/21/26 08:11:38.872&#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="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.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:288 @ 04/21/26 08:11:38.872&#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="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.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:303 @ 04/21/26 08:11:38.872&#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="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.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:308 @ 04/21/26 08:11:38.873&#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="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.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:325 @ 04/21/26 08:11:38.873&#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="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.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:329 @ 04/21/26 08:11:38.873&#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="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.DGYK2mBrx2/tests/integration-service/gitlab-integration-reporting.go:346 @ 04/21/26 08:11:38.873&#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="failed" time="922.992542046">
              <failure message="Timed out after 900.000s.&#xA;timed out when waiting for the build PipelineRun to start for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc001720f80&gt;: &#xA;    no pipelinerun found for component test-component-pac-bxblxq&#xA;    {&#xA;        s: &#34;no pipelinerun found for component test-component-pac-bxblxq&#34;,&#xA;    }" type="failed">[FAILED] Timed out after 900.000s.&#xA;timed out when waiting for the build PipelineRun to start for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc001720f80&gt;: &#xA;    no pipelinerun found for component test-component-pac-bxblxq&#xA;    {&#xA;        s: &#34;no pipelinerun found for component test-component-pac-bxblxq&#34;,&#xA;    }&#xA;In [BeforeAll] at: /tmp/tmp.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:86 @ 04/21/26 08:14:06.151&#xA;</failure>
              <system-err>&gt; Enter [BeforeAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:45 @ 04/21/26 07:58:44.065&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Build PipelineRun has not been created yet for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;[FAILED] Timed out after 900.000s.&#xA;timed out when waiting for the build PipelineRun to start for the component stat-rep-cjjl/test-component-pac-bxblxq&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc001720f80&gt;: &#xA;    no pipelinerun found for component test-component-pac-bxblxq&#xA;    {&#xA;        s: &#34;no pipelinerun found for component test-component-pac-bxblxq&#34;,&#xA;    }&#xA;In [BeforeAll] at: /tmp/tmp.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:86 @ 04/21/26 08:14:06.151&#xA;&lt; Exit [BeforeAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:45 @ 04/21/26 08:14:06.151 (15m22.086s)&#xA;&gt; Enter [AfterAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:92 @ 04/21/26 08:14:06.151&#xA;&lt; Exit [AfterAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:92 @ 04/21/26 08:14:06.886 (735ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 08:14:06.886&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 08:14:07.057 (171ms)&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:113 @ 04/21/26 08:14:07.057&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:132 @ 04/21/26 08:14:07.058&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:142 @ 04/21/26 08:14:07.058&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:149 @ 04/21/26 08:14:07.058&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:153 @ 04/21/26 08:14:07.058&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:158 @ 04/21/26 08:14:07.058&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:164 @ 04/21/26 08:14:07.059&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:183 @ 04/21/26 08:14:07.059&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:191 @ 04/21/26 08:14:07.059&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:205 @ 04/21/26 08:14:07.059&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:209 @ 04/21/26 08:14:07.059&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:213 @ 04/21/26 08:14:07.059&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:217 @ 04/21/26 08:14:07.06&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:232 @ 04/21/26 08:14:07.06&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:236 @ 04/21/26 08:14:07.06&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:245 @ 04/21/26 08:14:07.06&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:260 @ 04/21/26 08:14:07.06&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:265 @ 04/21/26 08:14:07.061&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:270 @ 04/21/26 08:14:07.061&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:276 @ 04/21/26 08:14:07.061&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:323 @ 04/21/26 08:14:07.061&#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="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.DGYK2mBrx2/tests/integration-service/status-reporting-to-pullrequest.go:368 @ 04/21/26 08:14:07.061&#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="34.659209718">
              <system-err>&gt; Enter [BeforeAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:60 @ 04/21/26 07:58:44.064&#xA;Successfully acquired repository lock for namespace group-vyrs&#xA;&lt; Exit [BeforeAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:60 @ 04/21/26 07:58:58.581 (14.518s)&#xA;&gt; Enter [It] creates the Component A successfully - /tmp/tmp.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:205 @ 04/21/26 07:58:58.581&#xA;Image repository for component go-component-skzqgr in namespace group-vyrs 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-skzqgr in namespace group-vyrs 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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:205 @ 04/21/26 07:59:18.722 (20.14s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 07:59:18.722&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 07:59:18.722 (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="failed" time="901.744858657">
              <failure message="Timed out after 900.001s.&#xA;timed out when waiting for the build PipelineRun to start for the componentA group-vyrs/go-component-skzqgr&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc000a92920&gt;: &#xA;    no pipelinerun found for component go-component-skzqgr&#xA;    {&#xA;        s: &#34;no pipelinerun found for component go-component-skzqgr&#34;,&#xA;    }" type="failed">[FAILED] Timed out after 900.001s.&#xA;timed out when waiting for the build PipelineRun to start for the componentA group-vyrs/go-component-skzqgr&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc000a92920&gt;: &#xA;    no pipelinerun found for component go-component-skzqgr&#xA;    {&#xA;        s: &#34;no pipelinerun found for component go-component-skzqgr&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:224 @ 04/21/26 08:14:18.723&#xA;</failure>
              <system-err>&gt; Enter [It] triggers a Build PipelineRun for componentA go-component - /tmp/tmp.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:213 @ 04/21/26 07:59:18.723&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;Build PipelineRun has not been created yet for the componentA group-vyrs/go-component-skzqgr&#xA;[FAILED] Timed out after 900.001s.&#xA;timed out when waiting for the build PipelineRun to start for the componentA group-vyrs/go-component-skzqgr&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc000a92920&gt;: &#xA;    no pipelinerun found for component go-component-skzqgr&#xA;    {&#xA;        s: &#34;no pipelinerun found for component go-component-skzqgr&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:224 @ 04/21/26 08:14:18.723&#xA;&lt; Exit [It] triggers a Build PipelineRun for componentA go-component - /tmp/tmp.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:213 @ 04/21/26 08:14:18.723 (15m0.001s)&#xA;&gt; Enter [AfterAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:149 @ 04/21/26 08:14:18.724&#xA;&lt; Exit [AfterAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:149 @ 04/21/26 08:14:20.347 (1.623s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 08:14:20.347&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 08:14:20.467 (120ms)&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:227 @ 04/21/26 08:14:20.468&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:231 @ 04/21/26 08:14:20.468&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:236 @ 04/21/26 08:14:20.468&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:258 @ 04/21/26 08:14:20.469&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:263 @ 04/21/26 08:14:20.469&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:270 @ 04/21/26 08:14:20.469&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:277 @ 04/21/26 08:14:20.469&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:296 @ 04/21/26 08:14:20.469&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:304 @ 04/21/26 08:14:20.47&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:318 @ 04/21/26 08:14:20.47&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:322 @ 04/21/26 08:14:20.47&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:327 @ 04/21/26 08:14:20.47&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:349 @ 04/21/26 08:14:20.47&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:354 @ 04/21/26 08:14:20.471&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:361 @ 04/21/26 08:14:20.471&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:368 @ 04/21/26 08:14:20.471&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:387 @ 04/21/26 08:14:20.471&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:395 @ 04/21/26 08:14:20.471&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:409 @ 04/21/26 08:14:20.472&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:413 @ 04/21/26 08:14:20.472&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:418 @ 04/21/26 08:14:20.472&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:440 @ 04/21/26 08:14:20.472&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:445 @ 04/21/26 08:14:20.472&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:452 @ 04/21/26 08:14:20.472&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:459 @ 04/21/26 08:14:20.473&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:479 @ 04/21/26 08:14:20.473&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:497 @ 04/21/26 08:14:20.473&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:513 @ 04/21/26 08:14:20.473&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:521 @ 04/21/26 08:14:20.473&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:556 @ 04/21/26 08:14:20.474&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:635 @ 04/21/26 08:14:20.474&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:648 @ 04/21/26 08:14:20.474&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:654 @ 04/21/26 08:14:20.474&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:663 @ 04/21/26 08:14:20.474&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:690 @ 04/21/26 08:14:20.475&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:720 @ 04/21/26 08:14:20.475&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:740 @ 04/21/26 08:14:20.475&#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="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.DGYK2mBrx2/tests/integration-service/group-snapshots-tests.go:780 @ 04/21/26 08:14:20.475&#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 triggers a build PipelineRun [integration-service]" classname="Red Hat App Studio E2E tests" status="failed" time="1224.115963006">
              <failure message="Unexpected error:&#xA;    &lt;context.deadlineExceededError&gt;: &#xA;    context deadline exceeded&#xA;    {}&#xA;occurred" type="failed">[FAILED] Unexpected error:&#xA;    &lt;context.deadlineExceededError&gt;: &#xA;    context deadline exceeded&#xA;    {}&#xA;occurred&#xA;In [It] at: /tmp/tmp.DGYK2mBrx2/tests/integration-service/integration.go:87 @ 04/21/26 08:19:07.178&#xA;</failure>
              <system-err>&gt; Enter [BeforeAll] with happy path for general flow of Integration service - /tmp/tmp.DGYK2mBrx2/tests/integration-service/integration.go:52 @ 04/21/26 07:58:44.17&#xA;&lt; Exit [BeforeAll] with happy path for general flow of Integration service - /tmp/tmp.DGYK2mBrx2/tests/integration-service/integration.go:52 @ 04/21/26 07:59:07.177 (23.006s)&#xA;&gt; Enter [It] triggers a build PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/integration-service/integration.go:85 @ 04/21/26 07:59:07.177&#xA;no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)no pipelinerun found for component test-component-pac-mkuohq (application: integ-app-tzfo, namespace: integration1-hbvq)&#xA;[FAILED] Unexpected error:&#xA;    &lt;context.deadlineExceededError&gt;: &#xA;    context deadline exceeded&#xA;    {}&#xA;occurred&#xA;In [It] at: /tmp/tmp.DGYK2mBrx2/tests/integration-service/integration.go:87 @ 04/21/26 08:19:07.178&#xA;&lt; Exit [It] triggers a build PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/integration-service/integration.go:85 @ 04/21/26 08:19:07.178 (20m0.001s)&#xA;&gt; Enter [AfterAll] with happy path for general flow of Integration service - /tmp/tmp.DGYK2mBrx2/tests/integration-service/integration.go:68 @ 04/21/26 08:19:07.179&#xA;&lt; Exit [AfterAll] with happy path for general flow of Integration service - /tmp/tmp.DGYK2mBrx2/tests/integration-service/integration.go:68 @ 04/21/26 08:19:08.042 (864ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/integration-service/integration.go:49 @ 04/21/26 08:19:08.043&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/integration-service/integration.go:49 @ 04/21/26 08:19:08.286 (243ms)&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:90 @ 04/21/26 08:19:08.287&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:101 @ 04/21/26 08:19:08.287&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:107 @ 04/21/26 08:19:08.287&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:128 @ 04/21/26 08:19:08.287&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:132 @ 04/21/26 08:19:08.288&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:137 @ 04/21/26 08:19:08.288&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:141 @ 04/21/26 08:19:08.288&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:154 @ 04/21/26 08:19:08.288&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:158 @ 04/21/26 08:19:08.288&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:173 @ 04/21/26 08:19:08.289&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:183 @ 04/21/26 08:19:08.289&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:188 @ 04/21/26 08:19:08.289&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:198 @ 04/21/26 08:19:08.289&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:205 @ 04/21/26 08:19:08.289&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:218 @ 04/21/26 08:19:08.289&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:222 @ 04/21/26 08:19:08.29&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:266 @ 04/21/26 08:19:08.29&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:273 @ 04/21/26 08:19:08.29&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:292 @ 04/21/26 08:19:08.29&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:296 @ 04/21/26 08:19:08.29&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:301 @ 04/21/26 08:19:08.291&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:305 @ 04/21/26 08:19:08.291&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:309 @ 04/21/26 08:19:08.291&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:324 @ 04/21/26 08:19:08.291&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:334 @ 04/21/26 08:19:08.291&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:340 @ 04/21/26 08:19:08.292&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:344 @ 04/21/26 08:19:08.292&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:349 @ 04/21/26 08:19:08.292&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:358 @ 04/21/26 08:19:08.292&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:364 @ 04/21/26 08:19:08.292&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:378 @ 04/21/26 08:19:08.292&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:382 @ 04/21/26 08:19:08.293&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:399 @ 04/21/26 08:19:08.293&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:406 @ 04/21/26 08:19:08.293&#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="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.DGYK2mBrx2/tests/integration-service/integration.go:413 @ 04/21/26 08:19:08.293&#xA;</system-err>
          </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-hkon [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="failed" time="1369.739037455">
              <failure message="Timed out after 1200.000s.&#xA;timed out when waiting for the PipelineRun to start for the Component build-e2e-wils/test-symlink-comp-hkon&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc001781550&gt;: &#xA;    no pipelinerun found for component test-symlink-comp-hkon&#xA;    {&#xA;        s: &#34;no pipelinerun found for component test-symlink-comp-hkon&#34;,&#xA;    }" type="failed">[FAILED] Timed out after 1200.000s.&#xA;timed out when waiting for the PipelineRun to start for the Component build-e2e-wils/test-symlink-comp-hkon&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc001781550&gt;: &#xA;    no pipelinerun found for component test-symlink-comp-hkon&#xA;    {&#xA;        s: &#34;no pipelinerun found for component test-symlink-comp-hkon&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.DGYK2mBrx2/tests/build/build_templates.go:200 @ 04/21/26 08:20:33.49&#xA;&#xA;There were additional failures detected after the initial failure. These are visible in the timeline&#xA;</failure>
              <system-err>&gt; Enter [BeforeAll] HACBS pipelines - /tmp/tmp.DGYK2mBrx2/tests/build/build_templates.go:237 @ 04/21/26 07:58:44.068&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;found credentials for image ref quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1776758335-fjky -&gt; user: redhat-appstudio-qe+redhat_appstudio_quality&#34;&#xA;Image repository for component test-comp-enlm in namespace build-e2e-wils 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-enlm, repo: https://github.com/redhat-appstudio-qe/devfile-sample-python-basic, baseBranchName: base-ghzjon, pacBranchName: konflux-test-comp-enlm&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;found credentials for image ref quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1776758357-ravr -&gt; user: redhat-appstudio-qe+redhat_appstudio_quality&#34;&#xA;Image repository for component test-comp-zfcf in namespace build-e2e-wils 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-zfcf, repo: https://github.com/redhat-appstudio-qe/devfile-sample-python-basic, baseBranchName: base-sxkach, pacBranchName: konflux-test-comp-zfcf&#xA;&#34;level&#34;=0 &#34;msg&#34;=&#34;found credentials for image ref quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1776758380-bobq -&gt; user: redhat-appstudio-qe+redhat_appstudio_quality&#34;&#xA;Image repository for component test-comp-xbyd in namespace build-e2e-wils 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-xbyd, repo: https://github.com/redhat-appstudio-qe/devfile-sample-python-basic, baseBranchName: base-glwtjs, pacBranchName: konflux-test-comp-xbyd&#xA;Image repository for component test-symlink-comp-hkon in namespace build-e2e-wils do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component test-symlink-comp-hkon in namespace build-e2e-wils 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-hkon, repo: https://github.com/redhat-appstudio-qe/devfile-sample-python-basic, baseBranchName: base-vwijvj, pacBranchName: konflux-test-symlink-comp-hkon&#xA;&lt; Exit [BeforeAll] HACBS pipelines - /tmp/tmp.DGYK2mBrx2/tests/build/build_templates.go:237 @ 04/21/26 08:00:33.49 (1m49.421s)&#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-hkon - /tmp/tmp.DGYK2mBrx2/tests/build/build_templates.go:325 @ 04/21/26 08:00:33.49&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;PipelineRun has not been created yet for Component build-e2e-wils/test-symlink-comp-hkon&#xA;[FAILED] Timed out after 1200.000s.&#xA;timed out when waiting for the PipelineRun to start for the Component build-e2e-wils/test-symlink-comp-hkon&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc001781550&gt;: &#xA;    no pipelinerun found for component test-symlink-comp-hkon&#xA;    {&#xA;        s: &#34;no pipelinerun found for component test-symlink-comp-hkon&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.DGYK2mBrx2/tests/build/build_templates.go:200 @ 04/21/26 08:20:33.49&#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-hkon - /tmp/tmp.DGYK2mBrx2/tests/build/build_templates.go:325 @ 04/21/26 08:20:33.49 (20m0.001s)&#xA;&gt; Enter [AfterAll] HACBS pipelines - /tmp/tmp.DGYK2mBrx2/tests/build/build_templates.go:271 @ 04/21/26 08:20:33.491&#xA;error while getting pipelineruns: no pipelinerun found for application test-app-fdjqerror while getting pipelineruns: no pipelinerun found for application test-app-fdjqerror while getting pipelineruns: no pipelinerun found for application test-app-fdjqerror while getting pipelineruns: no pipelinerun found for application test-app-fdjqerror while getting pipelineruns: no pipelinerun found for application test-app-fdjqerror while getting pipelineruns: no pipelinerun found for application test-app-fdjq&#xA;[FAILED] Timed out after 60.000s.&#xA;timed out when trying to remove the e2e-test finalizer from pipelineruns&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc0022182e0&gt;: &#xA;    no pipelinerun found for application test-app-fdjq&#xA;    {&#xA;        s: &#34;no pipelinerun found for application test-app-fdjq&#34;,&#xA;    }&#xA;In [AfterAll] at: /tmp/tmp.DGYK2mBrx2/tests/build/build_templates.go:289 @ 04/21/26 08:21:33.491&#xA;&lt; Exit [AfterAll] HACBS pipelines - /tmp/tmp.DGYK2mBrx2/tests/build/build_templates.go:271 @ 04/21/26 08:21:33.491 (1m0.001s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.DGYK2mBrx2/tests/build/build_templates.go:207 @ 04/21/26 08:21:33.492&#xA;&lt; Exit [AfterEach] [build-service-suite Build templates E2E test] - /tmp/tmp.DGYK2mBrx2/tests/build/build_templates.go:207 @ 04/21/26 08:21:33.807 (315ms)&#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="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.DGYK2mBrx2/tests/build/build_templates.go:338 @ 04/21/26 08:21:33.808&#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="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.DGYK2mBrx2/tests/build/build_templates.go:338 @ 04/21/26 08:21:33.808&#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="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.DGYK2mBrx2/tests/build/build_templates.go:338 @ 04/21/26 08:21:33.808&#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="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.DGYK2mBrx2/tests/build/build_templates.go:356 @ 04/21/26 08:21:33.809&#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="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.DGYK2mBrx2/tests/build/build_templates.go:366 @ 04/21/26 08:21:33.809&#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">
              <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.DGYK2mBrx2/tests/build/build_templates.go:378 @ 04/21/26 08:21:33.809&#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="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.DGYK2mBrx2/tests/build/build_templates.go:395 @ 04/21/26 08:21:33.809&#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">
              <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.DGYK2mBrx2/tests/build/build_templates.go:420 @ 04/21/26 08:21:33.809&#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="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.DGYK2mBrx2/tests/build/build_templates.go:498 @ 04/21/26 08:21:33.81&#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="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.DGYK2mBrx2/tests/build/build_templates.go:540 @ 04/21/26 08:21:33.81&#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">
              <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.DGYK2mBrx2/tests/build/build_templates.go:661 @ 04/21/26 08:21:33.81&#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="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.DGYK2mBrx2/tests/build/build_templates.go:356 @ 04/21/26 08:21:33.811&#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="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.DGYK2mBrx2/tests/build/build_templates.go:366 @ 04/21/26 08:21:33.811&#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">
              <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.DGYK2mBrx2/tests/build/build_templates.go:378 @ 04/21/26 08:21:33.811&#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="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.DGYK2mBrx2/tests/build/build_templates.go:395 @ 04/21/26 08:21:33.811&#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">
              <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.DGYK2mBrx2/tests/build/build_templates.go:420 @ 04/21/26 08:21:33.812&#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="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.DGYK2mBrx2/tests/build/build_templates.go:498 @ 04/21/26 08:21:33.812&#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="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.DGYK2mBrx2/tests/build/build_templates.go:540 @ 04/21/26 08:21:33.812&#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">
              <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.DGYK2mBrx2/tests/build/build_templates.go:661 @ 04/21/26 08:21:33.813&#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="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.DGYK2mBrx2/tests/build/build_templates.go:356 @ 04/21/26 08:21:33.813&#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">
              <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.DGYK2mBrx2/tests/build/build_templates.go:366 @ 04/21/26 08:21:33.813&#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">
              <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.DGYK2mBrx2/tests/build/build_templates.go:378 @ 04/21/26 08:21:33.813&#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="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.DGYK2mBrx2/tests/build/build_templates.go:395 @ 04/21/26 08:21:33.814&#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">
              <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.DGYK2mBrx2/tests/build/build_templates.go:420 @ 04/21/26 08:21:33.814&#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="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.DGYK2mBrx2/tests/build/build_templates.go:498 @ 04/21/26 08:21:33.814&#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="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.DGYK2mBrx2/tests/build/build_templates.go:540 @ 04/21/26 08:21:33.814&#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">
              <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.DGYK2mBrx2/tests/build/build_templates.go:661 @ 04/21/26 08:21:33.815&#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-hkon [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped - 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.DGYK2mBrx2/tests/build/build_templates.go:816 @ 04/21/26 08:21:33.815&#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 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="70.527159823">
              <system-err>&gt; Enter [BeforeAll] PaC component build - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:54 @ 04/21/26 07:58:44.261&#xA;&lt; Exit [BeforeAll] PaC component build - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:54 @ 04/21/26 07:59:08.85 (24.589s)&#xA;&gt; Enter [BeforeAll] when a new component without specified branch is created and with visibility private - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:117 @ 04/21/26 07:59:08.85&#xA;Image repository for component gl-test-custom-default-faramn in namespace build-e2e-uicq 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.DGYK2mBrx2/tests/build/pac_build.go:117 @ 04/21/26 07:59:28.91 (20.059s)&#xA;&gt; Enter [It] correctly targets the default branch (that is not named &#39;main&#39;) with PaC - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:136 @ 04/21/26 07:59:28.91&#xA;&lt; Exit [It] correctly targets the default branch (that is not named &#39;main&#39;) with PaC - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:136 @ 04/21/26 07:59:54.788 (25.878s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 07:59:54.788&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 07:59:54.788 (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.013172212">
              <system-err>&gt; Enter [It] workspace parameter is set correctly in PaC repository CR - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:153 @ 04/21/26 07:59:54.789&#xA;&lt; Exit [It] workspace parameter is set correctly in PaC repository CR - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:153 @ 04/21/26 07:59:54.802 (13ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 07:59:54.802&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 07:59:54.802 (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.028153172">
              <system-err>&gt; Enter [It] triggers a PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:176 @ 04/21/26 07:59:54.802&#xA;PipelineRun has not been created yet for the component build-e2e-uicq/gl-test-custom-branch-zjmuzc&#xA;&lt; Exit [It] triggers a PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:176 @ 04/21/26 08:00:14.83 (20.028s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:14.83&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:14.83 (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.000265707">
              <system-err>&gt; Enter [It] build pipeline uses the correct serviceAccount - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:191 @ 04/21/26 08:00:14.831&#xA;&lt; Exit [It] build pipeline uses the correct serviceAccount - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:191 @ 04/21/26 08:00:14.831 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:14.831&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:14.831 (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.012192966">
              <system-err>&gt; Enter [It] component build status is set correctly - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:195 @ 04/21/26 08:00:14.831&#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-ibbjka/-/merge_requests/1&#34;,&#34;configuration-time&#34;:&#34;Tue, 21 Apr 2026 07:59:50 UTC&#34;},&#34;message&#34;:&#34;done&#34;}&#xA;state: enabled&#xA;mergeUrl: https://gitlab.com/konflux-qe/devfile-sample-hello-world-ibbjka/-/merge_requests/1&#xA;errId: 0&#xA;errMessage: &#xA;configurationTime: Tue, 21 Apr 2026 07:59:50 UTC&#xA;&lt; Exit [It] component build status is set correctly - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:195 @ 04/21/26 08:00:14.843 (12ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:14.843&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:14.843 (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="1.136652195">
              <system-err>&gt; Enter [It] image repo and robot account created successfully - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:225 @ 04/21/26 08:00:14.844&#xA;&lt; Exit [It] image repo and robot account created successfully - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:225 @ 04/21/26 08:00:15.98 (1.136s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:15.98&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:15.98 (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.279562263">
              <system-err>&gt; Enter [It] created image repo is private - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:243 @ 04/21/26 08:00:15.981&#xA;&lt; Exit [It] created image repo is private - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:243 @ 04/21/26 08:00:16.26 (279ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:16.26&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:16.26 (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="21.214184399">
              <system-err>&gt; Enter [It] a related PipelineRun should be deleted after deleting the component - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:249 @ 04/21/26 08:00:16.261&#xA;&lt; Exit [It] a related PipelineRun should be deleted after deleting the component - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:249 @ 04/21/26 08:00:37.475 (21.214s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:37.475&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:37.475 (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="0.148127751">
              <system-err>&gt; Enter [It] PR branch should not exist in the repo - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:265 @ 04/21/26 08:00:37.475&#xA;&lt; Exit [It] PR branch should not exist in the repo - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:265 @ 04/21/26 08:00:37.623 (148ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:37.623&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:37.623 (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="5.940516572">
              <system-err>&gt; Enter [It] related image repo and the robot account should be deleted after deleting the component - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:278 @ 04/21/26 08:00:37.624&#xA;&lt; Exit [It] related image repo and the robot account should be deleted after deleting the component - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:278 @ 04/21/26 08:00:43.564 (5.94s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:43.564&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:00:43.564 (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="210.18874019">
              <system-err>&gt; Enter [BeforeAll] when a new Component with specified custom branch is created - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:306 @ 04/21/26 08:00:43.565&#xA;&lt; Exit [BeforeAll] when a new Component with specified custom branch is created - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:306 @ 04/21/26 08:00:53.596 (10.032s)&#xA;&gt; Enter [It] triggers a PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:332 @ 04/21/26 08:00:53.597&#xA;PipelineRun has not been created yet for the component build-e2e-uicq/gl-test-custom-branch-zjmuzc&#xA;PipelineRun has not been created yet for the component build-e2e-uicq/gl-test-custom-branch-zjmuzc&#xA;PipelineRun has not been created yet for the component build-e2e-uicq/gl-test-custom-branch-zjmuzc&#xA;PipelineRun has not been created yet for the component build-e2e-uicq/gl-test-custom-branch-zjmuzc&#xA;PipelineRun has not been created yet for the component build-e2e-uicq/gl-test-custom-branch-zjmuzc&#xA;PipelineRun has not been created yet for the component build-e2e-uicq/gl-test-custom-branch-zjmuzc&#xA;PipelineRun has not been created yet for the component build-e2e-uicq/gl-test-custom-branch-zjmuzc&#xA;PipelineRun has not been created yet for the component build-e2e-uicq/gl-test-custom-branch-zjmuzc&#xA;PipelineRun has not been created yet for the component build-e2e-uicq/gl-test-custom-branch-zjmuzc&#xA;PipelineRun has not been created yet for the component build-e2e-uicq/gl-test-custom-branch-zjmuzc&#xA;&lt; Exit [It] triggers a PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:332 @ 04/21/26 08:04:13.753 (3m20.156s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:04:13.753&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:04:13.753 (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.257778108">
              <system-err>&gt; Enter [It] should lead to a PaC init PR creation - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:347 @ 04/21/26 08:04:13.754&#xA;&lt; Exit [It] should lead to a PaC init PR creation - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:347 @ 04/21/26 08:04:14.011 (257ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:04:14.011&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:04:14.012 (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="411.061826359">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:365 @ 04/21/26 08:04:14.012&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-nrh9c found for Component build-e2e-uicq/gl-test-custom-branch-zjmuzc&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-nrh9c reason: Cancelled&#xA;an error happened during storing pipelineRun log build-e2e-uicq:gl-test-custom-branch-zjmuzc-on-pull-request-nrh9c: container &#34;step-init&#34; in pod &#34;gl-test-custom-branch-zjmuzc-on-pull-request-tpg78-init-pod&#34; is waiting to start: PodInitializing&#xA;failed to get logs for PipelineRun build-e2e-uicq:gl-test-custom-branch-zjmuzc-on-pull-request-nrh9c: container &#34;step-init&#34; in pod &#34;gl-test-custom-branch-zjmuzc-on-pull-request-tpg78-init-pod&#34; is waiting to start: PodInitializing&#xA;attempt 1/3: PipelineRun &#34;gl-test-custom-branch-zjmuzc-on-pull-request-nrh9c&#34; failed: &#xA; pod: gl-test-custom-branch-zjmuzc-on-pull-request-tpg78-init-pod | init container: prepare&#xA;2026/04/21 08:04:13 Entrypoint initialization&#xA;&#xA;pod: gl-test-custom-branch-zjmuzc-on-pull-request-tpg78-init-pod | container step-init: &#xA;New PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k found after retrigger for component build-e2e-uicq/gl-test-custom-branch-zjmuzc&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k found for Component build-e2e-uicq/gl-test-custom-branch-zjmuzc&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-67k5k reason: Succeeded&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:365 @ 04/21/26 08:11:05.074 (6m51.061s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:05.074&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:05.074 (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.88834585">
              <system-err>&gt; Enter [It] image repo and robot account created successfully - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:371 @ 04/21/26 08:11:05.075&#xA;&lt; Exit [It] image repo and robot account created successfully - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:371 @ 04/21/26 08:11:05.963 (888ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:05.963&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:05.963 (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.286418861">
              <system-err>&gt; Enter [It] created image repo is public - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:390 @ 04/21/26 08:11:05.963&#xA;&lt; Exit [It] created image repo is public - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:390 @ 04/21/26 08:11:06.249 (286ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:06.25&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:06.25 (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.33697464">
              <system-err>&gt; Enter [It] image tag is updated successfully - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:396 @ 04/21/26 08:11:06.25&#xA;Image tag quay.io/redhat-appstudio-qe/build-e2e-uicq/gl-test-custom-branch-zjmuzc:on-pr-2645818a190f3007adaf5d28bcd1909eb7568094 successfully found in Quay&#xA;&lt; Exit [It] image tag is updated successfully - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:396 @ 04/21/26 08:11:06.587 (336ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:06.587&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:06.587 (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.711106142">
              <system-err>&gt; Enter [It] should ensure pruning labels are set - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:425 @ 04/21/26 08:11:06.588&#xA;&lt; Exit [It] should ensure pruning labels are set - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:425 @ 04/21/26 08:11:07.299 (711ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:07.299&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:07.299 (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.469774169">
              <system-err>&gt; Enter [It] eventually leads to the PipelineRun status report at Checks tab - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:439 @ 04/21/26 08:11:07.3&#xA;&lt; Exit [It] eventually leads to the PipelineRun status report at Checks tab - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:439 @ 04/21/26 08:11:07.617 (317ms)&#xA;&gt; Enter [AfterAll] when a new Component with specified custom branch is created - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:324 @ 04/21/26 08:11:07.617&#xA;&lt; Exit [AfterAll] when a new Component with specified custom branch is created - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:324 @ 04/21/26 08:11:07.769 (152ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:07.769&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:07.769 (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="21.024286798">
              <system-err>&gt; Enter [BeforeAll] when the PaC init branch is updated - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:454 @ 04/21/26 08:11:07.77&#xA;created file sha: 8d7144a55817de12c628d02bb45f3cc00eda7654&#xA;&lt; Exit [BeforeAll] when the PaC init branch is updated - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:454 @ 04/21/26 08:11:08.773 (1.003s)&#xA;&gt; Enter [It] eventually leads to triggering another PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:464 @ 04/21/26 08:11:08.773&#xA;PipelineRun has not been created yet for the component build-e2e-uicq/gl-test-custom-branch-zjmuzc&#xA;&lt; Exit [It] eventually leads to triggering another PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:464 @ 04/21/26 08:11:28.794 (20.02s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:28.794&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:28.794 (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.21319864">
              <system-err>&gt; Enter [It] should lead to a PaC init PR update - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:479 @ 04/21/26 08:11:28.794&#xA;&lt; Exit [It] should lead to a PaC init PR update - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:479 @ 04/21/26 08:11:29.007 (213ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:29.007&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:11:29.008 (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="280.013537363">
              <system-err>&gt; Enter [It] PipelineRun should eventually finish - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:498 @ 04/21/26 08:11:29.008&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-68zfx found for Component build-e2e-uicq/gl-test-custom-branch-zjmuzc&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-68zfx reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-68zfx reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-68zfx reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-68zfx reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-68zfx reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-68zfx reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-68zfx reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-68zfx reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-68zfx reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-68zfx reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-68zfx reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-68zfx reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-68zfx reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-68zfx reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-pull-request-68zfx reason: Succeeded&#xA;&lt; Exit [It] PipelineRun should eventually finish - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:498 @ 04/21/26 08:16:09.021 (4m40.013s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:16:09.021&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:16:09.021 (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.407824005">
              <system-err>&gt; Enter [It] eventually leads to another update of a PR about the PipelineRun status report at Checks tab - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:504 @ 04/21/26 08:16:09.022&#xA;&lt; Exit [It] eventually leads to another update of a PR about the PipelineRun status report at Checks tab - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:504 @ 04/21/26 08:16:09.429 (407ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:16:09.43&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:16:09.43 (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="22.381807497">
              <system-err>&gt; Enter [BeforeAll] when the PaC init branch is merged - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:520 @ 04/21/26 08:16:09.43&#xA;merged result sha: bec2f411f12377de1ad89c634d3644de5710b3c6&#xA;&lt; Exit [BeforeAll] when the PaC init branch is merged - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:520 @ 04/21/26 08:16:11.791 (2.361s)&#xA;&gt; Enter [It] eventually leads to triggering another PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:530 @ 04/21/26 08:16:11.791&#xA;PipelineRun has not been created yet for the component build-e2e-uicq/gl-test-custom-branch-zjmuzc&#xA;&lt; Exit [It] eventually leads to triggering another PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:530 @ 04/21/26 08:16:31.812 (20.02s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:16:31.812&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:16:31.812 (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.016279314">
              <system-err>&gt; Enter [It] pipelineRun should eventually finish - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:546 @ 04/21/26 08:16:31.812&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-push-2xprq found for Component build-e2e-uicq/gl-test-custom-branch-zjmuzc&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-push-2xprq reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-push-2xprq reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-push-2xprq reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-push-2xprq reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-push-2xprq reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-push-2xprq reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-push-2xprq reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-push-2xprq reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-push-2xprq reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-push-2xprq reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-push-2xprq reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-push-2xprq reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-push-2xprq reason: Running&#xA;PipelineRun gl-test-custom-branch-zjmuzc-on-push-2xprq reason: Succeeded&#xA;&lt; Exit [It] pipelineRun should eventually finish - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:546 @ 04/21/26 08:20:51.828 (4m20.016s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:20:51.829&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:20:51.829 (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.551217599">
              <system-err>&gt; Enter [It] does not have expiration set - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:552 @ 04/21/26 08:20:51.829&#xA;&lt; Exit [It] does not have expiration set - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:552 @ 04/21/26 08:20:52.38 (551ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:20:52.38&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:20:52.38 (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="122.237996759">
              <system-err>&gt; Enter [It] After updating image visibility to private, it should not trigger another PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:564 @ 04/21/26 08:20:52.381&#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.DGYK2mBrx2/tests/build/pac_build.go:564 @ 04/21/26 08:22:54.618 (2m2.237s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:22:54.619&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:22:54.619 (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.316669182">
              <system-err>&gt; Enter [It] image repo is updated to private - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:595 @ 04/21/26 08:22:54.619&#xA;&lt; Exit [It] image repo is updated to private - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:595 @ 04/21/26 08:22:54.935 (316ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:22:54.936&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:22:54.936 (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 and recreated (with the same name in the same namespace) should no longer lead to a creation of a PaC PR [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="26.563056821">
              <system-err>&gt; Enter [BeforeAll] when the component is removed and recreated (with the same name in the same namespace) - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:650 @ 04/21/26 08:22:54.937&#xA;&lt; Exit [BeforeAll] when the component is removed and recreated (with the same name in the same namespace) - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:650 @ 04/21/26 08:22:58.189 (3.252s)&#xA;&gt; Enter [BeforeAll] when the component is removed and recreated (with the same name in the same namespace) - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:679 @ 04/21/26 08:22:58.189&#xA;&lt; Exit [BeforeAll] when the component is removed and recreated (with the same name in the same namespace) - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:679 @ 04/21/26 08:23:08.217 (10.028s)&#xA;&gt; Enter [It] should no longer lead to a creation of a PaC PR - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:715 @ 04/21/26 08:23:08.218&#xA;&lt; Exit [It] should no longer lead to a creation of a PaC PR - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:715 @ 04/21/26 08:23:18.219 (10.001s)&#xA;&gt; Enter [AfterAll] when the component is removed and recreated (with the same name in the same namespace) - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:697 @ 04/21/26 08:23:18.219&#xA;Found purge PR with id: 3&#xA;&lt; Exit [AfterAll] when the component is removed and recreated (with the same name in the same namespace) - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:697 @ 04/21/26 08:23:18.362 (143ms)&#xA;&gt; Enter [AfterAll] PaC component build - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:101 @ 04/21/26 08:23:18.362&#xA;&lt; Exit [AfterAll] PaC component build - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:101 @ 04/21/26 08:23:21.499 (3.137s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:23:21.5&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:23:21.5 (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] [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="84.325671121">
              <system-err>&gt; Enter [BeforeAll] component update with renovate - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:72 @ 04/21/26 07:58:44.062&#xA;ReleaseAdmissionPlan data: {&#34;Mapping&#34;:{&#34;Components&#34;:[{&#34;Name&#34;:&#34;gl-multi-component-parent-juon&#34;,&#34;Repository&#34;:&#34;quay.io/redhat-appstudio-qe/release-repository&#34;}]}}&#xA;&lt; Exit [BeforeAll] component update with renovate - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:72 @ 04/21/26 07:59:38.243 (54.181s)&#xA;&gt; Enter [It] creates component with nudges - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:235 @ 04/21/26 07:59:38.244&#xA;Image repository for component gl-multi-component-parent-juon in namespace build-e2e-dmfx 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-juon in namespace build-e2e-dmfx 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.DGYK2mBrx2/tests/build/renovate.go:235 @ 04/21/26 08:00:08.388 (30.144s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:00:08.388&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:00:08.388 (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="80.05541611">
              <system-err>&gt; Enter [It] triggers a PipelineRun for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:259 @ 04/21/26 08:00:08.389&#xA;PipelineRun has not been created yet for the component build-e2e-dmfx/gl-multi-component-parent-juon&#xA;PipelineRun has not been created yet for the component build-e2e-dmfx/gl-multi-component-parent-juon&#xA;PipelineRun has not been created yet for the component build-e2e-dmfx/gl-multi-component-parent-juon&#xA;PipelineRun has not been created yet for the component build-e2e-dmfx/gl-multi-component-parent-juon&#xA;&lt; Exit [It] triggers a PipelineRun for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:259 @ 04/21/26 08:01:28.444 (1m20.055s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:01:28.444&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:01:28.444 (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="731.204400576">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:274 @ 04/21/26 08:01:28.444&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 found for Component build-e2e-dmfx/gl-multi-component-parent-juon&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-5s929 reason: Failed&#xA;attempt 1/3: PipelineRun &#34;gl-multi-component-parent-juon-on-pull-request-5s929&#34; failed: &#xA; pod: gl-multi-component-parent-juon-on-pull-request-5s929-init-pod | init container: prepare&#xA;2026/04/21 08:01:30 Entrypoint initialization&#xA;&#xA;pod: gl-multi-component-parent-juon-on-pull-request-5s929-init-pod | container step-init: &#xA;time=&#34;2026-04-21T08:01:33Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-21T08:01:33Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-21T08:01:33Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-21T08:01:33Z&#34; level=info msg=&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai&#34;&#xA;time=&#34;2026-04-21T08:01:33Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-21T08:01:33Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-21T08:01:33Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;time=&#34;2026-04-21T08:01:33Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-21T08:01:33Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;New PipelineRun gl-multi-component-parent-juon-on-pull-request-4rpv6 found after retrigger for component build-e2e-dmfx/gl-multi-component-parent-juon&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-4rpv6 found for Component build-e2e-dmfx/gl-multi-component-parent-juon&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-4rpv6 reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-4rpv6 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-4rpv6 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-4rpv6 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-4rpv6 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-4rpv6 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-4rpv6 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-4rpv6 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-4rpv6 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-4rpv6 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-4rpv6 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-4rpv6 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-4rpv6 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-4rpv6 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-4rpv6 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-pull-request-4rpv6 reason: Succeeded&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:274 @ 04/21/26 08:13:39.649 (12m11.204s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:13:39.649&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:13:39.649 (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="271.219378789">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for child component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:285 @ 04/21/26 08:13:39.649&#xA;PipelineRun gl-multi-component-child-juon-on-pull-request-94r2k found for Component build-e2e-dmfx/gl-multi-component-child-juon&#xA;PipelineRun gl-multi-component-child-juon-on-pull-request-94r2k reason: Failed&#xA;attempt 1/3: PipelineRun &#34;gl-multi-component-child-juon-on-pull-request-94r2k&#34; failed: &#xA; pod: gl-multi-component-child-juon-on-pull-request-94r2k-init-pod | init container: prepare&#xA;2026/04/21 08:00:55 Entrypoint initialization&#xA;&#xA;pod: gl-multi-component-child-juon-on-pull-request-94r2k-init-pod | container step-init: &#xA;time=&#34;2026-04-21T08:00:57Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-21T08:00:57Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-21T08:00:57Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-21T08:00:57Z&#34; level=info msg=&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai&#34;&#xA;time=&#34;2026-04-21T08:00:57Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-21T08:00:57Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-21T08:00:57Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;time=&#34;2026-04-21T08:00:57Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-21T08:00:57Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;New PipelineRun gl-multi-component-child-juon-on-pull-request-4bxr6 found after retrigger for component build-e2e-dmfx/gl-multi-component-child-juon&#xA;PipelineRun gl-multi-component-child-juon-on-pull-request-4bxr6 found for Component build-e2e-dmfx/gl-multi-component-child-juon&#xA;PipelineRun gl-multi-component-child-juon-on-pull-request-4bxr6 reason: Running&#xA;PipelineRun gl-multi-component-child-juon-on-pull-request-4bxr6 reason: Running&#xA;PipelineRun gl-multi-component-child-juon-on-pull-request-4bxr6 reason: Running&#xA;PipelineRun gl-multi-component-child-juon-on-pull-request-4bxr6 reason: Running&#xA;PipelineRun gl-multi-component-child-juon-on-pull-request-4bxr6 reason: Running&#xA;PipelineRun gl-multi-component-child-juon-on-pull-request-4bxr6 reason: Running&#xA;PipelineRun gl-multi-component-child-juon-on-pull-request-4bxr6 reason: Running&#xA;PipelineRun gl-multi-component-child-juon-on-pull-request-4bxr6 reason: Running&#xA;PipelineRun gl-multi-component-child-juon-on-pull-request-4bxr6 reason: Running&#xA;PipelineRun gl-multi-component-child-juon-on-pull-request-4bxr6 reason: Running&#xA;PipelineRun gl-multi-component-child-juon-on-pull-request-4bxr6 reason: Running&#xA;PipelineRun gl-multi-component-child-juon-on-pull-request-4bxr6 reason: Running&#xA;PipelineRun gl-multi-component-child-juon-on-pull-request-4bxr6 reason: Running&#xA;PipelineRun gl-multi-component-child-juon-on-pull-request-4bxr6 reason: Succeeded&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for child component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:285 @ 04/21/26 08:18:10.868 (4m31.219s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:18:10.869&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:18:10.869 (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.240240301">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for child component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:289 @ 04/21/26 08:18:10.869&#xA;&lt; Exit [It] should lead to a PaC PR creation for child component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:289 @ 04/21/26 08:18:11.109 (240ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:18:11.109&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:18:11.109 (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.461686937">
              <system-err>&gt; Enter [It] Merging the PaC PR should be successful for child component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:307 @ 04/21/26 08:18:11.11&#xA;merged result sha: d162946a3de99685ad4e771d4d348212be3f35f8 for PR #1&#xA;&lt; Exit [It] Merging the PaC PR should be successful for child component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:307 @ 04/21/26 08:18:12.571 (1.461s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:18:12.571&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:18:12.572 (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.628590927">
              <system-err>&gt; Enter [It] create dockerfile and yaml manifest that references build and distribution repositories - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:318 @ 04/21/26 08:18:12.572&#xA;&lt; Exit [It] create dockerfile and yaml manifest that references build and distribution repositories - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:318 @ 04/21/26 08:19:18.2 (1m5.628s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:19:18.2&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:19:18.201 (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.258465279">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:358 @ 04/21/26 08:19:18.201&#xA;&lt; Exit [It] should lead to a PaC PR creation for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:358 @ 04/21/26 08:19:18.459 (258ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:19:18.459&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:19:18.459 (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.201085639">
              <system-err>&gt; Enter [It] Merging the PaC PR should be successful for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:375 @ 04/21/26 08:19:18.46&#xA;merged result sha: e520821b41fcaca08875ed887f22a7e64464b30a for PR #1&#xA;&lt; Exit [It] Merging the PaC PR should be successful for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:375 @ 04/21/26 08:19:19.661 (1.201s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:19:19.661&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:19:19.661 (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.026321292">
              <system-err>&gt; Enter [It] PR merge triggers PAC PipelineRun for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:385 @ 04/21/26 08:19:19.662&#xA;Push PipelineRun has not been created yet for the component build-e2e-dmfx/gl-multi-component-parent-juon&#xA;&lt; Exit [It] PR merge triggers PAC PipelineRun for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:385 @ 04/21/26 08:19:39.687 (20.026s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:19:39.688&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:19:39.688 (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="300.014370856">
              <system-err>&gt; Enter [It] PAC PipelineRun for parent component  is successful - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:401 @ 04/21/26 08:19:39.688&#xA;PipelineRun gl-multi-component-parent-juon-on-push-tp9s4 found for Component build-e2e-dmfx/gl-multi-component-parent-juon&#xA;PipelineRun gl-multi-component-parent-juon-on-push-tp9s4 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-push-tp9s4 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-push-tp9s4 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-push-tp9s4 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-push-tp9s4 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-push-tp9s4 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-push-tp9s4 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-push-tp9s4 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-push-tp9s4 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-push-tp9s4 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-push-tp9s4 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-push-tp9s4 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-push-tp9s4 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-push-tp9s4 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-push-tp9s4 reason: Running&#xA;PipelineRun gl-multi-component-parent-juon-on-push-tp9s4 reason: Succeeded&#xA;&lt; Exit [It] PAC PipelineRun for parent component  is successful - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:401 @ 04/21/26 08:24:39.702 (5m0.014s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:24:39.702&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:24:39.702 (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.348387183">
              <system-err>&gt; Enter [It] should lead to a nudge PR creation for child component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:412 @ 04/21/26 08:24:39.703&#xA;&lt; Exit [It] should lead to a nudge PR creation for child component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:412 @ 04/21/26 08:24:50.051 (10.348s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:24:50.051&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:24:50.051 (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.903746937">
              <system-err>&gt; Enter [It] merging the PR should be successful for child component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:429 @ 04/21/26 08:24:50.052&#xA;merged result sha: bd448245509308e42e0ad0148e0bdf9666a10382 for PR #3&#xA;&lt; Exit [It] merging the PR should be successful for child component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:429 @ 04/21/26 08:24:51.955 (1.903s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:24:51.955&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:24:51.955 (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="58.419964111">
              <system-err>&gt; Enter [It] Verify the nudge updated the contents - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:440 @ 04/21/26 08:24:51.956&#xA;Verifying Dockerfile.tmp updated to sha sha256:7b0337aaf3564fed1aa18a41b7da393dacf506924094dff2a17650e0a2792489content: FROM quay.io/redhat-appstudio-qe/build-e2e-dmfx/gl-multi-component-parent-juon@sha256:7b0337aaf3564fed1aa18a41b7da393dacf506924094dff2a17650e0a2792489&#xA;RUN echo hello&#xA;&#xA;&lt; Exit [It] Verify the nudge updated the contents - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:440 @ 04/21/26 08:24:52.261 (306ms)&#xA;&gt; Enter [AfterAll] component update with renovate - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:214 @ 04/21/26 08:24:52.262&#xA;&lt; Exit [AfterAll] component update with renovate - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:214 @ 04/21/26 08:25:50.375 (58.114s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:25:50.376&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:25:50.376 (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] [release-pipelines-suite FBC e2e-tests] with FBC happy path Post-release verification creates component from git source https://github.com/redhat-appstudio-qe/fbc-sample-repo-test [release-pipelines, fbc-release, fbcHappyPath]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC happy path Post-release verification Creates a push snapshot for a release [release-pipelines, fbc-release, fbcHappyPath]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC happy path Post-release verification verifies the fbc release pipelinerun is running and succeeds [release-pipelines, fbc-release, fbcHappyPath]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC happy path Post-release verification verifies release CR completed and set succeeded. [release-pipelines, fbc-release, fbcHappyPath]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC Staged Index Post-release verification creates component from git source https://github.com/redhat-appstudio-qe/fbc-sample-repo-test [release-pipelines, fbc-release, fbcStagedIndex]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC Staged Index Post-release verification Creates a push snapshot for a release [release-pipelines, fbc-release, fbcStagedIndex]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC Staged Index Post-release verification verifies the fbc release pipelinerun is running and succeeds [release-pipelines, fbc-release, fbcStagedIndex]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC Staged Index Post-release verification verifies release CR completed and set succeeded. [release-pipelines, fbc-release, fbcStagedIndex]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC hotfix process FBC hotfix post-release verification creates component from git source https://github.com/redhat-appstudio-qe/fbc-sample-repo-test [release-pipelines, fbc-release, fbcHotfix]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC hotfix process FBC hotfix post-release verification Creates a push snapshot for a release [release-pipelines, fbc-release, fbcHotfix]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC hotfix process FBC hotfix post-release verification verifies the fbc release pipelinerun is running and succeeds [release-pipelines, fbc-release, fbcHotfix]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC hotfix process FBC hotfix post-release verification verifies release CR completed and set succeeded. [release-pipelines, fbc-release, fbcHotfix]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC pre-GA process FBC pre-GA post-release verification creates component from git source https://github.com/redhat-appstudio-qe/fbc-sample-repo-test [release-pipelines, fbc-release, fbcPreGA]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC pre-GA process FBC pre-GA post-release verification Creates a push snapshot for a release [release-pipelines, fbc-release, fbcPreGA]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC pre-GA process FBC pre-GA post-release verification verifies the fbc release pipelinerun is running and succeeds [release-pipelines, fbc-release, fbcPreGA]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC pre-GA process FBC pre-GA post-release verification verifies release CR completed and set succeeded. [release-pipelines, fbc-release, fbcPreGA]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test 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="44.061737236">
              <system-err>&gt; Enter [BeforeAll] test pac with multiple components using same repository - /tmp/tmp.DGYK2mBrx2/tests/build/multi_component.go:40 @ 04/21/26 07:58:44.067&#xA;&lt; Exit [BeforeAll] test pac with multiple components using same repository - /tmp/tmp.DGYK2mBrx2/tests/build/multi_component.go:40 @ 04/21/26 07:59:08.07 (24.004s)&#xA;&gt; Enter [It] creates component with context directory go-component - /tmp/tmp.DGYK2mBrx2/tests/build/multi_component.go:106 @ 04/21/26 07:59:08.07&#xA;Image repository for component go-component-ulyptg in namespace build-e2e-clap 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 context directory go-component - /tmp/tmp.DGYK2mBrx2/tests/build/multi_component.go:106 @ 04/21/26 07:59:28.128 (20.058s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/multi_component.go:28 @ 04/21/26 07:59:28.128&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/multi_component.go:28 @ 04/21/26 07:59:28.128 (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-ulyptg [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="failed" time="1801.298065884">
              <failure message="Timed out after 1800.000s.&#xA;timed out when waiting for the PipelineRun to start for the component go-component-ulyptg/build-e2e-clap&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc00082a960&gt;: &#xA;    no pipelinerun found for component go-component-ulyptg&#xA;    {&#xA;        s: &#34;no pipelinerun found for component go-component-ulyptg&#34;,&#xA;    }" type="failed">[FAILED] Timed out after 1800.000s.&#xA;timed out when waiting for the PipelineRun to start for the component go-component-ulyptg/build-e2e-clap&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc00082a960&gt;: &#xA;    no pipelinerun found for component go-component-ulyptg&#xA;    {&#xA;        s: &#34;no pipelinerun found for component go-component-ulyptg&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.DGYK2mBrx2/tests/build/multi_component.go:137 @ 04/21/26 08:29:28.13&#xA;</failure>
              <system-err>&gt; Enter [It] triggers a PipelineRun for component go-component-ulyptg - /tmp/tmp.DGYK2mBrx2/tests/build/multi_component.go:125 @ 04/21/26 07:59:28.129&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;PipelineRun has not been created yet for the component build-e2e-clap/go-component-ulyptg&#xA;[FAILED] Timed out after 1800.000s.&#xA;timed out when waiting for the PipelineRun to start for the component go-component-ulyptg/build-e2e-clap&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc00082a960&gt;: &#xA;    no pipelinerun found for component go-component-ulyptg&#xA;    {&#xA;        s: &#34;no pipelinerun found for component go-component-ulyptg&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.DGYK2mBrx2/tests/build/multi_component.go:137 @ 04/21/26 08:29:28.13&#xA;&lt; Exit [It] triggers a PipelineRun for component go-component-ulyptg - /tmp/tmp.DGYK2mBrx2/tests/build/multi_component.go:125 @ 04/21/26 08:29:28.13 (30m0.001s)&#xA;&gt; Enter [AfterAll] test pac with multiple components using same repository - /tmp/tmp.DGYK2mBrx2/tests/build/multi_component.go:68 @ 04/21/26 08:29:28.13&#xA;&lt; Exit [AfterAll] test pac with multiple components using same repository - /tmp/tmp.DGYK2mBrx2/tests/build/multi_component.go:68 @ 04/21/26 08:29:29.205 (1.075s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/multi_component.go:28 @ 04/21/26 08:29:29.205&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/multi_component.go:28 @ 04/21/26 08:29:29.427 (222ms)&#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-ulyptg [build-service, github, pac-build, multi-component]" 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.DGYK2mBrx2/tests/build/multi_component.go:140 @ 04/21/26 08:29:29.427&#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-ulyptg [build-service, github, pac-build, multi-component]" 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.DGYK2mBrx2/tests/build/multi_component.go:159 @ 04/21/26 08:29:29.428&#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="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.DGYK2mBrx2/tests/build/multi_component.go:164 @ 04/21/26 08:29:29.428&#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="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.DGYK2mBrx2/tests/build/multi_component.go:174 @ 04/21/26 08:29:29.428&#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="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.DGYK2mBrx2/tests/build/multi_component.go:106 @ 04/21/26 08:29:29.428&#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-hdnaym [build-service, github, pac-build, multi-component]" 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.DGYK2mBrx2/tests/build/multi_component.go:125 @ 04/21/26 08:29:29.428&#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-hdnaym [build-service, github, pac-build, multi-component]" 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.DGYK2mBrx2/tests/build/multi_component.go:140 @ 04/21/26 08:29:29.429&#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-hdnaym [build-service, github, pac-build, multi-component]" 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.DGYK2mBrx2/tests/build/multi_component.go:159 @ 04/21/26 08:29:29.429&#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="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.DGYK2mBrx2/tests/build/multi_component.go:164 @ 04/21/26 08:29:29.429&#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="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.DGYK2mBrx2/tests/build/multi_component.go:174 @ 04/21/26 08:29:29.429&#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="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.DGYK2mBrx2/tests/build/multi_component.go:190 @ 04/21/26 08:29:29.429&#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="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.DGYK2mBrx2/tests/build/multi_component.go:205 @ 04/21/26 08:29:29.429&#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="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.DGYK2mBrx2/tests/build/multi_component.go:264 @ 04/21/26 08:29:29.43&#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 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="56.542223159">
              <system-err>&gt; Enter [BeforeAll] PaC component build - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:54 @ 04/21/26 07:58:44.261&#xA;&lt; Exit [BeforeAll] PaC component build - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:54 @ 04/21/26 07:59:05.152 (20.891s)&#xA;&gt; Enter [BeforeAll] when a new component without specified branch is created and with visibility private - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:117 @ 04/21/26 07:59:05.152&#xA;Image repository for component gh-test-custom-default-lyqksm in namespace build-e2e-xwhm 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.DGYK2mBrx2/tests/build/pac_build.go:117 @ 04/21/26 07:59:25.208 (20.056s)&#xA;&gt; Enter [It] correctly targets the default branch (that is not named &#39;main&#39;) with PaC - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:136 @ 04/21/26 07:59:25.208&#xA;&lt; Exit [It] correctly targets the default branch (that is not named &#39;main&#39;) with PaC - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:136 @ 04/21/26 07:59:40.803 (15.595s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 07:59:40.803&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 07:59:40.803 (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.075062899">
              <system-err>&gt; Enter [It] workspace parameter is set correctly in PaC repository CR - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:153 @ 04/21/26 07:59:40.804&#xA;&lt; Exit [It] workspace parameter is set correctly in PaC repository CR - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:153 @ 04/21/26 07:59:40.878 (75ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 07:59:40.878&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 07:59:40.878 (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="failed" time="1800.186251307">
              <failure message="Timed out after 1800.000s.&#xA;timed out when waiting for the PipelineRun to start for the component gh-test-custom-branch-ynagle/build-e2e-xwhm&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc000952580&gt;: &#xA;    no pipelinerun found for component gh-test-custom-default-lyqksm&#xA;    {&#xA;        s: &#34;no pipelinerun found for component gh-test-custom-default-lyqksm&#34;,&#xA;    }" type="failed">[FAILED] Timed out after 1800.000s.&#xA;timed out when waiting for the PipelineRun to start for the component gh-test-custom-branch-ynagle/build-e2e-xwhm&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc000952580&gt;: &#xA;    no pipelinerun found for component gh-test-custom-default-lyqksm&#xA;    {&#xA;        s: &#34;no pipelinerun found for component gh-test-custom-default-lyqksm&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:188 @ 04/21/26 08:29:40.879&#xA;</failure>
              <system-err>&gt; Enter [It] triggers a PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:176 @ 04/21/26 07:59:40.879&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;PipelineRun has not been created yet for the component build-e2e-xwhm/gh-test-custom-branch-ynagle&#xA;[FAILED] Timed out after 1800.000s.&#xA;timed out when waiting for the PipelineRun to start for the component gh-test-custom-branch-ynagle/build-e2e-xwhm&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc000952580&gt;: &#xA;    no pipelinerun found for component gh-test-custom-default-lyqksm&#xA;    {&#xA;        s: &#34;no pipelinerun found for component gh-test-custom-default-lyqksm&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:188 @ 04/21/26 08:29:40.879&#xA;&lt; Exit [It] triggers a PipelineRun - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:176 @ 04/21/26 08:29:40.879 (30m0s)&#xA;&gt; Enter [AfterAll] PaC component build - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:101 @ 04/21/26 08:29:40.88&#xA;&lt; Exit [AfterAll] PaC component build - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:101 @ 04/21/26 08:29:40.88 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:29:40.88&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/pac_build.go:28 @ 04/21/26 08:29:41.065 (185ms)&#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="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.DGYK2mBrx2/tests/build/pac_build.go:191 @ 04/21/26 08:29:41.066&#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="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.DGYK2mBrx2/tests/build/pac_build.go:195 @ 04/21/26 08:29:41.066&#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="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.DGYK2mBrx2/tests/build/pac_build.go:225 @ 04/21/26 08:29:41.066&#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="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.DGYK2mBrx2/tests/build/pac_build.go:243 @ 04/21/26 08:29:41.067&#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="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.DGYK2mBrx2/tests/build/pac_build.go:249 @ 04/21/26 08:29:41.067&#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="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.DGYK2mBrx2/tests/build/pac_build.go:265 @ 04/21/26 08:29:41.067&#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="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.DGYK2mBrx2/tests/build/pac_build.go:278 @ 04/21/26 08:29:41.067&#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="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.DGYK2mBrx2/tests/build/pac_build.go:332 @ 04/21/26 08:29:41.067&#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="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.DGYK2mBrx2/tests/build/pac_build.go:347 @ 04/21/26 08:29:41.068&#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="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.DGYK2mBrx2/tests/build/pac_build.go:365 @ 04/21/26 08:29:41.068&#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="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.DGYK2mBrx2/tests/build/pac_build.go:371 @ 04/21/26 08:29:41.068&#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="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.DGYK2mBrx2/tests/build/pac_build.go:390 @ 04/21/26 08:29:41.068&#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="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.DGYK2mBrx2/tests/build/pac_build.go:396 @ 04/21/26 08:29:41.068&#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="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.DGYK2mBrx2/tests/build/pac_build.go:425 @ 04/21/26 08:29:41.069&#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="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.DGYK2mBrx2/tests/build/pac_build.go:439 @ 04/21/26 08:29:41.069&#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="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.DGYK2mBrx2/tests/build/pac_build.go:464 @ 04/21/26 08:29:41.069&#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="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.DGYK2mBrx2/tests/build/pac_build.go:479 @ 04/21/26 08:29:41.069&#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="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.DGYK2mBrx2/tests/build/pac_build.go:498 @ 04/21/26 08:29:41.069&#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="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.DGYK2mBrx2/tests/build/pac_build.go:504 @ 04/21/26 08:29:41.069&#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="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.DGYK2mBrx2/tests/build/pac_build.go:530 @ 04/21/26 08:29:41.07&#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="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.DGYK2mBrx2/tests/build/pac_build.go:546 @ 04/21/26 08:29:41.07&#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="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.DGYK2mBrx2/tests/build/pac_build.go:552 @ 04/21/26 08:29:41.07&#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="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.DGYK2mBrx2/tests/build/pac_build.go:564 @ 04/21/26 08:29:41.07&#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="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.DGYK2mBrx2/tests/build/pac_build.go:595 @ 04/21/26 08:29:41.071&#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 and recreated (with the same name in the same namespace) should no longer lead to a creation of a PaC PR [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped - 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.DGYK2mBrx2/tests/build/pac_build.go:715 @ 04/21/26 08:29:41.071&#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="95.958032224">
              <system-err>&gt; Enter [BeforeAll] component update with renovate - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:72 @ 04/21/26 07:58:44.062&#xA;ReleaseAdmissionPlan data: {&#34;Mapping&#34;:{&#34;Components&#34;:[{&#34;Name&#34;:&#34;gh-multi-component-parent-gtux&#34;,&#34;Repository&#34;:&#34;quay.io/redhat-appstudio-qe/release-repository&#34;}]}}&#xA;&lt; Exit [BeforeAll] component update with renovate - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:72 @ 04/21/26 07:59:39.91 (55.847s)&#xA;&gt; Enter [It] creates component with nudges - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:235 @ 04/21/26 07:59:39.91&#xA;Image repository for component gh-multi-component-child-gtux in namespace build-e2e-rxgr 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-gtux in namespace build-e2e-rxgr 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-gtux in namespace build-e2e-rxgr 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.DGYK2mBrx2/tests/build/renovate.go:235 @ 04/21/26 08:00:20.019 (40.109s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:00:20.019&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:00:20.019 (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="failed" time="1814.219785723">
              <failure message="Timed out after 1800.000s.&#xA;timed out when waiting for the PipelineRun to start for the component gh-multi-component-parent-gtux/build-e2e-rxgr&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc000d20da0&gt;: &#xA;    no pipelinerun found for component gh-multi-component-parent-gtux&#xA;    {&#xA;        s: &#34;no pipelinerun found for component gh-multi-component-parent-gtux&#34;,&#xA;    }" type="failed">[FAILED] Timed out after 1800.000s.&#xA;timed out when waiting for the PipelineRun to start for the component gh-multi-component-parent-gtux/build-e2e-rxgr&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc000d20da0&gt;: &#xA;    no pipelinerun found for component gh-multi-component-parent-gtux&#xA;    {&#xA;        s: &#34;no pipelinerun found for component gh-multi-component-parent-gtux&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:272 @ 04/21/26 08:30:20.021&#xA;</failure>
              <system-err>&gt; Enter [It] triggers a PipelineRun for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:259 @ 04/21/26 08:00:20.02&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;PipelineRun has not been created yet for the component build-e2e-rxgr/gh-multi-component-parent-gtux&#xA;[FAILED] Timed out after 1800.000s.&#xA;timed out when waiting for the PipelineRun to start for the component gh-multi-component-parent-gtux/build-e2e-rxgr&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc000d20da0&gt;: &#xA;    no pipelinerun found for component gh-multi-component-parent-gtux&#xA;    {&#xA;        s: &#34;no pipelinerun found for component gh-multi-component-parent-gtux&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:272 @ 04/21/26 08:30:20.021&#xA;&lt; Exit [It] triggers a PipelineRun for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:259 @ 04/21/26 08:30:20.021 (30m0.001s)&#xA;&gt; Enter [AfterAll] component update with renovate - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:214 @ 04/21/26 08:30:20.021&#xA;&lt; Exit [AfterAll] component update with renovate - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:214 @ 04/21/26 08:30:34.052 (14.031s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:30:34.053&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:30:34.24 (187ms)&#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="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.DGYK2mBrx2/tests/build/renovate.go:274 @ 04/21/26 08:30:34.24&#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="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.DGYK2mBrx2/tests/build/renovate.go:285 @ 04/21/26 08:30:34.241&#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="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.DGYK2mBrx2/tests/build/renovate.go:289 @ 04/21/26 08:30:34.241&#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="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.DGYK2mBrx2/tests/build/renovate.go:307 @ 04/21/26 08:30:34.241&#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="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.DGYK2mBrx2/tests/build/renovate.go:318 @ 04/21/26 08:30:34.242&#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="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.DGYK2mBrx2/tests/build/renovate.go:358 @ 04/21/26 08:30:34.242&#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="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.DGYK2mBrx2/tests/build/renovate.go:375 @ 04/21/26 08:30:34.242&#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="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.DGYK2mBrx2/tests/build/renovate.go:385 @ 04/21/26 08:30:34.242&#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="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.DGYK2mBrx2/tests/build/renovate.go:401 @ 04/21/26 08:30:34.242&#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="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.DGYK2mBrx2/tests/build/renovate.go:412 @ 04/21/26 08:30:34.242&#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="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.DGYK2mBrx2/tests/build/renovate.go:429 @ 04/21/26 08:30:34.243&#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="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.DGYK2mBrx2/tests/build/renovate.go:440 @ 04/21/26 08:30:34.243&#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 creates component with nudges [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="passed" time="117.964849896">
              <system-err>&gt; Enter [BeforeAll] component update with renovate - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:72 @ 04/21/26 07:58:44.061&#xA;ReleaseAdmissionPlan data: {&#34;Mapping&#34;:{&#34;Components&#34;:[{&#34;Name&#34;:&#34;fj-multi-component-parent-jbus&#34;,&#34;Repository&#34;:&#34;quay.io/redhat-appstudio-qe/release-repository&#34;}]}}&#xA;&lt; Exit [BeforeAll] component update with renovate - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:72 @ 04/21/26 07:59:51.936 (1m7.875s)&#xA;&gt; Enter [It] creates component with nudges - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:235 @ 04/21/26 07:59:51.936&#xA;Image repository for component fj-multi-component-child-jbus in namespace build-e2e-bqvi 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-jbus in namespace build-e2e-bqvi 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-jbus in namespace build-e2e-bqvi 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-jbus in namespace build-e2e-bqvi 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.DGYK2mBrx2/tests/build/renovate.go:235 @ 04/21/26 08:00:42.025 (50.089s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:00:42.025&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:00:42.025 (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="passed" time="200.113684129">
              <system-err>&gt; Enter [It] triggers a PipelineRun for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:259 @ 04/21/26 08:00:42.026&#xA;PipelineRun has not been created yet for the component build-e2e-bqvi/fj-multi-component-parent-jbus&#xA;PipelineRun has not been created yet for the component build-e2e-bqvi/fj-multi-component-parent-jbus&#xA;PipelineRun has not been created yet for the component build-e2e-bqvi/fj-multi-component-parent-jbus&#xA;PipelineRun has not been created yet for the component build-e2e-bqvi/fj-multi-component-parent-jbus&#xA;PipelineRun has not been created yet for the component build-e2e-bqvi/fj-multi-component-parent-jbus&#xA;PipelineRun has not been created yet for the component build-e2e-bqvi/fj-multi-component-parent-jbus&#xA;PipelineRun has not been created yet for the component build-e2e-bqvi/fj-multi-component-parent-jbus&#xA;PipelineRun has not been created yet for the component build-e2e-bqvi/fj-multi-component-parent-jbus&#xA;PipelineRun has not been created yet for the component build-e2e-bqvi/fj-multi-component-parent-jbus&#xA;PipelineRun has not been created yet for the component build-e2e-bqvi/fj-multi-component-parent-jbus&#xA;&lt; Exit [It] triggers a PipelineRun for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:259 @ 04/21/26 08:04:02.139 (3m20.113s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:04:02.139&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:04:02.139 (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 the PipelineRun should eventually finish successfully for parent component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="passed" time="320.015782112">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:274 @ 04/21/26 08:04:02.14&#xA;PipelineRun fj-multi-component-parent-jbus-on-pull-request-mwfgb found for Component build-e2e-bqvi/fj-multi-component-parent-jbus&#xA;PipelineRun fj-multi-component-parent-jbus-on-pull-request-mwfgb reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-pull-request-mwfgb reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-pull-request-mwfgb reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-pull-request-mwfgb reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-pull-request-mwfgb reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-pull-request-mwfgb reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-pull-request-mwfgb reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-pull-request-mwfgb reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-pull-request-mwfgb reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-pull-request-mwfgb reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-pull-request-mwfgb reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-pull-request-mwfgb reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-pull-request-mwfgb reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-pull-request-mwfgb reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-pull-request-mwfgb reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-pull-request-mwfgb reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-pull-request-mwfgb reason: Succeeded&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:274 @ 04/21/26 08:09:22.155 (5m20.015s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:09:22.155&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:09:22.155 (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 the PipelineRun should eventually finish successfully for child component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="passed" time="100.012682003">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for child component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:285 @ 04/21/26 08:09:22.156&#xA;PipelineRun fj-multi-component-child-jbus-on-pull-request-ntz6f found for Component build-e2e-bqvi/fj-multi-component-child-jbus&#xA;PipelineRun fj-multi-component-child-jbus-on-pull-request-ntz6f reason: Running&#xA;PipelineRun fj-multi-component-child-jbus-on-pull-request-ntz6f reason: Running&#xA;PipelineRun fj-multi-component-child-jbus-on-pull-request-ntz6f reason: Running&#xA;PipelineRun fj-multi-component-child-jbus-on-pull-request-ntz6f reason: Running&#xA;PipelineRun fj-multi-component-child-jbus-on-pull-request-ntz6f reason: Running&#xA;PipelineRun fj-multi-component-child-jbus-on-pull-request-ntz6f reason: Succeeded&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for child component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:285 @ 04/21/26 08:11:02.169 (1m40.012s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:11:02.169&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:11:02.169 (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 should lead to a PaC PR creation for child component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="passed" time="19.101917648">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for child component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:289 @ 04/21/26 08:11:02.169&#xA;&lt; Exit [It] should lead to a PaC PR creation for child component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:289 @ 04/21/26 08:11:21.271 (19.102s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:11:21.271&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:11:21.271 (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 Merging the PaC PR should be successful for child component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="passed" time="14.126271029">
              <system-err>&gt; Enter [It] Merging the PaC PR should be successful for child component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:307 @ 04/21/26 08:11:21.272&#xA;merged result sha: a54bde0a55814f9dfd90cf24b62ae5866c83209f for PR #1&#xA;&lt; Exit [It] Merging the PaC PR should be successful for child component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:307 @ 04/21/26 08:11:35.397 (14.126s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:11:35.398&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:11:35.398 (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 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="passed" time="123.949139891">
              <system-err>&gt; Enter [It] create dockerfile and yaml manifest that references build and distribution repositories - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:318 @ 04/21/26 08:11:35.398&#xA;&lt; Exit [It] create dockerfile and yaml manifest that references build and distribution repositories - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:318 @ 04/21/26 08:13:39.347 (2m3.949s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:13:39.347&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:13:39.347 (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 should lead to a PaC PR creation for parent component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="passed" time="15.745756047">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:358 @ 04/21/26 08:13:39.348&#xA;&lt; Exit [It] should lead to a PaC PR creation for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:358 @ 04/21/26 08:13:55.093 (15.745s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:13:55.093&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:13:55.094 (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 Merging the PaC PR should be successful for parent component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="passed" time="23.543693341">
              <system-err>&gt; Enter [It] Merging the PaC PR should be successful for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:375 @ 04/21/26 08:13:55.094&#xA;merged result sha: 277654ab02ad4c6ebbf46f459150584371596abd for PR #1&#xA;&lt; Exit [It] Merging the PaC PR should be successful for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:375 @ 04/21/26 08:14:18.637 (23.543s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:14:18.638&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:14:18.638 (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 PR merge triggers PAC PipelineRun for parent component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="passed" time="0.03504529">
              <system-err>&gt; Enter [It] PR merge triggers PAC PipelineRun for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:385 @ 04/21/26 08:14:18.638&#xA;&lt; Exit [It] PR merge triggers PAC PipelineRun for parent component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:385 @ 04/21/26 08:14:18.673 (35ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:14:18.673&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:14:18.673 (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 PAC PipelineRun for parent component  is successful [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="passed" time="260.014321061">
              <system-err>&gt; Enter [It] PAC PipelineRun for parent component  is successful - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:401 @ 04/21/26 08:14:18.673&#xA;PipelineRun fj-multi-component-parent-jbus-on-push-9bpnd found for Component build-e2e-bqvi/fj-multi-component-parent-jbus&#xA;PipelineRun fj-multi-component-parent-jbus-on-push-9bpnd reason: ResolvingTaskRef&#xA;PipelineRun fj-multi-component-parent-jbus-on-push-9bpnd reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-push-9bpnd reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-push-9bpnd reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-push-9bpnd reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-push-9bpnd reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-push-9bpnd reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-push-9bpnd reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-push-9bpnd reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-push-9bpnd reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-push-9bpnd reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-push-9bpnd reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-push-9bpnd reason: Running&#xA;PipelineRun fj-multi-component-parent-jbus-on-push-9bpnd reason: Succeeded&#xA;&lt; Exit [It] PAC PipelineRun for parent component  is successful - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:401 @ 04/21/26 08:18:38.687 (4m20.014s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:18:38.688&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:18:38.688 (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 should lead to a nudge PR creation for child component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="failed" time="1214.671695723">
              <failure message="Timed out after 1200.001s.&#xA;timed out when waiting for component nudge PR to be created in build-nudge-child-hgfoft repository&#xA;Expected&#xA;    &lt;bool&gt;: false&#xA;to be true" type="failed">[FAILED] Timed out after 1200.001s.&#xA;timed out when waiting for component nudge PR to be created in build-nudge-child-hgfoft repository&#xA;Expected&#xA;    &lt;bool&gt;: false&#xA;to be true&#xA;In [It] at: /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:427 @ 04/21/26 08:38:38.689&#xA;</failure>
              <system-err>&gt; Enter [It] should lead to a nudge PR creation for child component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:412 @ 04/21/26 08:18:38.688&#xA;[FAILED] Timed out after 1200.001s.&#xA;timed out when waiting for component nudge PR to be created in build-nudge-child-hgfoft repository&#xA;Expected&#xA;    &lt;bool&gt;: false&#xA;to be true&#xA;In [It] at: /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:427 @ 04/21/26 08:38:38.689&#xA;&lt; Exit [It] should lead to a nudge PR creation for child component  - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:412 @ 04/21/26 08:38:38.689 (20m0.001s)&#xA;&gt; Enter [AfterAll] component update with renovate - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:214 @ 04/21/26 08:38:38.689&#xA;&lt; Exit [AfterAll] component update with renovate - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:214 @ 04/21/26 08:38:52.761 (14.072s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:38:52.762&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.DGYK2mBrx2/tests/build/renovate.go:28 @ 04/21/26 08:38:53.36 (598ms)&#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.DGYK2mBrx2/tests/build/renovate.go:429 @ 04/21/26 08:38:53.361&#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.DGYK2mBrx2/tests/build/renovate.go:440 @ 04/21/26 08:38:53.361&#xA;</system-err>
          </testcase>
      </testsuite>
  </testsuites>