<?xml version="1.0" encoding="UTF-8"?>
  <testsuites tests="157" disabled="122" errors="0" failures="0" time="1112.650323487">
      <testsuite name="Build Service E2E" package="/workspace/source/e2e-tests/tests" tests="157" disabled="7" skipped="115" errors="0" failures="0" time="1112.650323487" timestamp="2026-05-05T09:09:25">
          <properties>
              <property name="SuiteSucceeded" value="true"></property>
              <property name="SuiteHasProgrammaticFocus" value="false"></property>
              <property name="SpecialSuiteFailureReason" value=""></property>
              <property name="SuiteLabels" value="[]"></property>
              <property name="SuiteSemVerConstraints" value="[]"></property>
              <property name="SuiteComponentSemVerConstraints" value="[]"></property>
              <property name="RandomSeed" value="1777971902"></property>
              <property name="RandomizeAllSpecs" value="false"></property>
              <property name="LabelFilter" value="build-service &amp;&amp; github &amp;&amp; !github-webhook"></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="true"></property>
              <property name="FailFast" value="false"></property>
              <property name="FlakeAttempts" value="0"></property>
              <property name="DryRun" value="false"></property>
              <property name="ParallelTotal" value="5"></property>
              <property name="OutputInterceptorMode" value="none"></property>
          </properties>
          <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="Build Service E2E" status="passed" time="26.734633844">
              <system-err>&gt; Enter [BeforeAll] test build secret lookup - /workspace/source/e2e-tests/tests/secret_lookup.go:32 @ 05/05/26 09:09:25.94&#xA;&lt; Exit [BeforeAll] test build secret lookup - /workspace/source/e2e-tests/tests/secret_lookup.go:32 @ 05/05/26 09:09:29.84 (3.9s)&#xA;&gt; Enter [BeforeAll] when two secrets are created - /workspace/source/e2e-tests/tests/secret_lookup.go:100 @ 05/05/26 09:09:29.84&#xA;&lt; Exit [BeforeAll] when two secrets are created - /workspace/source/e2e-tests/tests/secret_lookup.go:100 @ 05/05/26 09:09:29.97 (130ms)&#xA;&gt; Enter [It] creates first component - /workspace/source/e2e-tests/tests/secret_lookup.go:123 @ 05/05/26 09:09:29.97&#xA;Image repository for component component-one-aqvp in namespace build-e2e-qzhr 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-aqvp in namespace build-e2e-qzhr 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 - /workspace/source/e2e-tests/tests/secret_lookup.go:123 @ 05/05/26 09:09:52.674 (22.704s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/secret_lookup.go:25 @ 05/05/26 09:09:52.674&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/secret_lookup.go:25 @ 05/05/26 09:09:52.674 (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="Build Service E2E" status="passed" time="10.128546365">
              <system-err>&gt; Enter [It] creates second component - /workspace/source/e2e-tests/tests/secret_lookup.go:140 @ 05/05/26 09:09:52.675&#xA;Image repository for component component-two-wpyc in namespace build-e2e-qzhr 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 - /workspace/source/e2e-tests/tests/secret_lookup.go:140 @ 05/05/26 09:10:02.803 (10.128s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/secret_lookup.go:25 @ 05/05/26 09:10:02.803&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/secret_lookup.go:25 @ 05/05/26 09:10:02.804 (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="Build Service E2E" status="passed" time="0.06715267">
              <system-err>&gt; Enter [It] check first component annotation has errors - /workspace/source/e2e-tests/tests/secret_lookup.go:158 @ 05/05/26 09:10:02.804&#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 - /workspace/source/e2e-tests/tests/secret_lookup.go:158 @ 05/05/26 09:10:02.871 (67ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/secret_lookup.go:25 @ 05/05/26 09:10:02.871&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/secret_lookup.go:25 @ 05/05/26 09:10:02.871 (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="Build Service E2E" status="passed" time="22.500645913">
              <system-err>&gt; Enter [It] triggered PipelineRun is for component  - /workspace/source/e2e-tests/tests/secret_lookup.go:178 @ 05/05/26 09:10:02.872&#xA;PipelineRun has not been created yet for the component build-e2e-qzhr/component-two-wpyc&#xA;&lt; Exit [It] triggered PipelineRun is for component  - /workspace/source/e2e-tests/tests/secret_lookup.go:178 @ 05/05/26 09:10:25.372 (22.5s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/secret_lookup.go:25 @ 05/05/26 09:10:25.372&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/secret_lookup.go:25 @ 05/05/26 09:10:25.372 (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="Build Service E2E" status="passed" time="124.850503839">
              <system-err>&gt; Enter [It] check only one pipelinerun should be triggered - /workspace/source/e2e-tests/tests/secret_lookup.go:193 @ 05/05/26 09:10:25.373&#xA;&lt; Exit [It] check only one pipelinerun should be triggered - /workspace/source/e2e-tests/tests/secret_lookup.go:193 @ 05/05/26 09:12:25.374 (2m0.001s)&#xA;&gt; Enter [AfterAll] test build secret lookup - /workspace/source/e2e-tests/tests/secret_lookup.go:61 @ 05/05/26 09:12:25.374&#xA;&lt; Exit [AfterAll] test build secret lookup - /workspace/source/e2e-tests/tests/secret_lookup.go:61 @ 05/05/26 09:12:30.223 (4.849s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/secret_lookup.go:25 @ 05/05/26 09:12:30.223&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/secret_lookup.go:25 @ 05/05/26 09:12:30.223 (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="Build Service E2E" 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 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="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private workspace parameter is set correctly in PaC repository CR [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private build pipeline uses the correct serviceAccount [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private component build status is set correctly [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private created image repo is private [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private a related PipelineRun should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private PR branch should not exist in the repo [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private related image repo and the robot account should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created should lead to a PaC init PR creation [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created created image repo is public [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created image tag is updated successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created should ensure pruning labels are set [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created eventually leads to the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated should lead to a PaC init PR update [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated PipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated eventually leads to another update of a PR about the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged does not have expiration set [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged After updating image visibility to private, it should not trigger another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged image repo is updated to private [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged retrigger the pipeline manually [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" 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="Build Service E2E" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the component is removed related image repo and robot accounts deleted [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the component is removed purge PR is created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private correctly targets the default branch (that is not named &#39;main&#39;) with PaC [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private workspace parameter is set correctly in PaC repository CR [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private build pipeline uses the correct serviceAccount [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private component build status is set correctly [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private created image repo is private [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private a related PipelineRun should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private PR branch should not exist in the repo [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private related image repo and the robot account should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created should lead to a PaC init PR creation [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created created image repo is public [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created image tag is updated successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created should ensure pruning labels are set [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created eventually leads to the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is updated eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is updated should lead to a PaC init PR update [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is updated PipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is updated eventually leads to another update of a PR about the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged does not have expiration set [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged After updating image visibility to private, it should not trigger another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged image repo is updated to private [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged retrigger the pipeline manually [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" 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="Build Service E2E" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the component is removed related image repo and robot accounts deleted [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the component is removed purge PR is created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace creates component with nudges [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace triggers a PipelineRun for parent component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for parent component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for child component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace should lead to a PaC PR creation for child component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace Merging the PaC PR should be successful for child component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace create dockerfile and yaml manifest that references build and distribution repositories [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace should lead to a PaC PR creation for parent component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace Merging the PaC PR should be successful for parent component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace PR merge triggers PAC PipelineRun for parent component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace PAC PipelineRun for parent component  is successful [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace should lead to a nudge PR creation for child component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace merging the PR should be successful for child component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace Verify the nudge updated the contents [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace creates component with nudges [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace triggers a PipelineRun for parent component  [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for parent component  [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for child component  [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace should lead to a PaC PR creation for child component  [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace Merging the PaC PR should be successful for child component  [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace create dockerfile and yaml manifest that references build and distribution repositories [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace should lead to a PaC PR creation for parent component  [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace Merging the PaC PR should be successful for parent component  [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace PR merge triggers PAC PipelineRun for parent component  [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace PAC PipelineRun for parent component  is successful [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace should lead to a nudge PR creation for child component  [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace merging the PR should be successful for child component  [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace Verify the nudge updated the contents [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" 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="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private workspace parameter is set correctly in PaC repository CR [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private build pipeline uses the correct serviceAccount [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private component build status is set correctly [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private created image repo is private [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private a related PipelineRun should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private PR branch should not exist in the repo [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private related image repo and the robot account should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created should lead to a PaC init PR creation [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created created image repo is public [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created image tag is updated successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created should ensure pruning labels are set [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created eventually leads to the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated should lead to a PaC init PR update [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated PipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated eventually leads to another update of a PR about the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged does not have expiration set [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged After updating image visibility to private, it should not trigger another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged image repo is updated to private [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged retrigger the pipeline manually [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" 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="Build Service E2E" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the component is removed related image repo and robot accounts deleted [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the component is removed purge PR is created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" 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="Build Service E2E" status="passed" time="73.176825953">
              <system-err>&gt; Enter [BeforeAll] test build annotations - /workspace/source/e2e-tests/tests/annotations.go:35 @ 05/05/26 09:09:25.952&#xA;&lt; Exit [BeforeAll] test build annotations - /workspace/source/e2e-tests/tests/annotations.go:35 @ 05/05/26 09:09:27.435 (1.483s)&#xA;&gt; Enter [BeforeAll] when component is created with invalid build request annotations - /workspace/source/e2e-tests/tests/annotations.go:69 @ 05/05/26 09:09:27.435&#xA;Image repository for component test-annotations-kshvqq in namespace build-e2e-vsdw 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 - /workspace/source/e2e-tests/tests/annotations.go:69 @ 05/05/26 09:09:37.561 (10.126s)&#xA;&gt; Enter [It] handles invalid request annotation - /workspace/source/e2e-tests/tests/annotations.go:89 @ 05/05/26 09:09:37.561&#xA;build status annotation value: {&#34;message&#34;:&#34;unexpected build request: foo&#34;}&#xA;&lt; Exit [It] handles invalid request annotation - /workspace/source/e2e-tests/tests/annotations.go:89 @ 05/05/26 09:10:38.791 (1m1.229s)&#xA;&gt; Enter [AfterAll] test build annotations - /workspace/source/e2e-tests/tests/annotations.go:51 @ 05/05/26 09:10:38.791&#xA;&lt; Exit [AfterAll] test build annotations - /workspace/source/e2e-tests/tests/annotations.go:51 @ 05/05/26 09:10:39.128 (337ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/annotations.go:24 @ 05/05/26 09:10:39.129&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/annotations.go:24 @ 05/05/26 09:10:39.129 (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="Build Service E2E" status="passed" time="45.925996545">
              <system-err>&gt; Enter [BeforeAll] component update with renovate - /workspace/source/e2e-tests/tests/renovate.go:72 @ 05/05/26 09:09:25.943&#xA;ReleaseAdmissionPlan data: {&#34;Mapping&#34;:{&#34;Components&#34;:[{&#34;Name&#34;:&#34;gh-multi-component-parent-dniy&#34;,&#34;Repository&#34;:&#34;quay.io/redhat-appstudio-qe/release-repository&#34;}]}}&#xA;&lt; Exit [BeforeAll] component update with renovate - /workspace/source/e2e-tests/tests/renovate.go:72 @ 05/05/26 09:09:31.626 (5.683s)&#xA;&gt; Enter [It] creates component with nudges - /workspace/source/e2e-tests/tests/renovate.go:235 @ 05/05/26 09:09:31.626&#xA;Image repository for component gh-multi-component-child-dniy in namespace build-e2e-npyc 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-dniy in namespace build-e2e-npyc 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-dniy in namespace build-e2e-npyc 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-dniy in namespace build-e2e-npyc 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 - /workspace/source/e2e-tests/tests/renovate.go:235 @ 05/05/26 09:10:11.868 (40.243s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:10:11.869&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:10:11.869 (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="Build Service E2E" status="passed" time="20.251182257">
              <system-err>&gt; Enter [It] triggers a PipelineRun for parent component  - /workspace/source/e2e-tests/tests/renovate.go:259 @ 05/05/26 09:10:11.87&#xA;PipelineRun has not been created yet for the component build-e2e-npyc/gh-multi-component-parent-dniy&#xA;&lt; Exit [It] triggers a PipelineRun for parent component  - /workspace/source/e2e-tests/tests/renovate.go:259 @ 05/05/26 09:10:32.12 (20.251s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:10:32.121&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:10:32.121 (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="Build Service E2E" status="passed" time="420.174251739">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for parent component  - /workspace/source/e2e-tests/tests/renovate.go:274 @ 05/05/26 09:10:32.121&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw found for Component build-e2e-npyc/gh-multi-component-parent-dniy&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-pull-request-8cfhw reason: Completed&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for parent component  - /workspace/source/e2e-tests/tests/renovate.go:274 @ 05/05/26 09:17:32.295 (7m0.174s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:17:32.295&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:17:32.295 (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="Build Service E2E" status="passed" time="0.062378646">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for child component  - /workspace/source/e2e-tests/tests/renovate.go:285 @ 05/05/26 09:17:32.296&#xA;PipelineRun gh-multi-component-child-dniy-on-pull-request-h99zx found for Component build-e2e-npyc/gh-multi-component-child-dniy&#xA;PipelineRun gh-multi-component-child-dniy-on-pull-request-h99zx reason: Completed&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for child component  - /workspace/source/e2e-tests/tests/renovate.go:285 @ 05/05/26 09:17:32.358 (62ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:17:32.358&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:17:32.358 (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="Build Service E2E" status="passed" time="0.204038847">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for child component  - /workspace/source/e2e-tests/tests/renovate.go:289 @ 05/05/26 09:17:32.359&#xA;&lt; Exit [It] should lead to a PaC PR creation for child component  - /workspace/source/e2e-tests/tests/renovate.go:289 @ 05/05/26 09:17:32.562 (204ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:17:32.563&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:17:32.563 (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="Build Service E2E" status="passed" time="2.007586408">
              <system-err>&gt; Enter [It] Merging the PaC PR should be successful for child component  - /workspace/source/e2e-tests/tests/renovate.go:307 @ 05/05/26 09:17:32.563&#xA;merged result sha: 233e4f14fc455f84a2b357a1331d377e362b7d5e for PR #1&#xA;&lt; Exit [It] Merging the PaC PR should be successful for child component  - /workspace/source/e2e-tests/tests/renovate.go:307 @ 05/05/26 09:17:34.571 (2.007s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:17:34.571&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:17:34.571 (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="Build Service E2E" status="passed" time="5.4990567200000005">
              <system-err>&gt; Enter [It] create dockerfile and yaml manifest that references build and distribution repositories - /workspace/source/e2e-tests/tests/renovate.go:318 @ 05/05/26 09:17:34.571&#xA;&lt; Exit [It] create dockerfile and yaml manifest that references build and distribution repositories - /workspace/source/e2e-tests/tests/renovate.go:318 @ 05/05/26 09:17:40.07 (5.499s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:17:40.07&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:17:40.07 (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="Build Service E2E" status="passed" time="0.168670866">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for parent component  - /workspace/source/e2e-tests/tests/renovate.go:358 @ 05/05/26 09:17:40.071&#xA;&lt; Exit [It] should lead to a PaC PR creation for parent component  - /workspace/source/e2e-tests/tests/renovate.go:358 @ 05/05/26 09:17:40.24 (168ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:17:40.24&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:17:40.24 (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="Build Service E2E" status="passed" time="2.136337197">
              <system-err>&gt; Enter [It] Merging the PaC PR should be successful for parent component  - /workspace/source/e2e-tests/tests/renovate.go:375 @ 05/05/26 09:17:40.241&#xA;merged result sha: 82f2b8d4bd752b28866ee924b797c0b3ca4b93bc for PR #1&#xA;&lt; Exit [It] Merging the PaC PR should be successful for parent component  - /workspace/source/e2e-tests/tests/renovate.go:375 @ 05/05/26 09:17:42.376 (2.136s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:17:42.377&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:17:42.377 (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="Build Service E2E" status="passed" time="20.178201737">
              <system-err>&gt; Enter [It] PR merge triggers PAC PipelineRun for parent component  - /workspace/source/e2e-tests/tests/renovate.go:385 @ 05/05/26 09:17:42.377&#xA;Push PipelineRun has not been created yet for the component build-e2e-npyc/gh-multi-component-parent-dniy&#xA;&lt; Exit [It] PR merge triggers PAC PipelineRun for parent component  - /workspace/source/e2e-tests/tests/renovate.go:385 @ 05/05/26 09:18:02.555 (20.178s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:18:02.555&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:18:02.555 (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="Build Service E2E" status="passed" time="280.172902727">
              <system-err>&gt; Enter [It] PAC PipelineRun for parent component  is successful - /workspace/source/e2e-tests/tests/renovate.go:401 @ 05/05/26 09:18:02.556&#xA;PipelineRun gh-multi-component-parent-dniy-on-push-p7xm8 found for Component build-e2e-npyc/gh-multi-component-parent-dniy&#xA;PipelineRun gh-multi-component-parent-dniy-on-push-p7xm8 reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-dniy-on-push-p7xm8 reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-dniy-on-push-p7xm8 reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-push-p7xm8 reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-push-p7xm8 reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-push-p7xm8 reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-push-p7xm8 reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-push-p7xm8 reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-push-p7xm8 reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-push-p7xm8 reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-push-p7xm8 reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-push-p7xm8 reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-push-p7xm8 reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-push-p7xm8 reason: Running&#xA;PipelineRun gh-multi-component-parent-dniy-on-push-p7xm8 reason: Completed&#xA;&lt; Exit [It] PAC PipelineRun for parent component  is successful - /workspace/source/e2e-tests/tests/renovate.go:401 @ 05/05/26 09:22:42.729 (4m40.173s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:22:42.729&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:22:42.729 (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="Build Service E2E" status="passed" time="263.959497431">
              <system-err>&gt; Enter [It] should lead to a nudge PR creation for child component  - /workspace/source/e2e-tests/tests/renovate.go:412 @ 05/05/26 09:22:42.73&#xA;&lt; Exit [It] should lead to a nudge PR creation for child component  - /workspace/source/e2e-tests/tests/renovate.go:412 @ 05/05/26 09:27:06.689 (4m23.959s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:27:06.689&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:27:06.689 (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="Build Service E2E" status="passed" time="2.132337343">
              <system-err>&gt; Enter [It] merging the PR should be successful for child component  - /workspace/source/e2e-tests/tests/renovate.go:429 @ 05/05/26 09:27:06.69&#xA;merged result sha: 31761e6f23c24ed19e6a9a9ef62bba687a80c9d8 for PR #3&#xA;&lt; Exit [It] merging the PR should be successful for child component  - /workspace/source/e2e-tests/tests/renovate.go:429 @ 05/05/26 09:27:08.821 (2.132s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:27:08.822&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:27:08.822 (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="Build Service E2E" status="passed" time="14.121679902">
              <system-err>&gt; Enter [It] Verify the nudge updated the contents - /workspace/source/e2e-tests/tests/renovate.go:440 @ 05/05/26 09:27:08.822&#xA;Verifying Dockerfile.tmp updated to sha sha256:6725e68b863f0db98534127e22f2a72df542db3508ee6f2cba55809dd9eaf064content: FROM quay.io/redhat-appstudio-qe/build-e2e-npyc/gh-multi-component-parent-dniy@sha256:6725e68b863f0db98534127e22f2a72df542db3508ee6f2cba55809dd9eaf064&#xA;RUN echo hello&#xA;&#xA;&lt; Exit [It] Verify the nudge updated the contents - /workspace/source/e2e-tests/tests/renovate.go:440 @ 05/05/26 09:27:09.016 (193ms)&#xA;&gt; Enter [AfterAll] component update with renovate - /workspace/source/e2e-tests/tests/renovate.go:214 @ 05/05/26 09:27:09.016&#xA;&lt; Exit [AfterAll] component update with renovate - /workspace/source/e2e-tests/tests/renovate.go:214 @ 05/05/26 09:27:22.944 (13.928s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:27:22.944&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/05/26 09:27:22.944 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace creates component with context directory go-component [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="13.350965084">
              <system-err>&gt; Enter [BeforeAll] test pac with multiple components using same repository - /workspace/source/e2e-tests/tests/multi_component.go:40 @ 05/05/26 09:09:25.941&#xA;&lt; Exit [BeforeAll] test pac with multiple components using same repository - /workspace/source/e2e-tests/tests/multi_component.go:40 @ 05/05/26 09:09:29.154 (3.214s)&#xA;&gt; Enter [It] creates component with context directory go-component - /workspace/source/e2e-tests/tests/multi_component.go:106 @ 05/05/26 09:09:29.155&#xA;Image repository for component go-component-rwmjui in namespace build-e2e-zpso 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 - /workspace/source/e2e-tests/tests/multi_component.go:106 @ 05/05/26 09:09:39.291 (10.136s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:09:39.291&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:09:39.291 (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-rwmjui [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="40.26399289">
              <system-err>&gt; Enter [It] triggers a PipelineRun for component go-component-rwmjui - /workspace/source/e2e-tests/tests/multi_component.go:125 @ 05/05/26 09:09:39.292&#xA;PipelineRun has not been created yet for the component build-e2e-zpso/go-component-rwmjui&#xA;PipelineRun has not been created yet for the component build-e2e-zpso/go-component-rwmjui&#xA;&lt; Exit [It] triggers a PipelineRun for component go-component-rwmjui - /workspace/source/e2e-tests/tests/multi_component.go:125 @ 05/05/26 09:10:19.556 (40.264s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:10:19.556&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:10:19.556 (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-rwmjui [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="0.416405282">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for component go-component-rwmjui - /workspace/source/e2e-tests/tests/multi_component.go:140 @ 05/05/26 09:10:19.557&#xA;&lt; Exit [It] should lead to a PaC PR creation for component go-component-rwmjui - /workspace/source/e2e-tests/tests/multi_component.go:140 @ 05/05/26 09:10:19.973 (416ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:10:19.973&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:10:19.973 (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-rwmjui [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="520.195680568">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for component go-component-rwmjui - /workspace/source/e2e-tests/tests/multi_component.go:159 @ 05/05/26 09:10:19.974&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 found for Component build-e2e-zpso/go-component-rwmjui&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Running&#xA;PipelineRun go-component-rwmjui-on-pull-request-srzj6 reason: Completed&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for component go-component-rwmjui - /workspace/source/e2e-tests/tests/multi_component.go:159 @ 05/05/26 09:19:00.169 (8m40.195s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:19:00.17&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:19:00.17 (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="Build Service E2E" status="passed" time="1.9655582759999999">
              <system-err>&gt; Enter [It] merging the PR should be successful - /workspace/source/e2e-tests/tests/multi_component.go:164 @ 05/05/26 09:19:00.171&#xA;merged result sha: b43fc749a046d07c9b0dad39ed10ab0679c09887 for PR #32866&#xA;&lt; Exit [It] merging the PR should be successful - /workspace/source/e2e-tests/tests/multi_component.go:164 @ 05/05/26 09:19:02.136 (1.965s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:19:02.136&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:19:02.136 (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="Build Service E2E" status="passed" time="20.199044622">
              <system-err>&gt; Enter [It] leads to triggering on push PipelineRun - /workspace/source/e2e-tests/tests/multi_component.go:174 @ 05/05/26 09:19:02.137&#xA;Push PipelineRun has not been created yet for the component build-e2e-zpso/go-component-rwmjui&#xA;&lt; Exit [It] leads to triggering on push PipelineRun - /workspace/source/e2e-tests/tests/multi_component.go:174 @ 05/05/26 09:19:22.336 (20.199s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:19:22.336&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:19:22.336 (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="Build Service E2E" status="passed" time="10.135774931">
              <system-err>&gt; Enter [It] creates component with context directory python-component - /workspace/source/e2e-tests/tests/multi_component.go:106 @ 05/05/26 09:19:22.336&#xA;Image repository for component python-component-eqheeb in namespace build-e2e-zpso 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 - /workspace/source/e2e-tests/tests/multi_component.go:106 @ 05/05/26 09:19:32.472 (10.135s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:19:32.472&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:19:32.472 (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-eqheeb [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="20.20160289">
              <system-err>&gt; Enter [It] triggers a PipelineRun for component python-component-eqheeb - /workspace/source/e2e-tests/tests/multi_component.go:125 @ 05/05/26 09:19:32.473&#xA;PipelineRun has not been created yet for the component build-e2e-zpso/python-component-eqheeb&#xA;&lt; Exit [It] triggers a PipelineRun for component python-component-eqheeb - /workspace/source/e2e-tests/tests/multi_component.go:125 @ 05/05/26 09:19:52.674 (20.201s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:19:52.674&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:19:52.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-eqheeb [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="0.347654031">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for component python-component-eqheeb - /workspace/source/e2e-tests/tests/multi_component.go:140 @ 05/05/26 09:19:52.675&#xA;&lt; Exit [It] should lead to a PaC PR creation for component python-component-eqheeb - /workspace/source/e2e-tests/tests/multi_component.go:140 @ 05/05/26 09:19:53.022 (347ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:19:53.022&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:19:53.022 (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-eqheeb [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="420.195846636">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for component python-component-eqheeb - /workspace/source/e2e-tests/tests/multi_component.go:159 @ 05/05/26 09:19:53.023&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 found for Component build-e2e-zpso/python-component-eqheeb&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: ResolvingTaskRef&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Running&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Running&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Running&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Running&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Running&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Running&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Running&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Running&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Running&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Running&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Running&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Running&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Running&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Running&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Running&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Running&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Running&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Running&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Running&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Running&#xA;PipelineRun python-component-eqheeb-on-pull-request-j6sb8 reason: Completed&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for component python-component-eqheeb - /workspace/source/e2e-tests/tests/multi_component.go:159 @ 05/05/26 09:26:53.218 (7m0.195s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:26:53.219&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:26:53.219 (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="Build Service E2E" status="passed" time="2.054382884">
              <system-err>&gt; Enter [It] merging the PR should be successful - /workspace/source/e2e-tests/tests/multi_component.go:164 @ 05/05/26 09:26:53.22&#xA;merged result sha: 7c828e7e064d5779d7b25b4c96ee39583ddf796d for PR #32868&#xA;&lt; Exit [It] merging the PR should be successful - /workspace/source/e2e-tests/tests/multi_component.go:164 @ 05/05/26 09:26:55.274 (2.054s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:26:55.274&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:26:55.274 (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="Build Service E2E" status="passed" time="20.203666656">
              <system-err>&gt; Enter [It] leads to triggering on push PipelineRun - /workspace/source/e2e-tests/tests/multi_component.go:174 @ 05/05/26 09:26:55.275&#xA;Push PipelineRun has not been created yet for the component build-e2e-zpso/python-component-eqheeb&#xA;&lt; Exit [It] leads to triggering on push PipelineRun - /workspace/source/e2e-tests/tests/multi_component.go:174 @ 05/05/26 09:27:15.478 (20.203s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:27:15.478&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:27:15.478 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace only one component is changed [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="3.432407745">
              <system-err>&gt; Enter [It] only one component is changed - /workspace/source/e2e-tests/tests/multi_component.go:190 @ 05/05/26 09:27:15.479&#xA;PR #32871 got created with sha 05fa231377bc9f91b5e40bb6c5aad716b9594f1d&#xA;&lt; Exit [It] only one component is changed - /workspace/source/e2e-tests/tests/multi_component.go:190 @ 05/05/26 09:27:18.911 (3.432s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:27:18.911&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:27:18.911 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace only related pipelinerun should be triggered [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="20.266233827">
              <system-err>&gt; Enter [It] only related pipelinerun should be triggered - /workspace/source/e2e-tests/tests/multi_component.go:205 @ 05/05/26 09:27:18.912&#xA;on pull PiplelineRun has not been created yet for the PR&#xA;&lt; Exit [It] only related pipelinerun should be triggered - /workspace/source/e2e-tests/tests/multi_component.go:205 @ 05/05/26 09:27:39.178 (20.266s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:27:39.178&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:27:39.178 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when a components is created with same git url in different namespace should fail to configure PaC for the component [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="19.329110978">
              <system-err>&gt; Enter [BeforeAll] when a components is created with same git url in different namespace - /workspace/source/e2e-tests/tests/multi_component.go:223 @ 05/05/26 09:27:39.179&#xA;Image repository for component go-component-ohinpt in namespace build-e2e-kdye do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [BeforeAll] when a components is created with same git url in different namespace - /workspace/source/e2e-tests/tests/multi_component.go:223 @ 05/05/26 09:27:50.573 (11.395s)&#xA;&gt; Enter [It] should fail to configure PaC for the component - /workspace/source/e2e-tests/tests/multi_component.go:264 @ 05/05/26 09:27:50.573&#xA;build status annotation value: {&#34;pac&#34;:{&#34;state&#34;:&#34;error&#34;,&#34;error-id&#34;:53,&#34;error-message&#34;:&#34;53: Git repository is already handled by Pipelines as Code&#34;},&#34;message&#34;:&#34;done&#34;}&#xA;build status: &amp;{State:error MergeUrl: ConfigurationTime: ErrorInfo:{ErrId:53 ErrMessage:53: Git repository is already handled by Pipelines as Code}}&#xA;&lt; Exit [It] should fail to configure PaC for the component - /workspace/source/e2e-tests/tests/multi_component.go:264 @ 05/05/26 09:27:50.639 (65ms)&#xA;&gt; Enter [AfterAll] when a components is created with same git url in different namespace - /workspace/source/e2e-tests/tests/multi_component.go:253 @ 05/05/26 09:27:50.639&#xA;&lt; Exit [AfterAll] when a components is created with same git url in different namespace - /workspace/source/e2e-tests/tests/multi_component.go:253 @ 05/05/26 09:27:50.97 (331ms)&#xA;&gt; Enter [AfterAll] test pac with multiple components using same repository - /workspace/source/e2e-tests/tests/multi_component.go:68 @ 05/05/26 09:27:50.97&#xA;&lt; Exit [AfterAll] test pac with multiple components using same repository - /workspace/source/e2e-tests/tests/multi_component.go:68 @ 05/05/26 09:27:58.507 (7.537s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:27:58.507&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/multi_component.go:28 @ 05/05/26 09:27:58.508 (0s)&#xA;</system-err>
          </testcase>
      </testsuite>
  </testsuites>