./mage -v ci:teste2e Running target: CI:TestE2E I1016 16:30:09.392175 23836 magefile.go:521] setting up new custom bundle for testing... I1016 16:30:09.862482 23836 util.go:521] found credentials for image ref quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1760632209-uhjk -> user: redhat-appstudio-qe+redhat_appstudio_quality Creating Tekton Bundle: - Added Pipeline: docker-build to image I1016 16:30:11.790550 23836 bundle.go:57] image digest for a new tekton bundle quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1760632209-uhjk: quay.io/redhat-appstudio-qe/test-images@sha256:6678c75b600a500e0a046fa8c99106ea65acdca8c7e756b3ee23a96ac750173a I1016 16:30:11.790572 23836 magefile.go:527] To use the custom docker bundle locally, run below cmd: export CUSTOM_DOCKER_BUILD_PIPELINE_BUNDLE=quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1760632209-uhjk I1016 16:30:11.790590 23836 e2e_repo.go:347] checking if repository is e2e-tests I1016 16:30:11.790596 23836 release_service.go:50] checking if repository is release-service I1016 16:30:13.109008 23836 release_service_catalog.go:104] checking if repository is release-service-catalog I1016 16:30:13.109026 23836 integration_service.go:49] checking if repository is integration-service I1016 16:30:13.109030 23836 image_controller.go:49] checking if repository is image-controller I1016 16:30:13.109034 23836 build_service.go:49] checking if repository is build-service I1016 16:30:13.109038 23836 build_service.go:30] require sprayproxy registering is set to TRUE I1016 16:30:13.109040 23836 build_service.go:33] setting 'build-service' test label exec: go "install" "-mod=mod" "github.com/onsi/ginkgo/v2/ginkgo" go: downloading github.com/go-task/slim-sprig/v3 v3.0.0 go: downloading github.com/google/pprof v0.0.0-20241210010833-40e02aabc2ad I1016 16:30:16.867233 23836 types.go:155] The following rules have matched build-service repo CI Workflow Rule. I1016 16:30:16.867252 23836 types.go:180] Will apply rules exec: ginkgo "--seed=1760632209" "--timeout=1h30m0s" "--grace-period=30s" "--output-interceptor-mode=none" "--label-filter=build-service" "--no-color" "--json-report=e2e-report.json" "--junit-report=e2e-report.xml" "--procs=20" "--nodes=20" "--p" "--output-dir=/workspace/artifact-dir" "./cmd" "--" Running Suite: Red Hat App Studio E2E tests - /tmp/tmp.0kRxSp7DEk/cmd ===================================================================== Random Seed: 1760632209 Will run 112 of 389 specs Running in parallel across 20 processes SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params when context points to a file [build-templates] /tmp/tmp.0kRxSp7DEk/tests/build/tkn-bundle.go:177 ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params creates Tekton bundles from specific context [build-templates] /tmp/tmp.0kRxSp7DEk/tests/build/tkn-bundle.go:188 ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params when context is the root directory [build-templates] /tmp/tmp.0kRxSp7DEk/tests/build/tkn-bundle.go:198 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/tkn-bundle.go:207 ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params creates Tekton bundles when using negation [build-templates] /tmp/tmp.0kRxSp7DEk/tests/build/tkn-bundle.go:217 ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params allows overriding HOME environment variable [build-templates] /tmp/tmp.0kRxSp7DEk/tests/build/tkn-bundle.go:227 ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params allows overriding STEP image [build-templates] /tmp/tmp.0kRxSp7DEk/tests/build/tkn-bundle.go:236 ------------------------------ SSSSSSSSSSSSS ------------------------------ P [PENDING] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci 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] /tmp/tmp.0kRxSp7DEk/tests/build/build_templates.go:489 ------------------------------ SSSSSSSSSS ------------------------------ P [PENDING] [build-service-suite Build templates E2E test] HACBS pipelines scenario sample-python-basic-oci 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] /tmp/tmp.0kRxSp7DEk/tests/build/build_templates.go:489 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/multi-platform.go:120 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/multi-platform.go:124 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/multi-platform.go:127 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/multi-platform.go:148 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/multi-platform.go:152 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/multi-platform.go:251 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/multi-platform.go:255 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/multi-platform.go:259 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/multi-platform.go:263 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/multi-platform.go:267 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/multi-platform.go:341 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/multi-platform.go:345 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/multi-platform.go:349 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/multi-platform.go:353 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/multi-platform.go:357 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/multi-platform.go:432 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/multi-platform.go:436 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/multi-platform.go:440 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/multi-platform.go:444 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/build/multi-platform.go:448 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/release/pipelines/release_to_github.go:139 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/release/pipelines/release_to_github.go:149 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/release/pipelines/release_to_github.go:182 ------------------------------ P [PENDING] [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] /tmp/tmp.0kRxSp7DEk/tests/release/pipelines/release_to_github.go:193 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS•••••••••••••••••••••••• ------------------------------ P [PENDING] [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, pac-build, secret-lookup] /tmp/tmp.0kRxSp7DEk/tests/build/build.go:1118 ------------------------------ •••••••••••••••••• ------------------------------ • [FAILED] [736.632 seconds] [build-service-suite Build service E2E tests] test of component update with renovate github when components are created in same namespace [It] the PipelineRun should eventually finish successfully for parent component [build-service, renovate, multi-component] /tmp/tmp.0kRxSp7DEk/tests/build/build.go:1469 Timeline >> PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: PipelineRunStopping PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: PipelineRunStopping PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: PipelineRunStopping PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: PipelineRunStopping PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: PipelineRunStopping PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: PipelineRunStopping PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: PipelineRunStopping PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: PipelineRunStopping PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: PipelineRunStopping PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: PipelineRunStopping PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: PipelineRunStopping PipelineRun gh-multi-component-parent-bdil-on-pull-request-77pcx reason: Failed attempt 1/3: PipelineRun "gh-multi-component-parent-bdil-on-pull-request-77pcx" failed: pod: gh-multi-component-parent-bdil-on-pull-request-77pcx-init-pod | init container: prepare 2025/10/16 16:33:30 Entrypoint initialization pod: gh-multi-component-parent-bdil-on-pull-request-77pcx-init-pod | init container: place-scripts 2025/10/16 16:33:31 Decoded script /tekton/scripts/script-0-tgh4g pod: gh-multi-component-parent-bdil-on-pull-request-77pcx-init-pod | container step-init: Build Initialize: quay.io/redhat-appstudio-qe/build-e2e-qjqo/gh-multi-component-parent-bdil:on-pr-bb87836646a184f7b1678533fbc5e3298c3636ae Determine if Image Already Exists PipelineRun gh-multi-component-parent-bdil-on-pull-request-vszrc reason: PipelineRun gh-multi-component-parent-bdil-on-pull-request-vszrc reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-bdil-on-pull-request-vszrc reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-vszrc reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-vszrc reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-vszrc reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-vszrc reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-vszrc reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-vszrc reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-vszrc reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-vszrc reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-vszrc reason: Failed attempt 2/3: PipelineRun "gh-multi-component-parent-bdil-on-pull-request-vszrc" failed: pod: gh-multi-component-parent-bdil-on-pull-request-vszrc-init-pod | init container: prepare 2025/10/16 16:38:42 Entrypoint initialization pod: gh-multi-component-parent-bdil-on-pull-request-vszrc-init-pod | init container: place-scripts 2025/10/16 16:38:44 Decoded script /tekton/scripts/script-0-7xqw4 pod: gh-multi-component-parent-bdil-on-pull-request-vszrc-init-pod | container step-init: Build Initialize: quay.io/redhat-appstudio-qe/build-e2e-qjqo/gh-multi-component-parent-bdil:on-pr-8d937bd308e90687c34529f0788faba0a09226bd Determine if Image Already Exists PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Running PipelineRun gh-multi-component-parent-bdil-on-pull-request-pqlhn reason: Failed attempt 3/3: PipelineRun "gh-multi-component-parent-bdil-on-pull-request-pqlhn" failed: pod: gh-multi-component-parent-bdil-on-pull-request-pqlhn-init-pod | init container: prepare 2025/10/16 16:41:13 Entrypoint initialization pod: gh-multi-component-parent-bdil-on-pull-request-pqlhn-init-pod | init container: place-scripts 2025/10/16 16:41:15 Decoded script /tekton/scripts/script-0-wj8pt pod: gh-multi-component-parent-bdil-on-pull-request-pqlhn-init-pod | container step-init: Build Initialize: quay.io/redhat-appstudio-qe/build-e2e-qjqo/gh-multi-component-parent-bdil:on-pr-ed91d3e4ec019d8ca7d2051800c9d7c34cc8ca67 Determine if Image Already Exists [FAILED] in [It] - /tmp/tmp.0kRxSp7DEk/tests/build/build.go:1470 @ 10/16/25 16:44:51.031 << Timeline [FAILED] Expected success, but got an error: <*errors.errorString | 0xc001498040>: pod: gh-multi-component-parent-bdil-on-pull-request-pqlhn-init-pod | init container: prepare 2025/10/16 16:41:13 Entrypoint initialization pod: gh-multi-component-parent-bdil-on-pull-request-pqlhn-init-pod | init container: place-scripts 2025/10/16 16:41:15 Decoded script /tekton/scripts/script-0-wj8pt pod: gh-multi-component-parent-bdil-on-pull-request-pqlhn-init-pod | container step-init: Build Initialize: quay.io/redhat-appstudio-qe/build-e2e-qjqo/gh-multi-component-parent-bdil:on-pr-ed91d3e4ec019d8ca7d2051800c9d7c34cc8ca67 Determine if Image Already Exists { s: "\n pod: gh-multi-component-parent-bdil-on-pull-request-pqlhn-init-pod | init container: prepare\n2025/10/16 16:41:13 Entrypoint initialization\n\n pod: gh-multi-component-parent-bdil-on-pull-request-pqlhn-init-pod | init container: place-scripts\n2025/10/16 16:41:15 Decoded script /tekton/scripts/script-0-wj8pt\n\npod: gh-multi-component-parent-bdil-on-pull-request-pqlhn-init-pod | container step-init: \nBuild Initialize: quay.io/redhat-appstudio-qe/build-e2e-qjqo/gh-multi-component-parent-bdil:on-pr-ed91d3e4ec019d8ca7d2051800c9d7c34cc8ca67\n\nDetermine if Image Already Exists\n", } In [It] at: /tmp/tmp.0kRxSp7DEk/tests/build/build.go:1470 @ 10/16/25 16:44:51.031 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSS•••••••••••••••••••••••••••••••••••••••••••• Summarizing 1 Failure: [FAIL] [build-service-suite Build service E2E tests] test of component update with renovate github when components are created in same namespace [It] the PipelineRun should eventually finish successfully for parent component [build-service, renovate, multi-component] /tmp/tmp.0kRxSp7DEk/tests/build/build.go:1470 Ran 87 of 389 Specs in 1971.062 seconds FAIL! -- 86 Passed | 1 Failed | 34 Pending | 268 Skipped Ginkgo ran 1 suite in 34m23.391823811s Test Suite Failed E1016 17:04:40.273660 23836 types.go:186] Failed to execute rule: build-service repo CI Workflow Rule: Execute the full workflow for e2e-tests repo in CI Error: running "ginkgo --seed=1760632209 --timeout=1h30m0s --grace-period=30s --output-interceptor-mode=none --label-filter=build-service --no-color --json-report=e2e-report.json --junit-report=e2e-report.xml --procs=20 --nodes=20 --p --output-dir=/workspace/artifact-dir ./cmd --" failed with exit code 1 make: *** [Makefile:25: ci/test/e2e] Error 1