<?xml version="1.0" encoding="UTF-8"?>
  <testsuites tests="154" disabled="141" errors="0" failures="2" time="1916.229540066">
      <testsuite name="Build Service E2E" package="/workspace/source/e2e-tests/tests" tests="154" disabled="7" skipped="134" errors="0" failures="2" time="1916.229540066" timestamp="2026-05-04T14:51:25">
          <properties>
              <property name="SuiteSucceeded" value="false"></property>
              <property name="SuiteHasProgrammaticFocus" value="false"></property>
              <property name="SpecialSuiteFailureReason" value=""></property>
              <property name="SuiteLabels" value="[]"></property>
              <property name="SuiteSemVerConstraints" value="[]"></property>
              <property name="SuiteComponentSemVerConstraints" value="[]"></property>
              <property name="RandomSeed" value="1777906001"></property>
              <property name="RandomizeAllSpecs" value="false"></property>
              <property name="LabelFilter" value="build-service &amp;&amp; forgejo"></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 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 and recreated (with the same name in the same namespace) should no longer lead to a creation of a PaC PR [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="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 and recreated (with the same name in the same namespace) should no longer lead to a creation of a PaC PR [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="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="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created creates first component [build-service, github, pac-build, secret-lookup]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created creates second component [build-service, github, pac-build, secret-lookup]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created check first component annotation has errors [build-service, github, pac-build, secret-lookup]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created triggered PipelineRun is for component  [build-service, github, pac-build, secret-lookup]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created check only one pipelinerun should be triggered [build-service, github, pac-build, secret-lookup]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created when second component is deleted, pac pr branch should not exist in the repo [build-service, github, pac-build, secret-lookup]" classname="Build Service E2E" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace creates component with context directory go-component [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace triggers a PipelineRun for component go-component-mdvehf [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace should lead to a PaC PR creation for component go-component-mdvehf [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace the PipelineRun should eventually finish successfully for component go-component-mdvehf [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace merging the PR should be successful [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace leads to triggering on push PipelineRun [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace creates component with context directory python-component [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace triggers a PipelineRun for component python-component-vdxops [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace should lead to a PaC PR creation for component python-component-vdxops [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace the PipelineRun should eventually finish successfully for component python-component-vdxops [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace merging the PR should be successful [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace leads to triggering on push PipelineRun [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace only one component is changed [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace only related pipelinerun should be triggered [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when a components is created with same git url in different namespace should fail to configure PaC for the component [build-service, github, pac-build, multi-component]" classname="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="passed" time="41.124891326">
              <system-err>&gt; Enter [BeforeAll] component update with renovate - /workspace/source/e2e-tests/tests/renovate.go:72 @ 05/04/26 14:51:25.333&#xA;ReleaseAdmissionPlan data: {&#34;Mapping&#34;:{&#34;Components&#34;:[{&#34;Name&#34;:&#34;fj-multi-component-parent-izli&#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/04/26 14:51:46.209 (20.876s)&#xA;&gt; Enter [It] creates component with nudges - /workspace/source/e2e-tests/tests/renovate.go:235 @ 05/04/26 14:51:46.21&#xA;Image repository for component fj-multi-component-child-izli in namespace build-e2e-vnss do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component fj-multi-component-parent-izli in namespace build-e2e-vnss 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/04/26 14:52:06.458 (20.248s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/04/26 14:52:06.458&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/04/26 14:52:06.458 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace triggers a PipelineRun for parent component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="failed" time="1806.931594415">
              <failure message="Timed out after 1800.001s.&#xA;timed out when waiting for the PipelineRun to start for the component fj-multi-component-parent-izli/build-e2e-vnss&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc0009ae100&gt;: &#xA;    no pipelinerun found for component fj-multi-component-parent-izli&#xA;    {&#xA;        s: &#34;no pipelinerun found for component fj-multi-component-parent-izli&#34;,&#xA;    }" type="failed">[FAILED] Timed out after 1800.001s.&#xA;timed out when waiting for the PipelineRun to start for the component fj-multi-component-parent-izli/build-e2e-vnss&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc0009ae100&gt;: &#xA;    no pipelinerun found for component fj-multi-component-parent-izli&#xA;    {&#xA;        s: &#34;no pipelinerun found for component fj-multi-component-parent-izli&#34;,&#xA;    }&#xA;In [It] at: /workspace/source/e2e-tests/tests/renovate.go:272 @ 05/04/26 15:22:06.46&#xA;</failure>
              <system-err>&gt; Enter [It] triggers a PipelineRun for parent component  - /workspace/source/e2e-tests/tests/renovate.go:259 @ 05/04/26 14:52:06.459&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;PipelineRun has not been created yet for the component build-e2e-vnss/fj-multi-component-parent-izli&#xA;[FAILED] Timed out after 1800.001s.&#xA;timed out when waiting for the PipelineRun to start for the component fj-multi-component-parent-izli/build-e2e-vnss&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc0009ae100&gt;: &#xA;    no pipelinerun found for component fj-multi-component-parent-izli&#xA;    {&#xA;        s: &#34;no pipelinerun found for component fj-multi-component-parent-izli&#34;,&#xA;    }&#xA;In [It] at: /workspace/source/e2e-tests/tests/renovate.go:272 @ 05/04/26 15:22:06.46&#xA;&lt; Exit [It] triggers a PipelineRun for parent component  - /workspace/source/e2e-tests/tests/renovate.go:259 @ 05/04/26 15:22:06.46 (30m0.001s)&#xA;&gt; Enter [AfterAll] component update with renovate - /workspace/source/e2e-tests/tests/renovate.go:214 @ 05/04/26 15:22:06.46&#xA;&lt; Exit [AfterAll] component update with renovate - /workspace/source/e2e-tests/tests/renovate.go:214 @ 05/04/26 15:22:12.661 (6.201s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/04/26 15:22:12.661&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/renovate.go:28 @ 05/04/26 15:22:13.39 (729ms)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for parent component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/renovate.go:274 @ 05/04/26 15:22:13.391&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for child component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/renovate.go:285 @ 05/04/26 15:22:13.391&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace should lead to a PaC PR creation for child component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/renovate.go:289 @ 05/04/26 15:22:13.392&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace Merging the PaC PR should be successful for child component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/renovate.go:307 @ 05/04/26 15:22:13.392&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace create dockerfile and yaml manifest that references build and distribution repositories [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/renovate.go:318 @ 05/04/26 15:22:13.392&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace should lead to a PaC PR creation for parent component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/renovate.go:358 @ 05/04/26 15:22:13.393&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace Merging the PaC PR should be successful for parent component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/renovate.go:375 @ 05/04/26 15:22:13.393&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace PR merge triggers PAC PipelineRun for parent component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/renovate.go:385 @ 05/04/26 15:22:13.393&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace PAC PipelineRun for parent component  is successful [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/renovate.go:401 @ 05/04/26 15:22:13.393&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace should lead to a nudge PR creation for child component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/renovate.go:412 @ 05/04/26 15:22:13.394&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace merging the PR should be successful for child component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/renovate.go:429 @ 05/04/26 15:22:13.394&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace Verify the nudge updated the contents [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/renovate.go:440 @ 05/04/26 15:22:13.394&#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="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace triggers a PipelineRun for parent component  [build-service, renovate, multi-component, github]" classname="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 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="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for child component  [build-service, renovate, multi-component, github]" classname="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 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="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace Merging the PaC PR should be successful for child component  [build-service, renovate, multi-component, github]" classname="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 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="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace should lead to a PaC PR creation for parent component  [build-service, renovate, multi-component, github]" classname="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 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="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace PR merge triggers PAC PipelineRun for parent component  [build-service, renovate, multi-component, github]" classname="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 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="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace should lead to a nudge PR creation for child component  [build-service, renovate, multi-component, github]" classname="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 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="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace Verify the nudge updated the contents [build-service, renovate, multi-component, github]" classname="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 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="passed" time="32.993213783">
              <system-err>&gt; Enter [BeforeAll] PaC component build - /workspace/source/e2e-tests/tests/pac_build.go:56 @ 05/04/26 14:51:25.252&#xA;&lt; Exit [BeforeAll] PaC component build - /workspace/source/e2e-tests/tests/pac_build.go:56 @ 05/04/26 14:51:37.358 (12.107s)&#xA;&gt; Enter [BeforeAll] when a new component without specified branch is created and with visibility private - /workspace/source/e2e-tests/tests/pac_build.go:118 @ 05/04/26 14:51:37.368&#xA;Image repository for component fj-test-custom-default-reccpf in namespace build-e2e-fomu do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [BeforeAll] when a new component without specified branch is created and with visibility private - /workspace/source/e2e-tests/tests/pac_build.go:118 @ 05/04/26 14:51:47.494 (10.127s)&#xA;&gt; Enter [It] correctly targets the default branch (that is not named &#39;main&#39;) with PaC - /workspace/source/e2e-tests/tests/pac_build.go:137 @ 05/04/26 14:51:47.494&#xA;&lt; Exit [It] correctly targets the default branch (that is not named &#39;main&#39;) with PaC - /workspace/source/e2e-tests/tests/pac_build.go:137 @ 05/04/26 14:51:58.245 (10.75s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 14:51:58.245&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 14:51:58.245 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private workspace parameter is set correctly in PaC repository CR [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="passed" time="0.116246294">
              <system-err>&gt; Enter [It] workspace parameter is set correctly in PaC repository CR - /workspace/source/e2e-tests/tests/pac_build.go:154 @ 05/04/26 14:51:58.246&#xA;&lt; Exit [It] workspace parameter is set correctly in PaC repository CR - /workspace/source/e2e-tests/tests/pac_build.go:154 @ 05/04/26 14:51:58.361 (116ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 14:51:58.362&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 14:51:58.362 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="passed" time="20.656129196">
              <system-err>&gt; Enter [It] triggers a PipelineRun - /workspace/source/e2e-tests/tests/pac_build.go:176 @ 05/04/26 14:51:58.362&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;&lt; Exit [It] triggers a PipelineRun - /workspace/source/e2e-tests/tests/pac_build.go:176 @ 05/04/26 14:52:19.018 (20.656s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 14:52:19.018&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 14:52:19.018 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private build pipeline uses the correct serviceAccount [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="passed" time="0.00032073">
              <system-err>&gt; Enter [It] build pipeline uses the correct serviceAccount - /workspace/source/e2e-tests/tests/pac_build.go:191 @ 05/04/26 14:52:19.019&#xA;&lt; Exit [It] build pipeline uses the correct serviceAccount - /workspace/source/e2e-tests/tests/pac_build.go:191 @ 05/04/26 14:52:19.019 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 14:52:19.019&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 14:52:19.019 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private component build status is set correctly [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="passed" time="0.058048067">
              <system-err>&gt; Enter [It] component build status is set correctly - /workspace/source/e2e-tests/tests/pac_build.go:195 @ 05/04/26 14:52:19.02&#xA;build status annotation value: {&#34;pac&#34;:{&#34;state&#34;:&#34;enabled&#34;,&#34;merge-url&#34;:&#34;https://codeberg.org/konflux-qe/devfile-sample-hello-world-sgriuk/pulls/1&#34;,&#34;configuration-time&#34;:&#34;Mon, 04 May 2026 14:51:59 UTC&#34;},&#34;message&#34;:&#34;done&#34;}&#xA;state: enabled&#xA;mergeUrl: https://codeberg.org/konflux-qe/devfile-sample-hello-world-sgriuk/pulls/1&#xA;errId: 0&#xA;errMessage: &#xA;configurationTime: Mon, 04 May 2026 14:51:59 UTC&#xA;&lt; Exit [It] component build status is set correctly - /workspace/source/e2e-tests/tests/pac_build.go:195 @ 05/04/26 14:52:19.077 (58ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 14:52:19.078&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 14:52:19.078 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="passed" time="1.011377028">
              <system-err>&gt; Enter [It] image repo and robot account created successfully - /workspace/source/e2e-tests/tests/pac_build.go:225 @ 05/04/26 14:52:19.078&#xA;&lt; Exit [It] image repo and robot account created successfully - /workspace/source/e2e-tests/tests/pac_build.go:225 @ 05/04/26 14:52:20.089 (1.011s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 14:52:20.09&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 14:52:20.09 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private created image repo is private [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="passed" time="0.28596111">
              <system-err>&gt; Enter [It] created image repo is private - /workspace/source/e2e-tests/tests/pac_build.go:243 @ 05/04/26 14:52:20.09&#xA;&lt; Exit [It] created image repo is private - /workspace/source/e2e-tests/tests/pac_build.go:243 @ 05/04/26 14:52:20.376 (286ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 14:52:20.376&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 14:52:20.376 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private a related PipelineRun should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="passed" time="44.85542857">
              <system-err>&gt; Enter [It] a related PipelineRun should be deleted after deleting the component - /workspace/source/e2e-tests/tests/pac_build.go:249 @ 05/04/26 14:52:20.377&#xA;&lt; Exit [It] a related PipelineRun should be deleted after deleting the component - /workspace/source/e2e-tests/tests/pac_build.go:249 @ 05/04/26 14:53:05.232 (44.855s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 14:53:05.232&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 14:53:05.232 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private PR branch should not exist in the repo [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="passed" time="0.259289614">
              <system-err>&gt; Enter [It] PR branch should not exist in the repo - /workspace/source/e2e-tests/tests/pac_build.go:264 @ 05/04/26 14:53:05.235&#xA;&lt; Exit [It] PR branch should not exist in the repo - /workspace/source/e2e-tests/tests/pac_build.go:264 @ 05/04/26 14:53:05.493 (259ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 14:53:05.494&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 14:53:05.494 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private related image repo and the robot account should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="passed" time="0.853961871">
              <system-err>&gt; Enter [It] related image repo and the robot account should be deleted after deleting the component - /workspace/source/e2e-tests/tests/pac_build.go:277 @ 05/04/26 14:53:05.494&#xA;&lt; Exit [It] related image repo and the robot account should be deleted after deleting the component - /workspace/source/e2e-tests/tests/pac_build.go:277 @ 05/04/26 14:53:06.348 (854ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 14:53:06.348&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 14:53:06.348 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="failed" time="1815.112146772">
              <failure message="Timed out after 1800.001s.&#xA;timed out when waiting for the PipelineRun to start for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc0006fca00&gt;: &#xA;    no pipelinerun found for component fj-test-custom-branch-ivbkrx&#xA;    {&#xA;        s: &#34;no pipelinerun found for component fj-test-custom-branch-ivbkrx&#34;,&#xA;    }" type="failed">[FAILED] Timed out after 1800.001s.&#xA;timed out when waiting for the PipelineRun to start for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc0006fca00&gt;: &#xA;    no pipelinerun found for component fj-test-custom-branch-ivbkrx&#xA;    {&#xA;        s: &#34;no pipelinerun found for component fj-test-custom-branch-ivbkrx&#34;,&#xA;    }&#xA;In [It] at: /workspace/source/e2e-tests/tests/pac_build.go:340 @ 05/04/26 15:23:18.662&#xA;</failure>
              <system-err>&gt; Enter [BeforeAll] when a new Component with specified custom branch is created - /workspace/source/e2e-tests/tests/pac_build.go:303 @ 05/04/26 14:53:06.349&#xA;Image repository for component fj-test-custom-branch-ivbkrx in namespace build-e2e-fomu do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [BeforeAll] when a new Component with specified custom branch is created - /workspace/source/e2e-tests/tests/pac_build.go:303 @ 05/04/26 14:53:18.66 (12.311s)&#xA;&gt; Enter [It] triggers a PipelineRun - /workspace/source/e2e-tests/tests/pac_build.go:327 @ 05/04/26 14:53:18.66&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;PipelineRun has not been created yet for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;[FAILED] Timed out after 1800.001s.&#xA;timed out when waiting for the PipelineRun to start for the component build-e2e-fomu/fj-test-custom-branch-ivbkrx&#xA;Expected success, but got an error:&#xA;    &lt;*errors.errorString | 0xc0006fca00&gt;: &#xA;    no pipelinerun found for component fj-test-custom-branch-ivbkrx&#xA;    {&#xA;        s: &#34;no pipelinerun found for component fj-test-custom-branch-ivbkrx&#34;,&#xA;    }&#xA;In [It] at: /workspace/source/e2e-tests/tests/pac_build.go:340 @ 05/04/26 15:23:18.662&#xA;&lt; Exit [It] triggers a PipelineRun - /workspace/source/e2e-tests/tests/pac_build.go:327 @ 05/04/26 15:23:18.662 (30m0.001s)&#xA;&gt; Enter [AfterAll] when a new Component with specified custom branch is created - /workspace/source/e2e-tests/tests/pac_build.go:320 @ 05/04/26 15:23:18.662&#xA;&lt; Exit [AfterAll] when a new Component with specified custom branch is created - /workspace/source/e2e-tests/tests/pac_build.go:320 @ 05/04/26 15:23:19.231 (570ms)&#xA;&gt; Enter [AfterAll] PaC component build - /workspace/source/e2e-tests/tests/pac_build.go:102 @ 05/04/26 15:23:19.232&#xA;&lt; Exit [AfterAll] PaC component build - /workspace/source/e2e-tests/tests/pac_build.go:102 @ 05/04/26 15:23:19.232 (0s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 15:23:19.232&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/e2e-tests/tests/pac_build.go:30 @ 05/04/26 15:23:21.461 (2.229s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created should lead to a PaC init PR creation [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/pac_build.go:342 @ 05/04/26 15:23:21.462&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/pac_build.go:360 @ 05/04/26 15:23:21.462&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/pac_build.go:365 @ 05/04/26 15:23:21.462&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created created image repo is public [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/pac_build.go:384 @ 05/04/26 15:23:21.462&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created image tag is updated successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/pac_build.go:390 @ 05/04/26 15:23:21.463&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created should ensure pruning labels are set [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/pac_build.go:416 @ 05/04/26 15:23:21.463&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created eventually leads to the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/pac_build.go:433 @ 05/04/26 15:23:21.463&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/pac_build.go:458 @ 05/04/26 15:23:21.464&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated should lead to a PaC init PR update [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/pac_build.go:473 @ 05/04/26 15:23:21.464&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated PipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/pac_build.go:492 @ 05/04/26 15:23:21.464&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated eventually leads to another update of a PR about the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/pac_build.go:497 @ 05/04/26 15:23:21.464&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/pac_build.go:523 @ 05/04/26 15:23:21.465&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/pac_build.go:539 @ 05/04/26 15:23:21.465&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged does not have expiration set [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/pac_build.go:545 @ 05/04/26 15:23:21.465&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged After updating image visibility to private, it should not trigger another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/pac_build.go:560 @ 05/04/26 15:23:21.465&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged image repo is updated to private [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/pac_build.go:590 @ 05/04/26 15:23:21.466&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged retrigger the pipeline manually [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="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 and recreated (with the same name in the same namespace) should no longer lead to a creation of a PaC PR [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped - Spec skipped because an earlier spec in an ordered container failed"></skipped>
              <system-err>[SKIPPED] Spec skipped because an earlier spec in an ordered container failed&#xA;In [It] at: /workspace/source/e2e-tests/tests/pac_build.go:701 @ 05/04/26 15:23:21.466&#xA;</system-err>
          </testcase>
      </testsuite>
  </testsuites>