./mage -v ci:teste2e Running target: CI:TestE2E I0912 08:53:23.249929 23983 magefile.go:521] setting up new custom bundle for testing... I0912 08:53:23.862517 23983 util.go:521] found credentials for image ref quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1757667203-kfdp -> user: redhat-appstudio-qe+redhat_appstudio_quality Creating Tekton Bundle: - Added Pipeline: docker-build to image I0912 08:53:25.242656 23983 bundle.go:57] image digest for a new tekton bundle quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1757667203-kfdp: quay.io/redhat-appstudio-qe/test-images@sha256:9b68372cd75208f872d39c15e01253a42d10b35b73cc9a56f5e2850e7132a56f I0912 08:53:25.242693 23983 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-1757667203-kfdp I0912 08:53:26.286418 23983 release_service_catalog.go:104] checking if repository is release-service-catalog I0912 08:53:26.286433 23983 integration_service.go:49] checking if repository is integration-service I0912 08:53:26.286437 23983 image_controller.go:49] checking if repository is image-controller I0912 08:53:26.286441 23983 build_service.go:49] checking if repository is build-service I0912 08:53:26.286445 23983 build_service.go:30] require sprayproxy registering is set to TRUE I0912 08:53:26.286447 23983 build_service.go:33] setting 'build-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 08:53:29.838272 23983 e2e_repo.go:347] checking if repository is e2e-tests I0912 08:53:29.838296 23983 release_service.go:50] checking if repository is release-service I0912 08:53:29.838304 23983 types.go:155] The following rules have matched build-service repo CI Workflow Rule. I0912 08:53:29.838310 23983 types.go:180] Will apply rules exec: ginkgo "--seed=1757667203" "--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.XcYTv04usB/cmd ===================================================================== Random Seed: 1757667203 Will run 112 of 401 specs Running in parallel across 20 processes ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params when context points to a file [build-templates] /tmp/tmp.XcYTv04usB/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.XcYTv04usB/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.XcYTv04usB/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.XcYTv04usB/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.XcYTv04usB/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.XcYTv04usB/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.XcYTv04usB/tests/build/tkn-bundle.go:236 ------------------------------ SSSSSSS ------------------------------ 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.XcYTv04usB/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.XcYTv04usB/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.XcYTv04usB/tests/build/multi-platform.go:127 ------------------------------ 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 that PipelineRun completes successfully [multi-platform, aws-host-pool] /tmp/tmp.XcYTv04usB/tests/build/multi-platform.go:148 ------------------------------ 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 test that cleanup happened successfully [multi-platform, aws-host-pool] /tmp/tmp.XcYTv04usB/tests/build/multi-platform.go:152 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/build/multi-platform.go:251 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/build/multi-platform.go:255 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/build/multi-platform.go:259 ------------------------------ SS ------------------------------ 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.XcYTv04usB/tests/build/multi-platform.go:263 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/build/multi-platform.go:267 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/build/multi-platform.go:341 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/build/multi-platform.go:345 ------------------------------ SS ------------------------------ 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.XcYTv04usB/tests/build/multi-platform.go:349 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/build/multi-platform.go:353 ------------------------------ SS ------------------------------ 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.XcYTv04usB/tests/build/multi-platform.go:357 ------------------------------ S ------------------------------ 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.XcYTv04usB/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.XcYTv04usB/tests/build/multi-platform.go:436 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/build/multi-platform.go:440 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/build/multi-platform.go:444 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/build/multi-platform.go:448 ------------------------------ SSSSSSSSSSSSSSSSSSS ------------------------------ 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.XcYTv04usB/tests/build/build_templates.go:478 ------------------------------ SSSSSSSSSSSSSSSSS ------------------------------ 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.XcYTv04usB/tests/build/build_templates.go:478 ------------------------------ SSSSSSSSSSSSSSSSS ------------------------------ 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.XcYTv04usB/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.XcYTv04usB/tests/release/pipelines/release_to_github.go:149 ------------------------------ S ------------------------------ 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.XcYTv04usB/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.XcYTv04usB/tests/release/pipelines/release_to_github.go:193 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ 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.XcYTv04usB/tests/integration-service/pipelinerun-resolution.go:77 ------------------------------ 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 triggers a build PipelineRun [integration-service, pipelinerun-resolution] /tmp/tmp.XcYTv04usB/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.XcYTv04usB/tests/integration-service/pipelinerun-resolution.go:103 ------------------------------ 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 waits for build PipelineRun to succeed [integration-service, pipelinerun-resolution] /tmp/tmp.XcYTv04usB/tests/integration-service/pipelinerun-resolution.go:114 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/integration-service/pipelinerun-resolution.go:122 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/integration-service/pipelinerun-resolution.go:126 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/integration-service/pipelinerun-resolution.go:132 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/integration-service/pipelinerun-resolution.go:136 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/integration-service/pipelinerun-resolution.go:149 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/integration-service/pipelinerun-resolution.go:153 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/integration-service/pipelinerun-resolution.go:169 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/integration-service/pipelinerun-resolution.go:176 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/integration-service/pipelinerun-resolution.go:180 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/integration-service/pipelinerun-resolution.go:226 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/integration-service/pipelinerun-resolution.go:263 ------------------------------ 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.XcYTv04usB/tests/integration-service/pipelinerun-resolution.go:287 ------------------------------ S ------------------------------ 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.XcYTv04usB/tests/integration-service/pipelinerun-resolution.go:320 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS•••••••••••••••••••••••• ------------------------------ 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.XcYTv04usB/tests/build/build.go:1097 ------------------------------ •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• Ran 112 of 401 Specs in 2335.751 seconds SUCCESS! -- 112 Passed | 0 Failed | 51 Pending | 238 Skipped Ginkgo ran 1 suite in 40m27.117431769s Test Suite Passed