./mage -v ci:teste2e Running target: CI:TestE2E I0421 03:02:50.959234 18115 magefile.go:529] setting up new custom bundle for testing... I0421 03:02:51.288535 18115 util.go:512] found credentials for image ref quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1776740571-wopo -> user: redhat-appstudio-qe+redhat_appstudio_quality Creating Tekton Bundle: - Added Pipeline: docker-build to image I0421 03:02:52.476534 18115 bundle.go:57] image digest for a new tekton bundle quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1776740571-wopo: quay.io/redhat-appstudio-qe/test-images@sha256:747a00dff112ab949db3188fe4da9adb31b04a8d876f2351be2f42bf0b18be8a I0421 03:02:52.476559 18115 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-1776740571-wopo I0421 03:02:52.476581 18115 image_controller.go:49] checking if repository is image-controller I0421 03:02:52.476587 18115 build_service.go:50] checking if repository is build-service I0421 03:02:52.476592 18115 build_service.go:31] require sprayproxy registering is set to TRUE I0421 03:02:52.476596 18115 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 I0421 03:02:56.018140 18115 e2e_repo.go:347] checking if repository is e2e-tests I0421 03:02:56.018185 18115 release_service.go:50] checking if repository is release-service I0421 03:02:57.002981 18115 release_service_catalog.go:104] checking if repository is release-service-catalog I0421 03:02:57.003000 18115 integration_service.go:49] checking if repository is integration-service I0421 03:02:57.003006 18115 types.go:155] The following rules have matched build-service repo CI Workflow Rule. I0421 03:02:57.003010 18115 types.go:180] Will apply rules exec: ginkgo "--seed=1776740570" "--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 v1.41.3 go: downloading github.com/aws/aws-sdk-go-v2/config v1.31.3 go: downloading github.com/aws/aws-sdk-go-v2/service/ec2 v1.143.0 go: downloading github.com/klauspost/crc32 v1.3.0 go: downloading github.com/minio/crc64nvme v1.1.1 go: downloading github.com/go-ini/ini v1.67.0 go: downloading github.com/dustin/go-humanize v1.0.1 go: downloading github.com/rs/xid v1.6.0 go: downloading github.com/tinylib/msgp v1.6.1 go: downloading github.com/minio/md5-simd v1.1.2 go: downloading github.com/go-openapi/strfmt v0.23.0 go: downloading github.com/go-playground/validator/v10 v10.17.0 go: downloading github.com/aws/smithy-go v1.24.2 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/oklog/ulid v1.3.1 go: downloading github.com/go-openapi/errors v0.22.2 go: downloading github.com/asaskevich/govalidator v0.0.0-20230301143203-a9d515a09cc2 go: downloading github.com/aws/aws-sdk-go-v2/service/sts v1.38.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/feature/ec2/imds v1.18.4 go: downloading github.com/aws/aws-sdk-go-v2/service/sso v1.28.2 go: downloading github.com/aws/aws-sdk-go-v2/service/ssooidc v1.34.0 go: downloading github.com/google/go-github/v45 v45.2.0 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/philhofer/fwd v1.2.0 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 go: downloading github.com/gabriel-vasile/mimetype v1.4.3 go: downloading github.com/leodido/go-urn v1.3.0 go: downloading github.com/go-playground/universal-translator v0.18.1 go: downloading github.com/go-playground/locales v0.14.1 Running Suite: Red Hat App Studio E2E tests - /tmp/tmp.YASifbV3l6/cmd ===================================================================== Random Seed: 1776740570 Will run 147 of 461 specs Running in parallel across 20 processes 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 if the release CR is created [release-pipelines, rh-push-to-registry-redhat-io, PushToRedhatIO] /tmp/tmp.YASifbV3l6/tests/release/pipelines/rh_push_to_registry_redhat_io.go:108 ------------------------------ SS ------------------------------ 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.YASifbV3l6/tests/release/pipelines/rh_push_to_registry_redhat_io.go:118 ------------------------------ SS ------------------------------ 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.YASifbV3l6/tests/release/pipelines/rh_push_to_registry_redhat_io.go:148 ------------------------------ S ------------------------------ 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.YASifbV3l6/tests/release/pipelines/fbc_release.go:123 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/rh_push_to_registry_redhat_io.go:159 ------------------------------ S ------------------------------ 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.YASifbV3l6/tests/release/pipelines/fbc_release.go:128 ------------------------------ SSSS ------------------------------ 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.YASifbV3l6/tests/release/pipelines/fbc_release.go:132 ------------------------------ SSS ------------------------------ 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.YASifbV3l6/tests/build/build_templates.go:507 ------------------------------ 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.YASifbV3l6/tests/build/build_templates.go:569 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/rh_push_to_external_registry.go:215 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/rhtap_service_push.go:150 ------------------------------ S ------------------------------ 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.YASifbV3l6/tests/release/pipelines/rh_push_to_external_registry.go:226 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/rh_push_to_external_registry.go:233 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/fbc_release.go:136 ------------------------------ 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.YASifbV3l6/tests/build/build_templates.go:744 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/rhtap_service_push.go:160 ------------------------------ SSSS ------------------------------ 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.YASifbV3l6/tests/release/pipelines/rhtap_service_push.go:190 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/fbc_release.go:178 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/rh_push_to_external_registry.go:248 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/rh_push_to_external_registry.go:265 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/rhtap_service_push.go:200 ------------------------------ 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.YASifbV3l6/tests/build/multi-platform.go:120 ------------------------------ SSS ------------------------------ 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.YASifbV3l6/tests/build/multi-platform.go:124 ------------------------------ S ------------------------------ 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.YASifbV3l6/tests/release/pipelines/fbc_release.go:183 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/fbc_release.go:187 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/release_to_github.go:138 ------------------------------ 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.YASifbV3l6/tests/build/multi-platform.go:127 ------------------------------ SSSS ------------------------------ 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.YASifbV3l6/tests/release/pipelines/multiarch_advisories.go:112 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/release_to_github.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 that PipelineRun completes successfully [multi-platform, aws-host-pool] /tmp/tmp.YASifbV3l6/tests/build/multi-platform.go:148 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/fbc_release.go:191 ------------------------------ SSS ------------------------------ 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.YASifbV3l6/tests/release/pipelines/fbc_release.go:233 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/fbc_release.go:238 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/release_to_github.go:181 ------------------------------ 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.YASifbV3l6/tests/build/multi-platform.go:152 ------------------------------ S ------------------------------ 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.YASifbV3l6/tests/release/pipelines/fbc_release.go:242 ------------------------------ S ------------------------------ 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.YASifbV3l6/tests/release/pipelines/multiarch_advisories.go:122 ------------------------------ SSS ------------------------------ 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.YASifbV3l6/tests/release/pipelines/release_to_github.go:192 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/multiarch_advisories.go:152 ------------------------------ SSS ------------------------------ 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.YASifbV3l6/tests/release/pipelines/fbc_release.go:246 ------------------------------ 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.YASifbV3l6/tests/build/multi-platform.go:251 ------------------------------ S ------------------------------ 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.YASifbV3l6/tests/release/pipelines/push_to_external_registry.go:157 ------------------------------ SSSS ------------------------------ 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.YASifbV3l6/tests/build/build_templates.go:507 ------------------------------ SSS ------------------------------ 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.YASifbV3l6/tests/release/pipelines/multiarch_advisories.go:163 ------------------------------ 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.YASifbV3l6/tests/build/multi-platform.go:255 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/fbc_release.go:286 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/push_to_external_registry.go:164 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/rh_advisories.go:117 ------------------------------ 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.YASifbV3l6/tests/build/multi-platform.go:259 ------------------------------ SSSS ------------------------------ 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.YASifbV3l6/tests/release/pipelines/fbc_release.go:291 ------------------------------ S ------------------------------ 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.YASifbV3l6/tests/release/pipelines/push_to_external_registry.go:168 ------------------------------ SS ------------------------------ 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.YASifbV3l6/tests/release/pipelines/rh_advisories.go:127 ------------------------------ 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.YASifbV3l6/tests/build/multi-platform.go:263 ------------------------------ 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.YASifbV3l6/tests/release/pipelines/push_to_external_registry.go:175 ------------------------------ 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.YASifbV3l6/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 verifies the fbc release pipelinerun is running and succeeds [release-pipelines, fbc-release, fbcPreGA] /tmp/tmp.YASifbV3l6/tests/release/pipelines/fbc_release.go:295 ------------------------------ SSSS ------------------------------ 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.YASifbV3l6/tests/release/pipelines/rh_advisories.go:157 ------------------------------ 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 check cleanup happened successfully [multi-platform, aws-dynamic] /tmp/tmp.YASifbV3l6/tests/build/multi-platform.go:267 ------------------------------ SS ------------------------------ 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.YASifbV3l6/tests/release/pipelines/fbc_release.go:299 ------------------------------ SSSS ------------------------------ 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.YASifbV3l6/tests/build/multi-platform.go:341 ------------------------------ SS ------------------------------ 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.YASifbV3l6/tests/release/pipelines/rh_advisories.go:168 ------------------------------ 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.YASifbV3l6/tests/build/build_templates.go:744 ------------------------------ SSS ------------------------------ 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.YASifbV3l6/tests/build/multi-platform.go:345 ------------------------------ SSSSSSSSS ------------------------------ 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.YASifbV3l6/tests/build/multi-platform.go:349 ------------------------------ SSSS ------------------------------ 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.YASifbV3l6/tests/build/multi-platform.go:353 ------------------------------ SSSSSSSS ------------------------------ 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.YASifbV3l6/tests/build/multi-platform.go:357 ------------------------------ SS ------------------------------ 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.YASifbV3l6/tests/build/multi-platform.go:432 ------------------------------ SSSSSSS ------------------------------ 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.YASifbV3l6/tests/build/multi-platform.go:436 ------------------------------ SSS ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params when context points to a file [build-templates] /tmp/tmp.YASifbV3l6/tests/build/tkn-bundle.go:188 ------------------------------ SSSSS ------------------------------ 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.YASifbV3l6/tests/build/multi-platform.go:440 ------------------------------ S ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params creates Tekton bundles from specific context [build-templates] /tmp/tmp.YASifbV3l6/tests/build/tkn-bundle.go:199 ------------------------------ 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.YASifbV3l6/tests/build/build_templates.go:507 ------------------------------ SSS ------------------------------ 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.YASifbV3l6/tests/build/multi-platform.go:444 ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params when context is the root directory [build-templates] /tmp/tmp.YASifbV3l6/tests/build/tkn-bundle.go:209 ------------------------------ SSSS ------------------------------ 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.YASifbV3l6/tests/build/tkn-bundle.go:218 ------------------------------ 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.YASifbV3l6/tests/build/build_templates.go:569 ------------------------------ S ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params creates Tekton bundles when using negation [build-templates] /tmp/tmp.YASifbV3l6/tests/build/tkn-bundle.go:228 ------------------------------ SSSS ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params allows overriding HOME environment variable [build-templates] /tmp/tmp.YASifbV3l6/tests/build/tkn-bundle.go:238 ------------------------------ SS ------------------------------ P [PENDING] [task-suite tkn bundle task] creates Tekton bundles with different params allows overriding STEP image [build-templates] /tmp/tmp.YASifbV3l6/tests/build/tkn-bundle.go:247 ------------------------------ SSS ------------------------------ 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.YASifbV3l6/tests/build/multi-platform.go:448 ------------------------------ SSSSSSS ------------------------------ 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.YASifbV3l6/tests/build/build_templates.go:744 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS• ------------------------------ • [FAILED] [15.980 seconds] [build-service-suite Build service E2E tests] test git provider gh 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, github, pac-custom-default-branch] [BeforeAll] /tmp/tmp.YASifbV3l6/tests/build/pac_build.go:54 [It] /tmp/tmp.YASifbV3l6/tests/build/pac_build.go:136 Timeline >> [FAILED] in [BeforeAll] - /tmp/tmp.YASifbV3l6/tests/build/pac_build.go:98 @ 04/21/26 03:05:29.995 error getting logs for pod/container image-controller-notification-resetter-cronjob-29612340-fp6vv/notification-resetter: error in opening the stream: container "notification-resetter" in pod "image-controller-notification-resetter-cronjob-29612340-fp6vv" is waiting to start: trying and failing to pull image << Timeline [FAILED] Unexpected error: <*errors.errorString | 0xc0015ea530>: error when getting the base branch name 'default' for the repo 'devfile-sample-hello-world-foogvd': GET https://api.github.com/repos/redhat-appstudio-qe/devfile-sample-hello-world-foogvd/git/ref/heads/default: 404 Not Found [] { s: "error when getting the base branch name 'default' for the repo 'devfile-sample-hello-world-foogvd': GET https://api.github.com/repos/redhat-appstudio-qe/devfile-sample-hello-world-foogvd/git/ref/heads/default: 404 Not Found []", } occurred In [BeforeAll] at: /tmp/tmp.YASifbV3l6/tests/build/pac_build.go:98 @ 04/21/26 03:05:29.995 ------------------------------ 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.YASifbV3l6/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.YASifbV3l6/tests/build/pac_build.go:642 ------------------------------ S••••• ------------------------------ • [FAILED] [121.833 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.YASifbV3l6/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"} 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.YASifbV3l6/tests/build/secret_lookup.go:175 @ 04/21/26 03:07:48.034 error getting logs for pod/container image-controller-notification-resetter-cronjob-29612340-fp6vv/notification-resetter: error in opening the stream: container "notification-resetter" in pod "image-controller-notification-resetter-cronjob-29612340-fp6vv" is waiting to start: trying and failing to pull image << Timeline [FAILED] Timed out after 120.001s. failed while checking build status for component "component-one-jytm" is correct Expected : false to be true In [It] at: /tmp/tmp.YASifbV3l6/tests/build/secret_lookup.go:175 @ 04/21/26 03:07:48.034 ------------------------------ 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.YASifbV3l6/tests/build/secret_lookup.go:206 ------------------------------ • [FAILED] [192.616 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.YASifbV3l6/tests/build/annotations.go:89 Timeline >> Image repository for component test-annotations-qnzqmm in namespace build-e2e-yhdk 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.YASifbV3l6/tests/build/annotations.go:119 @ 04/21/26 03:08:26.419 error getting logs for pod/container image-controller-notification-resetter-cronjob-29612340-fp6vv/notification-resetter: error in opening the stream: container "notification-resetter" in pod "image-controller-notification-resetter-cronjob-29612340-fp6vv" is waiting to start: trying and failing to pull image << Timeline [FAILED] Timed out after 120.000s. failed while checking build status message for component "test-annotations-qnzqmm" is correct after setting invalid annotations Expected success, but got an error: <*errors.errorString | 0xc00140fba0>: 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.YASifbV3l6/tests/build/annotations.go:119 @ 04/21/26 03:08:26.419 ------------------------------ • [FAILED] [326.148 seconds] [build-service-suite Build service E2E tests] test git provider gl 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, gitlab, pac-custom-default-branch] /tmp/tmp.YASifbV3l6/tests/build/pac_build.go:136 Timeline >> Image repository for component gl-test-custom-default-gginsf in namespace build-e2e-gpyy do not have right state ('' != 'ready') yet but it has status { { } { } []}. [FAILED] in [It] - /tmp/tmp.YASifbV3l6/tests/build/pac_build.go:150 @ 04/21/26 03:10:39.901 error getting logs for pod/container image-controller-notification-resetter-cronjob-29612340-fp6vv/notification-resetter: error in opening the stream: container "notification-resetter" in pod "image-controller-notification-resetter-cronjob-29612340-fp6vv" is waiting to start: trying and failing to pull image << Timeline [FAILED] Timed out after 300.001s. timed out when waiting for init PaC PR to be created against default branch in konflux-qe/devfile-sample-hello-world-gblhjn repository Expected : false to be true In [It] at: /tmp/tmp.YASifbV3l6/tests/build/pac_build.go:150 @ 04/21/26 03:10:39.901 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ 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.YASifbV3l6/tests/build/pac_build.go:600 ------------------------------ 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.YASifbV3l6/tests/build/pac_build.go:642 ------------------------------ S ------------------------------ • [FAILED] [345.004 seconds] [build-service-suite Build service E2E tests] test git provider fj 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, forgejo, pac-custom-default-branch] /tmp/tmp.YASifbV3l6/tests/build/pac_build.go:136 Timeline >> Image repository for component fj-test-custom-default-rwyxly in namespace build-e2e-mttm do not have right state ('' != 'ready') yet but it has status { { } { } []}. [FAILED] in [It] - /tmp/tmp.YASifbV3l6/tests/build/pac_build.go:150 @ 04/21/26 03:10:58.722 error getting logs for pod/container image-controller-notification-resetter-cronjob-29612340-fp6vv/notification-resetter: error in opening the stream: container "notification-resetter" in pod "image-controller-notification-resetter-cronjob-29612340-fp6vv" is waiting to start: trying and failing to pull image << Timeline [FAILED] Timed out after 313.499s. timed out when waiting for init PaC PR to be created against default branch in konflux-qe/devfile-sample-hello-world-uonxig repository Expected : false to be true In [It] at: /tmp/tmp.YASifbV3l6/tests/build/pac_build.go:150 @ 04/21/26 03:10:58.722 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ 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.YASifbV3l6/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.YASifbV3l6/tests/build/pac_build.go:642 ------------------------------ S ------------------------------ • [FAILED] [1801.571 seconds] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace [It] triggers a PipelineRun for component go-component-wnzssm [build-service, github, pac-build, multi-component] /tmp/tmp.YASifbV3l6/tests/build/multi_component.go:125 Timeline >> PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm PipelineRun has not been created yet for the component build-e2e-ykou/go-component-wnzssm [FAILED] in [It] - /tmp/tmp.YASifbV3l6/tests/build/multi_component.go:137 @ 04/21/26 03:35:27.173 error getting logs for pod/container image-controller-notification-resetter-cronjob-29612340-fp6vv/notification-resetter: error in opening the stream: container "notification-resetter" in pod "image-controller-notification-resetter-cronjob-29612340-fp6vv" is waiting to start: trying and failing to pull image << Timeline [FAILED] Timed out after 1800.001s. timed out when waiting for the PipelineRun to start for the component go-component-wnzssm/build-e2e-ykou Expected success, but got an error: <*errors.errorString | 0xc00116aa10>: no pipelinerun found for component go-component-wnzssm { s: "no pipelinerun found for component go-component-wnzssm", } In [It] at: /tmp/tmp.YASifbV3l6/tests/build/multi_component.go:137 @ 04/21/26 03:35:27.173 ------------------------------ SSSSSSSSSSSSS ------------------------------ • [FAILED] [1806.908 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.YASifbV3l6/tests/build/renovate.go:259 Timeline >> PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx PipelineRun has not been created yet for the component build-e2e-lajr/gh-multi-component-parent-fvtx [FAILED] in [It] - /tmp/tmp.YASifbV3l6/tests/build/renovate.go:272 @ 04/21/26 03:36:11.303 error getting logs for pod/container image-controller-notification-resetter-cronjob-29612340-fp6vv/notification-resetter: error in opening the stream: container "notification-resetter" in pod "image-controller-notification-resetter-cronjob-29612340-fp6vv" is waiting to start: trying and failing to pull image << Timeline [FAILED] Timed out after 1800.001s. timed out when waiting for the PipelineRun to start for the component gh-multi-component-parent-fvtx/build-e2e-lajr Expected success, but got an error: <*errors.errorString | 0xc0012621a0>: no pipelinerun found for component gh-multi-component-parent-fvtx { s: "no pipelinerun found for component gh-multi-component-parent-fvtx", } In [It] at: /tmp/tmp.YASifbV3l6/tests/build/renovate.go:272 @ 04/21/26 03:36:11.303 ------------------------------ SSSSSSSSSSSS ------------------------------ • [FAILED] [1806.959 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.YASifbV3l6/tests/build/renovate.go:259 Timeline >> PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw PipelineRun has not been created yet for the component build-e2e-rjeh/fj-multi-component-parent-ghlw [FAILED] in [It] - /tmp/tmp.YASifbV3l6/tests/build/renovate.go:272 @ 04/21/26 03:36:21.507 error getting logs for pod/container image-controller-notification-resetter-cronjob-29612340-fp6vv/notification-resetter: error in opening the stream: container "notification-resetter" in pod "image-controller-notification-resetter-cronjob-29612340-fp6vv" is waiting to start: trying and failing to pull image << Timeline [FAILED] Timed out after 1800.000s. timed out when waiting for the PipelineRun to start for the component fj-multi-component-parent-ghlw/build-e2e-rjeh Expected success, but got an error: <*errors.errorString | 0xc001cf02a0>: no pipelinerun found for component fj-multi-component-parent-ghlw { s: "no pipelinerun found for component fj-multi-component-parent-ghlw", } In [It] at: /tmp/tmp.YASifbV3l6/tests/build/renovate.go:272 @ 04/21/26 03:36:21.507 ------------------------------ SSSSSSSSSSSS ------------------------------ • [FAILED] [1807.183 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.YASifbV3l6/tests/build/renovate.go:259 Timeline >> PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks PipelineRun has not been created yet for the component build-e2e-chce/gl-multi-component-parent-iiks [FAILED] in [It] - /tmp/tmp.YASifbV3l6/tests/build/renovate.go:272 @ 04/21/26 03:36:21.779 error getting logs for pod/container image-controller-notification-resetter-cronjob-29612340-fp6vv/notification-resetter: error in opening the stream: container "notification-resetter" in pod "image-controller-notification-resetter-cronjob-29612340-fp6vv" is waiting to start: trying and failing to pull image << Timeline [FAILED] Timed out after 1800.001s. timed out when waiting for the PipelineRun to start for the component gl-multi-component-parent-iiks/build-e2e-chce Expected success, but got an error: <*errors.errorString | 0xc001ec2770>: no pipelinerun found for component gl-multi-component-parent-iiks { s: "no pipelinerun found for component gl-multi-component-parent-iiks", } In [It] at: /tmp/tmp.YASifbV3l6/tests/build/renovate.go:272 @ 04/21/26 03:36:21.779 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS Summarizing 9 Failures: [FAIL] [build-service-suite Build service E2E tests] test git provider gh 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, github, pac-custom-default-branch] /tmp/tmp.YASifbV3l6/tests/build/pac_build.go:98 [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.YASifbV3l6/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.YASifbV3l6/tests/build/annotations.go:119 [FAIL] [build-service-suite Build service E2E tests] test git provider gl 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, gitlab, pac-custom-default-branch] /tmp/tmp.YASifbV3l6/tests/build/pac_build.go:150 [FAIL] [build-service-suite Build service E2E tests] test git provider fj 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, forgejo, pac-custom-default-branch] /tmp/tmp.YASifbV3l6/tests/build/pac_build.go:150 [FAIL] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace [It] triggers a PipelineRun for component go-component-wnzssm [build-service, github, pac-build, multi-component] /tmp/tmp.YASifbV3l6/tests/build/multi_component.go:137 [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.YASifbV3l6/tests/build/renovate.go:272 [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.YASifbV3l6/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.YASifbV3l6/tests/build/renovate.go:272 Ran 15 of 461 Specs in 1874.939 seconds FAIL! -- 6 Passed | 9 Failed | 88 Pending | 358 Skipped Ginkgo ran 1 suite in 33m32.084148646s Test Suite Failed E0421 03:36:29.105533 18115 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=1776740570 --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