./mage -v ci:teste2e Running target: CI:TestE2E I0912 20:51:23.579274 23913 magefile.go:521] setting up new custom bundle for testing... I0912 20:51:24.027650 23913 util.go:521] found credentials for image ref quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1757710284-tzby -> user: redhat-appstudio-qe+redhat_appstudio_quality Creating Tekton Bundle: - Added Pipeline: docker-build to image I0912 20:51:25.239351 23913 bundle.go:57] image digest for a new tekton bundle quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1757710284-tzby: quay.io/redhat-appstudio-qe/test-images@sha256:53bae9cd756c2193dfb73bbd1fe63047667de08a354d9deaee85cd59f05a6b2a I0912 20:51:25.239375 23913 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-1757710284-tzby I0912 20:51:25.239396 23913 e2e_repo.go:347] checking if repository is e2e-tests I0912 20:51:25.239401 23913 release_service.go:50] checking if repository is release-service I0912 20:51:26.164041 23913 release_service_catalog.go:104] checking if repository is release-service-catalog I0912 20:51:26.164060 23913 integration_service.go:49] checking if repository is integration-service I0912 20:51:26.164064 23913 integration_service.go:30] require sprayproxy registering is set to TRUE I0912 20:51:26.164067 23913 integration_service.go:33] setting 'integration-service' test label exec: go "install" "-mod=mod" "github.com/onsi/ginkgo/v2/ginkgo" go: downloading github.com/google/pprof v0.0.0-20241210010833-40e02aabc2ad go: downloading github.com/go-task/slim-sprig/v3 v3.0.0 I0912 20:51:29.735371 23913 image_controller.go:49] checking if repository is image-controller I0912 20:51:29.735394 23913 build_service.go:49] checking if repository is build-service I0912 20:51:29.735404 23913 types.go:155] The following rules have matched Integration-service repo CI Workflow Rule. I0912 20:51:29.735413 23913 types.go:180] Will apply rules exec: ginkgo "--seed=1757710283" "--timeout=1h30m0s" "--grace-period=30s" "--output-interceptor-mode=none" "--label-filter=integration-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.1jSkijQ0B1/cmd ===================================================================== Random Seed: 1757710283 Will run 117 of 401 specs Running in parallel across 20 processes SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ 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.1jSkijQ0B1/tests/build/build.go:1097 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params when context points to a file [build-templates] /tmp/tmp.1jSkijQ0B1/tests/build/tkn-bundle.go:177 ------------------------------ S ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params creates Tekton bundles from specific context [build-templates] /tmp/tmp.1jSkijQ0B1/tests/build/tkn-bundle.go:188 ------------------------------ S ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params when context is the root directory [build-templates] /tmp/tmp.1jSkijQ0B1/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.1jSkijQ0B1/tests/build/tkn-bundle.go:207 ------------------------------ S ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params creates Tekton bundles when using negation [build-templates] /tmp/tmp.1jSkijQ0B1/tests/build/tkn-bundle.go:217 ------------------------------ S ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params allows overriding HOME environment variable [build-templates] /tmp/tmp.1jSkijQ0B1/tests/build/tkn-bundle.go:227 ------------------------------ S ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params allows overriding STEP image [build-templates] /tmp/tmp.1jSkijQ0B1/tests/build/tkn-bundle.go:236 ------------------------------ SSSSSSS ------------------------------ 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.1jSkijQ0B1/tests/release/pipelines/release_to_github.go:139 ------------------------------ S ------------------------------ 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.1jSkijQ0B1/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.1jSkijQ0B1/tests/release/pipelines/release_to_github.go:182 ------------------------------ S ------------------------------ 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.1jSkijQ0B1/tests/release/pipelines/release_to_github.go:193 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ P [PENDING] [build-service-suite Build templates E2E test] HACBS pipelines 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.1jSkijQ0B1/tests/build/build_templates.go:478 ------------------------------ SSSSSSSSSSSSSSSSSS ------------------------------ P [PENDING] [build-service-suite Build templates E2E test] HACBS pipelines 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.1jSkijQ0B1/tests/build/build_templates.go:478 ------------------------------ SSSSSSSSS ------------------------------ 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.1jSkijQ0B1/tests/build/multi-platform.go:120 ------------------------------ S ------------------------------ 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.1jSkijQ0B1/tests/build/multi-platform.go:124 ------------------------------ S ------------------------------ 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.1jSkijQ0B1/tests/build/multi-platform.go:127 ------------------------------ S ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] 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, pipelinerun-resolution] /tmp/tmp.1jSkijQ0B1/tests/integration-service/pipelinerun-resolution.go:77 ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when a new Component is created triggers a build PipelineRun [integration-service, pipelinerun-resolution] /tmp/tmp.1jSkijQ0B1/tests/integration-service/pipelinerun-resolution.go:98 ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] 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, pipelinerun-resolution] /tmp/tmp.1jSkijQ0B1/tests/integration-service/pipelinerun-resolution.go:103 ------------------------------ 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.1jSkijQ0B1/tests/build/multi-platform.go:148 ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when a new Component is created waits for build PipelineRun to succeed [integration-service, pipelinerun-resolution] /tmp/tmp.1jSkijQ0B1/tests/integration-service/pipelinerun-resolution.go:114 ------------------------------ 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.1jSkijQ0B1/tests/build/multi-platform.go:152 ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] 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, pipelinerun-resolution] /tmp/tmp.1jSkijQ0B1/tests/integration-service/pipelinerun-resolution.go:122 ------------------------------ 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.1jSkijQ0B1/tests/build/multi-platform.go:251 ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if the Snapshot is created [integration-service, pipelinerun-resolution] /tmp/tmp.1jSkijQ0B1/tests/integration-service/pipelinerun-resolution.go:126 ------------------------------ 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.1jSkijQ0B1/tests/build/multi-platform.go:255 ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] 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, pipelinerun-resolution] /tmp/tmp.1jSkijQ0B1/tests/integration-service/pipelinerun-resolution.go:132 ------------------------------ 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.1jSkijQ0B1/tests/build/multi-platform.go:259 ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] 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, pipelinerun-resolution] /tmp/tmp.1jSkijQ0B1/tests/integration-service/pipelinerun-resolution.go:136 ------------------------------ 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.1jSkijQ0B1/tests/build/multi-platform.go:263 ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if all of the integrationPipelineRuns passed [integration-service, pipelinerun-resolution, slow] /tmp/tmp.1jSkijQ0B1/tests/integration-service/pipelinerun-resolution.go:149 ------------------------------ 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.1jSkijQ0B1/tests/build/multi-platform.go:267 ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] 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, pipelinerun-resolution] /tmp/tmp.1jSkijQ0B1/tests/integration-service/pipelinerun-resolution.go:153 ------------------------------ 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.1jSkijQ0B1/tests/build/multi-platform.go:341 ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] 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, pipelinerun-resolution] /tmp/tmp.1jSkijQ0B1/tests/integration-service/pipelinerun-resolution.go:169 ------------------------------ 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.1jSkijQ0B1/tests/build/multi-platform.go:345 ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when integration pipelineRun is created it passes, annotations and labels not overwritten by integration service checks integration pipelineRun passed [integration-service, pipelinerun-resolution] /tmp/tmp.1jSkijQ0B1/tests/integration-service/pipelinerun-resolution.go:176 ------------------------------ 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.1jSkijQ0B1/tests/build/multi-platform.go:349 ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when integration pipelineRun is created it passes, annotations and labels not overwritten by integration service verifies that existing labels and annotations are not overwritten by integration service [integration-service, pipelinerun-resolution] /tmp/tmp.1jSkijQ0B1/tests/integration-service/pipelinerun-resolution.go:180 ------------------------------ 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.1jSkijQ0B1/tests/build/multi-platform.go:353 ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when integration pipelineRun is created it passes, annotations and labels not overwritten by integration service verifies that PipelinesAsCode specific annotations with dynamic values are preserved [integration-service, pipelinerun-resolution] /tmp/tmp.1jSkijQ0B1/tests/integration-service/pipelinerun-resolution.go:226 ------------------------------ 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.1jSkijQ0B1/tests/build/multi-platform.go:357 ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when integration pipelineRun is created it passes, annotations and labels not overwritten by integration service verifies that ResolutionRequest is deleted after pipeline resolution [integration-service, pipelinerun-resolution] /tmp/tmp.1jSkijQ0B1/tests/integration-service/pipelinerun-resolution.go:263 ------------------------------ 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.1jSkijQ0B1/tests/build/multi-platform.go:432 ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when integration pipelineRun is created it passes, annotations and labels not overwritten by integration service verifies that no orphaned ResolutionRequests remain in namespace after test completion [integration-service, pipelinerun-resolution] /tmp/tmp.1jSkijQ0B1/tests/integration-service/pipelinerun-resolution.go:287 ------------------------------ 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.1jSkijQ0B1/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.1jSkijQ0B1/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.1jSkijQ0B1/tests/build/multi-platform.go:444 ------------------------------ P [PENDING] [integration-service-suite Integration Service E2E tests ITS PipelineRun Resolution] with happy path for general flow of Integration service when integration pipelineRun is created it passes, annotations and labels not overwritten by integration service validates that second integration pipelineRun failed due to resolution not pipelinerun [integration-service, pipelinerun-resolution] /tmp/tmp.1jSkijQ0B1/tests/integration-service/pipelinerun-resolution.go:320 ------------------------------ 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.1jSkijQ0B1/tests/build/multi-platform.go:448 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSS••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• ------------------------------ • [FAILED] [1202.256 seconds] [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 [It] get all component snapshots for component A and check if older snapshot has been cancelled [integration-service, group-snapshot-creation] /tmp/tmp.1jSkijQ0B1/tests/integration-service/group-snapshots-tests.go:543 [FAILED] Timed out after 1200.001s. timeout while waiting for component snapshot and integration pipelinerun to be cancelled Expected success, but got an error: <*errors.errorString | 0xc0012fba40>: older snapshot has not been cancelled as expected { s: "older snapshot has not been cancelled as expected", } In [It] at: /tmp/tmp.1jSkijQ0B1/tests/integration-service/group-snapshots-tests.go:567 @ 09/12/25 21:39:50.885 ------------------------------ S Summarizing 1 Failure: [FAIL] [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 [It] get all component snapshots for component A and check if older snapshot has been cancelled [integration-service, group-snapshot-creation] /tmp/tmp.1jSkijQ0B1/tests/integration-service/group-snapshots-tests.go:567 Ran 116 of 401 Specs in 2813.662 seconds FAIL! -- 115 Passed | 1 Failed | 51 Pending | 234 Skipped Ginkgo ran 1 suite in 48m24.477783667s Test Suite Failed E0912 21:39:54.228431 23913 types.go:186] Failed to execute rule: Integration-service repo CI Workflow Rule: Execute the full workflow for e2e-tests repo in CI Error: running "ginkgo --seed=1757710283 --timeout=1h30m0s --grace-period=30s --output-interceptor-mode=none --label-filter=integration-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