<?xml version="1.0" encoding="UTF-8"?>
  <testsuites tests="461" disabled="340" errors="0" failures="0" time="1901.082036209">
      <testsuite name="Red Hat App Studio E2E tests" package="/tmp/tmp.YkUEHMxtIX/cmd" tests="461" disabled="88" skipped="252" errors="0" failures="0" time="1901.082036209" timestamp="2026-04-21T16:53:41">
          <properties>
              <property name="SuiteSucceeded" value="true"></property>
              <property name="SuiteHasProgrammaticFocus" value="false"></property>
              <property name="SpecialSuiteFailureReason" value=""></property>
              <property name="SuiteLabels" value="[]"></property>
              <property name="SuiteSemVerConstraints" value="[]"></property>
              <property name="RandomSeed" value="1776790278"></property>
              <property name="RandomizeAllSpecs" value="false"></property>
              <property name="LabelFilter" value="integration-service"></property>
              <property name="SemVerFilter" value=""></property>
              <property name="FocusStrings" value=""></property>
              <property name="SkipStrings" value=""></property>
              <property name="FocusFiles" value=""></property>
              <property name="SkipFiles" value=""></property>
              <property name="FailOnPending" value="false"></property>
              <property name="FailOnEmpty" value="false"></property>
              <property name="FailFast" value="false"></property>
              <property name="FlakeAttempts" value="0"></property>
              <property name="DryRun" value="false"></property>
              <property name="ParallelTotal" value="20"></property>
              <property name="OutputInterceptorMode" value="none"></property>
          </properties>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] infrastructure is running verifies if the chains controller is running [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] infrastructure is running verifies the signing secret is present [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task creates signature and attestation [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task succeeds when policy is met [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task does not pass when tests are not satisfied on non-strict mode [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task fails when tests are not satisfied on strict mode [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task fails when unexpected signature is used [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task ec-cli command verifies ec cli has error handling [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task ec-cli command verifies ec validate accepts a list of image references [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task Release Policy verifies redhat products pass the redhat policy rule collection before release  [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task Release Policy verifies the release policy: Task are trusted [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task Release Policy verifies the release policy: Task references are pinned [ec, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC happy path Post-release verification creates component from git source https://github.com/redhat-appstudio-qe/fbc-sample-repo-test [release-pipelines, fbc-release, fbcHappyPath]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC happy path Post-release verification Creates a push snapshot for a release [release-pipelines, fbc-release, fbcHappyPath]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC happy path Post-release verification verifies the fbc release pipelinerun is running and succeeds [release-pipelines, fbc-release, fbcHappyPath]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC happy path Post-release verification verifies release CR completed and set succeeded. [release-pipelines, fbc-release, fbcHappyPath]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC Staged Index Post-release verification creates component from git source https://github.com/redhat-appstudio-qe/fbc-sample-repo-test [release-pipelines, fbc-release, fbcStagedIndex]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC Staged Index Post-release verification Creates a push snapshot for a release [release-pipelines, fbc-release, fbcStagedIndex]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC Staged Index Post-release verification verifies the fbc release pipelinerun is running and succeeds [release-pipelines, fbc-release, fbcStagedIndex]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC Staged Index Post-release verification verifies release CR completed and set succeeded. [release-pipelines, fbc-release, fbcStagedIndex]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC hotfix process FBC hotfix post-release verification creates component from git source https://github.com/redhat-appstudio-qe/fbc-sample-repo-test [release-pipelines, fbc-release, fbcHotfix]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC hotfix process FBC hotfix post-release verification Creates a push snapshot for a release [release-pipelines, fbc-release, fbcHotfix]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC hotfix process FBC hotfix post-release verification verifies the fbc release pipelinerun is running and succeeds [release-pipelines, fbc-release, fbcHotfix]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC hotfix process FBC hotfix post-release verification verifies release CR completed and set succeeded. [release-pipelines, fbc-release, fbcHotfix]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC pre-GA process FBC pre-GA post-release verification creates component from git source https://github.com/redhat-appstudio-qe/fbc-sample-repo-test [release-pipelines, fbc-release, fbcPreGA]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC pre-GA process FBC pre-GA post-release verification Creates a push snapshot for a release [release-pipelines, fbc-release, fbcPreGA]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC pre-GA process FBC pre-GA post-release verification verifies the fbc release pipelinerun is running and succeeds [release-pipelines, fbc-release, fbcPreGA]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite FBC e2e-tests] with FBC pre-GA process FBC pre-GA post-release verification verifies release CR completed and set succeeded. [release-pipelines, fbc-release, fbcPreGA]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite [RELEASE-2136] Release CR fails when block-releases true in ReleasePlanAdmission.] post-release verification. block-releases true in ReleasePlanAdmission makes a Release CR set as failed in both IsReleased and IsValid with a proper message to user. [release-service, release-neg, negBlockReleases]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [upgrade-suite Create users and check their state] Verify AppStudioProvisionedUser [upgrade-verify]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [upgrade-suite Create users and check their state] creates AppStudioDeactivatedUser [upgrade-verify]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [upgrade-suite Create users and check their state] creates AppStudioBannedUser [upgrade-verify]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite Release service tenant pipeline] Post-release verification verifies that a Release CR should have been created in the dev namespace [release-service, tenant]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite Release service tenant pipeline] Post-release verification verifies that Tenant PipelineRun is triggered [release-service, tenant]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite Release service tenant pipeline] Post-release verification verifies that a Release is marked as succeeded. [release-service, tenant]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component A creates the Component A successfully [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="23.544128916">
              <system-err>&gt; Enter [BeforeAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:60 @ 04/21/26 16:53:42.582&#xA;Successfully acquired repository lock for namespace group-yugp&#xA;&lt; Exit [BeforeAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:60 @ 04/21/26 16:53:45.982 (3.401s)&#xA;&gt; Enter [It] creates the Component A successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:205 @ 04/21/26 16:53:45.982&#xA;Image repository for component go-component-lhcrru in namespace group-yugp do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component go-component-lhcrru in namespace group-yugp do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [It] creates the Component A successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:205 @ 04/21/26 16:54:06.124 (20.142s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 16:54:06.125&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 16:54:06.125 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component A triggers a Build PipelineRun for componentA go-component [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="40.279885034">
              <system-err>&gt; Enter [It] triggers a Build PipelineRun for componentA go-component - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:213 @ 04/21/26 16:54:06.125&#xA;Build PipelineRun has not been created yet for the componentA group-yugp/go-component-lhcrru&#xA;Build PipelineRun has not been created yet for the componentA group-yugp/go-component-lhcrru&#xA;&lt; Exit [It] triggers a Build PipelineRun for componentA go-component - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:213 @ 04/21/26 16:54:46.405 (40.279s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 16:54:46.405&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 16:54:46.405 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component A does not contain an annotation with a Snapshot Name [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.000342979">
              <system-err>&gt; Enter [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:227 @ 04/21/26 16:54:46.405&#xA;&lt; Exit [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:227 @ 04/21/26 16:54:46.406 (0s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 16:54:46.406&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 16:54:46.406 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component A should lead to build PipelineRunA finishing successfully [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="540.205017706">
              <system-err>&gt; Enter [It] should lead to build PipelineRunA finishing successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:231 @ 04/21/26 16:54:46.406&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 found for Component group-yugp/go-component-lhcrru&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: ResolvingTaskRef&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: ResolvingTaskRef&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Running&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Completed&#xA;&lt; Exit [It] should lead to build PipelineRunA finishing successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:231 @ 04/21/26 17:03:46.611 (9m0.205s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:03:46.611&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:03:46.611 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component A should lead to a PaC PR creation for componentA go-component [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.556304993">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for componentA go-component - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:236 @ 04/21/26 17:03:46.612&#xA;&lt; Exit [It] should lead to a PaC PR creation for componentA go-component - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:236 @ 04/21/26 17:03:47.167 (556ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:03:47.168&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:03:47.168 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Build PLRA is finished successfully checks if the Snapshot is created [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.068822529">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:258 @ 04/21/26 17:03:47.168&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:258 @ 04/21/26 17:03:47.237 (69ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:03:47.237&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:03:47.237 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Build PLRA is finished successfully should find the related Integration PipelineRuns [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.068865841">
              <system-err>&gt; Enter [It] should find the related Integration PipelineRuns - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:263 @ 04/21/26 17:03:47.237&#xA;&lt; Exit [It] should find the related Integration PipelineRuns - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:263 @ 04/21/26 17:03:47.306 (69ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:03:47.306&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:03:47.306 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Build PLRA is finished successfully integration pipeline should end up with success [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="20.136928138">
              <system-err>&gt; Enter [It] integration pipeline should end up with success - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:270 @ 04/21/26 17:03:47.306&#xA;PipelineRun integration-resolver-pipelinerun-5ffrr reason: Running&#xA;PipelineRun integration-resolver-pipelinerun-5ffrr reason: Succeeded&#xA;&lt; Exit [It] integration pipeline should end up with success - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:270 @ 04/21/26 17:04:07.443 (20.137s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:04:07.443&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:04:07.443 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Snapshot testing is completed successfully should merge the init PaC PR successfully [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="1.845143803">
              <system-err>&gt; Enter [It] should merge the init PaC PR successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:277 @ 04/21/26 17:04:07.444&#xA;merged result sha: 62081ecaff925d99e3cbecb435af286ab75ad636 for PR #21207&#xA;&lt; Exit [It] should merge the init PaC PR successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:277 @ 04/21/26 17:04:09.288 (1.845s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:04:09.289&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:04:09.289 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component B creates the Component B successfully [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="10.140919106">
              <system-err>&gt; Enter [It] creates the Component B successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:296 @ 04/21/26 17:04:09.289&#xA;Image repository for component python-component-gguptr in namespace group-yugp do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [It] creates the Component B successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:296 @ 04/21/26 17:04:19.43 (10.141s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:04:19.43&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:04:19.43 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component B triggers a Build PipelineRun for component python-component [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="20.206491804">
              <system-err>&gt; Enter [It] triggers a Build PipelineRun for component python-component - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:304 @ 04/21/26 17:04:19.43&#xA;Build PipelineRun has not been created yet for the componentB group-yugp/python-component-gguptr&#xA;&lt; Exit [It] triggers a Build PipelineRun for component python-component - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:304 @ 04/21/26 17:04:39.637 (20.206s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:04:39.637&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:04:39.637 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component B does not contain an annotation with a Snapshot Name [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.000309908">
              <system-err>&gt; Enter [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:318 @ 04/21/26 17:04:39.637&#xA;&lt; Exit [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:318 @ 04/21/26 17:04:39.637 (0s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:04:39.637&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:04:39.638 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component B should lead to build PipelineRun finishing successfully [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="320.205611508">
              <system-err>&gt; Enter [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:322 @ 04/21/26 17:04:39.638&#xA;PipelineRun python-component-gguptr-on-pull-request-xgp5s found for Component group-yugp/python-component-gguptr&#xA;PipelineRun python-component-gguptr-on-pull-request-xgp5s reason: ResolvingTaskRef&#xA;PipelineRun python-component-gguptr-on-pull-request-xgp5s reason: ResolvingTaskRef&#xA;PipelineRun python-component-gguptr-on-pull-request-xgp5s reason: Running&#xA;PipelineRun python-component-gguptr-on-pull-request-xgp5s reason: Running&#xA;PipelineRun python-component-gguptr-on-pull-request-xgp5s reason: Running&#xA;PipelineRun python-component-gguptr-on-pull-request-xgp5s reason: Running&#xA;PipelineRun python-component-gguptr-on-pull-request-xgp5s reason: Running&#xA;PipelineRun python-component-gguptr-on-pull-request-xgp5s reason: Running&#xA;PipelineRun python-component-gguptr-on-pull-request-xgp5s reason: Running&#xA;PipelineRun python-component-gguptr-on-pull-request-xgp5s reason: Running&#xA;PipelineRun python-component-gguptr-on-pull-request-xgp5s reason: Running&#xA;PipelineRun python-component-gguptr-on-pull-request-xgp5s reason: Running&#xA;PipelineRun python-component-gguptr-on-pull-request-xgp5s reason: Running&#xA;PipelineRun python-component-gguptr-on-pull-request-xgp5s reason: Running&#xA;PipelineRun python-component-gguptr-on-pull-request-xgp5s reason: Running&#xA;PipelineRun integration-resolver-pipelinerun-87k82 reason: Running&#xA;PipelineRun integration-resolver-pipelinerun-87k82 reason: Succeeded&#xA;&lt; Exit [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:322 @ 04/21/26 17:09:59.843 (5m20.205s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:09:59.843&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:09:59.843 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component B should lead to a PaC PR creation for component python-component [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.455015604">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for component python-component - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:327 @ 04/21/26 17:09:59.844&#xA;&lt; Exit [It] should lead to a PaC PR creation for component python-component - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:327 @ 04/21/26 17:10:00.299 (455ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:10:00.299&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:10:00.299 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Build PLR is finished successfully checks if the Snapshot is created [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.069972423">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:349 @ 04/21/26 17:10:00.299&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:349 @ 04/21/26 17:10:00.369 (70ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:10:00.369&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:10:00.369 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Build PLR is finished successfully should find the related Integration PipelineRuns [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.069777388">
              <system-err>&gt; Enter [It] should find the related Integration PipelineRuns - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:354 @ 04/21/26 17:10:00.37&#xA;&lt; Exit [It] should find the related Integration PipelineRuns - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:354 @ 04/21/26 17:10:00.439 (69ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:10:00.439&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:10:00.439 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Build PLR is finished successfully integration pipeline should end up with success [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.069752257">
              <system-err>&gt; Enter [It] integration pipeline should end up with success - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:361 @ 04/21/26 17:10:00.44&#xA;PipelineRun integration-resolver-pipelinerun-87k82 reason: Succeeded&#xA;&lt; Exit [It] integration pipeline should end up with success - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:361 @ 04/21/26 17:10:00.509 (69ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:10:00.509&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:10:00.509 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Snapshot testing is completed successfully should merge the init PaC PR successfully [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="1.867685676">
              <system-err>&gt; Enter [It] should merge the init PaC PR successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:368 @ 04/21/26 17:10:00.51&#xA;merged result sha: b94856ee23a4540383a75d3717db4f977f194f5a for PR #21210&#xA;&lt; Exit [It] should merge the init PaC PR successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:368 @ 04/21/26 17:10:02.377 (1.867s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:10:02.377&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:10:02.377 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component C creates the Component C successfully [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="10.140521307">
              <system-err>&gt; Enter [It] creates the Component C successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:387 @ 04/21/26 17:10:02.378&#xA;Image repository for component konflux-test-integration-clone-coxbuu in namespace group-yugp do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [It] creates the Component C successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:387 @ 04/21/26 17:10:12.518 (10.14s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:10:12.518&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:10:12.519 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component C triggers a Build PipelineRun for componentC konflux-test-integration-clone [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="20.206220516">
              <system-err>&gt; Enter [It] triggers a Build PipelineRun for componentC konflux-test-integration-clone - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:395 @ 04/21/26 17:10:12.519&#xA;Build PipelineRun has not been created yet for the componentC group-yugp/konflux-test-integration-clone-coxbuu&#xA;&lt; Exit [It] triggers a Build PipelineRun for componentC konflux-test-integration-clone - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:395 @ 04/21/26 17:10:32.725 (20.206s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:10:32.725&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:10:32.725 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component C does not contain an annotation with a Snapshot Name [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.000368079">
              <system-err>&gt; Enter [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:409 @ 04/21/26 17:10:32.726&#xA;&lt; Exit [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:409 @ 04/21/26 17:10:32.726 (0s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:10:32.726&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:10:32.726 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component C should lead to build PipelineRun finishing successfully [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="200.209800778">
              <system-err>&gt; Enter [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:413 @ 04/21/26 17:10:32.727&#xA;PipelineRun konflux-test-integration-clone-coxbuu-on-pull-request-v4ss4 found for Component group-yugp/konflux-test-integration-clone-coxbuu&#xA;PipelineRun konflux-test-integration-clone-coxbuu-on-pull-request-v4ss4 reason: ResolvingTaskRef&#xA;PipelineRun konflux-test-integration-clone-coxbuu-on-pull-request-v4ss4 reason: Running&#xA;PipelineRun konflux-test-integration-clone-coxbuu-on-pull-request-v4ss4 reason: Running&#xA;PipelineRun konflux-test-integration-clone-coxbuu-on-pull-request-v4ss4 reason: Running&#xA;PipelineRun konflux-test-integration-clone-coxbuu-on-pull-request-v4ss4 reason: Running&#xA;PipelineRun konflux-test-integration-clone-coxbuu-on-pull-request-v4ss4 reason: Running&#xA;PipelineRun konflux-test-integration-clone-coxbuu-on-pull-request-v4ss4 reason: Running&#xA;PipelineRun konflux-test-integration-clone-coxbuu-on-pull-request-v4ss4 reason: Running&#xA;PipelineRun konflux-test-integration-clone-coxbuu-on-pull-request-v4ss4 reason: Running&#xA;PipelineRun konflux-test-integration-clone-coxbuu-on-pull-request-v4ss4 reason: Running&#xA;PipelineRun integration-resolver-pipelinerun-lx5mf reason: Succeeded&#xA;&lt; Exit [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:413 @ 04/21/26 17:13:52.936 (3m20.209s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:13:52.936&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:13:52.936 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component C should lead to a PaC PR creation for componentC konflux-test-integration-clone [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.485369101">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for componentC konflux-test-integration-clone - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:418 @ 04/21/26 17:13:52.937&#xA;&lt; Exit [It] should lead to a PaC PR creation for componentC konflux-test-integration-clone - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:418 @ 04/21/26 17:13:53.422 (485ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:13:53.422&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:13:53.422 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Build PLR is finished successfully checks if the Snapshot is created [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.070158344">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:440 @ 04/21/26 17:13:53.423&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:440 @ 04/21/26 17:13:53.492 (70ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:13:53.493&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:13:53.493 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Build PLR is finished successfully should find the related Integration PipelineRuns [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.069508867">
              <system-err>&gt; Enter [It] should find the related Integration PipelineRuns - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:445 @ 04/21/26 17:13:53.493&#xA;&lt; Exit [It] should find the related Integration PipelineRuns - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:445 @ 04/21/26 17:13:53.562 (69ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:13:53.563&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:13:53.563 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Build PLR is finished successfully integration pipeline should end up with success [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.069625701">
              <system-err>&gt; Enter [It] integration pipeline should end up with success - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:452 @ 04/21/26 17:13:53.563&#xA;PipelineRun integration-resolver-pipelinerun-lx5mf reason: Succeeded&#xA;&lt; Exit [It] integration pipeline should end up with success - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:452 @ 04/21/26 17:13:53.632 (69ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:13:53.633&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:13:53.633 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when the Snapshot testing is completed successfully should merge the init PaC PR successfully [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="2.530222201">
              <system-err>&gt; Enter [It] should merge the init PaC PR successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:459 @ 04/21/26 17:13:53.633&#xA;merged result sha: 6b762ba111033e5b3989965c9d812ab8c090a21e for PR #8865&#xA;&lt; Exit [It] should merge the init PaC PR successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:459 @ 04/21/26 17:13:56.163 (2.53s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:13:56.163&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:13:56.163 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when both the init PaC PRs are merged should make change to the root folder [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="3.030473818">
              <system-err>&gt; Enter [It] should make change to the root folder - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:479 @ 04/21/26 17:13:56.164&#xA;PR #21212 got created with sha 1ec4560a76674d131cbd2a9f1fdd851fee2f1fc0&#xA;&lt; Exit [It] should make change to the root folder - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:479 @ 04/21/26 17:13:59.194 (3.03s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:13:59.194&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:13:59.194 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when both the init PaC PRs are merged should make change to the multiple-repo [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="2.170961712">
              <system-err>&gt; Enter [It] should make change to the multiple-repo - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:497 @ 04/21/26 17:13:59.195&#xA;PR #8867 got created with sha 19134f13bd35edc2b5677876bf33e1c72f74154e&#xA;&lt; Exit [It] should make change to the multiple-repo - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:497 @ 04/21/26 17:14:01.365 (2.171s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:14:01.365&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:14:01.365 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when both the init PaC PRs are merged wait for the last components build to finish [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.419213949">
              <system-err>&gt; Enter [It] wait for the last components build to finish - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:513 @ 04/21/26 17:14:01.366&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 found for Component group-yugp/go-component-lhcrru&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Completed&#xA;PipelineRun integration-resolver-pipelinerun-87k82 found for Component group-yugp/python-component-gguptr&#xA;PipelineRun integration-resolver-pipelinerun-87k82 reason: Succeeded&#xA;PipelineRun integration-resolver-pipelinerun-lx5mf found for Component group-yugp/konflux-test-integration-clone-coxbuu&#xA;PipelineRun integration-resolver-pipelinerun-lx5mf reason: Succeeded&#xA;&lt; Exit [It] wait for the last components build to finish - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:513 @ 04/21/26 17:14:01.785 (419ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:14:01.785&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:14:01.785 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when both the init PaC PRs are merged wait for all component snapshots to be created with proper PR group annotations [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.070570976">
              <system-err>&gt; Enter [It] wait for all component snapshots to be created with proper PR group annotations - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:521 @ 04/21/26 17:14:01.786&#xA;Component snapshot integ-app-phfi-20260421-165428-000 has PR group annotation: konflux-go-component-lhcrru&#xA;Component snapshot integ-app-phfi-20260421-170412-000 is missing PR group annotation&#xA;Component snapshot integ-app-phfi-20260421-170431-000 has PR group annotation: konflux-python-component-gguptr&#xA;Component snapshot integ-app-phfi-20260421-171017-000 has PR group annotation: konflux-konflux-test-integration-clone-coxbuu&#xA;All component snapshots are ready with PR group annotations&#xA;&lt; Exit [It] wait for all component snapshots to be created with proper PR group annotations - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:521 @ 04/21/26 17:14:01.856 (70ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:14:01.856&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:14:01.856 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when both the init PaC PRs are merged get all group snapshots and check if pr-group annotation contains all components [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="370.301051966">
              <system-err>&gt; Enter [It] get all group snapshots and check if pr-group annotation contains all components - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:556 @ 04/21/26 17:14:01.857&#xA;Attempting to find group snapshots for application integ-app-phfi in namespace group-yugp&#xA;Found 4 component snapshots:&#xA;PR Groups found: map[konflux-go-component-lhcrru:1 konflux-konflux-test-integration-clone-coxbuu:1 konflux-python-component-gguptr:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-phfi in namespace group-yugp&#xA;Found 5 component snapshots:&#xA;PR Groups found: map[konflux-go-component-lhcrru:1 konflux-konflux-test-integration-clone-coxbuu:1 konflux-python-component-gguptr:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-phfi in namespace group-yugp&#xA;Found 5 component snapshots:&#xA;PR Groups found: map[konflux-go-component-lhcrru:1 konflux-konflux-test-integration-clone-coxbuu:1 konflux-python-component-gguptr:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-phfi in namespace group-yugp&#xA;Found 5 component snapshots:&#xA;PR Groups found: map[konflux-go-component-lhcrru:1 konflux-konflux-test-integration-clone-coxbuu:1 konflux-python-component-gguptr:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-phfi in namespace group-yugp&#xA;Found 5 component snapshots:&#xA;PR Groups found: map[konflux-go-component-lhcrru:1 konflux-konflux-test-integration-clone-coxbuu:1 konflux-python-component-gguptr:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-phfi in namespace group-yugp&#xA;Found 5 component snapshots:&#xA;PR Groups found: map[konflux-go-component-lhcrru:1 konflux-konflux-test-integration-clone-coxbuu:1 konflux-python-component-gguptr:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-phfi in namespace group-yugp&#xA;Found 5 component snapshots:&#xA;PR Groups found: map[konflux-go-component-lhcrru:1 konflux-konflux-test-integration-clone-coxbuu:1 konflux-python-component-gguptr:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-phfi in namespace group-yugp&#xA;Found 5 component snapshots:&#xA;PR Groups found: map[konflux-go-component-lhcrru:1 konflux-konflux-test-integration-clone-coxbuu:1 konflux-python-component-gguptr:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-phfi in namespace group-yugp&#xA;Found 6 component snapshots:&#xA;PR Groups found: map[konflux-go-component-lhcrru:1 konflux-konflux-test-integration-clone-coxbuu:1 konflux-python-component-gguptr:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-phfi in namespace group-yugp&#xA;Found 6 component snapshots:&#xA;PR Groups found: map[konflux-go-component-lhcrru:1 konflux-konflux-test-integration-clone-coxbuu:1 konflux-python-component-gguptr:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-phfi in namespace group-yugp&#xA;Found 6 component snapshots:&#xA;PR Groups found: map[konflux-go-component-lhcrru:1 konflux-konflux-test-integration-clone-coxbuu:1 konflux-python-component-gguptr:1]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-phfi in namespace group-yugp&#xA;Found 8 component snapshots:&#xA;PR Groups found: map[konflux-go-component-lhcrru:1 konflux-konflux-test-integration-clone-coxbuu:1 konflux-python-component-gguptr:1 pr-branch-pieycn:2]&#xA;No group snapshots found yet. Component snapshots may not have been processed by integration service controller yet.&#xA;Attempting to find group snapshots for application integ-app-phfi in namespace group-yugp&#xA;Found 9 component snapshots:&#xA;PR Groups found: map[konflux-go-component-lhcrru:1 konflux-konflux-test-integration-clone-coxbuu:1 konflux-python-component-gguptr:1 pr-branch-pieycn:3]&#xA;Found 1 group snapshots!&#xA;  Group Snapshot 0: integ-app-phfi-20260421-171948-602 (type: group)&#xA;    Group Test Info: [{&#34;namespace&#34;:&#34;group-yugp&#34;,&#34;component&#34;:&#34;konflux-test-integration-clone-coxbuu&#34;,&#34;buildPipelineRun&#34;:&#34;konflux-test-integration-clone-coxbuu-on-pull-request-qjx8p&#34;,&#34;snapshot&#34;:&#34;integ-app-phfi-20260421-171405-000&#34;,&#34;repoUrl&#34;:&#34;https://github.com/redhat-appstudio-qe/konflux-test-integration-clone&#34;,&#34;pullRequestNumber&#34;:&#34;8867&#34;},{&#34;namespace&#34;:&#34;group-yugp&#34;,&#34;component&#34;:&#34;go-component-lhcrru&#34;,&#34;buildPipelineRun&#34;:&#34;go-component-lhcrru-on-pull-request-l996f&#34;,&#34;snapshot&#34;:&#34;integ-app-phfi-20260421-171403-000&#34;,&#34;repoUrl&#34;:&#34;https://github.com/redhat-appstudio-qe/group-snapshot-multi-component&#34;,&#34;pullRequestNumber&#34;:&#34;21212&#34;},{&#34;namespace&#34;:&#34;group-yugp&#34;,&#34;component&#34;:&#34;python-component-gguptr&#34;,&#34;buildPipelineRun&#34;:&#34;python-component-gguptr-on-pull-request-5gwtl&#34;,&#34;snapshot&#34;:&#34;integ-app-phfi-20260421-171404-000&#34;,&#34;repoUrl&#34;:&#34;https://github.com/redhat-appstudio-qe/group-snapshot-multi-component&#34;,&#34;pullRequestNumber&#34;:&#34;21212&#34;}]&#xA;Validating group test info annotation: [{&#34;namespace&#34;:&#34;group-yugp&#34;,&#34;component&#34;:&#34;konflux-test-integration-clone-coxbuu&#34;,&#34;buildPipelineRun&#34;:&#34;konflux-test-integration-clone-coxbuu-on-pull-request-qjx8p&#34;,&#34;snapshot&#34;:&#34;integ-app-phfi-20260421-171405-000&#34;,&#34;repoUrl&#34;:&#34;https://github.com/redhat-appstudio-qe/konflux-test-integration-clone&#34;,&#34;pullRequestNumber&#34;:&#34;8867&#34;},{&#34;namespace&#34;:&#34;group-yugp&#34;,&#34;component&#34;:&#34;go-component-lhcrru&#34;,&#34;buildPipelineRun&#34;:&#34;go-component-lhcrru-on-pull-request-l996f&#34;,&#34;snapshot&#34;:&#34;integ-app-phfi-20260421-171403-000&#34;,&#34;repoUrl&#34;:&#34;https://github.com/redhat-appstudio-qe/group-snapshot-multi-component&#34;,&#34;pullRequestNumber&#34;:&#34;21212&#34;},{&#34;namespace&#34;:&#34;group-yugp&#34;,&#34;component&#34;:&#34;python-component-gguptr&#34;,&#34;buildPipelineRun&#34;:&#34;python-component-gguptr-on-pull-request-5gwtl&#34;,&#34;snapshot&#34;:&#34;integ-app-phfi-20260421-171404-000&#34;,&#34;repoUrl&#34;:&#34;https://github.com/redhat-appstudio-qe/group-snapshot-multi-component&#34;,&#34;pullRequestNumber&#34;:&#34;21212&#34;}]&#xA;Group snapshot validation completed successfully&#xA;&lt; Exit [It] get all group snapshots and check if pr-group annotation contains all components - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:556 @ 04/21/26 17:20:12.157 (6m10.301s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:20:12.158&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:20:12.158 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when both the init PaC PRs are merged make sure that group snapshot contains last build pipelinerun for each component [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.269043849">
              <system-err>&gt; Enter [It] make sure that group snapshot contains last build pipelinerun for each component - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:635 @ 04/21/26 17:20:12.158&#xA;&lt; Exit [It] make sure that group snapshot contains last build pipelinerun for each component - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:635 @ 04/21/26 17:20:12.427 (269ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:20:12.427&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:20:12.427 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when Older snapshot and integration pipelinerun should be cancelled once new snapshot is created make change to the multiple-repo to trigger a new cycle of testing [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.787297167">
              <system-err>&gt; Enter [It] make change to the multiple-repo to trigger a new cycle of testing - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:648 @ 04/21/26 17:20:12.428&#xA;&lt; Exit [It] make change to the multiple-repo to trigger a new cycle of testing - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:648 @ 04/21/26 17:20:13.215 (787ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:20:13.215&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:20:13.215 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when Older snapshot and integration pipelinerun should be cancelled once new snapshot is created wait for the components A and B build to finish [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.144364993">
              <system-err>&gt; Enter [It] wait for the components A and B build to finish - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:654 @ 04/21/26 17:20:13.215&#xA;Waiting for build pipelineRun to be created for app group-yugp/integ-app-phfi, sha: e3976a05a69736e30cfd1bb2e24fdf64e2b7a827&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 found for Component group-yugp/go-component-lhcrru&#xA;PipelineRun go-component-lhcrru-on-pull-request-jzrq7 reason: Completed&#xA;PipelineRun integration-resolver-pipelinerun-4xpbk found for Component group-yugp/python-component-gguptr&#xA;PipelineRun integration-resolver-pipelinerun-4xpbk reason: Succeeded&#xA;&lt; Exit [It] wait for the components A and B build to finish - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:654 @ 04/21/26 17:20:13.359 (144ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:20:13.36&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:20:13.36 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when Older snapshot and integration pipelinerun should be cancelled once new snapshot is created get all component snapshots for component A and check if older snapshot has been cancelled [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="282.470388212">
              <system-err>&gt; Enter [It] get all component snapshots for component A and check if older snapshot has been cancelled - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:663 @ 04/21/26 17:20:13.36&#xA;&lt; Exit [It] get all component snapshots for component A and check if older snapshot has been cancelled - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:663 @ 04/21/26 17:24:55.83 (4m42.47s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:24:55.83&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:24:55.83 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when Older snapshot and integration pipelinerun should be cancelled once new snapshot is created get all group snapshots and check if older group snapshot is cancelled [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.127050798">
              <system-err>&gt; Enter [It] get all group snapshots and check if older group snapshot is cancelled - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:690 @ 04/21/26 17:24:55.831&#xA;&lt; Exit [It] get all group snapshots and check if older group snapshot is cancelled - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:690 @ 04/21/26 17:24:55.958 (127ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:24:55.958&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:24:55.958 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when ResolutionRequest is deleted after pipeline completes verifies that ResolutionRequest is deleted after pipeline resolution [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.476356174">
              <system-err>&gt; Enter [It] verifies that ResolutionRequest is deleted after pipeline resolution - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:720 @ 04/21/26 17:24:55.958&#xA;&lt; Exit [It] verifies that ResolutionRequest is deleted after pipeline resolution - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:720 @ 04/21/26 17:24:56.434 (476ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:24:56.434&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:24:56.435 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when ResolutionRequest is deleted after pipeline completes verifies that no orphaned ResolutionRequests remain in namespace after test completion [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="0.260227064">
              <system-err>&gt; Enter [It] verifies that no orphaned ResolutionRequests remain in namespace after test completion - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:740 @ 04/21/26 17:24:56.435&#xA;&lt; Exit [It] verifies that no orphaned ResolutionRequests remain in namespace after test completion - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:740 @ 04/21/26 17:24:56.695 (260ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:24:56.695&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:24:56.695 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when IntegrationTestScenario reference to task as pipelinerun resolution trigger pipelinerun for invalid integrationTestScenario by annotating snapshot and verify failing to create integration pipelinerun [integration-service, group-snapshot-creation]" classname="Red Hat App Studio E2E tests" status="passed" time="26.36748498">
              <system-err>&gt; Enter [BeforeAll] when IntegrationTestScenario reference to task as pipelinerun resolution - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:775 @ 04/21/26 17:24:56.696&#xA;&lt; Exit [BeforeAll] when IntegrationTestScenario reference to task as pipelinerun resolution - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:775 @ 04/21/26 17:24:56.767 (71ms)&#xA;&gt; Enter [It] trigger pipelinerun for invalid integrationTestScenario by annotating snapshot and verify failing to create integration pipelinerun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:780 @ 04/21/26 17:24:56.767&#xA;&lt; Exit [It] trigger pipelinerun for invalid integrationTestScenario by annotating snapshot and verify failing to create integration pipelinerun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:780 @ 04/21/26 17:25:17.031 (20.264s)&#xA;&gt; Enter [AfterAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:149 @ 04/21/26 17:25:17.031&#xA;&lt; Exit [AfterAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:149 @ 04/21/26 17:25:23.063 (6.031s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:25:23.063&#xA;&lt; Exit [AfterEach] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/group-snapshots-tests.go:50 @ 04/21/26 17:25:23.063 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when creating tenants on the old Konflux version should create both tenants concurrently [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when creating tenants on the old Konflux version should wait for all build PipelineRuns to succeed [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when backing up tenant data before upgrade should create backup CRs for both tenants concurrently [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when simulating disaster by deleting namespaces should delete both tenant namespaces [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when upgrading Konflux to the new version should upgrade the cluster and verify Velero survived [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when restoring tenants from backup on the new Konflux version should restore tenant-1 (KokoHazamar) via velero CLI method [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when restoring tenants from backup on the new Konflux version should restore tenant-2 (MosheKipod) via oc command method [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when performing post-restore recovery should rotate SA tokens on both tenants [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when verifying restored tenants should confirm structural integrity of both tenants [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Backwards-Compat] when verifying restored tenants should confirm functional pipeline execution after restore [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when creating tenants and running initial pipelines should create both tenants concurrently [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when creating tenants and running initial pipelines should wait for all build PipelineRuns to succeed [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when backing up tenant data should create backup CRs for both tenants concurrently [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when simulating disaster by deleting namespaces should delete both tenant namespaces [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when restoring from backup should restore tenant-1 (KokoHazamar) via velero CLI method [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when restoring from backup should restore tenant-2 (MosheKipod) via oc command method [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when performing post-restore recovery should rotate SA tokens on both tenants [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when verifying restored tenants should confirm structural integrity of both tenants [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [disaster-recovery DR Same-Version Backup/Restore] when verifying restored tenants should confirm functional pipeline execution after restore [disaster-recovery, Serial]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification verifies that the ReleasePlan CR is unmatched in the beginning [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification Creates ReleasePlanAdmission CR in corresponding managed namespace [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification when ReleasePlanAdmission CR is created in managed namespace verifies that the ReleasePlan CR is set to matched [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification when ReleasePlanAdmission CR is created in managed namespace verifies that the ReleasePlanAdmission CR is set to matched [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification Creates a manual release ReleasePlan CR in devNamespace [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification when the second ReleasePlan CR is created verifies that the second ReleasePlan CR is set to matched [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification when the second ReleasePlan CR is created verifies that the ReleasePlanAdmission CR has two matched ReleasePlan CRs [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification deletes one ReleasePlan CR [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification when One ReleasePlan CR is deleted in managed namespace verifies that the ReleasePlanAdmission CR has only one matching ReleasePlan [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification deletes the ReleasePlanAdmission CR [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite ReleasePlan and ReleasePlanAdmission match] RP and PRA status change verification when ReleasePlanAdmission CR is deleted in managed namespace verifies that the ReleasePlan CR has no matched ReleasePlanAdmission [release-service, release_plan_and_admission]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rhtap-service-push pipeline] Rhtap-service-push happy path Post-release verification verifies if the release CR is created [release-pipelines, rhtap-service-push, RhtapServicePush]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rhtap-service-push pipeline] Rhtap-service-push happy path Post-release verification verifies the rhtap release pipelinerun is running and succeeds [release-pipelines, rhtap-service-push, RhtapServicePush]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rhtap-service-push pipeline] Rhtap-service-push happy path Post-release verification verifies release CR completed and set succeeded. [release-pipelines, rhtap-service-push, RhtapServicePush]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rhtap-service-push pipeline] Rhtap-service-push happy path Post-release verification verifies if the PR in infra-deployments repo is created/updated [release-pipelines, rhtap-service-push, RhtapServicePush]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rh-push-to-redhat-io pipeline] Rh-push-to-redhat-io happy path Post-release verification verifies if the release CR is created [release-pipelines, rh-push-to-registry-redhat-io, PushToRedhatIO]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rh-push-to-redhat-io pipeline] Rh-push-to-redhat-io happy path Post-release verification verifies the rhio release pipelinerun is running and succeeds [release-pipelines, rh-push-to-registry-redhat-io, PushToRedhatIO]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rh-push-to-redhat-io pipeline] Rh-push-to-redhat-io happy path Post-release verification verifies release CR completed and set succeeded. [release-pipelines, rh-push-to-registry-redhat-io, PushToRedhatIO]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rh-push-to-redhat-io pipeline] Rh-push-to-redhat-io happy path Post-release verification verifies if the MR URL is valid [release-pipelines, rh-push-to-registry-redhat-io, PushToRedhatIO]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite Release service happy path] Post-release verification verifies that a Release CR should have been created in the dev namespace [release-service, happy-path]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite Release service happy path] Post-release verification verifies that Release PipelineRun is triggered [release-service, happy-path]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite Release service happy path] Post-release verification verifies that Enterprise Contract Task has succeeded in the Release PipelineRun [release-service, happy-path]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite Release service happy path] Post-release verification verifies that a Release is marked as succeeded. [release-service, happy-path]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] post-release verification. missing ReleasePlan makes a Release CR set as failed in both IsReleased and IsValid with a proper message to user. [release-service, release-neg, negMissingReleasePlan]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-service-suite [HACBS-2360] Release CR fails when missing ReleasePlan and ReleasePlanAdmission.] post-release verification. missing ReleasePlanAdmission makes a Release CR set as failed in both IsReleased and IsValid with a proper message to user. [release-service, release-neg, negMissingReleasePlan]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace creates component with context directory go-component [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="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-mqjxnm [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test 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-mqjxnm [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace the PipelineRun should eventually finish successfully for component go-component-mqjxnm [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace merging the PR should be successful [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace creates component with context directory python-component [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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-qdmvqn [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test 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-qdmvqn [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace the PipelineRun should eventually finish successfully for component python-component-qdmvqn [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace merging the PR should be successful [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace only one component is changed [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when a components is created with same git url in different namespace should fail to configure PaC for the component [build-service, github, pac-build, multi-component]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace creates component with nudges [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for parent component  [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace should lead to a PaC PR creation for child component  [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace create dockerfile and yaml manifest that references build and distribution repositories [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace Merging the PaC PR should be successful for parent component  [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace PAC PipelineRun for parent component  is successful [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace merging the PR should be successful for child component  [build-service, renovate, multi-component, gitlab]" classname="Red Hat App Studio E2E tests" status="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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build creates an application [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build creates an IntegrationTestScenario for the app [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build creates new branch for the build [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build creates component konflux-demo-component (private: false) from git source https://github.com/redhat-appstudio-qe/hacbs-test-project-konflux-demo [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Component is created triggers creation of a PR in the sample repo [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Component is created verifies component build status [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Component is created should eventually lead to triggering a &#39;push&#39; event type PipelineRun after merging the PaC init branch  [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun is created does not contain an annotation with a Snapshot Name [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun is created should eventually complete successfully [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun completes successfully should validate Tekton TaskRun test results successfully [konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun completes successfully should validate that the build pipelineRun is signed [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun completes successfully should find the related Snapshot CR [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun completes successfully should validate that the build pipelineRun is annotated with the name of the Snapshot [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Build PipelineRun completes successfully should find the related Integration Test PipelineRun [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when push pipelinerun is retriggered should eventually succeed [konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Integration Test PipelineRun is created should eventually complete successfully [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Integration Test PipelineRun completes successfully should lead to Snapshot CR being marked as passed [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Integration Test PipelineRun completes successfully should trigger creation of Release CR [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Release CR is created triggers creation of Release PipelineRun [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Release PipelineRun is triggered should eventually succeed [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [konflux-demo-suite] Maven project - Default build when Release PipelineRun is completed should lead to Release CR being marked as succeeded [konflux, upstream-konflux]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace creates component with nudges [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for parent component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace should lead to a PaC PR creation for child component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace create dockerfile and yaml manifest that references build and distribution repositories [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace Merging the PaC PR should be successful for parent component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace PAC PipelineRun for parent component  is successful [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace merging the PR should be successful for child component  [build-service, renovate, multi-component, github]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws host-pool allocation when the Component with multi-platform-build is created a PipelineRun is triggered [multi-platform, aws-host-pool]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws host-pool allocation when the Component with multi-platform-build is created the build-container task from component pipelinerun is buildah-remote [multi-platform, aws-host-pool]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws host-pool allocation when the Component with multi-platform-build is created The multi platform secret is populated [multi-platform, aws-host-pool]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws host-pool allocation when the Component with multi-platform-build is created that PipelineRun completes successfully [multi-platform, aws-host-pool]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws host-pool allocation when the Component with multi-platform-build is created test that cleanup happened successfully [multi-platform, aws-host-pool]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws dynamic allocation when the Component with multi-platform-build is created a PipelineRun is triggered [multi-platform, aws-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws dynamic allocation when the Component with multi-platform-build is created the build-container task from component pipelinerun is buildah-remote [multi-platform, aws-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws dynamic allocation when the Component with multi-platform-build is created The multi platform secret is populated [multi-platform, aws-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws dynamic allocation when the Component with multi-platform-build is created that PipelineRun completes successfully [multi-platform, aws-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] aws dynamic allocation when the Component with multi-platform-build is created check cleanup happened successfully [multi-platform, aws-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm system z dynamic allocation when the Component with multi-platform-build is created a PipelineRun is triggered [multi-platform, ibmz-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm system z dynamic allocation when the Component with multi-platform-build is created the build-container task from component pipelinerun is buildah-remote [multi-platform, ibmz-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm system z dynamic allocation when the Component with multi-platform-build is created The multi platform secret is populated [multi-platform, ibmz-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm system z dynamic allocation when the Component with multi-platform-build is created that PipelineRun completes successfully [multi-platform, ibmz-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm system z dynamic allocation when the Component with multi-platform-build is created check cleanup happened successfully [multi-platform, ibmz-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm power pc dynamic allocation when the Component with multi-platform-build is created a PipelineRun is triggered [multi-platform, ibmp-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm power pc dynamic allocation when the Component with multi-platform-build is created the build-container task from component pipelinerun is buildah-remote [multi-platform, ibmp-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm power pc dynamic allocation when the Component with multi-platform-build is created The multi platform secret is populated [multi-platform, ibmp-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm power pc dynamic allocation when the Component with multi-platform-build is created that PipelineRun completes successfully [multi-platform, ibmp-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [multi-platform-build-service-suite Multi Platform Controller E2E tests] ibm power pc dynamic allocation when the Component with multi-platform-build is created check cleanup happened successfully [multi-platform, ibmp-dynamic]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private correctly targets the default branch (that is not named &#39;main&#39;) with PaC [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private workspace parameter is set correctly in PaC repository CR [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private build pipeline uses the correct serviceAccount [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private component build status is set correctly [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private created image repo is private [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private a related PipelineRun should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private PR branch should not exist in the repo [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private related image repo and the robot account should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created should lead to a PaC init PR creation [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created created image repo is public [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created image tag is updated successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created should ensure pruning labels are set [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created eventually leads to the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated should lead to a PaC init PR update [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated PipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated eventually leads to another update of a PR about the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged does not have expiration set [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged After updating image visibility to private, it should not trigger another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged image repo is updated to private [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged retrigger the pipeline manually [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged retriggered pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the component is removed and recreated (with the same name in the same namespace) should no longer lead to a creation of a PaC PR [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rh-advisories pipeline] Rh-advisories happy path Post-release verification verifies if release CR is created [release-pipelines, rh-advisories, rhAdvisories]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rh-advisories pipeline] Rh-advisories happy path Post-release verification verifies the advs release pipelinerun is running and succeeds [release-pipelines, rh-advisories, rhAdvisories]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rh-advisories pipeline] Rh-advisories happy path Post-release verification verifies release CR completed and set succeeded. [release-pipelines, rh-advisories, rhAdvisories]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for rh-advisories pipeline] Rh-advisories happy path Post-release verification verifies if the repository URL is valid [release-pipelines, rh-advisories, rhAdvisories]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite Push to external registry] Post-release verification verifies that a Release CR should have been created in the dev namespace [release-pipelines, push-to-external-registry]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite Push to external registry] Post-release verification verifies that Release PipelineRun should eventually succeed [release-pipelines, push-to-external-registry]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite Push to external registry] Post-release verification tests if the image was pushed to quay [release-pipelines, push-to-external-registry]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite Push to external registry] Post-release verification verifies that a Release is marked as succeeded. [release-pipelines, push-to-external-registry]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private correctly targets the default branch (that is not named &#39;main&#39;) with PaC [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private component build status is set correctly [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private created image repo is private [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private PR branch should not exist in the repo [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created created image repo is public [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created should ensure pruning labels are set [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is updated eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is updated PipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged does not have expiration set [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged image repo is updated to private [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged retriggered pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the component is removed and recreated (with the same name in the same namespace) should no longer lead to a creation of a PaC PR [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [task-suite tkn bundle task] creates Tekton bundles with different params when context points to a file [build-templates]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [task-suite tkn bundle task] creates Tekton bundles with different params creates Tekton bundles from specific context [build-templates]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [task-suite tkn bundle task] creates Tekton bundles with different params when context is the root directory [build-templates]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [task-suite tkn bundle task] creates Tekton bundles with different params creates Tekton bundles when context points to a file and a directory [build-templates]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [task-suite tkn bundle task] creates Tekton bundles with different params creates Tekton bundles when using negation [build-templates]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [task-suite tkn bundle task] creates Tekton bundles with different params allows overriding HOME environment variable [build-templates]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [task-suite tkn bundle task] creates Tekton bundles with different params allows overriding STEP image [build-templates]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created creates first component [build-service, github, pac-build, secret-lookup]" classname="Red Hat App Studio E2E tests" status="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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created check first component annotation has errors [build-service, github, pac-build, secret-lookup]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created triggered PipelineRun is for component  [build-service, github, pac-build, secret-lookup]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created check only one pipelinerun should be triggered [build-service, github, pac-build, secret-lookup]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created when second component is deleted, pac pr branch should not exist in the repo [build-service, github, pac-build, secret-lookup]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace creates component with nudges [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace triggers a PipelineRun for parent component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for parent component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for child component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace should lead to a PaC PR creation for child component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace Merging the PaC PR should be successful for child component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace create dockerfile and yaml manifest that references build and distribution repositories [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace should lead to a PaC PR creation for parent component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace Merging the PaC PR should be successful for parent component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace PR merge triggers PAC PipelineRun for parent component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace PAC PipelineRun for parent component  is successful [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace should lead to a nudge PR creation for child component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace merging the PR should be successful for child component  [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace Verify the nudge updated the contents [build-service, renovate, multi-component, forgejo]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private correctly targets the default branch (that is not named &#39;main&#39;) with PaC [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private component build status is set correctly [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private created image repo is private [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private PR branch should not exist in the repo [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created created image repo is public [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created should ensure pruning labels are set [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated PipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged does not have expiration set [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged image repo is updated to private [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></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="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged retriggered pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the component is removed and recreated (with the same name in the same namespace) should no longer lead to a creation of a PaC PR [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for release-to-github pipeline] Release-to-github happy path Post-release verification verifies if release CR is created [release-pipelines, release-to-github, releaseToGithub]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for release-to-github pipeline] Release-to-github happy path Post-release verification verifies the release pipelinerun is running and succeeds [release-pipelines, release-to-github, releaseToGithub]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for release-to-github pipeline] Release-to-github happy path Post-release verification verifies release CR completed and set succeeded. [release-pipelines, release-to-github, releaseToGithub]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for release-to-github pipeline] Release-to-github happy path Post-release verification verifies if the Release exists in github repo [release-pipelines, release-to-github, releaseToGithub]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for multi arch with rh-advisories pipeline] Multi arch test happy path Post-release verification verifies the release CR is created [release-pipelines, rh-advisories, multiarch-advisories, multiArchAdvisories]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for multi arch with rh-advisories pipeline] Multi arch test happy path Post-release verification verifies the multiarch release pipelinerun is running and succeeds [release-pipelines, rh-advisories, multiarch-advisories, multiArchAdvisories]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for multi arch with rh-advisories pipeline] Multi arch test happy path Post-release verification verifies release CR completed and set succeeded. [release-pipelines, rh-advisories, multiarch-advisories, multiArchAdvisories]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite e2e tests for multi arch with rh-advisories pipeline] Multi arch test happy path Post-release verification verifies if the repository URL is valid [release-pipelines, rh-advisories, multiarch-advisories, multiArchAdvisories]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines triggers PipelineRun for symlink component with source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic with component name test-symlink-comp-ifuc [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci triggers PipelineRun for component with source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci triggers PipelineRun for component with source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci triggers PipelineRun for component with source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta-min [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) should eventually finish successfully for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta-min [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) should push Dockerfile to registry [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) floating tags are created successfully [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) image manifest mediaType is correct [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) check for source images if enabled in pipeline [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) when Pipeline Results are stored for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta-min should have Pipeline Records [build, build-templates, HACBS, pipeline-service, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) when Pipeline Results are stored for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta-min should have Pipeline Logs [build, build-templates, HACBS, pipeline-service, pipeline]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) should validate tekton taskrun test results for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta-min [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry verify-enterprise-contract check should pass [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry should have Hermeto content in the SBOM in case the build was hermetic [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta-min) build-definitions ec pipelines runs ec pipeline pipelines/enterprise-contract.yaml [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) should eventually finish successfully for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) should push Dockerfile to registry [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) floating tags are created successfully [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) image manifest mediaType is correct [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) check for source images if enabled in pipeline [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) when Pipeline Results are stored for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build should have Pipeline Records [build, build-templates, HACBS, pipeline-service, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) when Pipeline Results are stored for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build should have Pipeline Logs [build, build-templates, HACBS, pipeline-service, pipeline]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) should validate tekton taskrun test results for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry verify-enterprise-contract check should pass [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry should have Hermeto content in the SBOM in case the build was hermetic [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build) build-definitions ec pipelines runs ec pipeline pipelines/enterprise-contract.yaml [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) should eventually finish successfully for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) should push Dockerfile to registry [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) floating tags are created successfully [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) image manifest mediaType is correct [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) check for source images if enabled in pipeline [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) when Pipeline Results are stored for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta should have Pipeline Records [build, build-templates, HACBS, pipeline-service, pipeline]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) when Pipeline Results are stored for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta should have Pipeline Logs [build, build-templates, HACBS, pipeline-service, pipeline]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) should validate tekton taskrun test results for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic and Pipeline docker-build-oci-ta [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry verify-enterprise-contract check should pass [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) when the container image for component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic is created and pushed to container registry should have Hermeto content in the SBOM in case the build was hermetic [build, build-templates, HACBS, pipeline-service, pipeline, sbom, slow, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci (docker-build-oci-ta) build-definitions ec pipelines runs ec pipeline pipelines/enterprise-contract.yaml [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build templates E2E test] HACBS pipelines pipelineRun should fail for symlink component with Git source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic with component name test-symlink-comp-ifuc [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when a new Component with specified custom branch is created triggers a Build PipelineRun [integration-service, gitlab-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="42.971320136">
              <system-err>&gt; Enter [BeforeAll] Gitlab with status reporting of Integration tests in the assosiated merge request - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:45 @ 04/21/26 16:53:42.581&#xA;&lt; Exit [BeforeAll] Gitlab with status reporting of Integration tests in the assosiated merge request - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:45 @ 04/21/26 16:53:45.2 (2.62s)&#xA;&gt; Enter [BeforeAll] when a new Component with specified custom branch is created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:109 @ 04/21/26 16:53:45.201&#xA;Image repository for component test-comp-pac-gitlab-yofssk in namespace gitlab-rep-ycrl do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [BeforeAll] when a new Component with specified custom branch is created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:109 @ 04/21/26 16:54:05.343 (20.143s)&#xA;&gt; Enter [It] triggers a Build PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:130 @ 04/21/26 16:54:05.343&#xA;Build PipelineRun has not been created yet for the component gitlab-rep-ycrl/test-comp-pac-gitlab-yofssk&#xA;&lt; Exit [It] triggers a Build PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:130 @ 04/21/26 16:54:25.552 (20.208s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 16:54:25.552&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 16:54:25.552 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when a new Component with specified custom branch is created does not contain an annotation with a Snapshot Name [integration-service, gitlab-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.000325809">
              <system-err>&gt; Enter [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:144 @ 04/21/26 16:54:25.553&#xA;&lt; Exit [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:144 @ 04/21/26 16:54:25.553 (0s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 16:54:25.553&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 16:54:25.553 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when a new Component with specified custom branch is created should lead to build PipelineRun finishing successfully [integration-service, gitlab-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="560.20942441">
              <system-err>&gt; Enter [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:148 @ 04/21/26 16:54:25.553&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j found for Component gitlab-rep-ycrl/test-comp-pac-gitlab-yofssk&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: ResolvingTaskRef&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: ResolvingTaskRef&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun test-comp-pac-gitlab-yofssk-on-pull-request-kwn5j reason: Running&#xA;PipelineRun my-integration-test-gfqd-8994q reason: Running&#xA;PipelineRun my-integration-test-gfqd-8994q reason: Succeeded&#xA;&lt; Exit [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:148 @ 04/21/26 17:03:45.762 (9m20.209s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:45.762&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:45.762 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when a new Component with specified custom branch is created should have a related PaC init MR is created [integration-service, gitlab-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.899055945">
              <system-err>&gt; Enter [It] should have a related PaC init MR is created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:153 @ 04/21/26 17:03:45.763&#xA;&lt; Exit [It] should have a related PaC init MR is created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:153 @ 04/21/26 17:03:46.662 (899ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:46.662&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:46.662 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when a new Component with specified custom branch is created the PipelineRun should eventually finish successfully for component  [integration-service, gitlab-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.139800645">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for component  - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:172 @ 04/21/26 17:03:46.662&#xA;PipelineRun my-integration-test-gfqd-8994q found for Component gitlab-rep-ycrl/test-comp-pac-gitlab-yofssk&#xA;PipelineRun my-integration-test-gfqd-8994q reason: Succeeded&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for component  - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:172 @ 04/21/26 17:03:46.802 (139ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:46.802&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:46.802 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when the PaC build pipelineRun run succeeded checks if the BuildPipelineRun have the annotation of chains signed [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.143230882">
              <system-err>&gt; Enter [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:179 @ 04/21/26 17:03:46.802&#xA;&lt; Exit [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:179 @ 04/21/26 17:03:46.945 (143ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:46.946&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:46.946 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when the PaC build pipelineRun run succeeded checks if the Snapshot is created [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.069995259">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:183 @ 04/21/26 17:03:46.946&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:183 @ 04/21/26 17:03:47.016 (70ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:47.016&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:47.016 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when the PaC build pipelineRun run succeeded checks if the Build PipelineRun got annotated with Snapshot name [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.143067728">
              <system-err>&gt; Enter [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:188 @ 04/21/26 17:03:47.016&#xA;&lt; Exit [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:188 @ 04/21/26 17:03:47.159 (143ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:47.159&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:47.159 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when the Snapshot was created should find the Integration Test Scenario PipelineRun [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.07040464">
              <system-err>&gt; Enter [It] should find the Integration Test Scenario PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:194 @ 04/21/26 17:03:47.16&#xA;&lt; Exit [It] should find the Integration Test Scenario PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:194 @ 04/21/26 17:03:47.23 (70ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:47.23&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:47.23 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Integration PipelineRun is created should eventually complete successfully [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.140393609">
              <system-err>&gt; Enter [It] should eventually complete successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:207 @ 04/21/26 17:03:47.231&#xA;PipelineRun my-integration-test-mddg-jqgrb reason: Succeeded&#xA;PipelineRun my-integration-test-gfqd-8994q reason: Succeeded&#xA;&lt; Exit [It] should eventually complete successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:207 @ 04/21/26 17:03:47.371 (140ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:47.371&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:47.371 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Integration PipelineRun is created validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it pass [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.155228511">
              <system-err>&gt; Enter [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it pass - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:212 @ 04/21/26 17:03:47.371&#xA;&lt; Exit [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it pass - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:212 @ 04/21/26 17:03:47.526 (155ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:47.526&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:47.526 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Integration PipelineRun is created eventually leads to the integration test PipelineRun&#39;s Pass status reported at MR commit status [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.332063908">
              <system-err>&gt; Enter [It] eventually leads to the integration test PipelineRun&#39;s Pass status reported at MR commit status - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:229 @ 04/21/26 17:03:47.527&#xA;&lt; Exit [It] eventually leads to the integration test PipelineRun&#39;s Pass status reported at MR commit status - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:229 @ 04/21/26 17:03:47.858 (332ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:47.859&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:47.859 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Integration PipelineRun is created validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it fails [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.191148544">
              <system-err>&gt; Enter [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it fails - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:233 @ 04/21/26 17:03:47.86&#xA;&lt; Exit [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it fails - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:233 @ 04/21/26 17:03:48.05 (191ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:48.05&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:48.05 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Integration PipelineRun is created eventually leads to the integration test PipelineRun&#39;s Fail status reported at MR commit status [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.514643752">
              <system-err>&gt; Enter [It] eventually leads to the integration test PipelineRun&#39;s Fail status reported at MR commit status - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:250 @ 04/21/26 17:03:48.051&#xA;&lt; Exit [It] eventually leads to the integration test PipelineRun&#39;s Fail status reported at MR commit status - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:250 @ 04/21/26 17:03:48.565 (514ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:48.565&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:48.566 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Integration PipelineRun is created validates at least one MR note contains the final integration test result [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.15789809">
              <system-err>&gt; Enter [It] validates at least one MR note contains the final integration test result - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:254 @ 04/21/26 17:03:48.566&#xA;&lt; Exit [It] validates at least one MR note contains the final integration test result - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:254 @ 04/21/26 17:03:48.723 (157ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:48.724&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:48.724 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Integration PipelineRun is created merging the PR should be successful [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="1.600358387">
              <system-err>&gt; Enter [It] merging the PR should be successful - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:278 @ 04/21/26 17:03:48.725&#xA;merged result sha: 19213a65f17a86c9e50651c69e317428e69fcefc for MR #17384&#xA;&lt; Exit [It] merging the PR should be successful - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:278 @ 04/21/26 17:03:50.325 (1.6s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:50.325&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:50.325 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Integration PipelineRun is created leads to triggering on push PipelineRun [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.139820174">
              <system-err>&gt; Enter [It] leads to triggering on push PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:288 @ 04/21/26 17:03:50.325&#xA;&lt; Exit [It] leads to triggering on push PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:288 @ 04/21/26 17:03:50.465 (140ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:50.465&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:50.465 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Run integration tests after Merged MR should eventually complete successfully [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.139827985">
              <system-err>&gt; Enter [It] should eventually complete successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:303 @ 04/21/26 17:03:50.465&#xA;PipelineRun my-integration-test-mddg-jqgrb reason: Succeeded&#xA;PipelineRun my-integration-test-gfqd-8994q reason: Succeeded&#xA;&lt; Exit [It] should eventually complete successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:303 @ 04/21/26 17:03:50.605 (140ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:50.605&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:50.605 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Run integration tests after Merged MR validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it pass [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.150818407">
              <system-err>&gt; Enter [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it pass - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:308 @ 04/21/26 17:03:50.606&#xA;&lt; Exit [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it pass - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:308 @ 04/21/26 17:03:50.756 (150ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:50.756&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:50.756 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Run integration tests after Merged MR eventually leads to the integration test PipelineRun&#39;s Pass status reported at MR commit status [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.291278339">
              <system-err>&gt; Enter [It] eventually leads to the integration test PipelineRun&#39;s Pass status reported at MR commit status - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:325 @ 04/21/26 17:03:50.757&#xA;&lt; Exit [It] eventually leads to the integration test PipelineRun&#39;s Pass status reported at MR commit status - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:325 @ 04/21/26 17:03:51.048 (291ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:51.048&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:51.048 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Run integration tests after Merged MR validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it fails [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.140479952">
              <system-err>&gt; Enter [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it fails - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:329 @ 04/21/26 17:03:51.048&#xA;&lt; Exit [It] validates the Integration test scenario PipelineRun is reported to merge request CommitStatus, and it fails - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:329 @ 04/21/26 17:03:51.188 (140ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:51.189&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:51.189 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when Run integration tests after Merged MR eventually leads to the integration test PipelineRun&#39;s Fail status reported at MR commit status [integration-service, gitlab-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="1.915814817">
              <system-err>&gt; Enter [It] eventually leads to the integration test PipelineRun&#39;s Fail status reported at MR commit status - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:346 @ 04/21/26 17:03:51.189&#xA;&lt; Exit [It] eventually leads to the integration test PipelineRun&#39;s Fail status reported at MR commit status - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:346 @ 04/21/26 17:03:51.481 (292ms)&#xA;&gt; Enter [AfterAll] Gitlab with status reporting of Integration tests in the assosiated merge request - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:94 @ 04/21/26 17:03:51.481&#xA;&lt; Exit [AfterAll] Gitlab with status reporting of Integration tests in the assosiated merge request - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:94 @ 04/21/26 17:03:53.105 (1.623s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:53.105&#xA;&lt; Exit [AfterEach] [integration-service-suite Gitlab Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/gitlab-integration-reporting.go:42 @ 04/21/26 17:03:53.105 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [release-pipelines-suite [HACBS-1571]test-release-e2e-push-image-to-pyxis] Post-release verification tests that Release CR is created for the Snapshot [release-pipelines, rh-push-to-external-registry]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite [HACBS-1571]test-release-e2e-push-image-to-pyxis] Post-release verification verifies a release PipelineRun is started and succeeded in managed namespace [release-pipelines, rh-push-to-external-registry]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite [HACBS-1571]test-release-e2e-push-image-to-pyxis] Post-release verification validate the result of task create-pyxis-image contains image ids [release-pipelines, rh-push-to-external-registry]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite [HACBS-1571]test-release-e2e-push-image-to-pyxis] Post-release verification tests that Release CR has completed [release-pipelines, rh-push-to-external-registry]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [release-pipelines-suite [HACBS-1571]test-release-e2e-push-image-to-pyxis] Post-release verification validates that imageIds from task create-pyxis-image exist in Pyxis. [release-pipelines, rh-push-to-external-registry]" classname="Red Hat App Studio E2E tests" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build annotations when component is created with invalid build request annotations handles invalid request annotation [build-service, github, annotations]" classname="Red Hat App Studio E2E tests" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when a new Component with specified custom branch is created does not contain an annotation with a Snapshot Name [integration-service, github-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="32.90746361">
              <system-err>&gt; Enter [BeforeAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:45 @ 04/21/26 16:53:42.486&#xA;Image repository for component test-component-pac-wwsjhk in namespace stat-rep-bzsb do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Build PipelineRun has not been created yet for the component stat-rep-bzsb/test-component-pac-wwsjhk&#xA;&lt; Exit [BeforeAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:45 @ 04/21/26 16:54:15.393 (32.907s)&#xA;&gt; Enter [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:109 @ 04/21/26 16:54:15.393&#xA;&lt; Exit [It] does not contain an annotation with a Snapshot Name - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:109 @ 04/21/26 16:54:15.394 (0s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 16:54:15.394&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 16:54:15.394 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when a new Component with specified custom branch is created should have a related PaC init PR created [integration-service, github-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.351209007">
              <system-err>&gt; Enter [It] should have a related PaC init PR created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:113 @ 04/21/26 16:54:15.394&#xA;&lt; Exit [It] should have a related PaC init PR created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:113 @ 04/21/26 16:54:15.745 (351ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 16:54:15.745&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 16:54:15.745 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when a new Component with specified custom branch is created initialized integration test status is reported to github [integration-service, github-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="0.287802282">
              <system-err>&gt; Enter [It] initialized integration test status is reported to github - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:132 @ 04/21/26 16:54:15.746&#xA;&lt; Exit [It] initialized integration test status is reported to github - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:132 @ 04/21/26 16:54:16.033 (287ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 16:54:16.033&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 16:54:16.033 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when a new Component with specified custom branch is created should lead to build PipelineRun finishing successfully [integration-service, github-status-reporting, custom-branch]" classname="Red Hat App Studio E2E tests" status="passed" time="540.214881206">
              <system-err>&gt; Enter [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:142 @ 04/21/26 16:54:16.034&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: ResolvingTaskRef&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Running&#xA;PipelineRun test-component-pac-wwsjhk-on-pull-request-69nq9 reason: Completed&#xA;&lt; Exit [It] should lead to build PipelineRun finishing successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:142 @ 04/21/26 17:03:16.249 (9m0.214s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:16.249&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:16.249 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when the PaC build pipelineRun run succeeded checks if the BuildPipelineRun have the annotation of chains signed [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.464144291">
              <system-err>&gt; Enter [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:149 @ 04/21/26 17:03:16.249&#xA;&lt; Exit [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:149 @ 04/21/26 17:03:16.713 (464ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:16.713&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:16.713 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when the PaC build pipelineRun run succeeded checks if the Snapshot is created [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.192675875">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:153 @ 04/21/26 17:03:16.714&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:153 @ 04/21/26 17:03:16.906 (192ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:16.906&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:16.906 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when the PaC build pipelineRun run succeeded checks if the Build PipelineRun got annotated with Snapshot name [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.235814177">
              <system-err>&gt; Enter [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:158 @ 04/21/26 17:03:16.907&#xA;&lt; Exit [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:158 @ 04/21/26 17:03:17.142 (236ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:17.142&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:17.142 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when the Snapshot was created should find both the related Integration PipelineRuns [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.43189367">
              <system-err>&gt; Enter [It] should find both the related Integration PipelineRuns - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:164 @ 04/21/26 17:03:17.143&#xA;&lt; Exit [It] should find both the related Integration PipelineRuns - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:164 @ 04/21/26 17:03:17.574 (431ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:17.575&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:17.575 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns are created should eventually complete successfully [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="40.540039605">
              <system-err>&gt; Enter [It] should eventually complete successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:183 @ 04/21/26 17:03:17.575&#xA;PipelineRun my-integration-test-vbdb-psrlc reason: Running&#xA;PipelineRun my-integration-test-vbdb-psrlc reason: Succeeded&#xA;PipelineRun my-integration-test-limt-jsrbb reason: Succeeded&#xA;PipelineRun my-integration-test-ftkx-t68m4 reason: Running&#xA;PipelineRun my-integration-test-ftkx-t68m4 reason: Succeeded&#xA;&lt; Exit [It] should eventually complete successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:183 @ 04/21/26 17:03:58.115 (40.54s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:58.115&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:58.115 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully should lead to Snapshot CR being marked as failed [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.27979971">
              <system-err>&gt; Enter [It] should lead to Snapshot CR being marked as failed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:191 @ 04/21/26 17:03:58.116&#xA;&lt; Exit [It] should lead to Snapshot CR being marked as failed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:191 @ 04/21/26 17:03:58.395 (279ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:58.395&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:58.395 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully eventually leads to the status reported at Checks tab for the successful Integration PipelineRun [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.464496607">
              <system-err>&gt; Enter [It] eventually leads to the status reported at Checks tab for the successful Integration PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:205 @ 04/21/26 17:03:58.396&#xA;&lt; Exit [It] eventually leads to the status reported at Checks tab for the successful Integration PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:205 @ 04/21/26 17:03:58.86 (464ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:58.86&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:58.86 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully eventually leads to the status reported at Checks tab for the failed Integration PipelineRun [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.436678178">
              <system-err>&gt; Enter [It] eventually leads to the status reported at Checks tab for the failed Integration PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:209 @ 04/21/26 17:03:58.861&#xA;&lt; Exit [It] eventually leads to the status reported at Checks tab for the failed Integration PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:209 @ 04/21/26 17:03:59.297 (436ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:59.297&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:59.297 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully eventually leads to the status reported at Checks tab for the optional Integration PipelineRun [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.490079491">
              <system-err>&gt; Enter [It] eventually leads to the status reported at Checks tab for the optional Integration PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:213 @ 04/21/26 17:03:59.298&#xA;&lt; Exit [It] eventually leads to the status reported at Checks tab for the optional Integration PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:213 @ 04/21/26 17:03:59.787 (490ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:59.788&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:59.788 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully checks if the optional Integration Test Scenario status is reported in the Snapshot [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.070704486">
              <system-err>&gt; Enter [It] checks if the optional Integration Test Scenario status is reported in the Snapshot - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:217 @ 04/21/26 17:03:59.788&#xA;&lt; Exit [It] checks if the optional Integration Test Scenario status is reported in the Snapshot - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:217 @ 04/21/26 17:03:59.859 (70ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:59.859&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:59.859 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully checks if the finalizer was removed from the optional Integration PipelineRun [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.070854059">
              <system-err>&gt; Enter [It] checks if the finalizer was removed from the optional Integration PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:232 @ 04/21/26 17:03:59.859&#xA;&lt; Exit [It] checks if the finalizer was removed from the optional Integration PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:232 @ 04/21/26 17:03:59.93 (70ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:59.93&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:03:59.93 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully merging the PR, expected to succeed  [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="2.013487142">
              <system-err>&gt; Enter [It] merging the PR, expected to succeed  - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:236 @ 04/21/26 17:03:59.931&#xA;merged result sha: 3e208801efe5760b880dfdcac0c0988626d8f236 for PR #9428&#xA;&lt; Exit [It] merging the PR, expected to succeed  - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:236 @ 04/21/26 17:04:01.944 (2.013s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:04:01.944&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:04:01.944 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully leads to triggering a push PipelineRun [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="20.209208363">
              <system-err>&gt; Enter [It] leads to triggering a push PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:245 @ 04/21/26 17:04:01.945&#xA;Push PipelineRun has not been created yet for the component stat-rep-bzsb/test-component-pac-wwsjhk&#xA;&lt; Exit [It] leads to triggering a push PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:245 @ 04/21/26 17:04:22.153 (20.209s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:04:22.154&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:04:22.154 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully verifies that Push PipelineRuns completed [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.170362208">
              <system-err>&gt; Enter [It] verifies that Push PipelineRuns completed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:260 @ 04/21/26 17:04:22.154&#xA;PipelineRun my-integration-test-vbdb-psrlc reason: Succeeded&#xA;PipelineRun my-integration-test-limt-jsrbb reason: Succeeded&#xA;&lt; Exit [It] verifies that Push PipelineRuns completed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:260 @ 04/21/26 17:04:22.324 (170ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:04:22.324&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:04:22.324 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully validates the Integration test scenario PipelineRun is reported to merge request CheckRuns, and it pass [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.436214898">
              <system-err>&gt; Enter [It] validates the Integration test scenario PipelineRun is reported to merge request CheckRuns, and it pass - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:265 @ 04/21/26 17:04:22.325&#xA;&lt; Exit [It] validates the Integration test scenario PipelineRun is reported to merge request CheckRuns, and it pass - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:265 @ 04/21/26 17:04:22.76 (436ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:04:22.761&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:04:22.761 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns completes successfully eventually leads to the status reported at Checks tab for the failed Integration PipelineRun [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.496724211">
              <system-err>&gt; Enter [It] eventually leads to the status reported at Checks tab for the failed Integration PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:270 @ 04/21/26 17:04:22.761&#xA;&lt; Exit [It] eventually leads to the status reported at Checks tab for the failed Integration PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:270 @ 04/21/26 17:04:23.258 (496ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:04:23.258&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:04:23.258 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when The git-provider annotation is missing should set the git-reporting-failure annotation correctly [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="0.219588695">
              <system-err>&gt; Enter [It] should set the git-reporting-failure annotation correctly - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:276 @ 04/21/26 17:04:23.259&#xA;&lt; Exit [It] should set the git-reporting-failure annotation correctly - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:276 @ 04/21/26 17:04:23.478 (219ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:04:23.478&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:04:23.478 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when build pipelinerun fails build pipelinerun is created but fails [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="17.153391326">
              <system-err>&gt; Enter [It] build pipelinerun is created but fails - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:323 @ 04/21/26 17:04:23.479&#xA;Waiting for pipeline &#34;failing-build-plr-vbmy&#34; to finish&#xA;&lt; Exit [It] build pipelinerun is created but fails - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:323 @ 04/21/26 17:04:40.632 (17.153s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:04:40.632&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:04:40.632 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when build pipelinerun fails build pipelinerun failure is reported to integration test checkRun [integration-service, github-status-reporting]" classname="Red Hat App Studio E2E tests" status="passed" time="25.191464525">
              <system-err>&gt; Enter [It] build pipelinerun failure is reported to integration test checkRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:368 @ 04/21/26 17:04:40.632&#xA;failed to check expected checkRun text, actual text is %!s(&lt;nil&gt;): &#xA;%!(EXTRA string=build pipelinerun stat-rep-bzsb/failing-build-plr-vbmy is still in progress)&#xA;&lt; Exit [It] build pipelinerun failure is reported to integration test checkRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:368 @ 04/21/26 17:05:01.243 (20.611s)&#xA;&gt; Enter [AfterAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:92 @ 04/21/26 17:05:01.243&#xA;&lt; Exit [AfterAll] with status reporting of Integration tests in CheckRuns - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:92 @ 04/21/26 17:05:05.824 (4.58s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:05:05.824&#xA;&lt; Exit [AfterEach] [integration-service-suite Status Reporting of Integration tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/status-reporting-to-pullrequest.go:42 @ 04/21/26 17:05:05.824 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when a new Component is created triggers a build PipelineRun [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="53.664156596">
              <system-err>&gt; Enter [BeforeAll] with happy path for general flow of Integration service - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:52 @ 04/21/26 16:53:42.378&#xA;Image repository for component test-component-pac-fxckrd in namespace integration1-doty do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [BeforeAll] with happy path for general flow of Integration service - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:52 @ 04/21/26 16:53:55.185 (12.807s)&#xA;&gt; Enter [It] triggers a build PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:85 @ 04/21/26 16:53:55.186&#xA;no pipelinerun found for component test-component-pac-fxckrd (application: integ-app-ydav, namespace: integration1-doty)no pipelinerun found for component test-component-pac-fxckrd (application: integ-app-ydav, namespace: integration1-doty)&#xA;&lt; Exit [It] triggers a build PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:85 @ 04/21/26 16:54:36.041 (40.855s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 16:54:36.041&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 16:54:36.041 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when a new Component is created verifies if the build PipelineRun contains the finalizer [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.071991468">
              <system-err>&gt; Enter [It] verifies if the build PipelineRun contains the finalizer - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:90 @ 04/21/26 16:54:36.042&#xA;&lt; Exit [It] verifies if the build PipelineRun contains the finalizer - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:90 @ 04/21/26 16:54:36.113 (72ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 16:54:36.113&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 16:54:36.113 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when a new Component is created waits for build PipelineRun to succeed [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="540.203819209">
              <system-err>&gt; Enter [It] waits for build PipelineRun to succeed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:101 @ 04/21/26 16:54:36.114&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 found for Component integration1-doty/test-component-pac-fxckrd&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: ResolvingTaskRef&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun test-component-pac-fxckrd-on-pull-request-qqrg9 reason: Running&#xA;PipelineRun my-integration-test-vohi-7kfx6 reason: Running&#xA;PipelineRun my-integration-test-vohi-7kfx6 reason: Succeeded&#xA;&lt; Exit [It] waits for build PipelineRun to succeed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:101 @ 04/21/26 17:03:36.317 (9m0.203s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:36.318&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:36.318 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when a new Component is created should have a related PaC init PR created [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.644250815">
              <system-err>&gt; Enter [It] should have a related PaC init PR created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:107 @ 04/21/26 17:03:36.318&#xA;&lt; Exit [It] should have a related PaC init PR created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:107 @ 04/21/26 17:03:36.962 (644ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:36.962&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:36.962 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if the BuildPipelineRun have the annotation of chains signed [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.200180576">
              <system-err>&gt; Enter [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:128 @ 04/21/26 17:03:36.963&#xA;&lt; Exit [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:128 @ 04/21/26 17:03:37.163 (200ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:37.163&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:37.163 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if the Snapshot is created [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.257704338">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:132 @ 04/21/26 17:03:37.163&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:132 @ 04/21/26 17:03:37.421 (257ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:37.421&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:37.421 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if the Build PipelineRun got annotated with Snapshot name [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.291140531">
              <system-err>&gt; Enter [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:137 @ 04/21/26 17:03:37.421&#xA;&lt; Exit [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:137 @ 04/21/26 17:03:37.712 (291ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:37.712&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:37.712 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when the build pipelineRun run succeeded verifies that the finalizer has been removed from the build pipelinerun [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.11205248">
              <system-err>&gt; Enter [It] verifies that the finalizer has been removed from the build pipelinerun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:141 @ 04/21/26 17:03:37.713&#xA;&lt; Exit [It] verifies that the finalizer has been removed from the build pipelinerun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:141 @ 04/21/26 17:03:37.824 (112ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:37.825&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:37.825 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if all of the integrationPipelineRuns passed [integration-service, slow]" classname="Red Hat App Studio E2E tests" status="passed" time="0.22927206">
              <system-err>&gt; Enter [It] checks if all of the integrationPipelineRuns passed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:154 @ 04/21/26 17:03:37.825&#xA;Integration test scenario my-integration-test-vohi is found&#xA;PipelineRun my-integration-test-vohi-7kfx6 reason: Succeeded&#xA;&lt; Exit [It] checks if all of the integrationPipelineRuns passed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:154 @ 04/21/26 17:03:38.054 (229ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:38.054&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:38.054 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if the passed status of integration test is reported in the Snapshot [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.069592133">
              <system-err>&gt; Enter [It] checks if the passed status of integration test is reported in the Snapshot - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:158 @ 04/21/26 17:03:38.055&#xA;&lt; Exit [It] checks if the passed status of integration test is reported in the Snapshot - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:158 @ 04/21/26 17:03:38.124 (69ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:38.124&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:38.124 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if the skipped integration test is absent from the Snapshot&#39;s status annotation [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.069525812">
              <system-err>&gt; Enter [It] checks if the skipped integration test is absent from the Snapshot&#39;s status annotation - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:173 @ 04/21/26 17:03:38.125&#xA;&lt; Exit [It] checks if the skipped integration test is absent from the Snapshot&#39;s status annotation - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:173 @ 04/21/26 17:03:38.194 (69ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:38.194&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:38.194 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if the finalizer was removed from all of the related Integration pipelineRuns [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.250425297">
              <system-err>&gt; Enter [It] checks if the finalizer was removed from all of the related Integration pipelineRuns - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:183 @ 04/21/26 17:03:38.195&#xA;Integration test scenario my-integration-test-vohi is found&#xA;&lt; Exit [It] checks if the finalizer was removed from all of the related Integration pipelineRuns - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:183 @ 04/21/26 17:03:38.445 (250ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:38.445&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:38.445 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service creates a ReleasePlan [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.374363204">
              <system-err>&gt; Enter [It] creates a ReleasePlan - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:188 @ 04/21/26 17:03:38.445&#xA;IntegrationTestScenario my-integration-test-vohi is found&#xA;IntegrationTestScenario skipped-its is found&#xA;&lt; Exit [It] creates a ReleasePlan - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:188 @ 04/21/26 17:03:38.819 (374ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:38.82&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:38.82 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service creates an snapshot of push event [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.074095065">
              <system-err>&gt; Enter [It] creates an snapshot of push event - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:198 @ 04/21/26 17:03:38.82&#xA;&lt; Exit [It] creates an snapshot of push event - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:198 @ 04/21/26 17:03:38.894 (74ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:38.894&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:38.894 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when An snapshot of push event is created checks if the global candidate is updated after push event [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.14056957">
              <system-err>&gt; Enter [It] checks if the global candidate is updated after push event - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:205 @ 04/21/26 17:03:38.895&#xA;&lt; Exit [It] checks if the global candidate is updated after push event - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:205 @ 04/21/26 17:03:39.035 (140ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:39.035&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:39.035 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when An snapshot of push event is created checks if all of the integrationPipelineRuns created by push event passed [integration-service, slow]" classname="Red Hat App Studio E2E tests" status="passed" time="20.138654901">
              <system-err>&gt; Enter [It] checks if all of the integrationPipelineRuns created by push event passed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:218 @ 04/21/26 17:03:39.036&#xA;Integration test scenario my-integration-test-vohi is found&#xA;PipelineRun has not been created yet for test scenario %s and snapshot %s/%s my-integration-test-vohi integration1-doty snapshot-sample-crkf&#xA;PipelineRun my-integration-test-vohi-sh4bm reason: Succeeded&#xA;&lt; Exit [It] checks if all of the integrationPipelineRuns created by push event passed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:218 @ 04/21/26 17:03:59.174 (20.138s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:59.174&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:03:59.174 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when An snapshot of push event is created checks if a Release is created successfully [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="4.085008519">
              <system-err>&gt; Enter [It] checks if a Release is created successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:222 @ 04/21/26 17:03:59.175&#xA;&lt; Exit [It] checks if a Release is created successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:222 @ 04/21/26 17:03:59.243 (68ms)&#xA;&gt; Enter [AfterAll] with happy path for general flow of Integration service - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:68 @ 04/21/26 17:03:59.243&#xA;&lt; Exit [AfterAll] with happy path for general flow of Integration service - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:68 @ 04/21/26 17:04:03.259 (4.016s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:04:03.26&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:04:03.26 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail triggers a build PipelineRun [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="353.519843603">
              <system-err>&gt; Enter [BeforeAll] with an integration test fail - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:234 @ 04/21/26 17:04:03.26&#xA;Image repository for component test-component-pac-supelc in namespace integration2-zxhy do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [BeforeAll] with an integration test fail - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:234 @ 04/21/26 17:04:16.293 (13.032s)&#xA;&gt; Enter [It] triggers a build PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:266 @ 04/21/26 17:04:16.293&#xA;no pipelinerun found for component test-component-pac-supelc (application: integ-app-mbyf, namespace: integration2-zxhy)PipelineRun test-component-pac-supelc-on-pull-request-9pkxv found for Component integration2-zxhy/test-component-pac-supelc&#xA;PipelineRun test-component-pac-supelc-on-pull-request-9pkxv reason: ResolvingTaskRef&#xA;PipelineRun test-component-pac-supelc-on-pull-request-9pkxv reason: ResolvingTaskRef&#xA;PipelineRun test-component-pac-supelc-on-pull-request-9pkxv reason: Running&#xA;PipelineRun test-component-pac-supelc-on-pull-request-9pkxv reason: Running&#xA;PipelineRun test-component-pac-supelc-on-pull-request-9pkxv reason: Running&#xA;PipelineRun test-component-pac-supelc-on-pull-request-9pkxv reason: Running&#xA;PipelineRun test-component-pac-supelc-on-pull-request-9pkxv reason: Running&#xA;PipelineRun test-component-pac-supelc-on-pull-request-9pkxv reason: Running&#xA;PipelineRun test-component-pac-supelc-on-pull-request-9pkxv reason: Running&#xA;PipelineRun test-component-pac-supelc-on-pull-request-9pkxv reason: Running&#xA;PipelineRun test-component-pac-supelc-on-pull-request-9pkxv reason: Running&#xA;PipelineRun test-component-pac-supelc-on-pull-request-9pkxv reason: Running&#xA;PipelineRun test-component-pac-supelc-on-pull-request-9pkxv reason: Running&#xA;PipelineRun test-component-pac-supelc-on-pull-request-9pkxv reason: Running&#xA;PipelineRun test-component-pac-supelc-on-pull-request-9pkxv reason: Running&#xA;PipelineRun test-component-pac-supelc-on-pull-request-9pkxv reason: Running&#xA;PipelineRun my-integration-test-tiel-lr4j6 reason: Succeeded&#xA;&lt; Exit [It] triggers a build PipelineRun - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:266 @ 04/21/26 17:09:56.78 (5m40.487s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:56.78&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:56.78 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail should have a related PaC init PR created [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.385378539">
              <system-err>&gt; Enter [It] should have a related PaC init PR created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:273 @ 04/21/26 17:09:56.781&#xA;&lt; Exit [It] should have a related PaC init PR created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:273 @ 04/21/26 17:09:57.166 (385ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:57.166&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:57.166 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail checks if the BuildPipelineRun have the annotation of chains signed [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.141568167">
              <system-err>&gt; Enter [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:292 @ 04/21/26 17:09:57.166&#xA;&lt; Exit [It] checks if the BuildPipelineRun have the annotation of chains signed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:292 @ 04/21/26 17:09:57.308 (141ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:57.308&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:57.308 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail checks if the Snapshot is created [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.069148093">
              <system-err>&gt; Enter [It] checks if the Snapshot is created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:296 @ 04/21/26 17:09:57.308&#xA;&lt; Exit [It] checks if the Snapshot is created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:296 @ 04/21/26 17:09:57.377 (69ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:57.377&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:57.377 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail checks if the Build PipelineRun got annotated with Snapshot name [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.140047668">
              <system-err>&gt; Enter [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:301 @ 04/21/26 17:09:57.378&#xA;&lt; Exit [It] checks if the Build PipelineRun got annotated with Snapshot name - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:301 @ 04/21/26 17:09:57.518 (140ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:57.518&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:57.518 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail checks if all of the integrationPipelineRuns finished [integration-service, slow]" classname="Red Hat App Studio E2E tests" status="passed" time="0.137156186">
              <system-err>&gt; Enter [It] checks if all of the integrationPipelineRuns finished - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:305 @ 04/21/26 17:09:57.518&#xA;Integration test scenario my-integration-test-tiel is found&#xA;PipelineRun my-integration-test-tiel-lr4j6 reason: Succeeded&#xA;&lt; Exit [It] checks if all of the integrationPipelineRuns finished - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:305 @ 04/21/26 17:09:57.655 (137ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:57.655&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:57.655 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail checks if the failed status of integration test is reported in the Snapshot [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.069942302">
              <system-err>&gt; Enter [It] checks if the failed status of integration test is reported in the Snapshot - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:309 @ 04/21/26 17:09:57.656&#xA;&lt; Exit [It] checks if the failed status of integration test is reported in the Snapshot - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:309 @ 04/21/26 17:09:57.725 (70ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:57.726&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:57.726 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail checks if the skipped integration test is absent from the Snapshot&#39;s status annotation [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.069600374">
              <system-err>&gt; Enter [It] checks if the skipped integration test is absent from the Snapshot&#39;s status annotation - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:324 @ 04/21/26 17:09:57.726&#xA;&lt; Exit [It] checks if the skipped integration test is absent from the Snapshot&#39;s status annotation - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:324 @ 04/21/26 17:09:57.795 (69ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:57.796&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:57.796 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail checks if snapshot is marked as failed [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.068745762">
              <system-err>&gt; Enter [It] checks if snapshot is marked as failed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:334 @ 04/21/26 17:09:57.796&#xA;&lt; Exit [It] checks if snapshot is marked as failed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:334 @ 04/21/26 17:09:57.864 (68ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:57.865&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:57.865 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail checks if the finalizer was removed from all of the related Integration pipelineRuns [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.136453617">
              <system-err>&gt; Enter [It] checks if the finalizer was removed from all of the related Integration pipelineRuns - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:340 @ 04/21/26 17:09:57.865&#xA;Integration test scenario my-integration-test-tiel is found&#xA;&lt; Exit [It] checks if the finalizer was removed from all of the related Integration pipelineRuns - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:340 @ 04/21/26 17:09:58.001 (136ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:58.001&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:58.001 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail creates a new IntegrationTestScenario [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.07660961">
              <system-err>&gt; Enter [It] creates a new IntegrationTestScenario - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:344 @ 04/21/26 17:09:58.002&#xA;&lt; Exit [It] creates a new IntegrationTestScenario - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:344 @ 04/21/26 17:09:58.078 (76ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:58.078&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:58.078 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail updates the Snapshot with the re-run label for the new scenario [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.075208304">
              <system-err>&gt; Enter [It] updates the Snapshot with the re-run label for the new scenario - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:349 @ 04/21/26 17:09:58.079&#xA;&lt; Exit [It] updates the Snapshot with the re-run label for the new scenario - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:349 @ 04/21/26 17:09:58.154 (75ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:58.154&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:58.154 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail when An snapshot is updated with a re-run label for a given scenario checks if the new integration pipelineRun started [integration-service, slow]" classname="Red Hat App Studio E2E tests" status="passed" time="0.070125057">
              <system-err>&gt; Enter [It] checks if the new integration pipelineRun started - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:358 @ 04/21/26 17:09:58.154&#xA;&lt; Exit [It] checks if the new integration pipelineRun started - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:358 @ 04/21/26 17:09:58.224 (70ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:58.224&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:58.224 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail when An snapshot is updated with a re-run label for a given scenario checks if the re-run label was removed from the Snapshot [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.068807224">
              <system-err>&gt; Enter [It] checks if the re-run label was removed from the Snapshot - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:364 @ 04/21/26 17:09:58.225&#xA;&lt; Exit [It] checks if the re-run label was removed from the Snapshot - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:364 @ 04/21/26 17:09:58.293 (69ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:58.293&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:09:58.293 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail when An snapshot is updated with a re-run label for a given scenario checks if all integration pipelineRuns finished successfully [integration-service, slow]" classname="Red Hat App Studio E2E tests" status="passed" time="20.271892567">
              <system-err>&gt; Enter [It] checks if all integration pipelineRuns finished successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:378 @ 04/21/26 17:09:58.294&#xA;Integration test scenario my-integration-test-bcab is found&#xA;PipelineRun my-integration-test-bcab-lkh27 reason: ResolvingPipelineRef&#xA;PipelineRun my-integration-test-bcab-lkh27 reason: Succeeded&#xA;Integration test scenario my-integration-test-tiel is found&#xA;PipelineRun my-integration-test-tiel-lr4j6 reason: Succeeded&#xA;&lt; Exit [It] checks if all integration pipelineRuns finished successfully - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:378 @ 04/21/26 17:10:18.565 (20.272s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:10:18.566&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:10:18.566 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail when An snapshot is updated with a re-run label for a given scenario checks if the name of the re-triggered pipelinerun is reported in the Snapshot [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.13837346">
              <system-err>&gt; Enter [It] checks if the name of the re-triggered pipelinerun is reported in the Snapshot - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:382 @ 04/21/26 17:10:18.566&#xA;&lt; Exit [It] checks if the name of the re-triggered pipelinerun is reported in the Snapshot - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:382 @ 04/21/26 17:10:18.704 (138ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:10:18.704&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:10:18.704 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail when An snapshot is updated with a re-run label for a given scenario checks if snapshot is still marked as failed [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.068694562">
              <system-err>&gt; Enter [It] checks if snapshot is still marked as failed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:399 @ 04/21/26 17:10:18.705&#xA;&lt; Exit [It] checks if snapshot is still marked as failed - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:399 @ 04/21/26 17:10:18.773 (68ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:10:18.773&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:10:18.773 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail creates an snapshot of push event [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="0.073386743">
              <system-err>&gt; Enter [It] creates an snapshot of push event - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:406 @ 04/21/26 17:10:18.774&#xA;&lt; Exit [It] creates an snapshot of push event - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:406 @ 04/21/26 17:10:18.847 (73ms)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:10:18.847&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:10:18.847 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [integration-service-suite Integration Service E2E tests] with an integration test fail when An snapshot of push event is created checks no Release CRs are created [integration-service]" classname="Red Hat App Studio E2E tests" status="passed" time="4.058325776">
              <system-err>&gt; Enter [It] checks no Release CRs are created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:413 @ 04/21/26 17:10:18.848&#xA;&lt; Exit [It] checks no Release CRs are created - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:413 @ 04/21/26 17:10:18.915 (68ms)&#xA;&gt; Enter [AfterAll] with an integration test fail - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:250 @ 04/21/26 17:10:18.916&#xA;&lt; Exit [AfterAll] with an integration test fail - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:250 @ 04/21/26 17:10:22.906 (3.99s)&#xA;&gt; Enter [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:10:22.906&#xA;&lt; Exit [AfterEach] [integration-service-suite Integration Service E2E tests] - /tmp/tmp.YkUEHMxtIX/tests/integration-service/integration.go:49 @ 04/21/26 17:10:22.906 (0s)&#xA;</system-err>
          </testcase>
      </testsuite>
  </testsuites>