./mage -v ci:teste2e Running target: CI:TestE2E I1016 13:18:31.555256 23959 magefile.go:521] setting up new custom bundle for testing... I1016 13:18:33.868425 23959 util.go:521] found credentials for image ref quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1760620713-zxne -> user: redhat-appstudio-qe+redhat_appstudio_quality Creating Tekton Bundle: - Added Pipeline: docker-build to image I1016 13:18:36.181999 23959 bundle.go:57] image digest for a new tekton bundle quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1760620713-zxne: quay.io/redhat-appstudio-qe/test-images@sha256:b3de03a89f82a4c3de6ca283a71e711a6cc492ff39df401f700718b707b99ba5 I1016 13:18:36.182077 23959 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-1760620713-zxne I1016 13:18:36.182108 23959 image_controller.go:49] checking if repository is image-controller I1016 13:18:36.182119 23959 build_service.go:49] checking if repository is build-service I1016 13:18:36.182126 23959 build_service.go:30] require sprayproxy registering is set to TRUE I1016 13:18:36.182132 23959 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 13:18:39.789911 23959 e2e_repo.go:347] checking if repository is e2e-tests I1016 13:18:39.789932 23959 release_service.go:50] checking if repository is release-service I1016 13:18:41.196113 23959 release_service_catalog.go:104] checking if repository is release-service-catalog I1016 13:18:41.196136 23959 integration_service.go:49] checking if repository is integration-service I1016 13:18:41.196145 23959 types.go:155] The following rules have matched build-service repo CI Workflow Rule. I1016 13:18:41.196150 23959 types.go:180] Will apply rules exec: ginkgo "--seed=1760620711" "--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.yvmViwwG3E/cmd ===================================================================== Random Seed: 1760620711 Will run 112 of 389 specs Running in parallel across 20 processes SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ 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.yvmViwwG3E/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-oci-ta should have Pipeline Logs [build, build-templates, HACBS, pipeline-service, pipeline] /tmp/tmp.yvmViwwG3E/tests/build/build_templates.go:489 ------------------------------ SSSSS ------------------------------ 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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/tests/build/multi-platform.go:448 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ 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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/tests/release/pipelines/release_to_github.go:193 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params when context points to a file [build-templates] /tmp/tmp.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/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.yvmViwwG3E/tests/build/tkn-bundle.go:236 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS•••••••••••••••••••••••• ------------------------------ 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.yvmViwwG3E/tests/build/build.go:1118 ------------------------------ •••••••••••••••••••••••••••••••••••••• ------------------------------ • [FAILED] [303.851 seconds] [build-service-suite Build service E2E tests] test of component update with renovate gitlab when components are created in same namespace [It] the PipelineRun should eventually finish successfully for parent component [build-service, renovate, multi-component] /tmp/tmp.yvmViwwG3E/tests/build/build.go:1469 Timeline >> PipelineRun gl-multi-component-parent-vaql-on-pull-request-jpkv5 reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-vaql-on-pull-request-jpkv5 reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-vaql-on-pull-request-jpkv5 reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-vaql-on-pull-request-jpkv5 reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-vaql-on-pull-request-jpkv5 reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-vaql-on-pull-request-jpkv5 reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-vaql-on-pull-request-jpkv5 reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-vaql-on-pull-request-jpkv5 reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-vaql-on-pull-request-jpkv5 reason: Cancelled attempt 1/3: PipelineRun "gl-multi-component-parent-vaql-on-pull-request-jpkv5" failed: PipelineRun has not been created yet for the Component build-e2e-ieah/gl-multi-component-parent-vaql PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: Running PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: Running PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: Running PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: Running PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: Running PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: Running PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: Running PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: Running PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: Running PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: Running PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: Running PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: Running PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: Running PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: Running PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: Running PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: Running PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: Running PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: Running PipelineRun gl-multi-component-parent-vaql-on-pull-request-shhqj reason: Completed [FAILED] in [It] - /tmp/tmp.yvmViwwG3E/tests/build/build.go:1478 @ 10/16/25 13:39:05.367 << Timeline [FAILED] pipelinerun status results: [] Expected : not to be empty In [It] at: /tmp/tmp.yvmViwwG3E/tests/build/build.go:1478 @ 10/16/25 13:39:05.367 ------------------------------ SSSSSSSSSSS•••••••••••••••••••••••••••••••••••••• Summarizing 1 Failure: [FAIL] [build-service-suite Build service E2E tests] test of component update with renovate gitlab when components are created in same namespace [It] the PipelineRun should eventually finish successfully for parent component [build-service, renovate, multi-component] /tmp/tmp.yvmViwwG3E/tests/build/build.go:1478 Ran 101 of 389 Specs in 2203.130 seconds FAIL! -- 100 Passed | 1 Failed | 34 Pending | 254 Skipped Ginkgo ran 1 suite in 38m15.546296271s Test Suite Failed E1016 13:56:56.755661 23959 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=1760620711 --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