<?xml version="1.0" encoding="UTF-8"?>
  <testsuites tests="464" disabled="360" errors="0" failures="5" time="4575.678813843">
      <testsuite name="Red Hat App Studio E2E tests" package="/tmp/tmp.XKFaKtKOZB/cmd" tests="464" disabled="88" skipped="272" errors="0" failures="5" time="4575.678813843" timestamp="2026-04-20T07:01:04">
          <properties>
              <property name="SuiteSucceeded" value="false"></property>
              <property name="SuiteHasProgrammaticFocus" value="false"></property>
              <property name="SpecialSuiteFailureReason" value=""></property>
              <property name="SuiteLabels" value="[]"></property>
              <property name="SuiteSemVerConstraints" value="[]"></property>
              <property name="RandomSeed" value="1776668316"></property>
              <property name="RandomizeAllSpecs" value="false"></property>
              <property name="LabelFilter" value="build-service"></property>
              <property name="SemVerFilter" value=""></property>
              <property name="FocusStrings" value=""></property>
              <property name="SkipStrings" value=""></property>
              <property name="FocusFiles" value=""></property>
              <property name="SkipFiles" value=""></property>
              <property name="FailOnPending" value="false"></property>
              <property name="FailOnEmpty" value="false"></property>
              <property name="FailFast" value="false"></property>
              <property name="FlakeAttempts" value="0"></property>
              <property name="DryRun" value="false"></property>
              <property name="ParallelTotal" value="20"></property>
              <property name="OutputInterceptorMode" value="none"></property>
          </properties>
          <testcase name="[It] [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="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when a new Component with specified custom branch is created does not contain an annotation with a Snapshot Name [integration-service, gitlab-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when a new Component with specified custom branch is created should lead to build PipelineRun finishing successfully [integration-service, gitlab-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when a new Component with specified custom branch is created 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"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when a new Component with specified custom branch is created 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"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when 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"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when 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"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when 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"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when 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"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when 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"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when 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"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when 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"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when 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"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when 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"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when 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"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when 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"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when 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"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when 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"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when 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"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when 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"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when 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"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when 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"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created creates first component [build-service, github, pac-build, secret-lookup]" classname="Red Hat App Studio E2E tests" status="passed" time="23.152683991">
              <system-err>&gt; Enter [BeforeAll] test build secret lookup - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:32 @ 04/20/26 07:01:05.15&#xA;&lt; Exit [BeforeAll] test build secret lookup - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:32 @ 04/20/26 07:01:08.053 (2.903s)&#xA;&gt; Enter [BeforeAll] when two secrets are created - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:100 @ 04/20/26 07:01:08.053&#xA;&lt; Exit [BeforeAll] when two secrets are created - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:100 @ 04/20/26 07:01:08.174 (121ms)&#xA;&gt; Enter [It] creates first component - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:123 @ 04/20/26 07:01:08.174&#xA;Image repository for component component-one-yrdq in namespace build-e2e-gjqw do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component component-one-yrdq in namespace build-e2e-gjqw 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.XKFaKtKOZB/tests/build/secret_lookup.go:123 @ 04/20/26 07:01:28.302 (20.128s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:25 @ 04/20/26 07:01:28.303&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:25 @ 04/20/26 07:01:28.303 (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.120573536">
              <system-err>&gt; Enter [It] creates second component - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:140 @ 04/20/26 07:01:28.303&#xA;Image repository for component component-two-ilkk in namespace build-e2e-gjqw 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-ilkk in namespace build-e2e-gjqw 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.XKFaKtKOZB/tests/build/secret_lookup.go:140 @ 04/20/26 07:01:48.423 (20.12s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:25 @ 04/20/26 07:01:48.424&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:25 @ 04/20/26 07:01:48.424 (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="0.057938007">
              <system-err>&gt; Enter [It] check first component annotation has errors - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:158 @ 04/20/26 07:01:48.424&#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.XKFaKtKOZB/tests/build/secret_lookup.go:158 @ 04/20/26 07:01:48.482 (58ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:25 @ 04/20/26 07:01:48.482&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:25 @ 04/20/26 07:01:48.482 (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="100.657095441">
              <system-err>&gt; Enter [It] triggered PipelineRun is for component  - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:178 @ 04/20/26 07:01:48.483&#xA;PipelineRun has not been created yet for the component build-e2e-gjqw/component-two-ilkk&#xA;PipelineRun has not been created yet for the component build-e2e-gjqw/component-two-ilkk&#xA;PipelineRun has not been created yet for the component build-e2e-gjqw/component-two-ilkk&#xA;PipelineRun has not been created yet for the component build-e2e-gjqw/component-two-ilkk&#xA;&lt; Exit [It] triggered PipelineRun is for component  - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:178 @ 04/20/26 07:03:29.139 (1m40.657s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:25 @ 04/20/26 07:03:29.14&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:25 @ 04/20/26 07:03:29.14 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created check only one pipelinerun should be triggered [build-service, github, pac-build, secret-lookup]" classname="Red Hat App Studio E2E tests" status="passed" time="133.994211318">
              <system-err>&gt; Enter [It] check only one pipelinerun should be triggered - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:193 @ 04/20/26 07:03:29.14&#xA;&lt; Exit [It] check only one pipelinerun should be triggered - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:193 @ 04/20/26 07:05:29.141 (2m0.001s)&#xA;&gt; Enter [AfterAll] test build secret lookup - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:61 @ 04/20/26 07:05:29.141&#xA;&lt; Exit [AfterAll] test build secret lookup - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:61 @ 04/20/26 07:05:43.134 (13.993s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:25 @ 04/20/26 07:05:43.134&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/secret_lookup.go:25 @ 04/20/26 07:05:43.134 (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] [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] [disaster-recovery DR Same-Version Backup/Restore] when creating tenants and running initial pipelines should create both tenants concurrently [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when creating tenants and running initial pipelines should wait for all build PipelineRuns to succeed [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when backing up tenant data should create backup CRs for both tenants concurrently [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when simulating disaster by deleting namespaces should delete both tenant namespaces [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when restoring from backup should restore tenant-1 (KokoHazamar) via velero CLI method [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when restoring from backup should restore tenant-2 (MosheKipod) via oc command method [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when performing post-restore recovery should rotate SA tokens on both tenants [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when verifying restored tenants should confirm structural integrity of both tenants [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when verifying restored tenants should confirm functional pipeline execution after restore [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [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] [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 e2e tests for multi arch with rh-advisories pipeline] Multi arch test happy path Post-release verification verifies the release CR is created [release-pipelines, rh-advisories, multiarch-advisories, multiArchAdvisories]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for multi arch with rh-advisories pipeline] Multi arch test happy path Post-release verification verifies the multiarch release pipelinerun is running and succeeds [release-pipelines, rh-advisories, multiarch-advisories, multiArchAdvisories]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for multi arch with rh-advisories pipeline] Multi arch test happy path Post-release verification verifies release CR completed and set succeeded. [release-pipelines, rh-advisories, multiarch-advisories, multiArchAdvisories]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for multi arch with rh-advisories pipeline] Multi arch test happy path Post-release verification verifies if the repository URL is valid [release-pipelines, rh-advisories, multiarch-advisories, multiArchAdvisories]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite Release service happy path] Post-release verification verifies that a Release CR should have been created in the dev namespace [release-service, happy-path]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite Release service happy path] Post-release verification verifies that Release PipelineRun is triggered [release-service, happy-path]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite Release service happy path] Post-release verification verifies that Enterprise Contract Task has succeeded in the Release PipelineRun [release-service, happy-path]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite Release service happy path] Post-release verification verifies that a Release is marked as succeeded. [release-service, happy-path]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite 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] [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 [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] post-release verification. missing ReleasePlan makes a Release CR set as failed in both IsReleased and IsValid with a proper message to user. [release-service, release-neg, negMissingReleasePlan]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] post-release verification. missing ReleasePlanAdmission makes a Release CR set as failed in both IsReleased and IsValid with a proper message to user. [release-service, release-neg, negMissingReleasePlan]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [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] [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-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="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build creates an IntegrationTestScenario for the app [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build creates new branch for the build [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build creates component konflux-demo-component (private: false) from git source https://github.com/redhat-appstudio-qe/hacbs-test-project-konflux-demo [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Component is created triggers creation of a PR in the sample repo [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Component is created verifies component build status [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Component is created should eventually lead to triggering a &#39;push&#39; event type PipelineRun after merging the PaC init branch  [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun is created does not contain an annotation with a Snapshot Name [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun is created should eventually complete successfully [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun completes successfully should validate Tekton TaskRun test results successfully [konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun completes successfully should validate that the build pipelineRun is signed [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun completes successfully should find the related Snapshot CR [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun completes successfully should validate that the build pipelineRun is annotated with the name of the Snapshot [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun completes successfully should find the related Integration Test PipelineRun [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when push pipelinerun is retriggered should eventually succeed [konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Integration Test PipelineRun is created should eventually complete successfully [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Integration Test PipelineRun completes successfully should lead to Snapshot CR being marked as passed [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Integration Test PipelineRun completes successfully should trigger creation of Release CR [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Release CR is created triggers creation of Release PipelineRun [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Release PipelineRun is triggered should eventually succeed [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Release PipelineRun is completed should lead to Release CR being marked as succeeded [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] infrastructure is running verifies if the chains controller is running [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] infrastructure is running verifies the signing secret is present [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task creates signature and attestation [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task succeeds when policy is met [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task does not pass when tests are not satisfied on non-strict mode [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task fails when tests are not satisfied on strict mode [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task fails when unexpected signature is used [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task ec-cli command verifies ec cli has error handling [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task ec-cli command verifies ec validate accepts a list of image references [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task Release Policy verifies redhat products pass the redhat policy rule collection before release  [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task Release Policy verifies the release policy: Task are trusted [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task Release Policy verifies the release policy: Task references are pinned [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [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="skipped" time="0">
              <skipped message="skipped"></skipped>
          </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="skipped" time="0">
              <skipped message="skipped"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </testcase>
          <testcase name="[It] [upgrade-suite Create users and check their state] Verify AppStudioProvisionedUser [upgrade-verify]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [upgrade-suite Create users and check their state] creates AppStudioDeactivatedUser [upgrade-verify]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [upgrade-suite Create users and check their state] creates AppStudioBannedUser [upgrade-verify]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite [RELEASE-2136] Release CR fails when block-releases true in ReleasePlanAdmission.] post-release verification. block-releases true in ReleasePlanAdmission makes a Release CR set as failed in both IsReleased and IsValid with a proper message to user. [release-service, release-neg, negBlockReleases]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [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="skipped" time="0">
              <skipped message="skipped"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws host-pool allocation when the Component with multi-platform-build is created a PipelineRun is triggered [multi-platform, aws-host-pool]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws host-pool allocation when the Component with multi-platform-build is created the build-container task from component pipelinerun is buildah-remote [multi-platform, aws-host-pool]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws host-pool allocation when the Component with multi-platform-build is created The multi platform secret is populated [multi-platform, aws-host-pool]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws host-pool allocation when the Component with multi-platform-build is created that PipelineRun completes successfully [multi-platform, aws-host-pool]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws host-pool allocation when the Component with multi-platform-build is created test that cleanup happened successfully [multi-platform, aws-host-pool]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws dynamic allocation when the Component with multi-platform-build is created a PipelineRun is triggered [multi-platform, aws-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws dynamic allocation when the Component with multi-platform-build is created the build-container task from component pipelinerun is buildah-remote [multi-platform, aws-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws dynamic allocation when the Component with multi-platform-build is created The multi platform secret is populated [multi-platform, aws-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws dynamic allocation when the Component with multi-platform-build is created that PipelineRun completes successfully [multi-platform, aws-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws dynamic allocation when the Component with multi-platform-build is created check cleanup happened successfully [multi-platform, aws-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm system z dynamic allocation when the Component with multi-platform-build is created a PipelineRun is triggered [multi-platform, ibmz-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm system z dynamic allocation when the Component with multi-platform-build is created the build-container task from component pipelinerun is buildah-remote [multi-platform, ibmz-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm system z dynamic allocation when the Component with multi-platform-build is created The multi platform secret is populated [multi-platform, ibmz-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm system z dynamic allocation when the Component with multi-platform-build is created that PipelineRun completes successfully [multi-platform, ibmz-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm system z dynamic allocation when the Component with multi-platform-build is created check cleanup happened successfully [multi-platform, ibmz-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm power pc dynamic allocation when the Component with multi-platform-build is created a PipelineRun is triggered [multi-platform, ibmp-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm power pc dynamic allocation when the Component with multi-platform-build is created the build-container task from component pipelinerun is buildah-remote [multi-platform, ibmp-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm power pc dynamic allocation when the Component with multi-platform-build is created The multi platform secret is populated [multi-platform, ibmp-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm power pc dynamic allocation when the Component with multi-platform-build is created that PipelineRun completes successfully [multi-platform, ibmp-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm power pc dynamic allocation when the Component with multi-platform-build is created check cleanup happened successfully [multi-platform, ibmp-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [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="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when a new Component is created verifies if the build PipelineRun contains the finalizer [integration-service]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when a new Component is created waits for build PipelineRun to succeed [integration-service]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when a new Component is created should have a related PaC init PR created [integration-service]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </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"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification verifies that the ReleasePlan CR is unmatched in the beginning [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification Creates ReleasePlanAdmission CR in corresponding managed namespace [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification when ReleasePlanAdmission CR is created in managed namespace verifies that the ReleasePlan CR is set to matched [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification when ReleasePlanAdmission CR is created in managed namespace verifies that the ReleasePlanAdmission CR is set to matched [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification Creates a manual release ReleasePlan CR in devNamespace [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification when the second ReleasePlan CR is created verifies that the second ReleasePlan CR is set to matched [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification when the second ReleasePlan CR is created verifies that the ReleasePlanAdmission CR has two matched ReleasePlan CRs [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification deletes one ReleasePlan CR [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification when One ReleasePlan CR is deleted in managed namespace verifies that the ReleasePlanAdmission CR has only one matching ReleasePlan [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification deletes the ReleasePlanAdmission CR [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification when ReleasePlanAdmission CR is deleted in managed namespace verifies that the ReleasePlan CR has no matched ReleasePlanAdmission [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [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-xrat [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci triggers PipelineRun for component with source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci triggers PipelineRun for component with source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci triggers PipelineRun for component with source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta-min [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) should eventually finish successfully for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) should push Dockerfile to registry [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) floating tags are created successfully [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) image manifest mediaType is correct [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) check for source images if enabled in pipeline [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) when Pipeline Results are stored for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build should have Pipeline Records [build, build-templates, HACBS, pipeline-service, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) when Pipeline Results are stored for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build should have Pipeline Logs [build, build-templates, HACBS, pipeline-service, pipeline]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) should validate tekton taskrun test results for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry verify-enterprise-contract check should pass [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry should have Hermeto content in the SBOM in case the build was hermetic [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) build-definitions ec pipelines runs ec pipeline pipelines/enterprise-contract.yaml [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) should eventually finish successfully for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) should push Dockerfile to registry [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) floating tags are created successfully [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) image manifest mediaType is correct [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) check for source images if enabled in pipeline [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) when Pipeline Results are stored for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta should have Pipeline Records [build, build-templates, HACBS, pipeline-service, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) when Pipeline Results are stored for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta should have Pipeline Logs [build, build-templates, HACBS, pipeline-service, pipeline]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) should validate tekton taskrun test results for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry verify-enterprise-contract check should pass [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry should have Hermeto content in the SBOM in case the build was hermetic [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) build-definitions ec pipelines runs ec pipeline pipelines/enterprise-contract.yaml [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) should eventually finish successfully for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta-min [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) should push Dockerfile to registry [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) floating tags are created successfully [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) image manifest mediaType is correct [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) check for source images if enabled in pipeline [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) when Pipeline Results are stored for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta-min should have Pipeline Records [build, build-templates, HACBS, pipeline-service, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) when Pipeline Results are stored for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta-min should have Pipeline Logs [build, build-templates, HACBS, pipeline-service, pipeline]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) should validate tekton taskrun test results for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta-min [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry verify-enterprise-contract check should pass [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry should have Hermeto content in the SBOM in case the build was hermetic [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) build-definitions ec pipelines runs ec pipeline pipelines/enterprise-contract.yaml [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines pipelineRun should fail for symlink component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic with component name test-symlink-comp-xrat [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test 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="72.049373336">
              <system-err>&gt; Enter [BeforeAll] test build annotations - /tmp/tmp.XKFaKtKOZB/tests/build/annotations.go:35 @ 04/20/26 07:01:05.147&#xA;&lt; Exit [BeforeAll] test build annotations - /tmp/tmp.XKFaKtKOZB/tests/build/annotations.go:35 @ 04/20/26 07:01:06.659 (1.512s)&#xA;&gt; Enter [BeforeAll] when component is created with invalid build request annotations - /tmp/tmp.XKFaKtKOZB/tests/build/annotations.go:69 @ 04/20/26 07:01:06.659&#xA;Image repository for component test-annotations-wbqase in namespace build-e2e-ppsh 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.XKFaKtKOZB/tests/build/annotations.go:69 @ 04/20/26 07:01:16.795 (10.136s)&#xA;&gt; Enter [It] handles invalid request annotation - /tmp/tmp.XKFaKtKOZB/tests/build/annotations.go:89 @ 04/20/26 07:01:16.795&#xA;build status annotation value: {&#34;message&#34;:&#34;unexpected build request: foo&#34;}&#xA;&lt; Exit [It] handles invalid request annotation - /tmp/tmp.XKFaKtKOZB/tests/build/annotations.go:89 @ 04/20/26 07:02:16.862 (1m0.067s)&#xA;&gt; Enter [AfterAll] test build annotations - /tmp/tmp.XKFaKtKOZB/tests/build/annotations.go:51 @ 04/20/26 07:02:16.862&#xA;&lt; Exit [AfterAll] test build annotations - /tmp/tmp.XKFaKtKOZB/tests/build/annotations.go:51 @ 04/20/26 07:02:17.196 (334ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/annotations.go:24 @ 04/20/26 07:02:17.196&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/annotations.go:24 @ 04/20/26 07:02:17.196 (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] [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="55.534325413">
              <system-err>&gt; Enter [BeforeAll] component update with renovate - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:72 @ 04/20/26 07:01:05.043&#xA;ReleaseAdmissionPlan data: {&#34;Mapping&#34;:{&#34;Components&#34;:[{&#34;Name&#34;:&#34;fj-multi-component-parent-tqhc&#34;,&#34;Repository&#34;:&#34;quay.io/redhat-appstudio-qe/release-repository&#34;}]}}&#xA;&lt; Exit [BeforeAll] component update with renovate - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:72 @ 04/20/26 07:01:20.293 (15.249s)&#xA;&gt; Enter [It] creates component with nudges - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:235 @ 04/20/26 07:01:20.293&#xA;Image repository for component fj-multi-component-child-tqhc in namespace build-e2e-lifs do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component fj-multi-component-child-tqhc in namespace build-e2e-lifs 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-tqhc in namespace build-e2e-lifs 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-tqhc in namespace build-e2e-lifs 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.XKFaKtKOZB/tests/build/renovate.go:235 @ 04/20/26 07:02:00.577 (40.284s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:02:00.577&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:02:00.578 (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="124.18214629">
              <system-err>&gt; Enter [It] triggers a PipelineRun for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:259 @ 04/20/26 07:02:00.578&#xA;PipelineRun has not been created yet for the component build-e2e-lifs/fj-multi-component-parent-tqhc&#xA;PipelineRun has not been created yet for the component build-e2e-lifs/fj-multi-component-parent-tqhc&#xA;PipelineRun has not been created yet for the component build-e2e-lifs/fj-multi-component-parent-tqhc&#xA;PipelineRun has not been created yet for the component build-e2e-lifs/fj-multi-component-parent-tqhc&#xA;PipelineRun has not been created yet for the component build-e2e-lifs/fj-multi-component-parent-tqhc&#xA;&lt; Exit [It] triggers a PipelineRun for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:259 @ 04/20/26 07:04:04.76 (2m4.182s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:04:04.76&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:04:04.76 (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="540.160184791">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:274 @ 04/20/26 07:04:04.76&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 found for Component build-e2e-lifs/fj-multi-component-parent-tqhc&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: ResolvingTaskRef&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: ResolvingTaskRef&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: ResolvingTaskRef&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-pull-request-8l9m9 reason: Completed&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:274 @ 04/20/26 07:13:04.92 (9m0.16s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:13:04.92&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:13:04.921 (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="20.253661179">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:285 @ 04/20/26 07:13:04.921&#xA;PipelineRun fj-multi-component-child-tqhc-on-pull-request-m8bg4 found for Component build-e2e-lifs/fj-multi-component-child-tqhc&#xA;PipelineRun fj-multi-component-child-tqhc-on-pull-request-m8bg4 reason: Running&#xA;PipelineRun fj-multi-component-child-tqhc-on-pull-request-m8bg4 reason: Completed&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:285 @ 04/20/26 07:13:25.174 (20.253s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:13:25.175&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:13:25.175 (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="0.455801168">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:289 @ 04/20/26 07:13:25.175&#xA;&lt; Exit [It] should lead to a PaC PR creation for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:289 @ 04/20/26 07:13:25.631 (455ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:13:25.631&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:13:25.631 (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="2.184531464">
              <system-err>&gt; Enter [It] Merging the PaC PR should be successful for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:307 @ 04/20/26 07:13:25.631&#xA;merged result sha: d65dacf2b17ab922b5cd48c4f16b1557b1741270 for PR #1&#xA;&lt; Exit [It] Merging the PaC PR should be successful for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:307 @ 04/20/26 07:13:27.815 (2.184s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:13:27.816&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:13:27.816 (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="7.1354626660000005">
              <system-err>&gt; Enter [It] create dockerfile and yaml manifest that references build and distribution repositories - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:318 @ 04/20/26 07:13:27.816&#xA;&lt; Exit [It] create dockerfile and yaml manifest that references build and distribution repositories - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:318 @ 04/20/26 07:13:34.951 (7.135s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:13:34.952&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:13:34.952 (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="0.187057867">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:358 @ 04/20/26 07:13:34.952&#xA;&lt; Exit [It] should lead to a PaC PR creation for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:358 @ 04/20/26 07:13:35.139 (187ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:13:35.139&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:13:35.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 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="1.991337402">
              <system-err>&gt; Enter [It] Merging the PaC PR should be successful for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:375 @ 04/20/26 07:13:35.139&#xA;merged result sha: ac525782cb7b52a48c8b6ba42acdc79d4191ddd3 for PR #1&#xA;&lt; Exit [It] Merging the PaC PR should be successful for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:375 @ 04/20/26 07:13:37.13 (1.991s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:13:37.131&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:13:37.131 (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="20.674239194">
              <system-err>&gt; Enter [It] PR merge triggers PAC PipelineRun for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:385 @ 04/20/26 07:13:37.131&#xA;Push PipelineRun has not been created yet for the component build-e2e-lifs/fj-multi-component-parent-tqhc&#xA;&lt; Exit [It] PR merge triggers PAC PipelineRun for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:385 @ 04/20/26 07:13:57.805 (20.674s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:13:57.805&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:13:57.805 (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="680.871520015">
              <system-err>&gt; Enter [It] PAC PipelineRun for parent component  is successful - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:401 @ 04/20/26 07:13:57.806&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz found for Component build-e2e-lifs/fj-multi-component-parent-tqhc&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: ResolvingTaskRef&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: ResolvingTaskRef&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: ResolvingTaskRef&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: ResolvingTaskRef&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Running&#xA;PipelineRun fj-multi-component-parent-tqhc-on-push-msgdz reason: Completed&#xA;&lt; Exit [It] PAC PipelineRun for parent component  is successful - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:401 @ 04/20/26 07:25:18.677 (11m20.871s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:25:18.677&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:25:18.677 (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="1209.108187786">
              <failure message="Timed out after 1200.000s.&#xA;timed out when waiting for component nudge PR to be created in build-nudge-child-twawir repository&#xA;Expected&#xA;    &lt;bool&gt;: false&#xA;to be true" type="failed">[FAILED] Timed out after 1200.000s.&#xA;timed out when waiting for component nudge PR to be created in build-nudge-child-twawir repository&#xA;Expected&#xA;    &lt;bool&gt;: false&#xA;to be true&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:427 @ 04/20/26 07:45:18.678&#xA;</failure>
              <system-err>&gt; Enter [It] should lead to a nudge PR creation for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:412 @ 04/20/26 07:25:18.678&#xA;[FAILED] Timed out after 1200.000s.&#xA;timed out when waiting for component nudge PR to be created in build-nudge-child-twawir repository&#xA;Expected&#xA;    &lt;bool&gt;: false&#xA;to be true&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:427 @ 04/20/26 07:45:18.678&#xA;&lt; Exit [It] should lead to a nudge PR creation for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:412 @ 04/20/26 07:45:18.678 (20m0.001s)&#xA;&gt; Enter [AfterAll] component update with renovate - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:214 @ 04/20/26 07:45:18.679&#xA;&lt; Exit [AfterAll] component update with renovate - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:214 @ 04/20/26 07:45:26.701 (8.022s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:45:26.701&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:45:27.786 (1.084s)&#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.XKFaKtKOZB/tests/build/renovate.go:429 @ 04/20/26 07:45:27.787&#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.XKFaKtKOZB/tests/build/renovate.go:440 @ 04/20/26 07:45:27.787&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private correctly targets the default branch (that is not named &#39;main&#39;) with PaC [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="110.547004354">
              <system-err>&gt; Enter [BeforeAll] PaC component build - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:55 @ 04/20/26 07:01:05.044&#xA;&lt; Exit [BeforeAll] PaC component build - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:55 @ 04/20/26 07:01:23.112 (18.068s)&#xA;&gt; Enter [BeforeAll] when a new component without specified branch is created and with visibility private - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:118 @ 04/20/26 07:01:23.112&#xA;Image repository for component gl-test-custom-default-zybmpm in namespace build-e2e-cbhv do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component gl-test-custom-default-zybmpm in namespace build-e2e-cbhv 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.XKFaKtKOZB/tests/build/pac_build.go:118 @ 04/20/26 07:01:43.241 (20.129s)&#xA;&gt; Enter [It] correctly targets the default branch (that is not named &#39;main&#39;) with PaC - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:137 @ 04/20/26 07:01:43.241&#xA;&lt; Exit [It] correctly targets the default branch (that is not named &#39;main&#39;) with PaC - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:137 @ 04/20/26 07:02:55.59 (1m12.349s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:02:55.59&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:02:55.59 (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.123298938">
              <system-err>&gt; Enter [It] workspace parameter is set correctly in PaC repository CR - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:154 @ 04/20/26 07:02:55.591&#xA;&lt; Exit [It] workspace parameter is set correctly in PaC repository CR - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:154 @ 04/20/26 07:02:55.714 (123ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:02:55.714&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:02:55.714 (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.187651939">
              <system-err>&gt; Enter [It] triggers a PipelineRun - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:177 @ 04/20/26 07:02:55.714&#xA;PipelineRun has not been created yet for the component build-e2e-cbhv/gl-test-custom-branch-ktjgma&#xA;&lt; Exit [It] triggers a PipelineRun - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:177 @ 04/20/26 07:03:15.902 (20.187s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:15.902&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:15.902 (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.000313406">
              <system-err>&gt; Enter [It] build pipeline uses the correct serviceAccount - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:192 @ 04/20/26 07:03:15.903&#xA;&lt; Exit [It] build pipeline uses the correct serviceAccount - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:192 @ 04/20/26 07:03:15.903 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:15.903&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:15.903 (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.064640416">
              <system-err>&gt; Enter [It] component build status is set correctly - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:196 @ 04/20/26 07:03:15.903&#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-gsgnpn/-/merge_requests/1&#34;,&#34;configuration-time&#34;:&#34;Mon, 20 Apr 2026 07:02:52 UTC&#34;},&#34;message&#34;:&#34;done&#34;}&#xA;state: enabled&#xA;mergeUrl: https://gitlab.com/konflux-qe/devfile-sample-hello-world-gsgnpn/-/merge_requests/1&#xA;errId: 0&#xA;errMessage: &#xA;configurationTime: Mon, 20 Apr 2026 07:02:52 UTC&#xA;&lt; Exit [It] component build status is set correctly - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:196 @ 04/20/26 07:03:15.967 (64ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:15.968&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:15.968 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.970601997">
              <system-err>&gt; Enter [It] image repo and robot account created successfully - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:226 @ 04/20/26 07:03:15.968&#xA;&lt; Exit [It] image repo and robot account created successfully - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:226 @ 04/20/26 07:03:16.938 (970ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:16.939&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:16.939 (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.274432109">
              <system-err>&gt; Enter [It] created image repo is private - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:244 @ 04/20/26 07:03:16.939&#xA;&lt; Exit [It] created image repo is private - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:244 @ 04/20/26 07:03:17.213 (274ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:17.213&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:17.213 (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="46.73207979">
              <system-err>&gt; Enter [It] a related PipelineRun should be deleted after deleting the component - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:250 @ 04/20/26 07:03:17.214&#xA;&lt; Exit [It] a related PipelineRun should be deleted after deleting the component - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:250 @ 04/20/26 07:04:03.946 (46.732s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:04:03.946&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:04:03.946 (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.168417041">
              <system-err>&gt; Enter [It] PR branch should not exist in the repo - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:266 @ 04/20/26 07:04:03.946&#xA;&lt; Exit [It] PR branch should not exist in the repo - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:266 @ 04/20/26 07:04:04.114 (168ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:04:04.115&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:04:04.115 (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="0.845785097">
              <system-err>&gt; Enter [It] related image repo and the robot account should be deleted after deleting the component - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:279 @ 04/20/26 07:04:04.115&#xA;&lt; Exit [It] related image repo and the robot account should be deleted after deleting the component - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:279 @ 04/20/26 07:04:04.961 (845ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:04:04.961&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:04:04.961 (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="55.654553427">
              <system-err>&gt; Enter [BeforeAll] when a new Component with specified custom branch is created - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:307 @ 04/20/26 07:04:04.961&#xA;Image repository for component gl-test-custom-branch-ktjgma in namespace build-e2e-cbhv 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.XKFaKtKOZB/tests/build/pac_build.go:307 @ 04/20/26 07:04:20.355 (15.394s)&#xA;&gt; Enter [It] triggers a PipelineRun - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:333 @ 04/20/26 07:04:20.355&#xA;PipelineRun has not been created yet for the component build-e2e-cbhv/gl-test-custom-branch-ktjgma&#xA;PipelineRun has not been created yet for the component build-e2e-cbhv/gl-test-custom-branch-ktjgma&#xA;&lt; Exit [It] triggers a PipelineRun - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:333 @ 04/20/26 07:05:00.616 (40.26s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:05:00.616&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:05:00.616 (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.510614751">
              <system-err>&gt; Enter [It] should lead to a PaC init PR creation - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:348 @ 04/20/26 07:05:00.616&#xA;&lt; Exit [It] should lead to a PaC init PR creation - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:348 @ 04/20/26 07:05:01.127 (510ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:05:01.127&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:05:01.127 (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="failed" time="2887.568660974">
              <failure message="Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc00197ad70&gt;: &#xA;    &#xA;     pod: gl-test-custom-branch-ktjgma-on-pull-request-n9phc-init-pod | init container: prepare&#xA;    2026/04/20 07:46:23 Entrypoint initialization&#xA;    &#xA;    pod: gl-test-custom-branch-ktjgma-on-pull-request-n9phc-init-pod | container step-init: &#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;    time=&#34;2026-04-20T07:46:50Z&#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-20T07:46:50Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;    &#xA;    {&#xA;        s: &#34;\n pod: gl-test-custom-branch-ktjgma-on-pull-request-n9phc-init-pod | init container: prepare\n2026/04/20 07:46:23 Entrypoint initialization\n\npod: gl-test-custom-branch-ktjgma-on-pull-request-n9phc-init-pod | container step-init: \ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;Using in-cluster config\&#34; logger=KubeClient\ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;[param] enable: false\&#34;\ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128\&#34;\ntime=\&#34;2026-04-20T07:46:50Z\&#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-20T07:46:50Z\&#34; level=info msg=\&#34;[param] http-proxy-result-path: /tekton/results/http-proxy\&#34;\ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;[param] no-proxy-result-path: /tekton/results/no-proxy\&#34;\ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;Cache proxy is disabled in param or in backend\&#34;\ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;[result] HTTP PROXY: \&#34;\ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;[result] NO PROXY: \&#34;\n&#34;,&#xA;    }" type="failed">[FAILED] Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc00197ad70&gt;: &#xA;    &#xA;     pod: gl-test-custom-branch-ktjgma-on-pull-request-n9phc-init-pod | init container: prepare&#xA;    2026/04/20 07:46:23 Entrypoint initialization&#xA;    &#xA;    pod: gl-test-custom-branch-ktjgma-on-pull-request-n9phc-init-pod | container step-init: &#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;    time=&#34;2026-04-20T07:46:50Z&#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-20T07:46:50Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;    &#xA;    {&#xA;        s: &#34;\n pod: gl-test-custom-branch-ktjgma-on-pull-request-n9phc-init-pod | init container: prepare\n2026/04/20 07:46:23 Entrypoint initialization\n\npod: gl-test-custom-branch-ktjgma-on-pull-request-n9phc-init-pod | container step-init: \ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;Using in-cluster config\&#34; logger=KubeClient\ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;[param] enable: false\&#34;\ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128\&#34;\ntime=\&#34;2026-04-20T07:46:50Z\&#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-20T07:46:50Z\&#34; level=info msg=\&#34;[param] http-proxy-result-path: /tekton/results/http-proxy\&#34;\ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;[param] no-proxy-result-path: /tekton/results/no-proxy\&#34;\ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;Cache proxy is disabled in param or in backend\&#34;\ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;[result] HTTP PROXY: \&#34;\ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;[result] NO PROXY: \&#34;\n&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:368 @ 04/20/26 07:53:04.335&#xA;</failure>
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:366 @ 04/20/26 07:05:01.127&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh found for Component build-e2e-cbhv/gl-test-custom-branch-ktjgma&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: ResolvingTaskRef&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: ResolvingTaskRef&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: ResolvingTaskRef&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: ResolvingTaskRef&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: ResolvingTaskRef&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-chlvh reason: Failed&#xA;attempt 1/3: PipelineRun &#34;gl-test-custom-branch-ktjgma-on-pull-request-chlvh&#34; failed: &#xA; pod: gl-test-custom-branch-ktjgma-on-pull-request-chlvh-init-pod | init container: prepare&#xA;2026/04/20 07:06:40 Entrypoint initialization&#xA;&#xA;pod: gl-test-custom-branch-ktjgma-on-pull-request-chlvh-init-pod | container step-init: &#xA;time=&#34;2026-04-20T07:07:06Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-20T07:07:06Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-20T07:07:06Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-20T07:07:06Z&#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-20T07:07:06Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-20T07:07:06Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-20T07:07:06Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;time=&#34;2026-04-20T07:07:06Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-20T07:07:06Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;New PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 found after retrigger for component build-e2e-cbhv/gl-test-custom-branch-ktjgma&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 found for Component build-e2e-cbhv/gl-test-custom-branch-ktjgma&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: ResolvingTaskRef&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: ResolvingTaskRef&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun has not been created yet for the Component build-e2e-cbhv/gl-test-custom-branch-ktjgma&#xA;PipelineRun has not been created yet for the Component build-e2e-cbhv/gl-test-custom-branch-ktjgma&#xA;PipelineRun has not been created yet for the Component build-e2e-cbhv/gl-test-custom-branch-ktjgma&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun has not been created yet for the Component build-e2e-cbhv/gl-test-custom-branch-ktjgma&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-6qdq8 reason: Failed&#xA;attempt 2/3: PipelineRun &#34;gl-test-custom-branch-ktjgma-on-pull-request-6qdq8&#34; failed: &#xA; pod: gl-test-custom-branch-ktjgma-on-pull-request-6qdq8-init-pod | init container: prepare&#xA;2026/04/20 07:20:30 Entrypoint initialization&#xA;&#xA;pod: gl-test-custom-branch-ktjgma-on-pull-request-6qdq8-init-pod | container step-init: &#xA;time=&#34;2026-04-20T07:24:32Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-20T07:24:32Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-20T07:24:32Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-20T07:24:32Z&#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-20T07:24:32Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-20T07:24:32Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-20T07:24:33Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;time=&#34;2026-04-20T07:24:33Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-20T07:24:33Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;New PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc found after retrigger for component build-e2e-cbhv/gl-test-custom-branch-ktjgma&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc found for Component build-e2e-cbhv/gl-test-custom-branch-ktjgma&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: &#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: ResolvingTaskRef&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: ResolvingTaskRef&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: ResolvingTaskRef&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: ResolvingTaskRef&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: ResolvingTaskRef&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Running&#xA;PipelineRun gl-test-custom-branch-ktjgma-on-pull-request-n9phc reason: Failed&#xA;attempt 3/3: PipelineRun &#34;gl-test-custom-branch-ktjgma-on-pull-request-n9phc&#34; failed: &#xA; pod: gl-test-custom-branch-ktjgma-on-pull-request-n9phc-init-pod | init container: prepare&#xA;2026/04/20 07:46:23 Entrypoint initialization&#xA;&#xA;pod: gl-test-custom-branch-ktjgma-on-pull-request-n9phc-init-pod | container step-init: &#xA;time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-20T07:46:50Z&#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-20T07:46:50Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;[FAILED] Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc00197ad70&gt;: &#xA;    &#xA;     pod: gl-test-custom-branch-ktjgma-on-pull-request-n9phc-init-pod | init container: prepare&#xA;    2026/04/20 07:46:23 Entrypoint initialization&#xA;    &#xA;    pod: gl-test-custom-branch-ktjgma-on-pull-request-n9phc-init-pod | container step-init: &#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;    time=&#34;2026-04-20T07:46:50Z&#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-20T07:46:50Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;    time=&#34;2026-04-20T07:46:50Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;    &#xA;    {&#xA;        s: &#34;\n pod: gl-test-custom-branch-ktjgma-on-pull-request-n9phc-init-pod | init container: prepare\n2026/04/20 07:46:23 Entrypoint initialization\n\npod: gl-test-custom-branch-ktjgma-on-pull-request-n9phc-init-pod | container step-init: \ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;Using in-cluster config\&#34; logger=KubeClient\ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;[param] enable: false\&#34;\ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128\&#34;\ntime=\&#34;2026-04-20T07:46:50Z\&#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-20T07:46:50Z\&#34; level=info msg=\&#34;[param] http-proxy-result-path: /tekton/results/http-proxy\&#34;\ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;[param] no-proxy-result-path: /tekton/results/no-proxy\&#34;\ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;Cache proxy is disabled in param or in backend\&#34;\ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;[result] HTTP PROXY: \&#34;\ntime=\&#34;2026-04-20T07:46:50Z\&#34; level=info msg=\&#34;[result] NO PROXY: \&#34;\n&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:368 @ 04/20/26 07:53:04.335&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:366 @ 04/20/26 07:53:04.335 (48m3.207s)&#xA;&gt; Enter [AfterAll] when a new Component with specified custom branch is created - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:325 @ 04/20/26 07:53:04.335&#xA;&lt; Exit [AfterAll] when a new Component with specified custom branch is created - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:325 @ 04/20/26 07:53:04.481 (146ms)&#xA;&gt; Enter [AfterAll] PaC component build - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:102 @ 04/20/26 07:53:04.481&#xA;&lt; Exit [AfterAll] PaC component build - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:102 @ 04/20/26 07:53:04.481 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:53:04.481&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:53:08.696 (4.215s)&#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="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:372 @ 04/20/26 07:53:08.697&#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 floating tags are created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:391 @ 04/20/26 07:53:08.697&#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="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:404 @ 04/20/26 07:53:08.697&#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="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:410 @ 04/20/26 07:53:08.697&#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="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:439 @ 04/20/26 07:53:08.698&#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="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:453 @ 04/20/26 07:53:08.698&#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="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:478 @ 04/20/26 07:53:08.698&#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="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:493 @ 04/20/26 07:53:08.698&#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="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:512 @ 04/20/26 07:53:08.699&#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="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:518 @ 04/20/26 07:53:08.699&#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="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:544 @ 04/20/26 07:53:08.699&#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="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:560 @ 04/20/26 07:53:08.699&#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="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:566 @ 04/20/26 07:53:08.699&#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="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:578 @ 04/20/26 07:53:08.7&#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="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:609 @ 04/20/26 07:53:08.7&#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="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:729 @ 04/20/26 07:53:08.701&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace creates component with context directory go-component [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="passed" time="12.245109251">
              <system-err>&gt; Enter [BeforeAll] test pac with multiple components using same repository - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:40 @ 04/20/26 07:01:05.147&#xA;&lt; Exit [BeforeAll] test pac with multiple components using same repository - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:40 @ 04/20/26 07:01:07.206 (2.059s)&#xA;&gt; Enter [It] creates component with context directory go-component - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:106 @ 04/20/26 07:01:07.206&#xA;Image repository for component go-component-bmztel in namespace build-e2e-uymt 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.XKFaKtKOZB/tests/build/multi_component.go:106 @ 04/20/26 07:01:17.39 (10.184s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:28 @ 04/20/26 07:01:17.391&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:28 @ 04/20/26 07:01:17.391 (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-bmztel [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="passed" time="40.234333552">
              <system-err>&gt; Enter [It] triggers a PipelineRun for component go-component-bmztel - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:125 @ 04/20/26 07:01:17.391&#xA;PipelineRun has not been created yet for the component build-e2e-uymt/go-component-bmztel&#xA;PipelineRun has not been created yet for the component build-e2e-uymt/go-component-bmztel&#xA;&lt; Exit [It] triggers a PipelineRun for component go-component-bmztel - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:125 @ 04/20/26 07:01:57.625 (40.234s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:28 @ 04/20/26 07:01:57.625&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:28 @ 04/20/26 07:01:57.625 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace should lead to a PaC PR creation for component go-component-bmztel [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="passed" time="0.384969124">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for component go-component-bmztel - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:140 @ 04/20/26 07:01:57.626&#xA;&lt; Exit [It] should lead to a PaC PR creation for component go-component-bmztel - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:140 @ 04/20/26 07:01:58.011 (384ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:28 @ 04/20/26 07:01:58.011&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:28 @ 04/20/26 07:01:58.011 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace the PipelineRun should eventually finish successfully for component go-component-bmztel [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="passed" time="680.116964698">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for component go-component-bmztel - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:159 @ 04/20/26 07:01:58.012&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj found for Component build-e2e-uymt/go-component-bmztel&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Running&#xA;PipelineRun go-component-bmztel-on-pull-request-frwnj reason: Completed&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for component go-component-bmztel - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:159 @ 04/20/26 07:13:18.128 (11m20.117s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:28 @ 04/20/26 07:13:18.128&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:28 @ 04/20/26 07:13:18.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 merging the PR should be successful [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="passed" time="1.9448716560000001">
              <system-err>&gt; Enter [It] merging the PR should be successful - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:164 @ 04/20/26 07:13:18.129&#xA;merged result sha: dd689b8d243d19034b8191fd036ea496db59aa76 for PR #32472&#xA;&lt; Exit [It] merging the PR should be successful - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:164 @ 04/20/26 07:13:20.073 (1.944s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:28 @ 04/20/26 07:13:20.074&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:28 @ 04/20/26 07:13:20.074 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace leads to triggering on push PipelineRun [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="passed" time="20.258675727">
              <system-err>&gt; Enter [It] leads to triggering on push PipelineRun - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:174 @ 04/20/26 07:13:20.074&#xA;Push PipelineRun has not been created yet for the component build-e2e-uymt/go-component-bmztel&#xA;&lt; Exit [It] leads to triggering on push PipelineRun - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:174 @ 04/20/26 07:13:40.332 (20.258s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:28 @ 04/20/26 07:13:40.333&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:28 @ 04/20/26 07:13:40.333 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace creates component with context directory python-component [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="passed" time="10.160080518000001">
              <system-err>&gt; Enter [It] creates component with context directory python-component - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:106 @ 04/20/26 07:13:40.333&#xA;Image repository for component python-component-qneryh in namespace build-e2e-uymt 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 python-component - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:106 @ 04/20/26 07:13:50.493 (10.16s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:28 @ 04/20/26 07:13:50.493&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:28 @ 04/20/26 07:13:50.493 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace triggers a PipelineRun for component python-component-qneryh [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="passed" time="20.180379273">
              <system-err>&gt; Enter [It] triggers a PipelineRun for component python-component-qneryh - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:125 @ 04/20/26 07:13:50.494&#xA;PipelineRun has not been created yet for the component build-e2e-uymt/python-component-qneryh&#xA;&lt; Exit [It] triggers a PipelineRun for component python-component-qneryh - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:125 @ 04/20/26 07:14:10.674 (20.18s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:28 @ 04/20/26 07:14:10.674&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:28 @ 04/20/26 07:14:10.674 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace should lead to a PaC PR creation for component python-component-qneryh [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="passed" time="0.366289233">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for component python-component-qneryh - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:140 @ 04/20/26 07:14:10.674&#xA;&lt; Exit [It] should lead to a PaC PR creation for component python-component-qneryh - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:140 @ 04/20/26 07:14:11.04 (366ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:28 @ 04/20/26 07:14:11.04&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:28 @ 04/20/26 07:14:11.04 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace the PipelineRun should eventually finish successfully for component python-component-qneryh [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="failed" time="2516.849357744">
              <failure message="Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc001729420&gt;: &#xA;    &#xA;     pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | init container: prepare&#xA;    2026/04/20 07:40:55 Entrypoint initialization&#xA;    &#xA;     pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | init container: place-scripts&#xA;    2026/04/20 07:41:14 Decoded script /tekton/scripts/script-0-dswv9&#xA;    2026/04/20 07:41:14 Decoded script /tekton/scripts/script-1-jclgq&#xA;    &#xA;    pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | container step-clone: &#xA;    INFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#xA;    {&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776670916.3477,&#34;caller&#34;:&#34;git/git.go:394&#34;,&#34;msg&#34;:&#34;Retrying operation (attempt 1)&#34;}&#xA;    {&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776670925.2353692,&#34;caller&#34;:&#34;git/git.go:223&#34;,&#34;msg&#34;:&#34;Successfully cloned https://github.com/redhat-appstudio-qe/sample-multi-component @ 436f80634af29d23253f16847b366d05e48e563d (grafted, HEAD) in path /workspace/output/source&#34;}&#xA;    {&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776670925.235458,&#34;caller&#34;:&#34;git/git.go:394&#34;,&#34;msg&#34;:&#34;Retrying operation (attempt 1)&#34;}&#xA;    {&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776670925.2869456,&#34;caller&#34;:&#34;git/git.go:277&#34;,&#34;msg&#34;:&#34;Successfully initialized and updated submodules in path /workspace/output/source&#34;}&#xA;    Merge option disabled. Using checked-out revision 436f80634af29d23253f16847b366d05e48e563d directly.&#xA;    &#xA;    pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | container step-symlink-check: &#xA;    Running symlink check&#xA;    &#xA;     pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | init container: prepare&#xA;    2026/04/20 07:52:24 Entrypoint initialization&#xA;    &#xA;     pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | init container: place-scripts&#xA;    &#xA;    pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | container step-build: &#xA;    &#xA;    {&#xA;        s: &#34;\n pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | init container: prepare\n2026/04/20 07:40:55 Entrypoint initialization\n\n pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | init container: place-scripts\n2026/04/20 07:41:14 Decoded script /tekton/scripts/script-0-dswv9\n2026/04/20 07:41:14 Decoded script /tekton/scripts/script-1-jclgq\n\npod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | container step-clone: \nINFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt\n{\&#34;level\&#34;:\&#34;info\&#34;,\&#34;ts\&#34;:1776670916.3477,\&#34;caller\&#34;:\&#34;git/git.go:394\&#34;,\&#34;msg\&#34;:\&#34;Retrying operation (attempt 1)\&#34;}\n{\&#34;level\&#34;:\&#34;info\&#34;,\&#34;ts\&#34;:1776670925.2353692,\&#34;caller\&#34;:\&#34;git/git.go:223\&#34;,\&#34;msg\&#34;:\&#34;Successfully cloned https://github.com/redhat-appstudio-qe/sample-multi-component @ 436f80634af29d23253f16847b366d05e48e563d (grafted, HEAD) in path /workspace/output/source\&#34;}\n{\&#34;level\&#34;:\&#34;info\&#34;,\&#34;ts\&#34;:1776670925.235458,\&#34;caller\&#34;:\&#34;git/git.go:394\&#34;,\&#34;msg\&#34;:\&#34;Retrying operation (attempt 1)\&#34;}\n{\&#34;level\&#34;:\&#34;info\&#34;,\&#34;ts\&#34;:1776670925.2869456,\&#34;caller\&#34;:\&#34;git/git.go:277\&#34;,\&#34;msg\&#34;:\&#34;Successfully initialized and updated submodules in path /workspace/output/source\&#34;}\nMerge option disabled. Using checked-out revision 436f80634af29d23253f16847b366d05e48e563d directly.\n\npod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | container step-symlink-check: \nRunning symlink check\n\n pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | init container: prepare\n2026/04/20 07:52:24 Entrypoint initialization\n\n pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | init container: place-scripts\n\npod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | container step-build: \n&#34;,&#xA;    }" type="failed">[FAILED] Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc001729420&gt;: &#xA;    &#xA;     pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | init container: prepare&#xA;    2026/04/20 07:40:55 Entrypoint initialization&#xA;    &#xA;     pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | init container: place-scripts&#xA;    2026/04/20 07:41:14 Decoded script /tekton/scripts/script-0-dswv9&#xA;    2026/04/20 07:41:14 Decoded script /tekton/scripts/script-1-jclgq&#xA;    &#xA;    pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | container step-clone: &#xA;    INFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#xA;    {&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776670916.3477,&#34;caller&#34;:&#34;git/git.go:394&#34;,&#34;msg&#34;:&#34;Retrying operation (attempt 1)&#34;}&#xA;    {&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776670925.2353692,&#34;caller&#34;:&#34;git/git.go:223&#34;,&#34;msg&#34;:&#34;Successfully cloned https://github.com/redhat-appstudio-qe/sample-multi-component @ 436f80634af29d23253f16847b366d05e48e563d (grafted, HEAD) in path /workspace/output/source&#34;}&#xA;    {&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776670925.235458,&#34;caller&#34;:&#34;git/git.go:394&#34;,&#34;msg&#34;:&#34;Retrying operation (attempt 1)&#34;}&#xA;    {&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776670925.2869456,&#34;caller&#34;:&#34;git/git.go:277&#34;,&#34;msg&#34;:&#34;Successfully initialized and updated submodules in path /workspace/output/source&#34;}&#xA;    Merge option disabled. Using checked-out revision 436f80634af29d23253f16847b366d05e48e563d directly.&#xA;    &#xA;    pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | container step-symlink-check: &#xA;    Running symlink check&#xA;    &#xA;     pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | init container: prepare&#xA;    2026/04/20 07:52:24 Entrypoint initialization&#xA;    &#xA;     pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | init container: place-scripts&#xA;    &#xA;    pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | container step-build: &#xA;    &#xA;    {&#xA;        s: &#34;\n pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | init container: prepare\n2026/04/20 07:40:55 Entrypoint initialization\n\n pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | init container: place-scripts\n2026/04/20 07:41:14 Decoded script /tekton/scripts/script-0-dswv9\n2026/04/20 07:41:14 Decoded script /tekton/scripts/script-1-jclgq\n\npod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | container step-clone: \nINFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt\n{\&#34;level\&#34;:\&#34;info\&#34;,\&#34;ts\&#34;:1776670916.3477,\&#34;caller\&#34;:\&#34;git/git.go:394\&#34;,\&#34;msg\&#34;:\&#34;Retrying operation (attempt 1)\&#34;}\n{\&#34;level\&#34;:\&#34;info\&#34;,\&#34;ts\&#34;:1776670925.2353692,\&#34;caller\&#34;:\&#34;git/git.go:223\&#34;,\&#34;msg\&#34;:\&#34;Successfully cloned https://github.com/redhat-appstudio-qe/sample-multi-component @ 436f80634af29d23253f16847b366d05e48e563d (grafted, HEAD) in path /workspace/output/source\&#34;}\n{\&#34;level\&#34;:\&#34;info\&#34;,\&#34;ts\&#34;:1776670925.235458,\&#34;caller\&#34;:\&#34;git/git.go:394\&#34;,\&#34;msg\&#34;:\&#34;Retrying operation (attempt 1)\&#34;}\n{\&#34;level\&#34;:\&#34;info\&#34;,\&#34;ts\&#34;:1776670925.2869456,\&#34;caller\&#34;:\&#34;git/git.go:277\&#34;,\&#34;msg\&#34;:\&#34;Successfully initialized and updated submodules in path /workspace/output/source\&#34;}\nMerge option disabled. Using checked-out revision 436f80634af29d23253f16847b366d05e48e563d directly.\n\npod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | container step-symlink-check: \nRunning symlink check\n\n pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | init container: prepare\n2026/04/20 07:52:24 Entrypoint initialization\n\n pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | init container: place-scripts\n\npod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | container step-build: \n&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:161 @ 04/20/26 07:56:05.48&#xA;</failure>
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for component python-component-qneryh - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:159 @ 04/20/26 07:14:11.041&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc found for Component build-e2e-uymt/python-component-qneryh&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun has not been created yet for the Component build-e2e-uymt/python-component-qneryh&#xA;PipelineRun has not been created yet for the Component build-e2e-uymt/python-component-qneryh&#xA;PipelineRun has not been created yet for the Component build-e2e-uymt/python-component-qneryh&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun has not been created yet for the Component build-e2e-uymt/python-component-qneryh&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-4c5tc reason: Failed&#xA;attempt 1/3: PipelineRun &#34;python-component-qneryh-on-pull-request-4c5tc&#34; failed: &#xA; pod: python-component-qneryh-on-4cc81904d830c06e94b0fdc14701bee2-pod | init container: prepare&#xA;2026/04/20 07:16:49 Entrypoint initialization&#xA;&#xA; pod: python-component-qneryh-on-4cc81904d830c06e94b0fdc14701bee2-pod | init container: place-scripts&#xA;2026/04/20 07:16:50 Decoded script /tekton/scripts/script-0-kdd56&#xA;2026/04/20 07:16:50 Decoded script /tekton/scripts/script-1-kd2rx&#xA;2026/04/20 07:16:50 Decoded script /tekton/scripts/script-2-dvdpp&#xA;2026/04/20 07:16:50 Decoded script /tekton/scripts/script-3-n56kc&#xA;2026/04/20 07:16:50 Decoded script /tekton/scripts/script-4-vxmhq&#xA;&#xA; pod: python-component-qneryh-on-4cc81904d830c06e94b0fdc14701bee2-pod | init container: working-dir-initializer&#xA;&#xA;pod: python-component-qneryh-on-4cc81904d830c06e94b0fdc14701bee2-pod | container step-build: &#xA;[2026-04-20T07:16:58,697244361+00:00] Validate context path&#xA;[2026-04-20T07:16:58,703503816+00:00] Update CA trust&#xA;[2026-04-20T07:16:58,705565584+00:00] Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#xA;&#39;/mnt/trusted-ca/ca-bundle.crt&#39; -&gt; &#39;/etc/pki/ca-trust/source/anchors/ca-bundle.crt&#39;&#xA;[2026-04-20T07:17:05,545715158+00:00] Prepare Dockerfile&#xA;Checking if /var/workdir/cachi2/output/bom.json exists.&#xA;Could not find prefetched sbom. No content_sets found for ICM&#xA;[2026-04-20T07:17:05,559580414+00:00] Prepare system (architecture: x86_64)&#xA;[2026-04-20T07:17:05,588937025+00:00] Setup prefetched&#xA;Trying to pull registry.access.redhat.com/ubi9/python-39:1-117.1684741281...&#xA;Getting image source signatures&#xA;Checking if image destination supports signatures&#xA;Copying blob sha256:8a2e9815396eaa57b0dfe27b2dfc442417f06aa70974c358f198980b533c7942&#xA;Copying blob sha256:5465449a2ea5d8a7e05fa498c8ba35f0ce7714b0ad37e716961fca17dfa1ef13&#xA;Copying blob sha256:085efe85e9dfb0b3d5d2392e4b78660a3091bf1ded336315117a627fbdd0567d&#xA;Copying blob sha256:a07d808ddf4404b3885fef6100142a973cc667b2c3c4abcf4db96508795b1efb&#xA;Copying config sha256:45c8f23c11bb64f238236aaf5cbe05595778e1d4fb6c06109c6fcc0a6b57a45b&#xA;Writing manifest to image destination&#xA;Storing signatures&#xA;[2026-04-20T07:17:47,059580204+00:00] Unsetting proxy&#xA;{&#xA;  &#34;architecture&#34;: &#34;x86_64&#34;,&#xA;  &#34;build-date&#34;: &#34;2026-04-20T07:17:05Z&#34;,&#xA;  &#34;com.redhat.component&#34;: &#34;python-39-container&#34;,&#xA;  &#34;com.redhat.license_terms&#34;: &#34;https://www.redhat.com/en/about/red-hat-end-user-license-agreements#UBI&#34;,&#xA;  &#34;description&#34;: &#34;Python 3.9 available as container is a base platform for building and running various Python 3.9 applications and frameworks. Python is an easy to learn, powerful programming language. It has efficient high-level data structures and a simple but effective approach to object-oriented programming. Python&#39;s elegant syntax and dynamic typing, together with its interpreted nature, make it an ideal language for scripting and rapid application development in many areas on most platforms.&#34;,&#xA;  &#34;distribution-scope&#34;: &#34;public&#34;,&#xA;  &#34;io.buildah.version&#34;: &#34;1.42.2&#34;,&#xA;  &#34;io.buildpacks.stack.id&#34;: &#34;com.redhat.stacks.ubi9-python-39&#34;,&#xA;  &#34;io.k8s.description&#34;: &#34;Python 3.9 available as container is a base platform for building and running various Python 3.9 applications and frameworks. Python is an easy to learn, powerful programming language. It has efficient high-level data structures and a simple but effective approach to object-oriented programming. Python&#39;s elegant syntax and dynamic typing, together with its interpreted nature, make it an ideal language for scripting and rapid application development in many areas on most platforms.&#34;,&#xA;  &#34;io.k8s.display-name&#34;: &#34;Python 3.9&#34;,&#xA;  &#34;io.openshift.expose-services&#34;: &#34;8080:http&#34;,&#xA;  &#34;io.openshift.s2i.scripts-url&#34;: &#34;image:///usr/libexec/s2i&#34;,&#xA;  &#34;io.openshift.tags&#34;: &#34;builder,python,python39,python-39,rh-python39&#34;,&#xA;  &#34;io.s2i.scripts-url&#34;: &#34;image:///usr/libexec/s2i&#34;,&#xA;  &#34;maintainer&#34;: &#34;SoftwareCollections.org &lt;sclorg@redhat.com&gt;&#34;,&#xA;  &#34;name&#34;: &#34;ubi9/python-39&#34;,&#xA;  &#34;release&#34;: &#34;117.1684741281&#34;,&#xA;  &#34;summary&#34;: &#34;Platform for building and running Python 3.9 applications&#34;,&#xA;  &#34;url&#34;: &#34;https://access.redhat.com/containers/#/registry.access.redhat.com/ubi9/python-39/images/1-117.1684741281&#34;,&#xA;  &#34;usage&#34;: &#34;s2i build https://github.com/sclorg/s2i-python-container.git --context-dir=3.9/test/setup-test-app/ ubi9/python-39 python-sample-app&#34;,&#xA;  &#34;vcs-ref&#34;: &#34;ef445b5c6314a21228b14212dd382739dd3e93bf&#34;,&#xA;  &#34;vcs-type&#34;: &#34;git&#34;,&#xA;  &#34;vendor&#34;: &#34;Red Hat, Inc.&#34;,&#xA;  &#34;version&#34;: &#34;1&#34;,&#xA;  &#34;org.opencontainers.image.revision&#34;: &#34;ef445b5c6314a21228b14212dd382739dd3e93bf&#34;,&#xA;  &#34;org.opencontainers.image.source&#34;: &#34;https://github.com/redhat-appstudio-qe/sample-multi-component&#34;,&#xA;  &#34;quay.expires-after&#34;: &#34;5d&#34;,&#xA;  &#34;org.opencontainers.image.created&#34;: &#34;2026-04-20T07:17:05Z&#34;&#xA;}&#xA;[2026-04-20T07:17:47,201203883+00:00] Register sub-man&#xA;Adding the entitlement to the build&#xA;[2026-04-20T07:17:47,213990258+00:00] Add secrets&#xA;[2026-04-20T07:17:47,305730078+00:00] Run buildah build&#xA;[2026-04-20T07:17:47,308043071+00:00] buildah build --volume /tmp/entitlement:/etc/pki/entitlement --security-opt=unmask=/proc/interrupts --label architecture=x86_64 --label vcs-type=git --label vcs-ref=ef445b5c6314a21228b14212dd382739dd3e93bf --label org.opencontainers.image.revision=ef445b5c6314a21228b14212dd382739dd3e93bf --label org.opencontainers.image.source=https://github.com/redhat-appstudio-qe/sample-multi-component --label quay.expires-after=5d --label build-date=2026-04-20T07:17:05Z --label org.opencontainers.image.created=2026-04-20T07:17:05Z --annotation org.opencontainers.image.revision=ef445b5c6314a21228b14212dd382739dd3e93bf --annotation org.opencontainers.image.source=https://github.com/redhat-appstudio-qe/sample-multi-component --annotation org.opencontainers.image.created=2026-04-20T07:17:05Z --tls-verify=true --no-cache --ulimit nofile=4096:4096 --http-proxy=false -f /tmp/Dockerfile.FdiIld -t quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh:on-pr-ef445b5c6314a21228b14212dd382739dd3e93bf . &#xA;STEP 1/10: FROM registry.access.redhat.com/ubi9/python-39:1-117.1684741281&#xA;STEP 2/10: EXPOSE 8081/tcp&#xA;STEP 3/10: ENV FLASK_PORT=8081&#xA;STEP 4/10: WORKDIR /projects&#xA;STEP 5/10: COPY . .&#xA;STEP 6/10: RUN   if [ -f requirements.txt ];     then pip install -r requirements.txt;   elif [ `ls -1q *.txt | wc -l` == 1 ];     then pip install -r *.txt;   fi&#xA;Collecting Flask==2.3.3&#xA;  Downloading flask-2.3.3-py3-none-any.whl (96 kB)&#xA;Collecting click&gt;=8.1.3&#xA;  Downloading click-8.1.8-py3-none-any.whl (98 kB)&#xA;Collecting Werkzeug&gt;=2.3.7&#xA;  Downloading werkzeug-3.1.8-py3-none-any.whl (226 kB)&#xA;Collecting itsdangerous&gt;=2.1.2&#xA;  Downloading itsdangerous-2.2.0-py3-none-any.whl (16 kB)&#xA;Collecting Jinja2&gt;=3.1.2&#xA;  Downloading jinja2-3.1.6-py3-none-any.whl (134 kB)&#xA;Collecting importlib-metadata&gt;=3.6.0&#xA;  Downloading importlib_metadata-8.7.1-py3-none-any.whl (27 kB)&#xA;Collecting blinker&gt;=1.6.2&#xA;  Downloading blinker-1.9.0-py3-none-any.whl (8.5 kB)&#xA;Collecting zipp&gt;=3.20&#xA;  Downloading zipp-3.23.1-py3-none-any.whl (10 kB)&#xA;Collecting MarkupSafe&gt;=2.0&#xA;  Downloading markupsafe-3.0.3-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl (20 kB)&#xA;Installing collected packages: zipp, MarkupSafe, Werkzeug, Jinja2, itsdangerous, importlib-metadata, click, blinker, Flask&#xA;Successfully installed Flask-2.3.3 Jinja2-3.1.6 MarkupSafe-3.0.3 Werkzeug-3.1.8 blinker-1.9.0 click-8.1.8 importlib-metadata-8.7.1 itsdangerous-2.2.0 zipp-3.23.1&#xA;WARNING: You are using pip version 21.3.1; however, version 26.0.1 is available.&#xA;You should consider upgrading via the &#39;/opt/app-root/bin/python3.9 -m pip install --upgrade pip&#39; command.&#xA;STEP 7/10: CMD [ &#34;python&#34;, &#34;./app.py&#34; ]&#xA;STEP 8/10: COPY labels.json /usr/share/buildinfo/labels.json&#xA;STEP 9/10: COPY labels.json /root/buildinfo/labels.json&#xA;STEP 10/10: LABEL &#34;architecture&#34;=&#34;x86_64&#34; &#34;vcs-type&#34;=&#34;git&#34; &#34;vcs-ref&#34;=&#34;ef445b5c6314a21228b14212dd382739dd3e93bf&#34; &#34;org.opencontainers.image.revision&#34;=&#34;ef445b5c6314a21228b14212dd382739dd3e93bf&#34; &#34;org.opencontainers.image.source&#34;=&#34;https://github.com/redhat-appstudio-qe/sample-multi-component&#34; &#34;quay.expires-after&#34;=&#34;5d&#34; &#34;build-date&#34;=&#34;2026-04-20T07:17:05Z&#34; &#34;org.opencontainers.image.created&#34;=&#34;2026-04-20T07:17:05Z&#34;&#xA;COMMIT quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh:on-pr-ef445b5c6314a21228b14212dd382739dd3e93bf&#xA;--&gt; 80a6b5a25040&#xA;Successfully tagged quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh:on-pr-ef445b5c6314a21228b14212dd382739dd3e93bf&#xA;80a6b5a25040f3288da1a0abfc6b4fe09c1d89679757d141e59bd7d73fda4fb3&#xA;[2026-04-20T07:17:56,581946711+00:00] Unsetting proxy&#xA;[2026-04-20T07:17:56,584154952+00:00] Add metadata&#xA;Recording base image digests used&#xA;registry.access.redhat.com/ubi9/python-39:1-117.1684741281 registry.access.redhat.com/ubi9/python-39:1-117.1684741281@sha256:40a58935b9c22664927b22bf256f53a3d744ddb7316f3af18061099e199526ee&#xA;Getting image source signatures&#xA;Copying blob sha256:e630a20d16b85c2e77dca8438eef8d2694ddc98e6dbd0dc1030b9902e56c9823&#xA;Copying blob sha256:bc8a0003b3470be53e5cf295daf38c287d3f20ab90e8f5c2b6f17406b158d323&#xA;Copying blob sha256:d93d3cc0bc0c5ed9655bcdcf31183ed0b570076c0e6a13e0d7cb907d0b877b00&#xA;Copying blob sha256:d661a108c347030c3ef626a0e0020e084fba1e1023193824f5395fa90ef40bde&#xA;Copying blob sha256:629980bfa23ec05ce5acc61ed2866ddf8713f40bb2a61f0850395082f1457220&#xA;Copying config sha256:80a6b5a25040f3288da1a0abfc6b4fe09c1d89679757d141e59bd7d73fda4fb3&#xA;Writing manifest to image destination&#xA;[2026-04-20T07:18:08,421142878+00:00] End build&#xA;&#xA;pod: python-component-qneryh-on-4cc81904d830c06e94b0fdc14701bee2-pod | container step-push: &#xA;[2026-04-20T07:18:09,191789622+00:00] Update CA trust&#xA;INFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#xA;&#39;/mnt/trusted-ca/ca-bundle.crt&#39; -&gt; &#39;/etc/pki/ca-trust/source/anchors/ca-bundle.crt&#39;&#xA;[2026-04-20T07:18:17,429621250+00:00] Convert image&#xA;[2026-04-20T07:18:17,431696708+00:00] Push image with unique tag&#xA;Pushing to quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh:python-component-qneryh-on-pull-request-4c5tc-build-container&#xA;[retry] executing: buildah push --format=docker --retry 3 --tls-verify=true quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh:on-pr-ef445b5c6314a21228b14212dd382739dd3e93bf docker://quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh:python-component-qneryh-on-pull-request-4c5tc-build-container&#xA;Getting image source signatures&#xA;Copying blob sha256:e630a20d16b85c2e77dca8438eef8d2694ddc98e6dbd0dc1030b9902e56c9823&#xA;Copying blob sha256:bc8a0003b3470be53e5cf295daf38c287d3f20ab90e8f5c2b6f17406b158d323&#xA;Copying blob sha256:629980bfa23ec05ce5acc61ed2866ddf8713f40bb2a61f0850395082f1457220&#xA;Copying blob sha256:d93d3cc0bc0c5ed9655bcdcf31183ed0b570076c0e6a13e0d7cb907d0b877b00&#xA;Copying blob sha256:d661a108c347030c3ef626a0e0020e084fba1e1023193824f5395fa90ef40bde&#xA;Copying config sha256:80a6b5a25040f3288da1a0abfc6b4fe09c1d89679757d141e59bd7d73fda4fb3&#xA;Writing manifest to image destination&#xA;[2026-04-20T07:18:34,723283989+00:00] Push image with git revision&#xA;Pushing to quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh:on-pr-ef445b5c6314a21228b14212dd382739dd3e93bf&#xA;[retry] executing: buildah push --format=docker --retry 3 --tls-verify=true --digestfile /workspace/source/image-digest quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh:on-pr-ef445b5c6314a21228b14212dd382739dd3e93bf docker://quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh:on-pr-ef445b5c6314a21228b14212dd382739dd3e93bf&#xA;Getting image source signatures&#xA;Copying blob sha256:bc8a0003b3470be53e5cf295daf38c287d3f20ab90e8f5c2b6f17406b158d323&#xA;Copying blob sha256:e630a20d16b85c2e77dca8438eef8d2694ddc98e6dbd0dc1030b9902e56c9823&#xA;Copying blob sha256:d661a108c347030c3ef626a0e0020e084fba1e1023193824f5395fa90ef40bde&#xA;Copying blob sha256:d93d3cc0bc0c5ed9655bcdcf31183ed0b570076c0e6a13e0d7cb907d0b877b00&#xA;Copying blob sha256:629980bfa23ec05ce5acc61ed2866ddf8713f40bb2a61f0850395082f1457220&#xA;Copying config sha256:80a6b5a25040f3288da1a0abfc6b4fe09c1d89679757d141e59bd7d73fda4fb3&#xA;Writing manifest to image destination&#xA;sha256:4882ed2b4f950f7fac36ca85f0b4fb30a2efde4ae8db38912f66843e94b826b1quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh:on-pr-ef445b5c6314a21228b14212dd382739dd3e93bf&#xA;[retry] executing: kubectl get configmap cluster-config -n konflux-info -o json&#xA;Keyless signing is disabled (none of rekorInternalUrl, fulcioInternalUrl, defaultOIDCIssuer, tufInternalUrl are configured in the konflux-info/cluster-config configmap)&#xA;[2026-04-20T07:18:37,041780122+00:00] End push&#xA;&#xA;pod: python-component-qneryh-on-4cc81904d830c06e94b0fdc14701bee2-pod | container step-sbom-syft-generate: &#xA;[2026-04-20T07:18:37,740306178+00:00] Generate SBOM&#xA;Running syft on the image&#xA;Running syft on the source code&#xA;[0000]  WARN no explicit name and version provided for directory source, deriving artifact ID from the given path (which is not ideal)&#xA;[2026-04-20T07:19:02,121915995+00:00] End sbom-syft-generate&#xA;&#xA;pod: python-component-qneryh-on-4cc81904d830c06e94b0fdc14701bee2-pod | container step-prepare-sboms: &#xA;[2026-04-20T07:19:02,137680166+00:00] Prepare SBOM&#xA;[2026-04-20T07:19:02,145323636+00:00] Generate SBOM with mobster&#xA;Skipping SBOM validation&#xA;2026-04-20 07:19:13,193 [INFO] mobster.log: Logging level set to 20&#xA;2026-04-20 07:19:13,866 [INFO] mobster.oci: Fetching manifest for registry.access.redhat.com/ubi9/python-39@sha256:40a58935b9c22664927b22bf256f53a3d744ddb7316f3af18061099e199526ee&#xA;2026-04-20 07:19:15,618 [WARNING] mobster.oci.cosign.anonymous_fetcher: Cosign fetching attestation of type spdxjson failed for registry.access.redhat.com/ubi9/python-39@sha256:c62e9c0b7ec343ee4b0e0c695a3c8d42d8070e0b9a752079830be0892dc1f89d with output b&#39;Error: found no attestations\nerror during command execution: found no attestations\n&#39;&#xA;2026-04-20 07:19:16,050 [WARNING] mobster.oci.cosign.anonymous_fetcher: Cosign fetching attestation of type cyclonedx failed for registry.access.redhat.com/ubi9/python-39@sha256:c62e9c0b7ec343ee4b0e0c695a3c8d42d8070e0b9a752079830be0892dc1f89d with output b&#39;Error: found no attestations\nerror during command execution: found no attestations\n&#39;&#xA;2026-04-20 07:19:17,116 [WARNING] mobster.oci.cosign.anonymous_fetcher: Cosign fetching attestation of type spdxjson failed for registry.access.redhat.com/ubi9/python-39@sha256:c62e9c0b7ec343ee4b0e0c695a3c8d42d8070e0b9a752079830be0892dc1f89d with output b&#39;Error: found no attestations\nerror during command execution: found no attestations\n&#39;&#xA;2026-04-20 07:19:17,696 [WARNING] mobster.oci.cosign.anonymous_fetcher: Cosign fetching attestation of type cyclonedx failed for registry.access.redhat.com/ubi9/python-39@sha256:c62e9c0b7ec343ee4b0e0c695a3c8d42d8070e0b9a752079830be0892dc1f89d with output b&#39;Error: found no attestations\nerror during command execution: found no attestations\n&#39;&#xA;2026-04-20 07:19:18,749 [WARNING] mobster.oci.cosign.anonymous_fetcher: Cosign fetching attestation of type spdxjson failed for registry.access.redhat.com/ubi9/python-39@sha256:c62e9c0b7ec343ee4b0e0c695a3c8d42d8070e0b9a752079830be0892dc1f89d with output b&#39;Error: found no attestations\nerror during command execution: found no attestations\n&#39;&#xA;2026-04-20 07:19:19,208 [WARNING] mobster.oci.cosign.anonymous_fetcher: Cosign fetching attestation of type cyclonedx failed for registry.access.redhat.com/ubi9/python-39@sha256:c62e9c0b7ec343ee4b0e0c695a3c8d42d8070e0b9a752079830be0892dc1f89d with output b&#39;Error: found no attestations\nerror during command execution: found no attestations\n&#39;&#xA;2026-04-20 07:19:20,266 [WARNING] mobster.oci.cosign.anonymous_fetcher: Cosign fetching attestation of type spdxjson failed for registry.access.redhat.com/ubi9/python-39@sha256:c62e9c0b7ec343ee4b0e0c695a3c8d42d8070e0b9a752079830be0892dc1f89d with output b&#39;Error: found no attestations\nerror during command execution: found no attestations\n&#39;&#xA;2026-04-20 07:19:20,728 [WARNING] mobster.oci.cosign.anonymous_fetcher: Cosign fetching attestation of type cyclonedx failed for registry.access.redhat.com/ubi9/python-39@sha256:c62e9c0b7ec343ee4b0e0c695a3c8d42d8070e0b9a752079830be0892dc1f89d with output b&#39;Error: found no attestations\nerror during command execution: found no attestations\n&#39;&#xA;2026-04-20 07:19:20,770 [INFO] mobster.cmd.generate.oci_image.contextual_sbom.contextualize: Contextual mechanism won&#39;t be used, there is no parent image SBOM.&#xA;2026-04-20 07:19:20,770 [INFO] mobster.cmd.generate.oci_image: Contextual SBOM workflow finished successfully.&#xA;2026-04-20 07:19:20,773 [INFO] mobster.log: Contextual workflow completed in 7.05s&#xA;2026-04-20 07:19:20,979 [INFO] mobster.main: Exiting with code 0.&#xA;[2026-04-20T07:19:21,076596879+00:00] End prepare-sboms&#xA;&#xA;pod: python-component-qneryh-on-4cc81904d830c06e94b0fdc14701bee2-pod | container step-upload-sbom: &#xA;[2026-04-20T07:19:21,832198196+00:00] Upload SBOM&#xA;INFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#xA;&#39;/mnt/trusted-ca/ca-bundle.crt&#39; -&gt; &#39;/etc/pki/ca-trust/source/anchors/ca-bundle.crt&#39;&#xA;Using token for quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh&#xA;Pushing sbom to registry&#xA;[retry] executing: cosign attach sbom --sbom sbom.json --type spdx quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh:on-pr-ef445b5c6314a21228b14212dd382739dd3e93bf@sha256:4882ed2b4f950f7fac36ca85f0b4fb30a2efde4ae8db38912f66843e94b826b1&#xA;WARNING: SBOM attachments are deprecated and support will be removed in a Cosign release soon after 2024-02-22 (see https://github.com/sigstore/cosign/issues/2755). Instead, please use SBOM attestations.&#xA;WARNING: Attaching SBOMs this way does not sign them. To sign them, use &#39;cosign attest --predicate sbom.json --key &lt;key path&gt;&#39;.&#xA;Uploading SBOM file for [quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh@sha256:4882ed2b4f950f7fac36ca85f0b4fb30a2efde4ae8db38912f66843e94b826b1] to [quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh:sha256-4882ed2b4f950f7fac36ca85f0b4fb30a2efde4ae8db38912f66843e94b826b1.sbom] with mediaType [text/spdx+json].&#xA;&#xA;quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh@sha256:0a1e7961ccd8207ce332ec11779f5eb3a92a59edd2772838eb46c69247e92fd6&#xA;[2026-04-20T07:19:39,393400868+00:00] End upload-sbom&#xA;&#xA; pod: python-component-qneryh-on-5a944e915754ce6f70259d00cd809bcb-pod | init container: prepare&#xA;2026/04/20 07:20:03 Entrypoint initialization&#xA;&#xA; pod: python-component-qneryh-on-5a944e915754ce6f70259d00cd809bcb-pod | init container: place-scripts&#xA;2026/04/20 07:20:11 Decoded script /tekton/scripts/script-0-v2p5x&#xA;2026/04/20 07:20:11 Decoded script /tekton/scripts/script-1-wbh79&#xA;2026/04/20 07:20:11 Decoded script /tekton/scripts/script-2-dv52v&#xA;&#xA;pod: python-component-qneryh-on-5a944e915754ce6f70259d00cd809bcb-pod | container step-build: &#xA;[2026-04-20T07:24:33,893646500+00:00] Update CA trust&#xA;INFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#xA;&#39;/mnt/trusted-ca/ca-bundle.crt&#39; -&gt; &#39;/etc/pki/ca-trust/source/anchors/ca-bundle.crt&#39;&#xA;Running konflux-build-cli&#xA;time=&#34;2026-04-20T07:25:11Z&#34; level=info msg=&#34;[param] image: quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh:on-pr-ef445b5c6314a21228b14212dd382739dd3e93bf&#34;&#xA;time=&#34;2026-04-20T07:25:11Z&#34; level=info msg=&#34;[param] images: [quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh:on-pr-ef445b5c6314a21228b14212dd382739dd3e93bf@sha256:4882ed2b4f950f7fac36ca85f0b4fb30a2efde4ae8db38912f66843e94b826b1]&#34;&#xA;time=&#34;2026-04-20T07:25:11Z&#34; level=info msg=&#34;[param] buildah-format: docker&#34;&#xA;time=&#34;2026-04-20T07:25:11Z&#34; level=info msg=&#34;[param] always-build-index: false&#34;&#xA;time=&#34;2026-04-20T07:25:11Z&#34; level=info msg=&#34;[param] additional-tags: [python-component-qneryh-on-pull-request-4c5tc-build-image-index]&#34;&#xA;time=&#34;2026-04-20T07:25:11Z&#34; level=info msg=&#34;[param] output-manifest-path: /index-build-data/manifest_data.json&#34;&#xA;time=&#34;2026-04-20T07:25:11Z&#34; level=info msg=&#34;[param] result-path-image-digest: /tekton/results/IMAGE_DIGEST&#34;&#xA;time=&#34;2026-04-20T07:25:11Z&#34; level=info msg=&#34;[param] result-path-image-url: /tekton/results/IMAGE_URL&#34;&#xA;time=&#34;2026-04-20T07:25:11Z&#34; level=info msg=&#34;[param] result-path-image-ref: /tekton/results/IMAGE_REF&#34;&#xA;time=&#34;2026-04-20T07:25:11Z&#34; level=info msg=&#34;[param] result-path-images: /tekton/results/IMAGES&#34;&#xA;time=&#34;2026-04-20T07:25:11Z&#34; level=info msg=&#34;Creating manifest list: quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh:on-pr-ef445b5c6314a21228b14212dd382739dd3e93bf&#34;&#xA;time=&#34;2026-04-20T07:25:11Z&#34; level=info msg=&#34;buildah [stdout] 0593d75497f4c902e5bc93c4d7c8b39ac3eae4ff03acc71a7c00c5568c594902&#34; logger=CliExecutor&#xA;time=&#34;2026-04-20T07:25:11Z&#34; level=info msg=&#34;Skipping image index generation. Returning results for single image.&#34;&#xA;{&#34;image_digest&#34;:&#34;sha256:4882ed2b4f950f7fac36ca85f0b4fb30a2efde4ae8db38912f66843e94b826b1&#34;,&#34;image_url&#34;:&#34;quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh:on-pr-ef445b5c6314a21228b14212dd382739dd3e93bf&#34;,&#34;image_ref&#34;:&#34;quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh@sha256:4882ed2b4f950f7fac36ca85f0b4fb30a2efde4ae8db38912f66843e94b826b1&#34;,&#34;images&#34;:&#34;quay.io/redhat-appstudio-qe/build-e2e-uymt/python-component-qneryh@sha256:4882ed2b4f950f7fac36ca85f0b4fb30a2efde4ae8db38912f66843e94b826b1&#34;}&#xA;pod: python-component-qneryh-on-5a944e915754ce6f70259d00cd809bcb-pod | container step-create-sbom: &#xA;The manifest_data.json file does not exist. Skipping the SBOM creation...&#xA;&#xA;pod: python-component-qneryh-on-5a944e915754ce6f70259d00cd809bcb-pod | container step-upload-sbom: &#xA;&#xA; pod: python-component-qneryh-on-e6a91c289c3ca7d4b0709366d1f496c0-pod | init container: prepare&#xA;2026/04/20 07:16:18 Entrypoint initialization&#xA;&#xA; pod: python-component-qneryh-on-e6a91c289c3ca7d4b0709366d1f496c0-pod | init container: place-scripts&#xA;2026/04/20 07:16:20 Decoded script /tekton/scripts/script-0-2cnd7&#xA;2026/04/20 07:16:20 Decoded script /tekton/scripts/script-1-mblzt&#xA;&#xA;pod: python-component-qneryh-on-e6a91c289c3ca7d4b0709366d1f496c0-pod | container step-clone: &#xA;INFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#xA;{&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776669385.2614434,&#34;caller&#34;:&#34;git/git.go:394&#34;,&#34;msg&#34;:&#34;Retrying operation (attempt 1)&#34;}&#xA;{&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776669385.9378061,&#34;caller&#34;:&#34;git/git.go:223&#34;,&#34;msg&#34;:&#34;Successfully cloned https://github.com/redhat-appstudio-qe/sample-multi-component @ ef445b5c6314a21228b14212dd382739dd3e93bf (grafted, HEAD) in path /workspace/output/source&#34;}&#xA;{&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776669385.9378717,&#34;caller&#34;:&#34;git/git.go:394&#34;,&#34;msg&#34;:&#34;Retrying operation (attempt 1)&#34;}&#xA;{&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776669386.0135353,&#34;caller&#34;:&#34;git/git.go:277&#34;,&#34;msg&#34;:&#34;Successfully initialized and updated submodules in path /workspace/output/source&#34;}&#xA;Merge option disabled. Using checked-out revision ef445b5c6314a21228b14212dd382739dd3e93bf directly.&#xA;&#xA;pod: python-component-qneryh-on-e6a91c289c3ca7d4b0709366d1f496c0-pod | container step-symlink-check: &#xA;Running symlink check&#xA;&#xA; pod: python-component-qneryh-on-pull-request-4c5tc-init-pod | init container: prepare&#xA;2026/04/20 07:15:59 Entrypoint initialization&#xA;&#xA;pod: python-component-qneryh-on-pull-request-4c5tc-init-pod | container step-init: &#xA;time=&#34;2026-04-20T07:16:06Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-20T07:16:06Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-20T07:16:06Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-20T07:16:06Z&#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-20T07:16:06Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-20T07:16:06Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-20T07:16:07Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;time=&#34;2026-04-20T07:16:07Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-20T07:16:07Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;New PipelineRun python-component-qneryh-on-pull-request-p28cd found after retrigger for component build-e2e-uymt/python-component-qneryh&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd found for Component build-e2e-uymt/python-component-qneryh&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: &#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-p28cd reason: Failed&#xA;an error happened during storing pipelineRun log build-e2e-uymt:python-component-qneryh-on-pull-request-p28cd: container &#34;step-build&#34; in pod &#34;python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod&#34; is waiting to start: PodInitializing&#xA;failed to get logs for PipelineRun build-e2e-uymt:python-component-qneryh-on-pull-request-p28cd: container &#34;step-build&#34; in pod &#34;python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod&#34; is waiting to start: PodInitializing&#xA;attempt 2/3: PipelineRun &#34;python-component-qneryh-on-pull-request-p28cd&#34; failed: &#xA; pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | init container: prepare&#xA;2026/04/20 07:40:55 Entrypoint initialization&#xA;&#xA; pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | init container: place-scripts&#xA;2026/04/20 07:41:14 Decoded script /tekton/scripts/script-0-dswv9&#xA;2026/04/20 07:41:14 Decoded script /tekton/scripts/script-1-jclgq&#xA;&#xA;pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | container step-clone: &#xA;INFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#xA;{&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776670916.3477,&#34;caller&#34;:&#34;git/git.go:394&#34;,&#34;msg&#34;:&#34;Retrying operation (attempt 1)&#34;}&#xA;{&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776670925.2353692,&#34;caller&#34;:&#34;git/git.go:223&#34;,&#34;msg&#34;:&#34;Successfully cloned https://github.com/redhat-appstudio-qe/sample-multi-component @ 436f80634af29d23253f16847b366d05e48e563d (grafted, HEAD) in path /workspace/output/source&#34;}&#xA;{&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776670925.235458,&#34;caller&#34;:&#34;git/git.go:394&#34;,&#34;msg&#34;:&#34;Retrying operation (attempt 1)&#34;}&#xA;{&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776670925.2869456,&#34;caller&#34;:&#34;git/git.go:277&#34;,&#34;msg&#34;:&#34;Successfully initialized and updated submodules in path /workspace/output/source&#34;}&#xA;Merge option disabled. Using checked-out revision 436f80634af29d23253f16847b366d05e48e563d directly.&#xA;&#xA;pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | container step-symlink-check: &#xA;Running symlink check&#xA;&#xA; pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | init container: prepare&#xA;2026/04/20 07:52:24 Entrypoint initialization&#xA;&#xA; pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | init container: place-scripts&#xA;&#xA;pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | container step-build: &#xA;New PipelineRun python-component-qneryh-on-pull-request-rw2j2 found after retrigger for component build-e2e-uymt/python-component-qneryh&#xA;PipelineRun python-component-qneryh-on-pull-request-rw2j2 found for Component build-e2e-uymt/python-component-qneryh&#xA;PipelineRun python-component-qneryh-on-pull-request-rw2j2 reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-rw2j2 reason: ResolvingTaskRef&#xA;PipelineRun python-component-qneryh-on-pull-request-rw2j2 reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-rw2j2 reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-rw2j2 reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-rw2j2 reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-rw2j2 reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-rw2j2 reason: Running&#xA;PipelineRun python-component-qneryh-on-pull-request-rw2j2 reason: Failed&#xA;an error happened during storing pipelineRun log build-e2e-uymt:python-component-qneryh-on-pull-request-rw2j2: container &#34;step-build&#34; in pod &#34;python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod&#34; is waiting to start: PodInitializing&#xA;failed to get logs for PipelineRun build-e2e-uymt:python-component-qneryh-on-pull-request-rw2j2: container &#34;step-build&#34; in pod &#34;python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod&#34; is waiting to start: PodInitializing&#xA;attempt 3/3: PipelineRun &#34;python-component-qneryh-on-pull-request-rw2j2&#34; failed: &#xA; pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | init container: prepare&#xA;2026/04/20 07:40:55 Entrypoint initialization&#xA;&#xA; pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | init container: place-scripts&#xA;2026/04/20 07:41:14 Decoded script /tekton/scripts/script-0-dswv9&#xA;2026/04/20 07:41:14 Decoded script /tekton/scripts/script-1-jclgq&#xA;&#xA;pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | container step-clone: &#xA;INFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#xA;{&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776670916.3477,&#34;caller&#34;:&#34;git/git.go:394&#34;,&#34;msg&#34;:&#34;Retrying operation (attempt 1)&#34;}&#xA;{&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776670925.2353692,&#34;caller&#34;:&#34;git/git.go:223&#34;,&#34;msg&#34;:&#34;Successfully cloned https://github.com/redhat-appstudio-qe/sample-multi-component @ 436f80634af29d23253f16847b366d05e48e563d (grafted, HEAD) in path /workspace/output/source&#34;}&#xA;{&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776670925.235458,&#34;caller&#34;:&#34;git/git.go:394&#34;,&#34;msg&#34;:&#34;Retrying operation (attempt 1)&#34;}&#xA;{&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776670925.2869456,&#34;caller&#34;:&#34;git/git.go:277&#34;,&#34;msg&#34;:&#34;Successfully initialized and updated submodules in path /workspace/output/source&#34;}&#xA;Merge option disabled. Using checked-out revision 436f80634af29d23253f16847b366d05e48e563d directly.&#xA;&#xA;pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | container step-symlink-check: &#xA;Running symlink check&#xA;&#xA; pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | init container: prepare&#xA;2026/04/20 07:52:24 Entrypoint initialization&#xA;&#xA; pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | init container: place-scripts&#xA;&#xA;pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | container step-build: &#xA;[FAILED] Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc001729420&gt;: &#xA;    &#xA;     pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | init container: prepare&#xA;    2026/04/20 07:40:55 Entrypoint initialization&#xA;    &#xA;     pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | init container: place-scripts&#xA;    2026/04/20 07:41:14 Decoded script /tekton/scripts/script-0-dswv9&#xA;    2026/04/20 07:41:14 Decoded script /tekton/scripts/script-1-jclgq&#xA;    &#xA;    pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | container step-clone: &#xA;    INFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt&#xA;    {&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776670916.3477,&#34;caller&#34;:&#34;git/git.go:394&#34;,&#34;msg&#34;:&#34;Retrying operation (attempt 1)&#34;}&#xA;    {&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776670925.2353692,&#34;caller&#34;:&#34;git/git.go:223&#34;,&#34;msg&#34;:&#34;Successfully cloned https://github.com/redhat-appstudio-qe/sample-multi-component @ 436f80634af29d23253f16847b366d05e48e563d (grafted, HEAD) in path /workspace/output/source&#34;}&#xA;    {&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776670925.235458,&#34;caller&#34;:&#34;git/git.go:394&#34;,&#34;msg&#34;:&#34;Retrying operation (attempt 1)&#34;}&#xA;    {&#34;level&#34;:&#34;info&#34;,&#34;ts&#34;:1776670925.2869456,&#34;caller&#34;:&#34;git/git.go:277&#34;,&#34;msg&#34;:&#34;Successfully initialized and updated submodules in path /workspace/output/source&#34;}&#xA;    Merge option disabled. Using checked-out revision 436f80634af29d23253f16847b366d05e48e563d directly.&#xA;    &#xA;    pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | container step-symlink-check: &#xA;    Running symlink check&#xA;    &#xA;     pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | init container: prepare&#xA;    2026/04/20 07:52:24 Entrypoint initialization&#xA;    &#xA;     pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | init container: place-scripts&#xA;    &#xA;    pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | container step-build: &#xA;    &#xA;    {&#xA;        s: &#34;\n pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | init container: prepare\n2026/04/20 07:40:55 Entrypoint initialization\n\n pod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | init container: place-scripts\n2026/04/20 07:41:14 Decoded script /tekton/scripts/script-0-dswv9\n2026/04/20 07:41:14 Decoded script /tekton/scripts/script-1-jclgq\n\npod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | container step-clone: \nINFO: Using mounted CA bundle: /mnt/trusted-ca/ca-bundle.crt\n{\&#34;level\&#34;:\&#34;info\&#34;,\&#34;ts\&#34;:1776670916.3477,\&#34;caller\&#34;:\&#34;git/git.go:394\&#34;,\&#34;msg\&#34;:\&#34;Retrying operation (attempt 1)\&#34;}\n{\&#34;level\&#34;:\&#34;info\&#34;,\&#34;ts\&#34;:1776670925.2353692,\&#34;caller\&#34;:\&#34;git/git.go:223\&#34;,\&#34;msg\&#34;:\&#34;Successfully cloned https://github.com/redhat-appstudio-qe/sample-multi-component @ 436f80634af29d23253f16847b366d05e48e563d (grafted, HEAD) in path /workspace/output/source\&#34;}\n{\&#34;level\&#34;:\&#34;info\&#34;,\&#34;ts\&#34;:1776670925.235458,\&#34;caller\&#34;:\&#34;git/git.go:394\&#34;,\&#34;msg\&#34;:\&#34;Retrying operation (attempt 1)\&#34;}\n{\&#34;level\&#34;:\&#34;info\&#34;,\&#34;ts\&#34;:1776670925.2869456,\&#34;caller\&#34;:\&#34;git/git.go:277\&#34;,\&#34;msg\&#34;:\&#34;Successfully initialized and updated submodules in path /workspace/output/source\&#34;}\nMerge option disabled. Using checked-out revision 436f80634af29d23253f16847b366d05e48e563d directly.\n\npod: python-component-qneryh-on-00076e4d849fc98435946452ae05b8c4-pod | container step-symlink-check: \nRunning symlink check\n\n pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | init container: prepare\n2026/04/20 07:52:24 Entrypoint initialization\n\n pod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | init container: place-scripts\n\npod: python-component-qneryh-on-2ea195d8c49c54385740a1f8293ab511-pod | container step-build: \n&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:161 @ 04/20/26 07:56:05.48&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for component python-component-qneryh - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:159 @ 04/20/26 07:56:05.48 (41m54.439s)&#xA;&gt; Enter [AfterAll] test pac with multiple components using same repository - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:68 @ 04/20/26 07:56:05.481&#xA;&lt; Exit [AfterAll] test pac with multiple components using same repository - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:68 @ 04/20/26 07:56:06.641 (1.16s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:28 @ 04/20/26 07:56:06.641&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/multi_component.go:28 @ 04/20/26 07:56:07.89 (1.249s)&#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.XKFaKtKOZB/tests/build/multi_component.go:164 @ 04/20/26 07:56:07.891&#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.XKFaKtKOZB/tests/build/multi_component.go:174 @ 04/20/26 07:56:07.891&#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.XKFaKtKOZB/tests/build/multi_component.go:190 @ 04/20/26 07:56:07.892&#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.XKFaKtKOZB/tests/build/multi_component.go:205 @ 04/20/26 07:56:07.892&#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.XKFaKtKOZB/tests/build/multi_component.go:264 @ 04/20/26 07:56:07.892&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private correctly targets the default branch (that is not named &#39;main&#39;) with PaC [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="61.34423043">
              <system-err>&gt; Enter [BeforeAll] PaC component build - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:55 @ 04/20/26 07:01:05.042&#xA;&lt; Exit [BeforeAll] PaC component build - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:55 @ 04/20/26 07:01:14.409 (9.367s)&#xA;&gt; Enter [BeforeAll] when a new component without specified branch is created and with visibility private - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:118 @ 04/20/26 07:01:14.409&#xA;Image repository for component fj-test-custom-default-lejqsh in namespace build-e2e-ohzt do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component fj-test-custom-default-lejqsh in namespace build-e2e-ohzt 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.XKFaKtKOZB/tests/build/pac_build.go:118 @ 04/20/26 07:01:34.539 (20.13s)&#xA;&gt; Enter [It] correctly targets the default branch (that is not named &#39;main&#39;) with PaC - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:137 @ 04/20/26 07:01:34.539&#xA;&lt; Exit [It] correctly targets the default branch (that is not named &#39;main&#39;) with PaC - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:137 @ 04/20/26 07:02:06.386 (31.846s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:02:06.386&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:02:06.386 (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.123683885">
              <system-err>&gt; Enter [It] workspace parameter is set correctly in PaC repository CR - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:154 @ 04/20/26 07:02:06.386&#xA;&lt; Exit [It] workspace parameter is set correctly in PaC repository CR - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:154 @ 04/20/26 07:02:06.51 (123ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:02:06.51&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:02:06.51 (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.947266341">
              <system-err>&gt; Enter [It] triggers a PipelineRun - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:177 @ 04/20/26 07:02:06.51&#xA;PipelineRun has not been created yet for the component build-e2e-ohzt/fj-test-custom-branch-mcigvw&#xA;&lt; Exit [It] triggers a PipelineRun - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:177 @ 04/20/26 07:02:27.457 (20.947s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:02:27.458&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:02:27.458 (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.000413858">
              <system-err>&gt; Enter [It] build pipeline uses the correct serviceAccount - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:192 @ 04/20/26 07:02:27.458&#xA;&lt; Exit [It] build pipeline uses the correct serviceAccount - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:192 @ 04/20/26 07:02:27.458 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:02:27.458&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:02:27.458 (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.577714619">
              <system-err>&gt; Enter [It] component build status is set correctly - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:196 @ 04/20/26 07:02:27.459&#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-ojbsps/pulls/1&#34;,&#34;configuration-time&#34;:&#34;Mon, 20 Apr 2026 07:02:07 UTC&#34;},&#34;message&#34;:&#34;done&#34;}&#xA;state: enabled&#xA;mergeUrl: https://codeberg.org/konflux-qe/devfile-sample-hello-world-ojbsps/pulls/1&#xA;errId: 0&#xA;errMessage: &#xA;configurationTime: Mon, 20 Apr 2026 07:02:07 UTC&#xA;&lt; Exit [It] component build status is set correctly - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:196 @ 04/20/26 07:02:28.036 (577ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:02:28.036&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:02:28.037 (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.6496872329999999">
              <system-err>&gt; Enter [It] image repo and robot account created successfully - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:226 @ 04/20/26 07:02:28.037&#xA;&lt; Exit [It] image repo and robot account created successfully - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:226 @ 04/20/26 07:02:29.686 (1.649s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:02:29.687&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:02:29.687 (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.315432792">
              <system-err>&gt; Enter [It] created image repo is private - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:244 @ 04/20/26 07:02:29.687&#xA;&lt; Exit [It] created image repo is private - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:244 @ 04/20/26 07:02:30.002 (315ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:02:30.003&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:02:30.003 (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="86.718677546">
              <system-err>&gt; Enter [It] a related PipelineRun should be deleted after deleting the component - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:250 @ 04/20/26 07:02:30.003&#xA;&lt; Exit [It] a related PipelineRun should be deleted after deleting the component - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:250 @ 04/20/26 07:03:56.722 (1m26.718s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:56.722&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:56.722 (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.429214608">
              <system-err>&gt; Enter [It] PR branch should not exist in the repo - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:266 @ 04/20/26 07:03:56.722&#xA;&lt; Exit [It] PR branch should not exist in the repo - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:266 @ 04/20/26 07:03:57.151 (429ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:57.151&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:57.151 (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="1.2974100210000001">
              <system-err>&gt; Enter [It] related image repo and the robot account should be deleted after deleting the component - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:279 @ 04/20/26 07:03:57.152&#xA;&lt; Exit [It] related image repo and the robot account should be deleted after deleting the component - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:279 @ 04/20/26 07:03:58.449 (1.297s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:58.449&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:58.449 (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="51.449028503">
              <system-err>&gt; Enter [BeforeAll] when a new Component with specified custom branch is created - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:307 @ 04/20/26 07:03:58.45&#xA;Image repository for component fj-test-custom-branch-mcigvw in namespace build-e2e-ohzt 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.XKFaKtKOZB/tests/build/pac_build.go:307 @ 04/20/26 07:04:09.068 (10.618s)&#xA;&gt; Enter [It] triggers a PipelineRun - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:333 @ 04/20/26 07:04:09.068&#xA;PipelineRun has not been created yet for the component build-e2e-ohzt/fj-test-custom-branch-mcigvw&#xA;PipelineRun has not been created yet for the component build-e2e-ohzt/fj-test-custom-branch-mcigvw&#xA;&lt; Exit [It] triggers a PipelineRun - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:333 @ 04/20/26 07:04:49.898 (40.83s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:04:49.899&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:04:49.899 (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="0.201996302">
              <system-err>&gt; Enter [It] should lead to a PaC init PR creation - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:348 @ 04/20/26 07:04:49.899&#xA;&lt; Exit [It] should lead to a PaC init PR creation - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:348 @ 04/20/26 07:04:50.101 (202ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:04:50.101&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:04:50.101 (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="failed" time="3093.393001864">
              <failure message="Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc002007150&gt;: &#xA;    &#xA;     pod: fj-test-custom-branch-mcigvw-on-pull-request-89sf2-init-pod | init container: prepare&#xA;    2026/04/20 07:46:20 Entrypoint initialization&#xA;    &#xA;    pod: fj-test-custom-branch-mcigvw-on-pull-request-89sf2-init-pod | container step-init: &#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;    &#xA;    {&#xA;        s: &#34;\n pod: fj-test-custom-branch-mcigvw-on-pull-request-89sf2-init-pod | init container: prepare\n2026/04/20 07:46:20 Entrypoint initialization\n\npod: fj-test-custom-branch-mcigvw-on-pull-request-89sf2-init-pod | container step-init: \ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;Using in-cluster config\&#34; logger=KubeClient\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] enable: false\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] http-proxy-result-path: /tekton/results/http-proxy\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] no-proxy-result-path: /tekton/results/no-proxy\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;Cache proxy is disabled in param or in backend\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[result] HTTP PROXY: \&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[result] NO PROXY: \&#34;\n&#34;,&#xA;    }" type="failed">[FAILED] Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc002007150&gt;: &#xA;    &#xA;     pod: fj-test-custom-branch-mcigvw-on-pull-request-89sf2-init-pod | init container: prepare&#xA;    2026/04/20 07:46:20 Entrypoint initialization&#xA;    &#xA;    pod: fj-test-custom-branch-mcigvw-on-pull-request-89sf2-init-pod | container step-init: &#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;    &#xA;    {&#xA;        s: &#34;\n pod: fj-test-custom-branch-mcigvw-on-pull-request-89sf2-init-pod | init container: prepare\n2026/04/20 07:46:20 Entrypoint initialization\n\npod: fj-test-custom-branch-mcigvw-on-pull-request-89sf2-init-pod | container step-init: \ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;Using in-cluster config\&#34; logger=KubeClient\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] enable: false\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] http-proxy-result-path: /tekton/results/http-proxy\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] no-proxy-result-path: /tekton/results/no-proxy\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;Cache proxy is disabled in param or in backend\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[result] HTTP PROXY: \&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[result] NO PROXY: \&#34;\n&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:368 @ 04/20/26 07:56:21.91&#xA;</failure>
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:366 @ 04/20/26 07:04:50.102&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 found for Component build-e2e-ohzt/fj-test-custom-branch-mcigvw&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: ResolvingTaskRef&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: ResolvingTaskRef&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: ResolvingTaskRef&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: ResolvingTaskRef&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: ResolvingTaskRef&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-7qh55 reason: Failed&#xA;attempt 1/3: PipelineRun &#34;fj-test-custom-branch-mcigvw-on-pull-request-7qh55&#34; failed: &#xA; pod: fj-test-custom-branch-mcigvw-on-pull-request-7qh55-init-pod | init container: prepare&#xA;2026/04/20 07:06:39 Entrypoint initialization&#xA;&#xA;pod: fj-test-custom-branch-mcigvw-on-pull-request-7qh55-init-pod | container step-init: &#xA;time=&#34;2026-04-20T07:07:06Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-20T07:07:06Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-20T07:07:06Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-20T07:07:06Z&#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-20T07:07:06Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-20T07:07:06Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-20T07:07:06Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;time=&#34;2026-04-20T07:07:06Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-20T07:07:06Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;New PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv found after retrigger for component build-e2e-ohzt/fj-test-custom-branch-mcigvw&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv found for Component build-e2e-ohzt/fj-test-custom-branch-mcigvw&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: &#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: ResolvingTaskRef&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: ResolvingTaskRef&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun has not been created yet for the Component build-e2e-ohzt/fj-test-custom-branch-mcigvw&#xA;PipelineRun has not been created yet for the Component build-e2e-ohzt/fj-test-custom-branch-mcigvw&#xA;PipelineRun has not been created yet for the Component build-e2e-ohzt/fj-test-custom-branch-mcigvw&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun has not been created yet for the Component build-e2e-ohzt/fj-test-custom-branch-mcigvw&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-vtzvv reason: Failed&#xA;attempt 2/3: PipelineRun &#34;fj-test-custom-branch-mcigvw-on-pull-request-vtzvv&#34; failed: &#xA; pod: fj-test-custom-branch-mcigvw-on-pull-request-vtzvv-init-pod | init container: prepare&#xA;2026/04/20 07:17:19 Entrypoint initialization&#xA;&#xA;pod: fj-test-custom-branch-mcigvw-on-pull-request-vtzvv-init-pod | container step-init: &#xA;time=&#34;2026-04-20T07:17:32Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-20T07:17:32Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-20T07:17:32Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-20T07:17:32Z&#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-20T07:17:32Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-20T07:17:32Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-20T07:17:32Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;time=&#34;2026-04-20T07:17:32Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-20T07:17:32Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;New PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 found after retrigger for component build-e2e-ohzt/fj-test-custom-branch-mcigvw&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 found for Component build-e2e-ohzt/fj-test-custom-branch-mcigvw&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: &#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: ResolvingTaskRef&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: ResolvingTaskRef&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: ResolvingTaskRef&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: ResolvingTaskRef&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Running&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: PipelineRunStopping&#xA;PipelineRun fj-test-custom-branch-mcigvw-on-pull-request-89sf2 reason: Failed&#xA;attempt 3/3: PipelineRun &#34;fj-test-custom-branch-mcigvw-on-pull-request-89sf2&#34; failed: &#xA; pod: fj-test-custom-branch-mcigvw-on-pull-request-89sf2-init-pod | init container: prepare&#xA;2026/04/20 07:46:20 Entrypoint initialization&#xA;&#xA;pod: fj-test-custom-branch-mcigvw-on-pull-request-89sf2-init-pod | container step-init: &#xA;time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai&#34;&#xA;time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;[FAILED] Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc002007150&gt;: &#xA;    &#xA;     pod: fj-test-custom-branch-mcigvw-on-pull-request-89sf2-init-pod | init container: prepare&#xA;    2026/04/20 07:46:20 Entrypoint initialization&#xA;    &#xA;    pod: fj-test-custom-branch-mcigvw-on-pull-request-89sf2-init-pod | container step-init: &#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;    &#xA;    {&#xA;        s: &#34;\n pod: fj-test-custom-branch-mcigvw-on-pull-request-89sf2-init-pod | init container: prepare\n2026/04/20 07:46:20 Entrypoint initialization\n\npod: fj-test-custom-branch-mcigvw-on-pull-request-89sf2-init-pod | container step-init: \ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;Using in-cluster config\&#34; logger=KubeClient\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] enable: false\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] http-proxy-result-path: /tekton/results/http-proxy\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] no-proxy-result-path: /tekton/results/no-proxy\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;Cache proxy is disabled in param or in backend\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[result] HTTP PROXY: \&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[result] NO PROXY: \&#34;\n&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:368 @ 04/20/26 07:56:21.91&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:366 @ 04/20/26 07:56:21.91 (51m31.808s)&#xA;&gt; Enter [AfterAll] when a new Component with specified custom branch is created - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:325 @ 04/20/26 07:56:21.91&#xA;&lt; Exit [AfterAll] when a new Component with specified custom branch is created - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:325 @ 04/20/26 07:56:22.453 (542ms)&#xA;&gt; Enter [AfterAll] PaC component build - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:102 @ 04/20/26 07:56:22.453&#xA;&lt; Exit [AfterAll] PaC component build - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:102 @ 04/20/26 07:56:22.453 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:56:22.453&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:56:23.494 (1.041s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:372 @ 04/20/26 07:56:23.495&#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 floating tags are created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:391 @ 04/20/26 07:56:23.495&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created created image repo is public [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:404 @ 04/20/26 07:56:23.496&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created image tag is updated successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:410 @ 04/20/26 07:56:23.496&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created should ensure pruning labels are set [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:439 @ 04/20/26 07:56:23.496&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created eventually leads to the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:453 @ 04/20/26 07:56:23.496&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:478 @ 04/20/26 07:56:23.496&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated should lead to a PaC init PR update [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:493 @ 04/20/26 07:56:23.497&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated PipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:512 @ 04/20/26 07:56:23.497&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated eventually leads to another update of a PR about the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:518 @ 04/20/26 07:56:23.497&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:544 @ 04/20/26 07:56:23.497&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:560 @ 04/20/26 07:56:23.497&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged does not have expiration set [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:566 @ 04/20/26 07:56:23.498&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged After updating image visibility to private, it should not trigger another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:578 @ 04/20/26 07:56:23.498&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged image repo is updated to private [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:609 @ 04/20/26 07:56:23.498&#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="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:729 @ 04/20/26 07:56:23.498&#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="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite Release service tenant pipeline] Post-release verification verifies that Tenant PipelineRun is triggered [release-service, tenant]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite Release service tenant pipeline] Post-release verification verifies that a Release is marked as succeeded. [release-service, tenant]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [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="115.774294874">
              <system-err>&gt; Enter [BeforeAll] PaC component build - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:55 @ 04/20/26 07:01:05.042&#xA;&lt; Exit [BeforeAll] PaC component build - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:55 @ 04/20/26 07:01:23.498 (18.456s)&#xA;&gt; Enter [BeforeAll] when a new component without specified branch is created and with visibility private - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:118 @ 04/20/26 07:01:23.498&#xA;Image repository for component gh-test-custom-default-sqvujy in namespace build-e2e-kseb do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component gh-test-custom-default-sqvujy in namespace build-e2e-kseb 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.XKFaKtKOZB/tests/build/pac_build.go:118 @ 04/20/26 07:01:43.636 (20.138s)&#xA;&gt; Enter [It] correctly targets the default branch (that is not named &#39;main&#39;) with PaC - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:137 @ 04/20/26 07:01:43.636&#xA;&lt; Exit [It] correctly targets the default branch (that is not named &#39;main&#39;) with PaC - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:137 @ 04/20/26 07:03:00.816 (1m17.18s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:00.816&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:00.816 (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.13187924">
              <system-err>&gt; Enter [It] workspace parameter is set correctly in PaC repository CR - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:154 @ 04/20/26 07:03:00.817&#xA;&lt; Exit [It] workspace parameter is set correctly in PaC repository CR - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:154 @ 04/20/26 07:03:00.948 (131ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:00.949&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:00.949 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="20.200375165">
              <system-err>&gt; Enter [It] triggers a PipelineRun - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:177 @ 04/20/26 07:03:00.949&#xA;PipelineRun has not been created yet for the component build-e2e-kseb/gh-test-custom-branch-dvkcvc&#xA;&lt; Exit [It] triggers a PipelineRun - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:177 @ 04/20/26 07:03:21.149 (20.2s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:21.149&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:21.15 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private build pipeline uses the correct serviceAccount [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.000391868">
              <system-err>&gt; Enter [It] build pipeline uses the correct serviceAccount - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:192 @ 04/20/26 07:03:21.15&#xA;&lt; Exit [It] build pipeline uses the correct serviceAccount - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:192 @ 04/20/26 07:03:21.15 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:21.15&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:21.15 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private component build status is set correctly [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.066090605">
              <system-err>&gt; Enter [It] component build status is set correctly - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:196 @ 04/20/26 07:03:21.151&#xA;build status annotation value: {&#34;pac&#34;:{&#34;state&#34;:&#34;enabled&#34;,&#34;merge-url&#34;:&#34;https://github.com/redhat-appstudio-qe/devfile-sample-hello-world-onzqbg/pull/1&#34;,&#34;configuration-time&#34;:&#34;Mon, 20 Apr 2026 07:02:58 UTC&#34;},&#34;message&#34;:&#34;done&#34;}&#xA;state: enabled&#xA;mergeUrl: https://github.com/redhat-appstudio-qe/devfile-sample-hello-world-onzqbg/pull/1&#xA;errId: 0&#xA;errMessage: &#xA;configurationTime: Mon, 20 Apr 2026 07:02:58 UTC&#xA;&lt; Exit [It] component build status is set correctly - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:196 @ 04/20/26 07:03:21.216 (66ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:21.217&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:21.217 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="1.497876306">
              <system-err>&gt; Enter [It] image repo and robot account created successfully - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:226 @ 04/20/26 07:03:21.217&#xA;&lt; Exit [It] image repo and robot account created successfully - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:226 @ 04/20/26 07:03:22.714 (1.497s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:22.715&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:22.715 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private created image repo is private [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.283153983">
              <system-err>&gt; Enter [It] created image repo is private - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:244 @ 04/20/26 07:03:22.716&#xA;&lt; Exit [It] created image repo is private - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:244 @ 04/20/26 07:03:22.998 (282ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:22.999&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:03:22.999 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private a related PipelineRun should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="42.738172127">
              <system-err>&gt; Enter [It] a related PipelineRun should be deleted after deleting the component - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:250 @ 04/20/26 07:03:22.999&#xA;&lt; Exit [It] a related PipelineRun should be deleted after deleting the component - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:250 @ 04/20/26 07:04:05.737 (42.738s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:04:05.737&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:04:05.737 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private PR branch should not exist in the repo [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.153689508">
              <system-err>&gt; Enter [It] PR branch should not exist in the repo - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:266 @ 04/20/26 07:04:05.738&#xA;&lt; Exit [It] PR branch should not exist in the repo - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:266 @ 04/20/26 07:04:05.891 (153ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:04:05.891&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:04:05.891 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private related image repo and the robot account should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.973073816">
              <system-err>&gt; Enter [It] related image repo and the robot account should be deleted after deleting the component - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:279 @ 04/20/26 07:04:05.892&#xA;&lt; Exit [It] related image repo and the robot account should be deleted after deleting the component - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:279 @ 04/20/26 07:04:06.865 (973ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:04:06.865&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:04:06.865 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="60.94768064">
              <system-err>&gt; Enter [BeforeAll] when a new Component with specified custom branch is created - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:307 @ 04/20/26 07:04:06.865&#xA;Image repository for component gh-test-custom-branch-dvkcvc in namespace build-e2e-kseb do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component gh-test-custom-branch-dvkcvc in namespace build-e2e-kseb 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.XKFaKtKOZB/tests/build/pac_build.go:307 @ 04/20/26 07:04:27.003 (20.137s)&#xA;&gt; Enter [It] triggers a PipelineRun - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:333 @ 04/20/26 07:04:27.003&#xA;PipelineRun has not been created yet for the component build-e2e-kseb/gh-test-custom-branch-dvkcvc&#xA;&lt; Exit [It] triggers a PipelineRun - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:333 @ 04/20/26 07:05:07.813 (40.81s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:05:07.813&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:05:07.813 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created should lead to a PaC init PR creation [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.235698203">
              <system-err>&gt; Enter [It] should lead to a PaC init PR creation - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:348 @ 04/20/26 07:05:07.814&#xA;&lt; Exit [It] should lead to a PaC init PR creation - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:348 @ 04/20/26 07:05:08.049 (235ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:05:08.049&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:05:08.049 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="680.132945625">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:366 @ 04/20/26 07:05:08.05&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq found for Component build-e2e-kseb/gh-test-custom-branch-dvkcvc&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq reason: Completed&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:366 @ 04/20/26 07:16:28.182 (11m20.133s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:16:28.182&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:16:28.182 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="1.020852328">
              <system-err>&gt; Enter [It] image repo and robot account created successfully - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:372 @ 04/20/26 07:16:28.183&#xA;&lt; Exit [It] image repo and robot account created successfully - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:372 @ 04/20/26 07:16:29.203 (1.02s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:16:29.204&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:16:29.204 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created floating tags are created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.673391766">
              <system-err>&gt; Enter [It] floating tags are created successfully - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:391 @ 04/20/26 07:16:29.205&#xA;&lt; Exit [It] floating tags are created successfully - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:391 @ 04/20/26 07:16:29.878 (673ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:16:29.878&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:16:29.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 with specified custom branch is created created image repo is public [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.530393321">
              <system-err>&gt; Enter [It] created image repo is public - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:404 @ 04/20/26 07:16:29.878&#xA;&lt; Exit [It] created image repo is public - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:404 @ 04/20/26 07:16:30.408 (530ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:16:30.408&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:16:30.409 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created image tag is updated successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.485178542">
              <system-err>&gt; Enter [It] image tag is updated successfully - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:410 @ 04/20/26 07:16:30.409&#xA;Image tag quay.io/redhat-appstudio-qe/build-e2e-kseb/gh-test-custom-branch-dvkcvc:on-pr-0c08ccf1f2ab3ca9c35c075bda81006a6a12efde successfully found in Quay&#xA;&lt; Exit [It] image tag is updated successfully - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:410 @ 04/20/26 07:16:30.894 (485ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:16:30.894&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:16:30.894 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created should ensure pruning labels are set [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.584999816">
              <system-err>&gt; Enter [It] should ensure pruning labels are set - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:439 @ 04/20/26 07:16:30.895&#xA;&lt; Exit [It] should ensure pruning labels are set - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:439 @ 04/20/26 07:16:31.479 (584ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:16:31.48&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:16:31.48 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created eventually leads to the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.490243426">
              <system-err>&gt; Enter [It] eventually leads to the PipelineRun status report at Checks tab - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:453 @ 04/20/26 07:16:31.48&#xA;&lt; Exit [It] eventually leads to the PipelineRun status report at Checks tab - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:453 @ 04/20/26 07:16:31.872 (391ms)&#xA;&gt; Enter [AfterAll] when a new Component with specified custom branch is created - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:325 @ 04/20/26 07:16:31.872&#xA;&lt; Exit [AfterAll] when a new Component with specified custom branch is created - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:325 @ 04/20/26 07:16:31.97 (98ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:16:31.97&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:16:31.97 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="20.814305914">
              <system-err>&gt; Enter [BeforeAll] when the PaC init branch is updated - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:468 @ 04/20/26 07:16:31.971&#xA;created file sha: 44e0f27d7f8cbd710f07900eee4c0ddc9c1e34c4&#xA;&lt; Exit [BeforeAll] when the PaC init branch is updated - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:468 @ 04/20/26 07:16:32.587 (616ms)&#xA;&gt; Enter [It] eventually leads to triggering another PipelineRun - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:478 @ 04/20/26 07:16:32.587&#xA;PipelineRun has not been created yet for the component build-e2e-kseb/gh-test-custom-branch-dvkcvc&#xA;&lt; Exit [It] eventually leads to triggering another PipelineRun - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:478 @ 04/20/26 07:16:52.785 (20.198s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:16:52.785&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:16:52.785 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated should lead to a PaC init PR update [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.206589181">
              <system-err>&gt; Enter [It] should lead to a PaC init PR update - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:493 @ 04/20/26 07:16:52.786&#xA;&lt; Exit [It] should lead to a PaC init PR update - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:493 @ 04/20/26 07:16:52.992 (206ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:16:52.992&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:16:52.992 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated PipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="failed" time="2372.092285912">
              <failure message="Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc001a0e620&gt;: &#xA;    &#xA;     pod: gh-test-custom-branch-dvkcvc-on-pull-request-t52m4-init-pod | init container: prepare&#xA;    2026/04/20 07:46:21 Entrypoint initialization&#xA;    &#xA;    pod: gh-test-custom-branch-dvkcvc-on-pull-request-t52m4-init-pod | container step-init: &#xA;    time=&#34;2026-04-20T07:46:48Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;    &#xA;     pod: gh-test-custom-branch-dvkcvc-on-pull-request-v67bq-init-pod | init container: prepare&#xA;    2026/04/20 07:06:41 Entrypoint initialization&#xA;    &#xA;    pod: gh-test-custom-branch-dvkcvc-on-pull-request-v67bq-init-pod | container step-init: &#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;    time=&#34;2026-04-20T07:07:08Z&#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-20T07:07:08Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;    &#xA;    {&#xA;        s: &#34;\n pod: gh-test-custom-branch-dvkcvc-on-pull-request-t52m4-init-pod | init container: prepare\n2026/04/20 07:46:21 Entrypoint initialization\n\npod: gh-test-custom-branch-dvkcvc-on-pull-request-t52m4-init-pod | container step-init: \ntime=\&#34;2026-04-20T07:46:48Z\&#34; level=info msg=\&#34;Using in-cluster config\&#34; logger=KubeClient\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] enable: false\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] http-proxy-result-path: /tekton/results/http-proxy\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] no-proxy-result-path: /tekton/results/no-proxy\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;Cache proxy is disabled in param or in backend\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[result] HTTP PROXY: \&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[result] NO PROXY: \&#34;\n\n pod: gh-test-custom-branch-dvkcvc-on-pull-request-v67bq-init-pod | init container: prepare\n2026/04/20 07:06:41 Entrypoint initialization\n\npod: gh-test-custom-branch-dvkcvc-on-pull-request-v67bq-init-pod | container step-init: \ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;Using in-cluster config\&#34; logger=KubeClient\ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;[param] enable: false\&#34;\ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128\&#34;\ntime=\&#34;2026-04-20T07:07:08Z\&#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-20T07:07:08Z\&#34; level=info msg=\&#34;[param] http-proxy-result-path: /tekton/results/http-proxy\&#34;\ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;[param] no-proxy-result-path: /tekton/results/no-proxy\&#34;\ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;Cache proxy is disabled in param or in backend\&#34;\ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;[result] HTTP PROXY: \&#34;\ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;[result] NO PROXY: \&#34;\n&#34;,&#xA;    }" type="failed">[FAILED] Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc001a0e620&gt;: &#xA;    &#xA;     pod: gh-test-custom-branch-dvkcvc-on-pull-request-t52m4-init-pod | init container: prepare&#xA;    2026/04/20 07:46:21 Entrypoint initialization&#xA;    &#xA;    pod: gh-test-custom-branch-dvkcvc-on-pull-request-t52m4-init-pod | container step-init: &#xA;    time=&#34;2026-04-20T07:46:48Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;    &#xA;     pod: gh-test-custom-branch-dvkcvc-on-pull-request-v67bq-init-pod | init container: prepare&#xA;    2026/04/20 07:06:41 Entrypoint initialization&#xA;    &#xA;    pod: gh-test-custom-branch-dvkcvc-on-pull-request-v67bq-init-pod | container step-init: &#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;    time=&#34;2026-04-20T07:07:08Z&#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-20T07:07:08Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;    &#xA;    {&#xA;        s: &#34;\n pod: gh-test-custom-branch-dvkcvc-on-pull-request-t52m4-init-pod | init container: prepare\n2026/04/20 07:46:21 Entrypoint initialization\n\npod: gh-test-custom-branch-dvkcvc-on-pull-request-t52m4-init-pod | container step-init: \ntime=\&#34;2026-04-20T07:46:48Z\&#34; level=info msg=\&#34;Using in-cluster config\&#34; logger=KubeClient\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] enable: false\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] http-proxy-result-path: /tekton/results/http-proxy\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] no-proxy-result-path: /tekton/results/no-proxy\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;Cache proxy is disabled in param or in backend\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[result] HTTP PROXY: \&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[result] NO PROXY: \&#34;\n\n pod: gh-test-custom-branch-dvkcvc-on-pull-request-v67bq-init-pod | init container: prepare\n2026/04/20 07:06:41 Entrypoint initialization\n\npod: gh-test-custom-branch-dvkcvc-on-pull-request-v67bq-init-pod | container step-init: \ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;Using in-cluster config\&#34; logger=KubeClient\ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;[param] enable: false\&#34;\ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128\&#34;\ntime=\&#34;2026-04-20T07:07:08Z\&#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-20T07:07:08Z\&#34; level=info msg=\&#34;[param] http-proxy-result-path: /tekton/results/http-proxy\&#34;\ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;[param] no-proxy-result-path: /tekton/results/no-proxy\&#34;\ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;Cache proxy is disabled in param or in backend\&#34;\ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;[result] HTTP PROXY: \&#34;\ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;[result] NO PROXY: \&#34;\n&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:514 @ 04/20/26 07:56:23.487&#xA;</failure>
              <system-err>&gt; Enter [It] PipelineRun should eventually finish - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:512 @ 04/20/26 07:16:52.993&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k found for Component build-e2e-kseb/gh-test-custom-branch-dvkcvc&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun has not been created yet for the Component build-e2e-kseb/gh-test-custom-branch-dvkcvc&#xA;PipelineRun has not been created yet for the Component build-e2e-kseb/gh-test-custom-branch-dvkcvc&#xA;PipelineRun has not been created yet for the Component build-e2e-kseb/gh-test-custom-branch-dvkcvc&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun has not been created yet for the Component build-e2e-kseb/gh-test-custom-branch-dvkcvc&#xA;PipelineRun has not been created yet for the Component build-e2e-kseb/gh-test-custom-branch-dvkcvc&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-89k6k reason: Failed&#xA;attempt 1/3: PipelineRun &#34;gh-test-custom-branch-dvkcvc-on-pull-request-89k6k&#34; failed: &#xA; pod: gh-test-custom-branch-dvkcvc-on-pull-request-89k6k-init-pod | init container: prepare&#xA;2026/04/20 07:17:29 Entrypoint initialization&#xA;&#xA;pod: gh-test-custom-branch-dvkcvc-on-pull-request-89k6k-init-pod | container step-init: &#xA;time=&#34;2026-04-20T07:17:55Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-20T07:17:55Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-20T07:17:55Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-20T07:17:55Z&#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-20T07:17:55Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-20T07:17:55Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-20T07:17:55Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;time=&#34;2026-04-20T07:17:55Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-20T07:17:55Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;&#xA; pod: gh-test-custom-branch-dvkcvc-on-pull-request-v67bq-init-pod | init container: prepare&#xA;2026/04/20 07:06:41 Entrypoint initialization&#xA;&#xA;pod: gh-test-custom-branch-dvkcvc-on-pull-request-v67bq-init-pod | container step-init: &#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-20T07:07:08Z&#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-20T07:07:08Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;New PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-v67bq found after retrigger for component build-e2e-kseb/gh-test-custom-branch-dvkcvc&#xA;PipelineRun has not been created yet for the Component build-e2e-kseb/gh-test-custom-branch-dvkcvc&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 found for Component build-e2e-kseb/gh-test-custom-branch-dvkcvc&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: &#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-726t7 reason: Failed&#xA;attempt 2/3: PipelineRun &#34;gh-test-custom-branch-dvkcvc-on-pull-request-726t7&#34; failed: &#xA; pod: gh-test-custom-branch-dvkcvc-on-pull-request-726t7-init-pod | init container: prepare&#xA;2026/04/20 07:36:51 Entrypoint initialization&#xA;&#xA;pod: gh-test-custom-branch-dvkcvc-on-pull-request-726t7-init-pod | container step-init: &#xA;time=&#34;2026-04-20T07:37:24Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-20T07:37:24Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-20T07:37:24Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-20T07:37:24Z&#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-20T07:37:24Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-20T07:37:24Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-20T07:37:24Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;time=&#34;2026-04-20T07:37:24Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-20T07:37:24Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;&#xA; pod: gh-test-custom-branch-dvkcvc-on-pull-request-v67bq-init-pod | init container: prepare&#xA;2026/04/20 07:06:41 Entrypoint initialization&#xA;&#xA;pod: gh-test-custom-branch-dvkcvc-on-pull-request-v67bq-init-pod | container step-init: &#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-20T07:07:08Z&#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-20T07:07:08Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;New PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 found after retrigger for component build-e2e-kseb/gh-test-custom-branch-dvkcvc&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 found for Component build-e2e-kseb/gh-test-custom-branch-dvkcvc&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: &#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: ResolvingTaskRef&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Running&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: PipelineRunStopping&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: PipelineRunStopping&#xA;PipelineRun gh-test-custom-branch-dvkcvc-on-pull-request-t52m4 reason: Failed&#xA;attempt 3/3: PipelineRun &#34;gh-test-custom-branch-dvkcvc-on-pull-request-t52m4&#34; failed: &#xA; pod: gh-test-custom-branch-dvkcvc-on-pull-request-t52m4-init-pod | init container: prepare&#xA;2026/04/20 07:46:21 Entrypoint initialization&#xA;&#xA;pod: gh-test-custom-branch-dvkcvc-on-pull-request-t52m4-init-pod | container step-init: &#xA;time=&#34;2026-04-20T07:46:48Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai&#34;&#xA;time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;&#xA; pod: gh-test-custom-branch-dvkcvc-on-pull-request-v67bq-init-pod | init container: prepare&#xA;2026/04/20 07:06:41 Entrypoint initialization&#xA;&#xA;pod: gh-test-custom-branch-dvkcvc-on-pull-request-v67bq-init-pod | container step-init: &#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-20T07:07:08Z&#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-20T07:07:08Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;[FAILED] Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc001a0e620&gt;: &#xA;    &#xA;     pod: gh-test-custom-branch-dvkcvc-on-pull-request-t52m4-init-pod | init container: prepare&#xA;    2026/04/20 07:46:21 Entrypoint initialization&#xA;    &#xA;    pod: gh-test-custom-branch-dvkcvc-on-pull-request-t52m4-init-pod | container step-init: &#xA;    time=&#34;2026-04-20T07:46:48Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;    time=&#34;2026-04-20T07:46:49Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;    &#xA;     pod: gh-test-custom-branch-dvkcvc-on-pull-request-v67bq-init-pod | init container: prepare&#xA;    2026/04/20 07:06:41 Entrypoint initialization&#xA;    &#xA;    pod: gh-test-custom-branch-dvkcvc-on-pull-request-v67bq-init-pod | container step-init: &#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;    time=&#34;2026-04-20T07:07:08Z&#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-20T07:07:08Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;    time=&#34;2026-04-20T07:07:08Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;    &#xA;    {&#xA;        s: &#34;\n pod: gh-test-custom-branch-dvkcvc-on-pull-request-t52m4-init-pod | init container: prepare\n2026/04/20 07:46:21 Entrypoint initialization\n\npod: gh-test-custom-branch-dvkcvc-on-pull-request-t52m4-init-pod | container step-init: \ntime=\&#34;2026-04-20T07:46:48Z\&#34; level=info msg=\&#34;Using in-cluster config\&#34; logger=KubeClient\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] enable: false\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] http-proxy-result-path: /tekton/results/http-proxy\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[param] no-proxy-result-path: /tekton/results/no-proxy\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;Cache proxy is disabled in param or in backend\&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[result] HTTP PROXY: \&#34;\ntime=\&#34;2026-04-20T07:46:49Z\&#34; level=info msg=\&#34;[result] NO PROXY: \&#34;\n\n pod: gh-test-custom-branch-dvkcvc-on-pull-request-v67bq-init-pod | init container: prepare\n2026/04/20 07:06:41 Entrypoint initialization\n\npod: gh-test-custom-branch-dvkcvc-on-pull-request-v67bq-init-pod | container step-init: \ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;Using in-cluster config\&#34; logger=KubeClient\ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;[param] enable: false\&#34;\ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128\&#34;\ntime=\&#34;2026-04-20T07:07:08Z\&#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-20T07:07:08Z\&#34; level=info msg=\&#34;[param] http-proxy-result-path: /tekton/results/http-proxy\&#34;\ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;[param] no-proxy-result-path: /tekton/results/no-proxy\&#34;\ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;Cache proxy is disabled in param or in backend\&#34;\ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;[result] HTTP PROXY: \&#34;\ntime=\&#34;2026-04-20T07:07:08Z\&#34; level=info msg=\&#34;[result] NO PROXY: \&#34;\n&#34;,&#xA;    }&#xA;In [It] at: /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:514 @ 04/20/26 07:56:23.487&#xA;&lt; Exit [It] PipelineRun should eventually finish - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:512 @ 04/20/26 07:56:23.487 (39m30.495s)&#xA;&gt; Enter [AfterAll] PaC component build - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:102 @ 04/20/26 07:56:23.488&#xA;&lt; Exit [AfterAll] PaC component build - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:102 @ 04/20/26 07:56:23.488 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:56:23.488&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/pac_build.go:29 @ 04/20/26 07:56:25.085 (1.597s)&#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.XKFaKtKOZB/tests/build/pac_build.go:518 @ 04/20/26 07:56:25.085&#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.XKFaKtKOZB/tests/build/pac_build.go:544 @ 04/20/26 07:56:25.086&#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.XKFaKtKOZB/tests/build/pac_build.go:560 @ 04/20/26 07:56:25.086&#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.XKFaKtKOZB/tests/build/pac_build.go:566 @ 04/20/26 07:56:25.086&#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.XKFaKtKOZB/tests/build/pac_build.go:578 @ 04/20/26 07:56:25.086&#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.XKFaKtKOZB/tests/build/pac_build.go:609 @ 04/20/26 07:56:25.087&#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.XKFaKtKOZB/tests/build/pac_build.go:729 @ 04/20/26 07:56:25.087&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace creates component with nudges [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="passed" time="66.537685761">
              <system-err>&gt; Enter [BeforeAll] component update with renovate - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:72 @ 04/20/26 07:01:05.141&#xA;ReleaseAdmissionPlan data: {&#34;Mapping&#34;:{&#34;Components&#34;:[{&#34;Name&#34;:&#34;gl-multi-component-parent-hdgg&#34;,&#34;Repository&#34;:&#34;quay.io/redhat-appstudio-qe/release-repository&#34;}]}}&#xA;&lt; Exit [BeforeAll] component update with renovate - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:72 @ 04/20/26 07:01:31.416 (26.276s)&#xA;&gt; Enter [It] creates component with nudges - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:235 @ 04/20/26 07:01:31.416&#xA;Image repository for component gl-multi-component-child-hdgg in namespace build-e2e-mggg do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component gl-multi-component-child-hdgg in namespace build-e2e-mggg do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component gl-multi-component-child-hdgg in namespace build-e2e-mggg 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-hdgg in namespace build-e2e-mggg 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.XKFaKtKOZB/tests/build/renovate.go:235 @ 04/20/26 07:02:11.678 (40.261s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:02:11.678&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:02:11.678 (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="112.89789625">
              <system-err>&gt; Enter [It] triggers a PipelineRun for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:259 @ 04/20/26 07:02:11.678&#xA;PipelineRun has not been created yet for the component build-e2e-mggg/gl-multi-component-parent-hdgg&#xA;PipelineRun has not been created yet for the component build-e2e-mggg/gl-multi-component-parent-hdgg&#xA;PipelineRun has not been created yet for the component build-e2e-mggg/gl-multi-component-parent-hdgg&#xA;PipelineRun has not been created yet for the component build-e2e-mggg/gl-multi-component-parent-hdgg&#xA;PipelineRun has not been created yet for the component build-e2e-mggg/gl-multi-component-parent-hdgg&#xA;&lt; Exit [It] triggers a PipelineRun for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:259 @ 04/20/26 07:04:04.576 (1m52.897s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:04:04.576&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:04:04.576 (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="1715.273506998">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:274 @ 04/20/26 07:04:04.577&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb found for Component build-e2e-mggg/gl-multi-component-parent-hdgg&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-4rprb reason: Failed&#xA;attempt 1/3: PipelineRun &#34;gl-multi-component-parent-hdgg-on-pull-request-4rprb&#34; failed: &#xA; pod: gl-multi-component-parent-hdgg-on-pull-request-4rprb-init-pod | init container: prepare&#xA;2026/04/20 07:05:25 Entrypoint initialization&#xA;&#xA;pod: gl-multi-component-parent-hdgg-on-pull-request-4rprb-init-pod | container step-init: &#xA;time=&#34;2026-04-20T07:05:44Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-20T07:05:44Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-20T07:05:44Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-20T07:05:44Z&#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-20T07:05:44Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-20T07:05:44Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-20T07:05:45Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;time=&#34;2026-04-20T07:05:45Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-20T07:05:45Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;New PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 found after retrigger for component build-e2e-mggg/gl-multi-component-parent-hdgg&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 found for Component build-e2e-mggg/gl-multi-component-parent-hdgg&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: &#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun has not been created yet for the Component build-e2e-mggg/gl-multi-component-parent-hdgg&#xA;PipelineRun has not been created yet for the Component build-e2e-mggg/gl-multi-component-parent-hdgg&#xA;PipelineRun has not been created yet for the Component build-e2e-mggg/gl-multi-component-parent-hdgg&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun has not been created yet for the Component build-e2e-mggg/gl-multi-component-parent-hdgg&#xA;PipelineRun has not been created yet for the Component build-e2e-mggg/gl-multi-component-parent-hdgg&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-pull-request-p9qj7 reason: Completed&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:274 @ 04/20/26 07:32:39.85 (28m35.273s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:32:39.85&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:32:39.85 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for child component  [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="passed" time="0.722720828">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:285 @ 04/20/26 07:32:39.851&#xA;PipelineRun gl-multi-component-child-hdgg-on-pull-request-rf4z5 found for Component build-e2e-mggg/gl-multi-component-child-hdgg&#xA;PipelineRun gl-multi-component-child-hdgg-on-pull-request-rf4z5 reason: Completed&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:285 @ 04/20/26 07:32:40.573 (722ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:32:40.574&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:32:40.574 (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.284831289">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:289 @ 04/20/26 07:32:40.574&#xA;&lt; Exit [It] should lead to a PaC PR creation for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:289 @ 04/20/26 07:32:40.859 (285ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:32:40.859&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:32:40.859 (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.633638283">
              <system-err>&gt; Enter [It] Merging the PaC PR should be successful for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:307 @ 04/20/26 07:32:40.859&#xA;merged result sha: 4fba845bf20d46dd435bab4825c82913592fe4f9 for PR #1&#xA;&lt; Exit [It] Merging the PaC PR should be successful for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:307 @ 04/20/26 07:32:42.493 (1.633s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:32:42.493&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:32:42.493 (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.733019202">
              <system-err>&gt; Enter [It] create dockerfile and yaml manifest that references build and distribution repositories - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:318 @ 04/20/26 07:32:42.493&#xA;&lt; Exit [It] create dockerfile and yaml manifest that references build and distribution repositories - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:318 @ 04/20/26 07:33:48.226 (1m5.733s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:33:48.226&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:33:48.226 (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.190161073">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:358 @ 04/20/26 07:33:48.227&#xA;&lt; Exit [It] should lead to a PaC PR creation for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:358 @ 04/20/26 07:33:48.417 (190ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:33:48.417&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:33:48.417 (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="2.076040857">
              <system-err>&gt; Enter [It] Merging the PaC PR should be successful for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:375 @ 04/20/26 07:33:48.418&#xA;merged result sha: de002b1032a392e2dd08f425737ea70828aa0ef6 for PR #1&#xA;&lt; Exit [It] Merging the PaC PR should be successful for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:375 @ 04/20/26 07:33:50.493 (2.076s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:33:50.493&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:33:50.493 (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="104.357569154">
              <system-err>&gt; Enter [It] PR merge triggers PAC PipelineRun for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:385 @ 04/20/26 07:33:50.494&#xA;Push PipelineRun has not been created yet for the component build-e2e-mggg/gl-multi-component-parent-hdgg&#xA;Push PipelineRun has not been created yet for the component build-e2e-mggg/gl-multi-component-parent-hdgg&#xA;Push PipelineRun has not been created yet for the component build-e2e-mggg/gl-multi-component-parent-hdgg&#xA;&lt; Exit [It] PR merge triggers PAC PipelineRun for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:385 @ 04/20/26 07:35:34.851 (1m44.357s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:35:34.851&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:35:34.851 (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="1971.305123362">
              <system-err>&gt; Enter [It] PAC PipelineRun for parent component  is successful - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:401 @ 04/20/26 07:35:34.852&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t found for Component build-e2e-mggg/gl-multi-component-parent-hdgg&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-2pp7t reason: PipelineRunStopping&#xA;attempt 1/3: PipelineRun &#34;gl-multi-component-parent-hdgg-on-push-2pp7t&#34; failed: context deadline exceededNew PipelineRun gl-multi-component-parent-hdgg-on-push-wmwq2 found after retrigger for component build-e2e-mggg/gl-multi-component-parent-hdgg&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-wmwq2 found for Component build-e2e-mggg/gl-multi-component-parent-hdgg&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-wmwq2 reason: ResolvingTaskRef&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-wmwq2 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-wmwq2 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-wmwq2 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-wmwq2 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-wmwq2 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-wmwq2 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-wmwq2 reason: Running&#xA;PipelineRun gl-multi-component-parent-hdgg-on-push-wmwq2 reason: Completed&#xA;&lt; Exit [It] PAC PipelineRun for parent component  is successful - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:401 @ 04/20/26 08:08:26.157 (32m51.305s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 08:08:26.157&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 08:08:26.157 (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.412694085">
              <system-err>&gt; Enter [It] should lead to a nudge PR creation for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:412 @ 04/20/26 08:08:26.158&#xA;&lt; Exit [It] should lead to a nudge PR creation for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:412 @ 04/20/26 08:08:36.57 (10.412s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 08:08:36.57&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 08:08:36.57 (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.382810586">
              <system-err>&gt; Enter [It] merging the PR should be successful for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:429 @ 04/20/26 08:08:36.571&#xA;merged result sha: a6cb115463ac2aa8887f7a65f594abbe98f68e3d for PR #3&#xA;&lt; Exit [It] merging the PR should be successful for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:429 @ 04/20/26 08:08:37.953 (1.382s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 08:08:37.953&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 08:08:37.953 (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="12.878041329">
              <system-err>&gt; Enter [It] Verify the nudge updated the contents - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:440 @ 04/20/26 08:08:37.954&#xA;Verifying Dockerfile.tmp updated to sha sha256:0f46a9c066cd33cd6a34fc895a47a18dcdb39bc47d5edcb58c53019601e8766fcontent: FROM quay.io/redhat-appstudio-qe/build-e2e-mggg/gl-multi-component-parent-hdgg@sha256:0f46a9c066cd33cd6a34fc895a47a18dcdb39bc47d5edcb58c53019601e8766f&#xA;RUN echo hello&#xA;&#xA;&lt; Exit [It] Verify the nudge updated the contents - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:440 @ 04/20/26 08:08:38.335 (381ms)&#xA;&gt; Enter [AfterAll] component update with renovate - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:214 @ 04/20/26 08:08:38.335&#xA;&lt; Exit [AfterAll] component update with renovate - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:214 @ 04/20/26 08:08:50.832 (12.496s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 08:08:50.832&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 08:08:50.832 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace creates component with nudges [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="passed" time="67.001193409">
              <system-err>&gt; Enter [BeforeAll] component update with renovate - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:72 @ 04/20/26 07:01:05.044&#xA;ReleaseAdmissionPlan data: {&#34;Mapping&#34;:{&#34;Components&#34;:[{&#34;Name&#34;:&#34;gh-multi-component-parent-unkt&#34;,&#34;Repository&#34;:&#34;quay.io/redhat-appstudio-qe/release-repository&#34;}]}}&#xA;&lt; Exit [BeforeAll] component update with renovate - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:72 @ 04/20/26 07:01:31.766 (26.722s)&#xA;&gt; Enter [It] creates component with nudges - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:235 @ 04/20/26 07:01:31.766&#xA;Image repository for component gh-multi-component-child-unkt in namespace build-e2e-rdig do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component gh-multi-component-child-unkt in namespace build-e2e-rdig do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component gh-multi-component-child-unkt in namespace build-e2e-rdig 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-unkt in namespace build-e2e-rdig 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.XKFaKtKOZB/tests/build/renovate.go:235 @ 04/20/26 07:02:12.044 (40.278s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:02:12.045&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:02:12.045 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace triggers a PipelineRun for parent component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="passed" time="132.845296203">
              <system-err>&gt; Enter [It] triggers a PipelineRun for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:259 @ 04/20/26 07:02:12.045&#xA;PipelineRun has not been created yet for the component build-e2e-rdig/gh-multi-component-parent-unkt&#xA;PipelineRun has not been created yet for the component build-e2e-rdig/gh-multi-component-parent-unkt&#xA;PipelineRun has not been created yet for the component build-e2e-rdig/gh-multi-component-parent-unkt&#xA;PipelineRun has not been created yet for the component build-e2e-rdig/gh-multi-component-parent-unkt&#xA;PipelineRun has not been created yet for the component build-e2e-rdig/gh-multi-component-parent-unkt&#xA;&lt; Exit [It] triggers a PipelineRun for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:259 @ 04/20/26 07:04:24.89 (2m12.845s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:04:24.89&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:04:24.89 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for parent component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="passed" time="2346.760038403">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:274 @ 04/20/26 07:04:24.891&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf found for Component build-e2e-rdig/gh-multi-component-parent-unkt&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-p4wlf reason: Failed&#xA;attempt 1/3: PipelineRun &#34;gh-multi-component-parent-unkt-on-pull-request-p4wlf&#34; failed: &#xA; pod: gh-multi-component-parent-unkt-on-pull-request-p4wlf-init-pod | init container: prepare&#xA;2026/04/20 07:05:53 Entrypoint initialization&#xA;&#xA;pod: gh-multi-component-parent-unkt-on-pull-request-p4wlf-init-pod | container step-init: &#xA;time=&#34;2026-04-20T07:06:03Z&#34; level=info msg=&#34;Using in-cluster config&#34; logger=KubeClient&#xA;time=&#34;2026-04-20T07:06:03Z&#34; level=info msg=&#34;[param] enable: false&#34;&#xA;time=&#34;2026-04-20T07:06:03Z&#34; level=info msg=&#34;[param] default-http-proxy: squid.caching.svc.cluster.local:3128&#34;&#xA;time=&#34;2026-04-20T07:06:03Z&#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-20T07:06:03Z&#34; level=info msg=&#34;[param] http-proxy-result-path: /tekton/results/http-proxy&#34;&#xA;time=&#34;2026-04-20T07:06:03Z&#34; level=info msg=&#34;[param] no-proxy-result-path: /tekton/results/no-proxy&#34;&#xA;time=&#34;2026-04-20T07:06:03Z&#34; level=info msg=&#34;Cache proxy is disabled in param or in backend&#34;&#xA;time=&#34;2026-04-20T07:06:03Z&#34; level=info msg=&#34;[result] HTTP PROXY: &#34;&#xA;time=&#34;2026-04-20T07:06:03Z&#34; level=info msg=&#34;[result] NO PROXY: &#34;&#xA;New PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 found after retrigger for component build-e2e-rdig/gh-multi-component-parent-unkt&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 found for Component build-e2e-rdig/gh-multi-component-parent-unkt&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun has not been created yet for the Component build-e2e-rdig/gh-multi-component-parent-unkt&#xA;PipelineRun has not been created yet for the Component build-e2e-rdig/gh-multi-component-parent-unkt&#xA;PipelineRun has not been created yet for the Component build-e2e-rdig/gh-multi-component-parent-unkt&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun has not been created yet for the Component build-e2e-rdig/gh-multi-component-parent-unkt&#xA;PipelineRun has not been created yet for the Component build-e2e-rdig/gh-multi-component-parent-unkt&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-pull-request-8wqk2 reason: Completed&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:274 @ 04/20/26 07:43:31.65 (39m6.76s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:43:31.651&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:43:31.651 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for child component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="passed" time="0.585353349">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:285 @ 04/20/26 07:43:31.651&#xA;PipelineRun gh-multi-component-child-unkt-on-pull-request-mhgpt found for Component build-e2e-rdig/gh-multi-component-child-unkt&#xA;PipelineRun gh-multi-component-child-unkt-on-pull-request-mhgpt reason: Completed&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:285 @ 04/20/26 07:43:32.236 (585ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:43:32.236&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:43:32.236 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace should lead to a PaC PR creation for child component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="passed" time="0.190422317">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:289 @ 04/20/26 07:43:32.237&#xA;&lt; Exit [It] should lead to a PaC PR creation for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:289 @ 04/20/26 07:43:32.427 (190ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:43:32.427&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:43:32.427 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace Merging the PaC PR should be successful for child component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="passed" time="1.8620946950000001">
              <system-err>&gt; Enter [It] Merging the PaC PR should be successful for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:307 @ 04/20/26 07:43:32.428&#xA;merged result sha: 726a752be1a626ea98c749611e700d292c97e6a6 for PR #1&#xA;&lt; Exit [It] Merging the PaC PR should be successful for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:307 @ 04/20/26 07:43:34.289 (1.862s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:43:34.29&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:43:34.29 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace create dockerfile and yaml manifest that references build and distribution repositories [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="passed" time="5.230193715">
              <system-err>&gt; Enter [It] create dockerfile and yaml manifest that references build and distribution repositories - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:318 @ 04/20/26 07:43:34.291&#xA;&lt; Exit [It] create dockerfile and yaml manifest that references build and distribution repositories - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:318 @ 04/20/26 07:43:39.52 (5.23s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:43:39.521&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:43:39.521 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace should lead to a PaC PR creation for parent component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="passed" time="0.159002471">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:358 @ 04/20/26 07:43:39.521&#xA;&lt; Exit [It] should lead to a PaC PR creation for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:358 @ 04/20/26 07:43:39.68 (159ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:43:39.68&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:43:39.68 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace Merging the PaC PR should be successful for parent component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="passed" time="1.827865735">
              <system-err>&gt; Enter [It] Merging the PaC PR should be successful for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:375 @ 04/20/26 07:43:39.681&#xA;merged result sha: 7c14af206a41ad33f781aed1b65f4576e7e5c2fe for PR #1&#xA;&lt; Exit [It] Merging the PaC PR should be successful for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:375 @ 04/20/26 07:43:41.508 (1.827s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:43:41.508&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:43:41.508 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace PR merge triggers PAC PipelineRun for parent component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="passed" time="20.636357864">
              <system-err>&gt; Enter [It] PR merge triggers PAC PipelineRun for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:385 @ 04/20/26 07:43:41.509&#xA;Push PipelineRun has not been created yet for the component build-e2e-rdig/gh-multi-component-parent-unkt&#xA;&lt; Exit [It] PR merge triggers PAC PipelineRun for parent component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:385 @ 04/20/26 07:44:02.145 (20.636s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:44:02.145&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 07:44:02.145 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace PAC PipelineRun for parent component  is successful [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="passed" time="1971.323902976">
              <system-err>&gt; Enter [It] PAC PipelineRun for parent component  is successful - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:401 @ 04/20/26 07:44:02.146&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c found for Component build-e2e-rdig/gh-multi-component-parent-unkt&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-8mn2c reason: PipelineRunStopping&#xA;attempt 1/3: PipelineRun &#34;gh-multi-component-parent-unkt-on-push-8mn2c&#34; failed: context deadline exceededNew PipelineRun gh-multi-component-parent-unkt-on-push-dh8p7 found after retrigger for component build-e2e-rdig/gh-multi-component-parent-unkt&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-dh8p7 found for Component build-e2e-rdig/gh-multi-component-parent-unkt&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-dh8p7 reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-dh8p7 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-dh8p7 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-dh8p7 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-dh8p7 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-dh8p7 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-dh8p7 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-dh8p7 reason: Running&#xA;PipelineRun gh-multi-component-parent-unkt-on-push-dh8p7 reason: Completed&#xA;&lt; Exit [It] PAC PipelineRun for parent component  is successful - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:401 @ 04/20/26 08:16:53.47 (32m51.324s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 08:16:53.47&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 08:16:53.47 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace should lead to a nudge PR creation for child component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="passed" time="10.369694271">
              <system-err>&gt; Enter [It] should lead to a nudge PR creation for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:412 @ 04/20/26 08:16:53.471&#xA;&lt; Exit [It] should lead to a nudge PR creation for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:412 @ 04/20/26 08:17:03.84 (10.369s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 08:17:03.84&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 08:17:03.84 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace merging the PR should be successful for child component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="passed" time="2.118625176">
              <system-err>&gt; Enter [It] merging the PR should be successful for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:429 @ 04/20/26 08:17:03.841&#xA;merged result sha: dbc5a4b3043e275c8037509bffa493c3670506da for PR #3&#xA;&lt; Exit [It] merging the PR should be successful for child component  - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:429 @ 04/20/26 08:17:05.959 (2.118s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 08:17:05.959&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 08:17:05.959 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace Verify the nudge updated the contents [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="passed" time="14.316582282">
              <system-err>&gt; Enter [It] Verify the nudge updated the contents - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:440 @ 04/20/26 08:17:05.96&#xA;Verifying Dockerfile.tmp updated to sha sha256:ad856c761b5b819f2eaea28d685c1968b4e0e9ee6e3af29f91df6a6e319f405econtent: FROM quay.io/redhat-appstudio-qe/build-e2e-rdig/gh-multi-component-parent-unkt@sha256:ad856c761b5b819f2eaea28d685c1968b4e0e9ee6e3af29f91df6a6e319f405e&#xA;RUN echo hello&#xA;&#xA;&lt; Exit [It] Verify the nudge updated the contents - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:440 @ 04/20/26 08:17:06.195 (236ms)&#xA;&gt; Enter [AfterAll] component update with renovate - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:214 @ 04/20/26 08:17:06.196&#xA;&lt; Exit [AfterAll] component update with renovate - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:214 @ 04/20/26 08:17:20.276 (14.08s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 08:17:20.276&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /tmp/tmp.XKFaKtKOZB/tests/build/renovate.go:28 @ 04/20/26 08:17:20.276 (0s)&#xA;</system-err>
          </testcase>
      </testsuite>
  </testsuites>