./mage -v ci:teste2e Running target: CI:TestE2E I0420 19:05:43.262414 18073 magefile.go:529] setting up new custom bundle for testing... I0420 19:05:43.641762 18073 util.go:512] found credentials for image ref quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1776711943-harn -> user: redhat-appstudio-qe+redhat_appstudio_quality Creating Tekton Bundle: - Added Pipeline: docker-build to image I0420 19:05:44.799470 18073 bundle.go:57] image digest for a new tekton bundle quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1776711943-harn: quay.io/redhat-appstudio-qe/test-images@sha256:ad18f980c11bc278d5676072b9e980395452c827181b5208732dac22cf2b6e09 I0420 19:05:44.799496 18073 magefile.go:535] 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-1776711943-harn I0420 19:05:45.825748 18073 release_service_catalog.go:104] checking if repository is release-service-catalog I0420 19:05:45.825772 18073 integration_service.go:49] checking if repository is integration-service I0420 19:05:45.825778 18073 image_controller.go:49] checking if repository is image-controller I0420 19:05:45.825785 18073 build_service.go:50] checking if repository is build-service I0420 19:05:45.825789 18073 build_service.go:31] require sprayproxy registering is set to TRUE I0420 19:05:45.825795 18073 build_service.go:34] setting test label filter: 'build-service' 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-20260106004452-d7df1bf2cac7 I0420 19:05:50.752028 18073 e2e_repo.go:347] checking if repository is e2e-tests I0420 19:05:50.752047 18073 release_service.go:50] checking if repository is release-service I0420 19:05:50.752057 18073 types.go:155] The following rules have matched build-service repo CI Workflow Rule. I0420 19:05:50.752061 18073 types.go:180] Will apply rules exec: ginkgo "--seed=1776711943" "--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" "--" go: downloading github.com/konflux-ci/build-service v0.0.0-20240611083846-2dee6cfe6fe4 go: downloading github.com/minio/minio-go/v7 v7.0.99 go: downloading github.com/IBM/go-sdk-core/v5 v5.15.3 go: downloading github.com/IBM/vpc-go-sdk v0.48.0 go: downloading github.com/aws/aws-sdk-go-v2/service/ec2 v1.143.0 go: downloading github.com/aws/aws-sdk-go-v2 v1.41.3 go: downloading github.com/aws/aws-sdk-go-v2/config v1.31.3 go: downloading github.com/go-ini/ini v1.67.0 go: downloading github.com/minio/md5-simd v1.1.2 go: downloading github.com/dustin/go-humanize v1.0.1 go: downloading github.com/klauspost/crc32 v1.3.0 go: downloading github.com/minio/crc64nvme v1.1.1 go: downloading github.com/tinylib/msgp v1.6.1 go: downloading github.com/rs/xid v1.6.0 go: downloading github.com/google/go-github/v45 v45.2.0 go: downloading github.com/go-openapi/strfmt v0.23.0 go: downloading github.com/go-playground/validator/v10 v10.17.0 go: downloading go.mongodb.org/mongo-driver v1.17.4 go: downloading github.com/mitchellh/mapstructure v1.5.1-0.20231216201459-8508981c8b6c go: downloading github.com/go-openapi/errors v0.22.2 go: downloading github.com/oklog/ulid v1.3.1 go: downloading github.com/asaskevich/govalidator v0.0.0-20230301143203-a9d515a09cc2 go: downloading github.com/aws/smithy-go v1.24.2 go: downloading github.com/leodido/go-urn v1.3.0 go: downloading github.com/gabriel-vasile/mimetype v1.4.3 go: downloading github.com/go-playground/universal-translator v0.18.1 go: downloading github.com/philhofer/fwd v1.2.0 go: downloading github.com/aws/aws-sdk-go-v2/credentials v1.18.7 go: downloading github.com/aws/aws-sdk-go-v2/internal/ini v1.8.3 go: downloading github.com/aws/aws-sdk-go-v2/service/sso v1.28.2 go: downloading github.com/aws/aws-sdk-go-v2/service/sts v1.38.0 go: downloading github.com/aws/aws-sdk-go-v2/service/ssooidc v1.34.0 go: downloading github.com/aws/aws-sdk-go-v2/feature/ec2/imds v1.18.4 go: downloading github.com/go-playground/locales v0.14.1 go: downloading github.com/aws/aws-sdk-go-v2/internal/configsources v1.4.19 go: downloading github.com/aws/aws-sdk-go-v2/internal/endpoints/v2 v2.7.19 go: downloading github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding v1.13.6 go: downloading github.com/aws/aws-sdk-go-v2/service/internal/presigned-url v1.13.19 Running Suite: Red Hat App Studio E2E tests - /tmp/tmp.mugTBrSshy/cmd ===================================================================== Random Seed: 1776711943 Will run 147 of 461 specs Running in parallel across 20 processes ------------------------------ 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.mugTBrSshy/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.mugTBrSshy/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.mugTBrSshy/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.mugTBrSshy/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.mugTBrSshy/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.mugTBrSshy/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.mugTBrSshy/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.mugTBrSshy/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.mugTBrSshy/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.mugTBrSshy/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.mugTBrSshy/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.mugTBrSshy/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.mugTBrSshy/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.mugTBrSshy/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.mugTBrSshy/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.mugTBrSshy/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.mugTBrSshy/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.mugTBrSshy/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.mugTBrSshy/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.mugTBrSshy/tests/build/multi-platform.go:448 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ 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.mugTBrSshy/tests/release/pipelines/release_to_github.go:138 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/rh_push_to_registry_redhat_io.go:108 ------------------------------ SS ------------------------------ 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.mugTBrSshy/tests/release/pipelines/release_to_github.go:148 ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/rh_push_to_registry_redhat_io.go:118 ------------------------------ SSS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/rh_push_to_registry_redhat_io.go:148 ------------------------------ SS ------------------------------ 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.mugTBrSshy/tests/release/pipelines/release_to_github.go:181 ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/rh_push_to_registry_redhat_io.go:159 ------------------------------ SS ------------------------------ 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.mugTBrSshy/tests/release/pipelines/release_to_github.go:192 ------------------------------ SSSSSS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/rh_push_to_external_registry.go:215 ------------------------------ SSSSSSSS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/rh_push_to_external_registry.go:226 ------------------------------ S ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/build/build_templates.go:507 ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/multiarch_advisories.go:112 ------------------------------ S ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/rh_push_to_external_registry.go:233 ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/multiarch_advisories.go:122 ------------------------------ SS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/rh_push_to_external_registry.go:248 ------------------------------ S ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/multiarch_advisories.go:152 ------------------------------ SS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/multiarch_advisories.go:163 ------------------------------ S ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/rh_push_to_external_registry.go:265 ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/build/build_templates.go:569 ------------------------------ SSSSSS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/rh_advisories.go:117 ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params when context points to a file [build-templates] /tmp/tmp.mugTBrSshy/tests/build/tkn-bundle.go:188 ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/build/build_templates.go:744 ------------------------------ S ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/rh_advisories.go:127 ------------------------------ SS ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params creates Tekton bundles from specific context [build-templates] /tmp/tmp.mugTBrSshy/tests/build/tkn-bundle.go:199 ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/rh_advisories.go:157 ------------------------------ SSSS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/push_to_external_registry.go:157 ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params when context is the root directory [build-templates] /tmp/tmp.mugTBrSshy/tests/build/tkn-bundle.go:209 ------------------------------ SSSSSS ------------------------------ P [PENDING] [release-pipelines-suite Push to external registry] Post-release verification verifies that Release PipelineRun should eventually succeed [release-pipelines, push-to-external-registry] /tmp/tmp.mugTBrSshy/tests/release/pipelines/push_to_external_registry.go:164 ------------------------------ SS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/fbc_release.go:123 ------------------------------ P [PENDING] [release-pipelines-suite Push to external registry] Post-release verification tests if the image was pushed to quay [release-pipelines, push-to-external-registry] /tmp/tmp.mugTBrSshy/tests/release/pipelines/push_to_external_registry.go:168 ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/rh_advisories.go:168 ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/fbc_release.go:128 ------------------------------ P [PENDING] [release-pipelines-suite Push to external registry] Post-release verification verifies that a Release is marked as succeeded. [release-pipelines, push-to-external-registry] /tmp/tmp.mugTBrSshy/tests/release/pipelines/push_to_external_registry.go:175 ------------------------------ 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.mugTBrSshy/tests/build/tkn-bundle.go:218 ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/fbc_release.go:132 ------------------------------ SSSS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/fbc_release.go:136 ------------------------------ SS ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params creates Tekton bundles when using negation [build-templates] /tmp/tmp.mugTBrSshy/tests/build/tkn-bundle.go:228 ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/build/build_templates.go:507 ------------------------------ S ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params allows overriding HOME environment variable [build-templates] /tmp/tmp.mugTBrSshy/tests/build/tkn-bundle.go:238 ------------------------------ SS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/rhtap_service_push.go:150 ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/fbc_release.go:178 ------------------------------ SSSS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/rhtap_service_push.go:160 ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params allows overriding STEP image [build-templates] /tmp/tmp.mugTBrSshy/tests/build/tkn-bundle.go:247 ------------------------------ SS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/build/build_templates.go:569 ------------------------------ SSSSSSS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/fbc_release.go:183 ------------------------------ S ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/rhtap_service_push.go:190 ------------------------------ S ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/build/build_templates.go:744 ------------------------------ SSS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/fbc_release.go:187 ------------------------------ S ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/rhtap_service_push.go:200 ------------------------------ SSSSS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/fbc_release.go:191 ------------------------------ SSSSS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/fbc_release.go:233 ------------------------------ SSSSSSSS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/fbc_release.go:238 ------------------------------ SSS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/fbc_release.go:242 ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/build/build_templates.go:507 ------------------------------ S ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/fbc_release.go:246 ------------------------------ SSSS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/build/build_templates.go:569 ------------------------------ S ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/fbc_release.go:286 ------------------------------ SSS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/fbc_release.go:291 ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/build/build_templates.go:744 ------------------------------ SS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/fbc_release.go:295 ------------------------------ SSS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/release/pipelines/fbc_release.go:299 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ • [FAILED] [10.562 seconds] [build-service-suite Build service E2E tests] test git provider gl PaC component build [BeforeAll] when a new component without specified branch is created and with visibility private correctly targets the default branch (that is not named 'main') with PaC [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch] [BeforeAll] /tmp/tmp.mugTBrSshy/tests/build/pac_build.go:54 [It] /tmp/tmp.mugTBrSshy/tests/build/pac_build.go:136 [FAILED] Unexpected error: <*errors.errorString | 0xc001d54500>: failed to create test namespace build-e2e-btwj: error when creating build-e2e-btwj namespace: Internal error occurred: failed calling webhook "validate.kyverno.svc-fail": failed to call webhook: Post "https://kyverno-svc.kyverno.svc:443/validate/fail?timeout=10s": dial tcp 10.96.231.48:443: connect: connection refused { s: "failed to create test namespace build-e2e-btwj: error when creating build-e2e-btwj namespace: Internal error occurred: failed calling webhook \"validate.kyverno.svc-fail\": failed to call webhook: Post \"https://kyverno-svc.kyverno.svc:443/validate/fail?timeout=10s\": dial tcp 10.96.231.48:443: connect: connection refused", } occurred In [BeforeAll] at: /tmp/tmp.mugTBrSshy/tests/build/pac_build.go:60 @ 04/20/26 19:08:30.143 ------------------------------ • [FAILED] [10.561 seconds] [build-service-suite Build service E2E tests] test pac with multiple components using same repository [BeforeAll] when components are created in same namespace creates component with context directory go-component [build-service, github, pac-build, multi-component] [BeforeAll] /tmp/tmp.mugTBrSshy/tests/build/multi_component.go:40 [It] /tmp/tmp.mugTBrSshy/tests/build/multi_component.go:106 Timeline >> [FAILED] in [BeforeAll] - /tmp/tmp.mugTBrSshy/tests/build/multi_component.go:45 @ 04/20/26 19:08:30.143 [PANICKED] in [AfterAll] - /usr/lib/golang/src/runtime/panic.go:262 @ 04/20/26 19:08:30.143 << Timeline [FAILED] Unexpected error: <*errors.errorString | 0xc000612420>: failed to create test namespace build-e2e-nmwx: error when creating build-e2e-nmwx namespace: Internal error occurred: failed calling webhook "validate.kyverno.svc-fail": failed to call webhook: Post "https://kyverno-svc.kyverno.svc:443/validate/fail?timeout=10s": dial tcp 10.96.231.48:443: connect: connection refused { s: "failed to create test namespace build-e2e-nmwx: error when creating build-e2e-nmwx namespace: Internal error occurred: failed calling webhook \"validate.kyverno.svc-fail\": failed to call webhook: Post \"https://kyverno-svc.kyverno.svc:443/validate/fail?timeout=10s\": dial tcp 10.96.231.48:443: connect: connection refused", } occurred In [BeforeAll] at: /tmp/tmp.mugTBrSshy/tests/build/multi_component.go:45 @ 04/20/26 19:08:30.143 There were additional failures detected. To view them in detail run ginkgo -vv ------------------------------ SSSSSSSS ------------------------------ • [FAILED] [10.565 seconds] [build-service-suite Build service E2E tests] test git provider fj PaC component build [BeforeAll] when a new component without specified branch is created and with visibility private correctly targets the default branch (that is not named 'main') with PaC [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch] [BeforeAll] /tmp/tmp.mugTBrSshy/tests/build/pac_build.go:54 [It] /tmp/tmp.mugTBrSshy/tests/build/pac_build.go:136 [FAILED] Unexpected error: <*errors.errorString | 0xc0013282b0>: failed to create test namespace build-e2e-xxai: error when creating build-e2e-xxai namespace: Internal error occurred: failed calling webhook "validate.kyverno.svc-fail": failed to call webhook: Post "https://kyverno-svc.kyverno.svc:443/validate/fail?timeout=10s": dial tcp 10.96.231.48:443: connect: connection refused { s: "failed to create test namespace build-e2e-xxai: error when creating build-e2e-xxai namespace: Internal error occurred: failed calling webhook \"validate.kyverno.svc-fail\": failed to call webhook: Post \"https://kyverno-svc.kyverno.svc:443/validate/fail?timeout=10s\": dial tcp 10.96.231.48:443: connect: connection refused", } occurred In [BeforeAll] at: /tmp/tmp.mugTBrSshy/tests/build/pac_build.go:60 @ 04/20/26 19:08:30.144 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/build/pac_build.go:600 ------------------------------ S ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/build/pac_build.go:642 ------------------------------ SSSS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/build/pac_build.go:600 ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/build/pac_build.go:642 ------------------------------ S••••• ------------------------------ • [FAILED] [121.779 seconds] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created [It] check first component annotation has errors [build-service, github, pac-build, secret-lookup] /tmp/tmp.mugTBrSshy/tests/build/secret_lookup.go:158 Timeline >> build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} [FAILED] in [It] - /tmp/tmp.mugTBrSshy/tests/build/secret_lookup.go:175 @ 04/20/26 19:11:04.092 << Timeline [FAILED] Timed out after 120.001s. failed while checking build status for component "component-one-xepm" is correct Expected : false to be true In [It] at: /tmp/tmp.mugTBrSshy/tests/build/secret_lookup.go:175 @ 04/20/26 19:11:04.092 ------------------------------ SS ------------------------------ 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, github, pac-build, secret-lookup] /tmp/tmp.mugTBrSshy/tests/build/secret_lookup.go:206 ------------------------------ • [FAILED] [212.092 seconds] [build-service-suite Build service E2E tests] test build annotations when component is created with invalid build request annotations [It] handles invalid request annotation [build-service, github, annotations] /tmp/tmp.mugTBrSshy/tests/build/annotations.go:89 Timeline >> Image repository for component test-annotations-yeyads in namespace build-e2e-wzoe do not have right state ('' != 'ready') yet but it has status { { } { } []}. build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} build status annotation value: {"message":"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap"} [FAILED] in [It] - /tmp/tmp.mugTBrSshy/tests/build/annotations.go:119 @ 04/20/26 19:11:50.705 << Timeline [FAILED] Timed out after 120.000s. failed while checking build status message for component "test-annotations-yeyads" is correct after setting invalid annotations Expected success, but got an error: <*errors.errorString | 0xc0009babe0>: build status message is not as expected, got: "307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap", expected: "unexpected build request: foo" { s: "build status message is not as expected, got: \"307: 307: pipeline referenced in 'build.appstudio.openshift.io/pipeline' annotation doesn't exist in build-pipeline-config ConfigMap\", expected: \"unexpected build request: foo\"", } In [It] at: /tmp/tmp.mugTBrSshy/tests/build/annotations.go:119 @ 04/20/26 19:11:50.705 ------------------------------ • [FAILED] [357.139 seconds] [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 [It] correctly targets the default branch (that is not named 'main') with PaC [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch] /tmp/tmp.mugTBrSshy/tests/build/pac_build.go:136 Timeline >> Image repository for component gh-test-custom-default-rsghxv in namespace build-e2e-pogd do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component gh-test-custom-default-rsghxv in namespace build-e2e-pogd do not have right state ('' != 'ready') yet but it has status { { } { } []}. [FAILED] in [It] - /tmp/tmp.mugTBrSshy/tests/build/pac_build.go:150 @ 04/20/26 19:14:16.002 << Timeline [FAILED] Timed out after 300.000s. timed out when waiting for init PaC PR to be created against default branch in devfile-sample-hello-world-qzzkbn repository Expected : false to be true In [It] at: /tmp/tmp.mugTBrSshy/tests/build/pac_build.go:150 @ 04/20/26 19:14:16.002 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/build/pac_build.go:600 ------------------------------ P [PENDING] [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] /tmp/tmp.mugTBrSshy/tests/build/pac_build.go:642 ------------------------------ S ------------------------------ • [FAILED] [1806.816 seconds] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace [It] triggers a PipelineRun for parent component [build-service, renovate, multi-component, forgejo] /tmp/tmp.mugTBrSshy/tests/build/renovate.go:259 Timeline >> PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc PipelineRun has not been created yet for the component build-e2e-ciif/fj-multi-component-parent-qxbc [FAILED] in [It] - /tmp/tmp.mugTBrSshy/tests/build/renovate.go:272 @ 04/20/26 19:39:15.707 << Timeline [FAILED] Timed out after 1800.001s. timed out when waiting for the PipelineRun to start for the component fj-multi-component-parent-qxbc/build-e2e-ciif Expected success, but got an error: <*errors.errorString | 0xc0008a2980>: no pipelinerun found for component fj-multi-component-parent-qxbc { s: "no pipelinerun found for component fj-multi-component-parent-qxbc", } In [It] at: /tmp/tmp.mugTBrSshy/tests/build/renovate.go:272 @ 04/20/26 19:39:15.707 ------------------------------ SSSSSSSSSSSS ------------------------------ • [FAILED] [1806.839 seconds] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace [It] triggers a PipelineRun for parent component [build-service, renovate, multi-component, github] /tmp/tmp.mugTBrSshy/tests/build/renovate.go:259 Timeline >> PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu PipelineRun has not been created yet for the component build-e2e-zcbu/gh-multi-component-parent-glqu [FAILED] in [It] - /tmp/tmp.mugTBrSshy/tests/build/renovate.go:272 @ 04/20/26 19:39:35.95 << Timeline [FAILED] Timed out after 1800.000s. timed out when waiting for the PipelineRun to start for the component gh-multi-component-parent-glqu/build-e2e-zcbu Expected success, but got an error: <*errors.errorString | 0xc0015d0220>: no pipelinerun found for component gh-multi-component-parent-glqu { s: "no pipelinerun found for component gh-multi-component-parent-glqu", } In [It] at: /tmp/tmp.mugTBrSshy/tests/build/renovate.go:272 @ 04/20/26 19:39:35.95 ------------------------------ SSSSSSSSSSSS ------------------------------ • [FAILED] [1806.783 seconds] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace [It] triggers a PipelineRun for parent component [build-service, renovate, multi-component, gitlab] /tmp/tmp.mugTBrSshy/tests/build/renovate.go:259 Timeline >> PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd PipelineRun has not been created yet for the component build-e2e-zvfb/gl-multi-component-parent-vrjd [FAILED] in [It] - /tmp/tmp.mugTBrSshy/tests/build/renovate.go:272 @ 04/20/26 19:39:36.15 << Timeline [FAILED] Timed out after 1800.001s. timed out when waiting for the PipelineRun to start for the component gl-multi-component-parent-vrjd/build-e2e-zvfb Expected success, but got an error: <*errors.errorString | 0xc001dde2d0>: no pipelinerun found for component gl-multi-component-parent-vrjd { s: "no pipelinerun found for component gl-multi-component-parent-vrjd", } In [It] at: /tmp/tmp.mugTBrSshy/tests/build/renovate.go:272 @ 04/20/26 19:39:36.15 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS Summarizing 9 Failures: [FAIL] [build-service-suite Build service E2E tests] test pac with multiple components using same repository [BeforeAll] when components are created in same namespace creates component with context directory go-component [build-service, github, pac-build, multi-component] /tmp/tmp.mugTBrSshy/tests/build/multi_component.go:45 [FAIL] [build-service-suite Build service E2E tests] test git provider gl PaC component build [BeforeAll] when a new component without specified branch is created and with visibility private correctly targets the default branch (that is not named 'main') with PaC [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch] /tmp/tmp.mugTBrSshy/tests/build/pac_build.go:60 [FAIL] [build-service-suite Build service E2E tests] test git provider fj PaC component build [BeforeAll] when a new component without specified branch is created and with visibility private correctly targets the default branch (that is not named 'main') with PaC [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch] /tmp/tmp.mugTBrSshy/tests/build/pac_build.go:60 [FAIL] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created [It] check first component annotation has errors [build-service, github, pac-build, secret-lookup] /tmp/tmp.mugTBrSshy/tests/build/secret_lookup.go:175 [FAIL] [build-service-suite Build service E2E tests] test build annotations when component is created with invalid build request annotations [It] handles invalid request annotation [build-service, github, annotations] /tmp/tmp.mugTBrSshy/tests/build/annotations.go:119 [FAIL] [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 [It] correctly targets the default branch (that is not named 'main') with PaC [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch] /tmp/tmp.mugTBrSshy/tests/build/pac_build.go:150 [FAIL] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace [It] triggers a PipelineRun for parent component [build-service, renovate, multi-component, forgejo] /tmp/tmp.mugTBrSshy/tests/build/renovate.go:272 [FAIL] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace [It] triggers a PipelineRun for parent component [build-service, renovate, multi-component, github] /tmp/tmp.mugTBrSshy/tests/build/renovate.go:272 [FAIL] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace [It] triggers a PipelineRun for parent component [build-service, renovate, multi-component, gitlab] /tmp/tmp.mugTBrSshy/tests/build/renovate.go:272 Ran 14 of 461 Specs in 1884.000 seconds FAIL! -- 5 Passed | 9 Failed | 88 Pending | 359 Skipped Ginkgo ran 1 suite in 33m52.28995319s Test Suite Failed E0420 19:39:43.080138 18073 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=1776711943 --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