go: downloading github.com/devfile/library/v2 v2.2.1-0.20230418160146-e75481b7eebd go: downloading github.com/google/go-containerregistry v0.21.0 go: downloading github.com/konflux-ci/application-api v0.0.0-20260529131129-a9594acdc104 go: downloading github.com/konflux-ci/e2e-tests v0.0.0-20260707100404-eca3dcc01e3c go: downloading github.com/onsi/gomega v1.39.1 go: downloading github.com/openshift/library-go v0.0.0-20220525173854-9b950a41acdc go: downloading github.com/tektoncd/pipeline v1.9.2 go: downloading k8s.io/api v0.34.2 go: downloading k8s.io/apimachinery v0.34.2 go: downloading knative.dev/pkg v0.0.0-20250424013628-d5e74d29daa3 go: downloading sigs.k8s.io/controller-runtime v0.20.2 go: downloading sigs.k8s.io/yaml v1.6.0 go: downloading github.com/fatih/color v1.18.0 go: downloading github.com/go-git/go-git/v5 v5.16.5 go: downloading github.com/gobwas/glob v0.2.3 go: downloading github.com/gregjones/httpcache v0.0.0-20190611155906-901d90724c79 go: downloading github.com/pkg/errors v0.9.1 go: downloading k8s.io/client-go v0.34.2 go: downloading k8s.io/klog v1.0.0 go: downloading github.com/docker/cli v29.2.1+incompatible go: downloading github.com/mitchellh/go-homedir v1.1.0 go: downloading github.com/opencontainers/go-digest v1.0.0 go: downloading k8s.io/apiextensions-apiserver v0.34.2 go: downloading github.com/konflux-ci/image-controller v0.0.0-20260623200458-d2ed99f6f8a6 go: downloading k8s.io/utils v0.0.0-20251002143259-bc988d571ff4 go: downloading github.com/opencontainers/image-spec v1.1.1 go: downloading oras.land/oras-go/v2 v2.5.0 go: downloading github.com/conforma/crds/api v0.1.7 go: downloading github.com/openshift-pipelines/pipelines-as-code v0.34.0 go: downloading gopkg.in/yaml.v2 v2.4.0 go: downloading github.com/avast/retry-go/v4 v4.3.3 go: downloading k8s.io/klog/v2 v2.130.1 go: downloading github.com/magefile/mage v1.14.0 go: downloading github.com/moby/buildkit v0.12.5 go: downloading github.com/tektoncd/cli v0.44.1 go: downloading github.com/go-logr/logr v1.4.3 go: downloading github.com/google/go-cmp v0.7.0 go: downloading github.com/google/cel-go v0.27.0 go: downloading k8s.io/kube-openapi v0.0.0-20260127142750-a19766b6e2d4 go: downloading github.com/gogo/protobuf v1.3.2 go: downloading sigs.k8s.io/randfill v1.0.0 go: downloading sigs.k8s.io/structured-merge-diff/v6 v6.3.2 go: downloading github.com/evanphx/json-patch/v5 v5.9.11 go: downloading go.yaml.in/yaml/v2 v2.4.3 go: downloading github.com/fsnotify/fsnotify v1.9.0 go: downloading github.com/spf13/afero v1.15.0 go: downloading github.com/mattn/go-colorable v0.1.14 go: downloading github.com/mattn/go-isatty v0.0.20 go: downloading dario.cat/mergo v1.0.2 go: downloading github.com/ProtonMail/go-crypto v1.3.0 go: downloading github.com/go-git/go-billy/v5 v5.7.0 go: downloading github.com/sergi/go-diff v1.4.0 go: downloading github.com/peterbourgon/diskv v2.0.1+incompatible go: downloading gopkg.in/inf.v0 v0.9.1 go: downloading github.com/sirupsen/logrus v1.9.4 go: downloading github.com/docker/distribution v2.8.2+incompatible go: downloading codeberg.org/mvdkleijn/forgejo-sdk/forgejo/v2 v2.2.0 go: downloading github.com/gofri/go-github-ratelimit v1.0.3-0.20230428184158-a500e14de53f go: downloading github.com/google/go-github/v66 v66.0.0 go: downloading golang.org/x/oauth2 v0.35.0 go: downloading github.com/xanzy/go-gitlab v0.114.0 go: downloading github.com/codeready-toolchain/api v0.0.0-20231217224957-34f7cb3fcbf7 go: downloading github.com/konflux-ci/integration-service v0.0.0-20260327093127-2b0e36d45a91 go: downloading github.com/konflux-ci/release-service v0.0.0-20260127184035-c36c56a3c440 go: downloading github.com/openshift/api v0.0.0-20260112161841-5b45879294d5 go: downloading github.com/openshift/client-go v0.0.0-20260108185524-48f4ccfc4e13 go: downloading github.com/redhat-appstudio/jvm-build-service v0.0.0-20240126122210-0e2ee7e2e5b0 go: downloading github.com/vmware-tanzu/velero v1.17.2 go: downloading github.com/konflux-ci/operator-toolkit v0.0.0-20251118152634-b4f41f073069 go: downloading github.com/codeready-toolchain/toolchain-common v0.0.0-20220523142428-2558e76260fb go: downloading github.com/codeready-toolchain/toolchain-e2e v0.0.0-20220525131508-60876bfb99d3 go: downloading github.com/bmatcuk/doublestar/v4 v4.7.1 go: downloading github.com/munnerz/goautoneg v0.0.0-20191010083416-a7dc8b61c822 go: downloading golang.org/x/net v0.50.0 go: downloading github.com/spf13/pflag v1.0.10 go: downloading golang.org/x/term v0.41.0 go: downloading github.com/docker/docker v23.0.7+incompatible go: downloading golang.org/x/sys v0.42.0 go: downloading go.yaml.in/yaml/v3 v3.0.4 go: downloading cel.dev/expr v0.25.1 go: downloading google.golang.org/genproto/googleapis/api v0.0.0-20260128011058-8636f8732409 go: downloading google.golang.org/protobuf v1.36.11 go: downloading github.com/emicklei/go-restful/v3 v3.13.0 go: downloading github.com/go-openapi/jsonreference v0.21.5 go: downloading github.com/go-openapi/swag v0.25.5 go: downloading github.com/google/gnostic-models v0.7.1 go: downloading sigs.k8s.io/json v0.0.0-20250730193827-2d320260d730 go: downloading github.com/json-iterator/go v1.1.12 go: downloading golang.org/x/text v0.34.0 go: downloading golang.org/x/crypto v0.48.0 go: downloading github.com/cyphar/filepath-securejoin v0.3.6 go: downloading github.com/go-git/gcfg v1.5.1-0.20230307220236-3a3c6141e376 go: downloading github.com/pjbgf/sha1cd v0.5.0 go: downloading github.com/emirpasic/gods v1.18.1 go: downloading github.com/jbenet/go-context v0.0.0-20150711004518-d14ea06fba99 go: downloading github.com/google/btree v1.1.3 go: downloading github.com/docker/docker-credential-helpers v0.9.3 go: downloading github.com/containerd/stargz-snapshotter/estargz v0.18.2 go: downloading github.com/klauspost/compress v1.18.4 go: downloading github.com/42wim/httpsig v1.2.3 go: downloading github.com/go-fed/httpsig v1.1.1-0.20201223112313-55836744818e go: downloading github.com/hashicorp/go-version v1.8.0 go: downloading github.com/google/go-querystring v1.2.0 go: downloading github.com/hashicorp/go-cleanhttp v0.5.2 go: downloading github.com/hashicorp/go-retryablehttp v0.7.8 go: downloading golang.org/x/time v0.14.0 go: downloading github.com/santhosh-tekuri/jsonschema/v5 v5.3.1 go: downloading github.com/hashicorp/go-multierror v1.1.1 go: downloading github.com/operator-framework/operator-lib v0.19.0 go: downloading github.com/fxamacker/cbor/v2 v2.9.0 go: downloading github.com/containerd/typeurl/v2 v2.2.2 go: downloading contrib.go.opencensus.io/exporter/ocagent v0.7.1-0.20230502190836-7399e0f8ee5e go: downloading contrib.go.opencensus.io/exporter/prometheus v0.4.2 go: downloading go.opencensus.io v0.24.0 go: downloading go.uber.org/zap v1.27.1 go: downloading google.golang.org/grpc v1.79.3 go: downloading github.com/antlr4-go/antlr/v4 v4.13.1 go: downloading google.golang.org/genproto/googleapis/rpc v0.0.0-20260128011058-8636f8732409 go: downloading gomodules.xyz/jsonpatch/v2 v2.5.0 go: downloading github.com/go-openapi/jsonpointer v0.22.5 go: downloading github.com/go-openapi/swag/cmdutils v0.25.5 go: downloading github.com/go-openapi/swag/conv v0.25.5 go: downloading github.com/go-openapi/swag/fileutils v0.25.5 go: downloading github.com/go-openapi/swag/jsonname v0.25.5 go: downloading github.com/go-openapi/swag/jsonutils v0.25.5 go: downloading github.com/go-openapi/swag/loading v0.25.5 go: downloading github.com/go-openapi/swag/mangling v0.25.5 go: downloading github.com/go-openapi/swag/netutils v0.25.5 go: downloading github.com/go-openapi/swag/stringutils v0.25.5 go: downloading github.com/go-openapi/swag/typeutils v0.25.5 go: downloading github.com/go-openapi/swag/yamlutils v0.25.5 go: downloading github.com/modern-go/concurrent v0.0.0-20180306012644-bacd9c7ef1dd go: downloading github.com/modern-go/reflect2 v1.0.3-0.20250322232337-35a7c28c31ee go: downloading github.com/cloudflare/circl v1.6.3 go: downloading gopkg.in/warnings.v0 v0.1.2 go: downloading github.com/golang/groupcache v0.0.0-20241129210726-2c02b8208cf8 go: downloading github.com/kevinburke/ssh_config v1.4.0 go: downloading github.com/skeema/knownhosts v1.3.2 go: downloading github.com/xanzy/ssh-agent v0.3.3 go: downloading github.com/klauspost/cpuid/v2 v2.3.0 go: downloading github.com/vbatts/tar-split v0.12.2 go: downloading github.com/prometheus/client_golang v1.23.2 go: downloading github.com/hashicorp/errwrap v1.1.0 go: downloading github.com/x448/float16 v0.8.4 go: downloading github.com/davecgh/go-spew v1.1.2-0.20180830191138-d8f796af33cc go: downloading gopkg.in/evanphx/json-patch.v4 v4.13.0 go: downloading github.com/census-instrumentation/opencensus-proto v0.4.1 go: downloading github.com/golang/protobuf v1.5.4 go: downloading google.golang.org/api v0.262.0 go: downloading github.com/prometheus/statsd_exporter v0.28.0 go: downloading go.uber.org/multierr v1.11.0 go: downloading github.com/blendle/zapdriver v1.3.1 go: downloading golang.org/x/exp v0.0.0-20260112195511-716be5621a96 go: downloading github.com/pmezard/go-difflib v1.0.1-0.20181226105442-5d4384ee4fb2 go: downloading github.com/google/uuid v1.6.0 go: downloading github.com/beorn7/perks v1.0.1 go: downloading github.com/cespare/xxhash/v2 v2.3.0 go: downloading github.com/prometheus/client_model v0.6.2 go: downloading github.com/prometheus/common v0.67.5 go: downloading github.com/prometheus/procfs v0.19.2 go: downloading github.com/grpc-ecosystem/grpc-gateway/v2 v2.27.6 Running Suite: Build Pipeline E2E - /workspace/source/e2e-tests/tests/build =========================================================================== Random Seed: 1786960483 Will run 128 of 128 specs Running in parallel across 3 processes ------------------------------ • [31.838 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "from-scratch" triggers a PipelineRun [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:89 Timeline >> Image repository for component component-from-scratch in namespace build-e2e-from-scratch do not have right state ('' != 'ready') yet but it has status { { } { } []}. Created component for scenario: from-scratch RUNNING SCENARIO: from-scratch PipelineRun has not been created yet for the component build-e2e-from-scratch/component-from-scratch << Timeline ------------------------------ • [45.133 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "oci-archive" triggers a PipelineRun [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:89 Timeline >> Image repository for component component-oci-archive in namespace build-e2e-oci-archive do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component component-oci-archive in namespace build-e2e-oci-archive do not have right state ('' != 'ready') yet but it has status { { } { } []}. Created component for scenario: oci-archive RUNNING SCENARIO: oci-archive PipelineRun has not been created yet for the component build-e2e-oci-archive/component-oci-archive << Timeline ------------------------------ • [53.782 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-bundler" triggers a PipelineRun [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:89 Timeline >> Image repository for component component-prefetch-bundler in namespace build-e2e-prefetch-bundler do not have right state ('' != 'ready') yet but it has status { { } { } []}. Created component for scenario: prefetch-bundler RUNNING SCENARIO: prefetch-bundler PipelineRun has not been created yet for the component build-e2e-prefetch-bundler/component-prefetch-bundler PipelineRun has not been created yet for the component build-e2e-prefetch-bundler/component-prefetch-bundler << Timeline ------------------------------ • [400.186 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "from-scratch" the PipelineRun should eventually finish [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:103 Timeline >> PipelineRun component-from-scratch-on-pull-request-hdcbq found for Component build-e2e-from-scratch/component-from-scratch PipelineRun component-from-scratch-on-pull-request-hdcbq reason: ResolvingTaskRef PipelineRun component-from-scratch-on-pull-request-hdcbq reason: Running PipelineRun component-from-scratch-on-pull-request-hdcbq reason: Running PipelineRun component-from-scratch-on-pull-request-hdcbq reason: Running PipelineRun component-from-scratch-on-pull-request-hdcbq reason: Running PipelineRun component-from-scratch-on-pull-request-hdcbq reason: Running PipelineRun component-from-scratch-on-pull-request-hdcbq reason: Running PipelineRun component-from-scratch-on-pull-request-hdcbq reason: Running PipelineRun component-from-scratch-on-pull-request-hdcbq reason: Running PipelineRun component-from-scratch-on-pull-request-hdcbq reason: Running PipelineRun component-from-scratch-on-pull-request-hdcbq reason: Running PipelineRun component-from-scratch-on-pull-request-hdcbq reason: Running PipelineRun component-from-scratch-on-pull-request-hdcbq reason: Running PipelineRun component-from-scratch-on-pull-request-hdcbq reason: Running PipelineRun component-from-scratch-on-pull-request-hdcbq reason: Running PipelineRun component-from-scratch-on-pull-request-hdcbq reason: Running PipelineRun component-from-scratch-on-pull-request-hdcbq reason: Running PipelineRun component-from-scratch-on-pull-request-hdcbq reason: Running PipelineRun component-from-scratch-on-pull-request-hdcbq reason: Running PipelineRun component-from-scratch-on-pull-request-hdcbq reason: Running PipelineRun component-from-scratch-on-pull-request-hdcbq reason: Completed << Timeline ------------------------------ • [1.265 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "from-scratch" should push Dockerfile to registry [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:123 ------------------------------ • [0.398 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "from-scratch" should validate tekton taskrun test results [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:130 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "from-scratch" [It] floating tags are created successfully [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:137 [SKIPPED] floating tag validation is not needed for: from-scratch In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:139 @ 08/17/26 10:04:27.886 ------------------------------ • [0.454 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "from-scratch" image manifest mediaType is correct [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:153 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "from-scratch" [It] should have Hermeto content in the SBOM in case the build was hermetic [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:180 [SKIPPED] Hermetic build is not enabled, skipping the test In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:182 @ 08/17/26 10:04:28.342 ------------------------------ S [SKIPPED] [1.073 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "from-scratch" [It] check for source images if enabled in pipeline [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:214 Timeline >> Source build is enabled: false [SKIPPED] in [It] - /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:04:28.342 << Timeline [SKIPPED] Skipping source image check since it is not enabled in the pipeline In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:04:28.342 ------------------------------ • [400.182 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "oci-archive" the PipelineRun should eventually finish [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:103 Timeline >> PipelineRun component-oci-archive-on-pull-request-pf8sq found for Component build-e2e-oci-archive/component-oci-archive PipelineRun component-oci-archive-on-pull-request-pf8sq reason: ResolvingTaskRef PipelineRun component-oci-archive-on-pull-request-pf8sq reason: Running PipelineRun component-oci-archive-on-pull-request-pf8sq reason: Running PipelineRun component-oci-archive-on-pull-request-pf8sq reason: Running PipelineRun component-oci-archive-on-pull-request-pf8sq reason: Running PipelineRun component-oci-archive-on-pull-request-pf8sq reason: Running PipelineRun component-oci-archive-on-pull-request-pf8sq reason: Running PipelineRun component-oci-archive-on-pull-request-pf8sq reason: Running PipelineRun component-oci-archive-on-pull-request-pf8sq reason: Running PipelineRun component-oci-archive-on-pull-request-pf8sq reason: Running PipelineRun component-oci-archive-on-pull-request-pf8sq reason: Running PipelineRun component-oci-archive-on-pull-request-pf8sq reason: Running PipelineRun component-oci-archive-on-pull-request-pf8sq reason: Running PipelineRun component-oci-archive-on-pull-request-pf8sq reason: Running PipelineRun component-oci-archive-on-pull-request-pf8sq reason: Running PipelineRun component-oci-archive-on-pull-request-pf8sq reason: Running PipelineRun component-oci-archive-on-pull-request-pf8sq reason: Running PipelineRun component-oci-archive-on-pull-request-pf8sq reason: Running PipelineRun component-oci-archive-on-pull-request-pf8sq reason: Running PipelineRun component-oci-archive-on-pull-request-pf8sq reason: Running PipelineRun component-oci-archive-on-pull-request-pf8sq reason: Completed << Timeline ------------------------------ • [1.509 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "oci-archive" should push Dockerfile to registry [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:123 ------------------------------ • [0.507 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "oci-archive" should validate tekton taskrun test results [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:130 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "oci-archive" [It] floating tags are created successfully [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:137 [SKIPPED] floating tag validation is not needed for: oci-archive In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:139 @ 08/17/26 10:04:41.531 ------------------------------ • [0.306 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "oci-archive" image manifest mediaType is correct [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:153 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "oci-archive" [It] should have Hermeto content in the SBOM in case the build was hermetic [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:180 [SKIPPED] Hermetic build is not enabled, skipping the test In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:182 @ 08/17/26 10:04:41.838 ------------------------------ S [SKIPPED] [2.994 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "oci-archive" [It] check for source images if enabled in pipeline [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:214 Timeline >> Source build is enabled: false [SKIPPED] in [It] - /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:04:41.839 << Timeline [SKIPPED] Skipping source image check since it is not enabled in the pipeline In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:04:41.839 ------------------------------ • [33.333 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-cargo" triggers a PipelineRun [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:89 Timeline >> Image repository for component component-prefetch-cargo in namespace build-e2e-prefetch-cargo do not have right state ('' != 'ready') yet but it has status { { } { } []}. Created component for scenario: prefetch-cargo RUNNING SCENARIO: prefetch-cargo PipelineRun has not been created yet for the component build-e2e-prefetch-cargo/component-prefetch-cargo << Timeline ------------------------------ • [33.281 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-generic" triggers a PipelineRun [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:89 Timeline >> Image repository for component component-prefetch-generic in namespace build-e2e-prefetch-generic do not have right state ('' != 'ready') yet but it has status { { } { } []}. Created component for scenario: prefetch-generic RUNNING SCENARIO: prefetch-generic PipelineRun has not been created yet for the component build-e2e-prefetch-generic/component-prefetch-generic << Timeline ------------------------------ • [480.171 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-bundler" the PipelineRun should eventually finish [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:103 Timeline >> PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 found for Component build-e2e-prefetch-bundler/component-prefetch-bundler PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: ResolvingTaskRef PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Running PipelineRun component-prefetch-bundler-on-pull-request-qt5s8 reason: Completed << Timeline ------------------------------ • [1.086 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-bundler" should push Dockerfile to registry [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:123 ------------------------------ • [0.421 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-bundler" should validate tekton taskrun test results [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:130 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-bundler" [It] floating tags are created successfully [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:137 [SKIPPED] floating tag validation is not needed for: prefetch-bundler In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:139 @ 08/17/26 10:06:09.66 ------------------------------ • [0.310 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-bundler" image manifest mediaType is correct [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:153 ------------------------------ • [0.324 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-bundler" should have Hermeto content in the SBOM in case the build was hermetic [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:180 ------------------------------ S [SKIPPED] [1.022 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-bundler" [It] check for source images if enabled in pipeline [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:214 Timeline >> Source build is enabled: false [SKIPPED] in [It] - /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:06:10.296 << Timeline [SKIPPED] Skipping source image check since it is not enabled in the pipeline In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:06:10.296 ------------------------------ • [33.635 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-gomod" triggers a PipelineRun [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:89 Timeline >> Created component for scenario: prefetch-gomod RUNNING SCENARIO: prefetch-gomod PipelineRun has not been created yet for the component build-e2e-prefetch-gomod/component-prefetch-gomod << Timeline ------------------------------ • [300.187 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-cargo" the PipelineRun should eventually finish [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:103 Timeline >> PipelineRun component-prefetch-cargo-on-pull-request-v5r4j found for Component build-e2e-prefetch-cargo/component-prefetch-cargo PipelineRun component-prefetch-cargo-on-pull-request-v5r4j reason: Running PipelineRun component-prefetch-cargo-on-pull-request-v5r4j reason: Running PipelineRun component-prefetch-cargo-on-pull-request-v5r4j reason: Running PipelineRun component-prefetch-cargo-on-pull-request-v5r4j reason: Running PipelineRun component-prefetch-cargo-on-pull-request-v5r4j reason: Running PipelineRun component-prefetch-cargo-on-pull-request-v5r4j reason: Running PipelineRun component-prefetch-cargo-on-pull-request-v5r4j reason: Running PipelineRun component-prefetch-cargo-on-pull-request-v5r4j reason: Running PipelineRun component-prefetch-cargo-on-pull-request-v5r4j reason: Running PipelineRun component-prefetch-cargo-on-pull-request-v5r4j reason: Running PipelineRun component-prefetch-cargo-on-pull-request-v5r4j reason: Running PipelineRun component-prefetch-cargo-on-pull-request-v5r4j reason: Running PipelineRun component-prefetch-cargo-on-pull-request-v5r4j reason: Running PipelineRun component-prefetch-cargo-on-pull-request-v5r4j reason: Running PipelineRun component-prefetch-cargo-on-pull-request-v5r4j reason: Running PipelineRun component-prefetch-cargo-on-pull-request-v5r4j reason: Completed << Timeline ------------------------------ • [1.590 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-cargo" should push Dockerfile to registry [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:123 ------------------------------ • [1.048 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-cargo" should validate tekton taskrun test results [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:130 ------------------------------ S [SKIPPED] [0.001 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-cargo" [It] floating tags are created successfully [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:137 [SKIPPED] floating tag validation is not needed for: prefetch-cargo In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:139 @ 08/17/26 10:10:05.577 ------------------------------ • [0.316 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-cargo" image manifest mediaType is correct [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:153 ------------------------------ • [0.306 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-cargo" should have Hermeto content in the SBOM in case the build was hermetic [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:180 ------------------------------ S [SKIPPED] [2.012 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-cargo" [It] check for source images if enabled in pipeline [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:214 Timeline >> Source build is enabled: false [SKIPPED] in [It] - /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:10:06.202 << Timeline [SKIPPED] Skipping source image check since it is not enabled in the pipeline In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:10:06.202 ------------------------------ • [33.990 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-npm" triggers a PipelineRun [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:89 Timeline >> Image repository for component component-prefetch-npm in namespace build-e2e-prefetch-npm do not have right state ('' != 'ready') yet but it has status { { } { } []}. Created component for scenario: prefetch-npm RUNNING SCENARIO: prefetch-npm PipelineRun has not been created yet for the component build-e2e-prefetch-npm/component-prefetch-npm << Timeline ------------------------------ • [240.171 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-gomod" the PipelineRun should eventually finish [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:103 Timeline >> PipelineRun component-prefetch-gomod-on-pull-request-gmd9x found for Component build-e2e-prefetch-gomod/component-prefetch-gomod PipelineRun component-prefetch-gomod-on-pull-request-gmd9x reason: Running PipelineRun component-prefetch-gomod-on-pull-request-gmd9x reason: Running PipelineRun component-prefetch-gomod-on-pull-request-gmd9x reason: Running PipelineRun component-prefetch-gomod-on-pull-request-gmd9x reason: Running PipelineRun component-prefetch-gomod-on-pull-request-gmd9x reason: Running PipelineRun component-prefetch-gomod-on-pull-request-gmd9x reason: Running PipelineRun component-prefetch-gomod-on-pull-request-gmd9x reason: Running PipelineRun component-prefetch-gomod-on-pull-request-gmd9x reason: Running PipelineRun component-prefetch-gomod-on-pull-request-gmd9x reason: Running PipelineRun component-prefetch-gomod-on-pull-request-gmd9x reason: Running PipelineRun component-prefetch-gomod-on-pull-request-gmd9x reason: Running PipelineRun component-prefetch-gomod-on-pull-request-gmd9x reason: Running PipelineRun component-prefetch-gomod-on-pull-request-gmd9x reason: Completed << Timeline ------------------------------ • [1.222 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-gomod" should push Dockerfile to registry [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:123 ------------------------------ • [0.413 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-gomod" should validate tekton taskrun test results [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:130 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-gomod" [It] floating tags are created successfully [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:137 [SKIPPED] floating tag validation is not needed for: prefetch-gomod In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:139 @ 08/17/26 10:10:46.763 ------------------------------ • [0.302 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-gomod" image manifest mediaType is correct [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:153 ------------------------------ • [0.209 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-gomod" should have Hermeto content in the SBOM in case the build was hermetic [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:180 ------------------------------ S [SKIPPED] [1.395 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-gomod" [It] check for source images if enabled in pipeline [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:214 Timeline >> Source build is enabled: false [SKIPPED] in [It] - /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:10:47.277 << Timeline [SKIPPED] Skipping source image check since it is not enabled in the pipeline In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:10:47.277 ------------------------------ • [34.529 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-pip" triggers a PipelineRun [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:89 Timeline >> Image repository for component component-prefetch-pip in namespace build-e2e-prefetch-pip do not have right state ('' != 'ready') yet but it has status { { } { } []}. Created component for scenario: prefetch-pip RUNNING SCENARIO: prefetch-pip PipelineRun has not been created yet for the component build-e2e-prefetch-pip/component-prefetch-pip << Timeline ------------------------------ • [380.183 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-generic" the PipelineRun should eventually finish [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:103 Timeline >> PipelineRun component-prefetch-generic-on-pull-request-c8z9n found for Component build-e2e-prefetch-generic/component-prefetch-generic PipelineRun component-prefetch-generic-on-pull-request-c8z9n reason: ResolvingTaskRef PipelineRun component-prefetch-generic-on-pull-request-c8z9n reason: Running PipelineRun component-prefetch-generic-on-pull-request-c8z9n reason: Running PipelineRun component-prefetch-generic-on-pull-request-c8z9n reason: Running PipelineRun component-prefetch-generic-on-pull-request-c8z9n reason: Running PipelineRun component-prefetch-generic-on-pull-request-c8z9n reason: Running PipelineRun component-prefetch-generic-on-pull-request-c8z9n reason: Running PipelineRun component-prefetch-generic-on-pull-request-c8z9n reason: Running PipelineRun component-prefetch-generic-on-pull-request-c8z9n reason: Running PipelineRun component-prefetch-generic-on-pull-request-c8z9n reason: Running PipelineRun component-prefetch-generic-on-pull-request-c8z9n reason: Running PipelineRun component-prefetch-generic-on-pull-request-c8z9n reason: Running PipelineRun component-prefetch-generic-on-pull-request-c8z9n reason: Running PipelineRun component-prefetch-generic-on-pull-request-c8z9n reason: Running PipelineRun component-prefetch-generic-on-pull-request-c8z9n reason: Running PipelineRun component-prefetch-generic-on-pull-request-c8z9n reason: Running PipelineRun component-prefetch-generic-on-pull-request-c8z9n reason: Running PipelineRun component-prefetch-generic-on-pull-request-c8z9n reason: Running PipelineRun component-prefetch-generic-on-pull-request-c8z9n reason: Running PipelineRun component-prefetch-generic-on-pull-request-c8z9n reason: Completed << Timeline ------------------------------ • [1.295 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-generic" should push Dockerfile to registry [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:123 ------------------------------ • [0.599 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-generic" should validate tekton taskrun test results [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:130 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-generic" [It] floating tags are created successfully [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:137 [SKIPPED] floating tag validation is not needed for: prefetch-generic In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:139 @ 08/17/26 10:11:40.194 ------------------------------ • [0.328 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-generic" image manifest mediaType is correct [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:153 ------------------------------ • [0.231 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-generic" should have Hermeto content in the SBOM in case the build was hermetic [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:180 ------------------------------ S [SKIPPED] [1.245 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-generic" [It] check for source images if enabled in pipeline [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:214 Timeline >> Source build is enabled: false [SKIPPED] in [It] - /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:11:40.755 << Timeline [SKIPPED] Skipping source image check since it is not enabled in the pipeline In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:11:40.755 ------------------------------ • [33.260 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-rpm" triggers a PipelineRun [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:89 Timeline >> Image repository for component component-prefetch-rpm in namespace build-e2e-prefetch-rpm do not have right state ('' != 'ready') yet but it has status { { } { } []}. Created component for scenario: prefetch-rpm RUNNING SCENARIO: prefetch-rpm PipelineRun has not been created yet for the component build-e2e-prefetch-rpm/component-prefetch-rpm << Timeline ------------------------------ • [260.187 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-npm" the PipelineRun should eventually finish [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:103 Timeline >> PipelineRun component-prefetch-npm-on-pull-request-8b42x found for Component build-e2e-prefetch-npm/component-prefetch-npm PipelineRun component-prefetch-npm-on-pull-request-8b42x reason: Running PipelineRun component-prefetch-npm-on-pull-request-8b42x reason: Running PipelineRun component-prefetch-npm-on-pull-request-8b42x reason: Running PipelineRun component-prefetch-npm-on-pull-request-8b42x reason: Running PipelineRun component-prefetch-npm-on-pull-request-8b42x reason: Running PipelineRun component-prefetch-npm-on-pull-request-8b42x reason: Running PipelineRun component-prefetch-npm-on-pull-request-8b42x reason: Running PipelineRun component-prefetch-npm-on-pull-request-8b42x reason: Running PipelineRun component-prefetch-npm-on-pull-request-8b42x reason: Running PipelineRun component-prefetch-npm-on-pull-request-8b42x reason: Running PipelineRun component-prefetch-npm-on-pull-request-8b42x reason: Running PipelineRun component-prefetch-npm-on-pull-request-8b42x reason: Running PipelineRun component-prefetch-npm-on-pull-request-8b42x reason: Running PipelineRun component-prefetch-npm-on-pull-request-8b42x reason: Completed << Timeline ------------------------------ • [1.358 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-npm" should push Dockerfile to registry [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:123 ------------------------------ • [0.439 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-npm" should validate tekton taskrun test results [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:130 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-npm" [It] floating tags are created successfully [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:137 [SKIPPED] floating tag validation is not needed for: prefetch-npm In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:139 @ 08/17/26 10:15:04.192 ------------------------------ • [0.274 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-npm" image manifest mediaType is correct [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:153 ------------------------------ • [0.292 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-npm" should have Hermeto content in the SBOM in case the build was hermetic [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:180 ------------------------------ S [SKIPPED] [2.103 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-npm" [It] check for source images if enabled in pipeline [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:214 Timeline >> Source build is enabled: false [SKIPPED] in [It] - /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:15:04.76 << Timeline [SKIPPED] Skipping source image check since it is not enabled in the pipeline In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:15:04.76 ------------------------------ • [33.489 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-yarn-classic" triggers a PipelineRun [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:89 Timeline >> Image repository for component component-prefetch-yarn-classic in namespace build-e2e-prefetch-yarn-classic do not have right state ('' != 'ready') yet but it has status { { } { } []}. Created component for scenario: prefetch-yarn-classic RUNNING SCENARIO: prefetch-yarn-classic PipelineRun has not been created yet for the component build-e2e-prefetch-yarn-classic/component-prefetch-yarn-classic << Timeline ------------------------------ • [240.184 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-rpm" the PipelineRun should eventually finish [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:103 Timeline >> PipelineRun component-prefetch-rpm-on-pull-request-mvr2h found for Component build-e2e-prefetch-rpm/component-prefetch-rpm PipelineRun component-prefetch-rpm-on-pull-request-mvr2h reason: Running PipelineRun component-prefetch-rpm-on-pull-request-mvr2h reason: Running PipelineRun component-prefetch-rpm-on-pull-request-mvr2h reason: Running PipelineRun component-prefetch-rpm-on-pull-request-mvr2h reason: Running PipelineRun component-prefetch-rpm-on-pull-request-mvr2h reason: Running PipelineRun component-prefetch-rpm-on-pull-request-mvr2h reason: Running PipelineRun component-prefetch-rpm-on-pull-request-mvr2h reason: Running PipelineRun component-prefetch-rpm-on-pull-request-mvr2h reason: Running PipelineRun component-prefetch-rpm-on-pull-request-mvr2h reason: Running PipelineRun component-prefetch-rpm-on-pull-request-mvr2h reason: Running PipelineRun component-prefetch-rpm-on-pull-request-mvr2h reason: Running PipelineRun component-prefetch-rpm-on-pull-request-mvr2h reason: Running PipelineRun component-prefetch-rpm-on-pull-request-mvr2h reason: Completed << Timeline ------------------------------ • [1.171 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-rpm" should push Dockerfile to registry [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:123 ------------------------------ • [0.811 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-rpm" should validate tekton taskrun test results [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:130 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-rpm" [It] floating tags are created successfully [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:137 [SKIPPED] floating tag validation is not needed for: prefetch-rpm In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:139 @ 08/17/26 10:16:17.429 ------------------------------ • [0.284 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-rpm" image manifest mediaType is correct [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:153 ------------------------------ • [0.224 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-rpm" should have Hermeto content in the SBOM in case the build was hermetic [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:180 ------------------------------ S [SKIPPED] [1.544 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-rpm" [It] check for source images if enabled in pipeline [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:214 Timeline >> Source build is enabled: false [SKIPPED] in [It] - /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:16:17.939 << Timeline [SKIPPED] Skipping source image check since it is not enabled in the pipeline In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:16:17.939 ------------------------------ • [320.171 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-pip" the PipelineRun should eventually finish [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:103 Timeline >> PipelineRun component-prefetch-pip-on-pull-request-gm49h found for Component build-e2e-prefetch-pip/component-prefetch-pip PipelineRun component-prefetch-pip-on-pull-request-gm49h reason: Running PipelineRun component-prefetch-pip-on-pull-request-gm49h reason: Running PipelineRun component-prefetch-pip-on-pull-request-gm49h reason: Running PipelineRun component-prefetch-pip-on-pull-request-gm49h reason: Running PipelineRun component-prefetch-pip-on-pull-request-gm49h reason: Running PipelineRun component-prefetch-pip-on-pull-request-gm49h reason: Running PipelineRun component-prefetch-pip-on-pull-request-gm49h reason: Running PipelineRun component-prefetch-pip-on-pull-request-gm49h reason: Running PipelineRun component-prefetch-pip-on-pull-request-gm49h reason: Running PipelineRun component-prefetch-pip-on-pull-request-gm49h reason: Running PipelineRun component-prefetch-pip-on-pull-request-gm49h reason: Running PipelineRun component-prefetch-pip-on-pull-request-gm49h reason: Running PipelineRun component-prefetch-pip-on-pull-request-gm49h reason: Running PipelineRun component-prefetch-pip-on-pull-request-gm49h reason: Running PipelineRun component-prefetch-pip-on-pull-request-gm49h reason: Running PipelineRun component-prefetch-pip-on-pull-request-gm49h reason: Running PipelineRun component-prefetch-pip-on-pull-request-gm49h reason: Completed << Timeline ------------------------------ • [1.230 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-pip" should push Dockerfile to registry [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:123 ------------------------------ • [0.526 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-pip" should validate tekton taskrun test results [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:130 ------------------------------ • [0.762 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-pip" floating tags are created successfully [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:137 ------------------------------ • [0.312 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-pip" image manifest mediaType is correct [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:153 ------------------------------ • [0.364 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-pip" should have Hermeto content in the SBOM in case the build was hermetic [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:180 ------------------------------ S [SKIPPED] [1.655 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-pip" [It] check for source images if enabled in pipeline [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:214 Timeline >> Source build is enabled: false [SKIPPED] in [It] - /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:16:46.572 << Timeline [SKIPPED] Skipping source image check since it is not enabled in the pipeline In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:16:46.572 ------------------------------ • [33.366 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-yarn-modern" triggers a PipelineRun [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:89 Timeline >> Image repository for component component-prefetch-yarn-modern in namespace build-e2e-prefetch-yarn-modern do not have right state ('' != 'ready') yet but it has status { { } { } []}. Created component for scenario: prefetch-yarn-modern RUNNING SCENARIO: prefetch-yarn-modern PipelineRun has not been created yet for the component build-e2e-prefetch-yarn-modern/component-prefetch-yarn-modern << Timeline ------------------------------ • [31.730 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-gitlab-basic-auth" triggers a PipelineRun [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:89 Timeline >> Image repository for component component-sample-gitlab-basic-auth in namespace build-e2e-sample-gitlab-basic-auth do not have right state ('' != 'ready') yet but it has status { { } { } []}. Created component for scenario: sample-gitlab-basic-auth RUNNING SCENARIO: sample-gitlab-basic-auth PipelineRun has not been created yet for the component build-e2e-sample-gitlab-basic-auth/component-sample-gitlab-basic-auth << Timeline ------------------------------ • [180.183 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-yarn-modern" the PipelineRun should eventually finish [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:103 Timeline >> PipelineRun component-prefetch-yarn-modern-on-pull-request-gdq66 found for Component build-e2e-prefetch-yarn-modern/component-prefetch-yarn-modern PipelineRun component-prefetch-yarn-modern-on-pull-request-gdq66 reason: ResolvingTaskRef PipelineRun component-prefetch-yarn-modern-on-pull-request-gdq66 reason: Running PipelineRun component-prefetch-yarn-modern-on-pull-request-gdq66 reason: Running PipelineRun component-prefetch-yarn-modern-on-pull-request-gdq66 reason: Running PipelineRun component-prefetch-yarn-modern-on-pull-request-gdq66 reason: Running PipelineRun component-prefetch-yarn-modern-on-pull-request-gdq66 reason: Running PipelineRun component-prefetch-yarn-modern-on-pull-request-gdq66 reason: Running PipelineRun component-prefetch-yarn-modern-on-pull-request-gdq66 reason: Running PipelineRun component-prefetch-yarn-modern-on-pull-request-gdq66 reason: Running PipelineRun component-prefetch-yarn-modern-on-pull-request-gdq66 reason: Completed << Timeline ------------------------------ • [1.154 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-yarn-modern" should push Dockerfile to registry [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:123 ------------------------------ • [0.603 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-yarn-modern" should validate tekton taskrun test results [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:130 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-yarn-modern" [It] floating tags are created successfully [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:137 [SKIPPED] floating tag validation is not needed for: prefetch-yarn-modern In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:139 @ 08/17/26 10:19:54.791 ------------------------------ • [0.276 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-yarn-modern" image manifest mediaType is correct [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:153 ------------------------------ • [0.193 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-yarn-modern" should have Hermeto content in the SBOM in case the build was hermetic [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:180 ------------------------------ S [SKIPPED] [1.754 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-yarn-modern" [It] check for source images if enabled in pipeline [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:214 Timeline >> Source build is enabled: false [SKIPPED] in [It] - /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:19:55.262 << Timeline [SKIPPED] Skipping source image check since it is not enabled in the pipeline In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:19:55.262 ------------------------------ • [31.722 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-docker" triggers a PipelineRun [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:89 Timeline >> Image repository for component component-sample-python-basic-docker in namespace build-e2e-sample-python-basic-docker do not have right state ('' != 'ready') yet but it has status { { } { } []}. Created component for scenario: sample-python-basic-docker RUNNING SCENARIO: sample-python-basic-docker PipelineRun has not been created yet for the component build-e2e-sample-python-basic-docker/component-sample-python-basic-docker << Timeline ------------------------------ • [300.118 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-gitlab-basic-auth" the PipelineRun should eventually finish [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:103 Timeline >> PipelineRun component-sample-gitlab-basic-auth-on-pull-request-4tnqh found for Component build-e2e-sample-gitlab-basic-auth/component-sample-gitlab-basic-auth PipelineRun component-sample-gitlab-basic-auth-on-pull-request-4tnqh reason: Running PipelineRun component-sample-gitlab-basic-auth-on-pull-request-4tnqh reason: Running PipelineRun component-sample-gitlab-basic-auth-on-pull-request-4tnqh reason: Running PipelineRun component-sample-gitlab-basic-auth-on-pull-request-4tnqh reason: Running PipelineRun component-sample-gitlab-basic-auth-on-pull-request-4tnqh reason: Running PipelineRun component-sample-gitlab-basic-auth-on-pull-request-4tnqh reason: Running PipelineRun component-sample-gitlab-basic-auth-on-pull-request-4tnqh reason: Running PipelineRun component-sample-gitlab-basic-auth-on-pull-request-4tnqh reason: Running PipelineRun component-sample-gitlab-basic-auth-on-pull-request-4tnqh reason: Running PipelineRun component-sample-gitlab-basic-auth-on-pull-request-4tnqh reason: Running PipelineRun component-sample-gitlab-basic-auth-on-pull-request-4tnqh reason: Running PipelineRun component-sample-gitlab-basic-auth-on-pull-request-4tnqh reason: Running PipelineRun component-sample-gitlab-basic-auth-on-pull-request-4tnqh reason: Running PipelineRun component-sample-gitlab-basic-auth-on-pull-request-4tnqh reason: Running PipelineRun component-sample-gitlab-basic-auth-on-pull-request-4tnqh reason: Running PipelineRun component-sample-gitlab-basic-auth-on-pull-request-4tnqh reason: Succeeded << Timeline ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-gitlab-basic-auth" [It] should push Dockerfile to registry [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:123 [SKIPPED] Skipping push Dockerfile to registry validation, it is not applicable here In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:125 @ 08/17/26 10:22:20.078 ------------------------------ • [0.118 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-gitlab-basic-auth" should validate tekton taskrun test results [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:130 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-gitlab-basic-auth" [It] floating tags are created successfully [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:137 [SKIPPED] floating tag validation is not needed for: sample-gitlab-basic-auth In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:139 @ 08/17/26 10:22:20.196 ------------------------------ • [0.309 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-gitlab-basic-auth" image manifest mediaType is correct [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:153 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-gitlab-basic-auth" [It] should have Hermeto content in the SBOM in case the build was hermetic [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:180 [SKIPPED] Hermetic build is not enabled, skipping the test In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:182 @ 08/17/26 10:22:20.507 ------------------------------ S [SKIPPED] [3.329 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-gitlab-basic-auth" [It] check for source images if enabled in pipeline [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:214 [SKIPPED] Not applicable, skiping source image validation for the scenario sample-gitlab-basic-auth In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:216 @ 08/17/26 10:22:20.507 ------------------------------ • [420.187 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-yarn-classic" the PipelineRun should eventually finish [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:103 Timeline >> PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c found for Component build-e2e-prefetch-yarn-classic/component-prefetch-yarn-classic PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Running PipelineRun component-prefetch-yarn-classic-on-pull-request-g769c reason: Completed << Timeline ------------------------------ • [1.092 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-yarn-classic" should push Dockerfile to registry [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:123 ------------------------------ • [0.589 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-yarn-classic" should validate tekton taskrun test results [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:130 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-yarn-classic" [It] floating tags are created successfully [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:137 [SKIPPED] floating tag validation is not needed for: prefetch-yarn-classic In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:139 @ 08/17/26 10:22:42.223 ------------------------------ • [0.318 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-yarn-classic" image manifest mediaType is correct [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:153 ------------------------------ • [0.289 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-yarn-classic" should have Hermeto content in the SBOM in case the build was hermetic [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:180 ------------------------------ S [SKIPPED] [2.524 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "prefetch-yarn-classic" [It] check for source images if enabled in pipeline [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:214 Timeline >> Source build is enabled: false [SKIPPED] in [It] - /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:22:42.832 << Timeline [SKIPPED] Skipping source image check since it is not enabled in the pipeline In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:22:42.832 ------------------------------ • [33.025 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-oci-docker-build" triggers a PipelineRun [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:89 Timeline >> Created component for scenario: sample-python-basic-oci-docker-build RUNNING SCENARIO: sample-python-basic-oci-docker-build PipelineRun has not been created yet for the component build-e2e-sample-python-basic-oci-docker-build/component-sample-python-basic-oci-docker-build << Timeline ------------------------------ • [160.193 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-docker" the PipelineRun should eventually finish [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:103 Timeline >> PipelineRun component-sample-python-basic-docker-on-pull-request-zf6z5 found for Component build-e2e-sample-python-basic-docker/component-sample-python-basic-docker PipelineRun component-sample-python-basic-docker-on-pull-request-zf6z5 reason: Running PipelineRun component-sample-python-basic-docker-on-pull-request-zf6z5 reason: Running PipelineRun component-sample-python-basic-docker-on-pull-request-zf6z5 reason: Running PipelineRun component-sample-python-basic-docker-on-pull-request-zf6z5 reason: Running PipelineRun component-sample-python-basic-docker-on-pull-request-zf6z5 reason: Running PipelineRun component-sample-python-basic-docker-on-pull-request-zf6z5 reason: Running PipelineRun component-sample-python-basic-docker-on-pull-request-zf6z5 reason: Running PipelineRun component-sample-python-basic-docker-on-pull-request-zf6z5 reason: Running PipelineRun component-sample-python-basic-docker-on-pull-request-zf6z5 reason: Completed << Timeline ------------------------------ • [1.570 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-docker" should push Dockerfile to registry [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:123 ------------------------------ • [0.412 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-docker" should validate tekton taskrun test results [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:130 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-docker" [It] floating tags are created successfully [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:137 [SKIPPED] floating tag validation is not needed for: sample-python-basic-docker In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:139 @ 08/17/26 10:23:10.916 ------------------------------ • [0.279 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-docker" image manifest mediaType is correct [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:153 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-docker" [It] should have Hermeto content in the SBOM in case the build was hermetic [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:180 [SKIPPED] Hermetic build is not enabled, skipping the test In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:182 @ 08/17/26 10:23:11.196 ------------------------------ S [SKIPPED] [2.153 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-docker" [It] check for source images if enabled in pipeline [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:214 Timeline >> Source build is enabled: false [SKIPPED] in [It] - /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:23:11.197 << Timeline [SKIPPED] Skipping source image check since it is not enabled in the pipeline In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:23:11.197 ------------------------------ • [33.248 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-oci-docker-build-oci-ta" triggers a PipelineRun [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:89 Timeline >> Image repository for component component-sample-python-basic-oci-docker-build-oci-ta in namespace build-e2e-sample-python-basic-oci-docker-build-oci-ta do not have right state ('' != 'ready') yet but it has status { { } { } []}. Created component for scenario: sample-python-basic-oci-docker-build-oci-ta RUNNING SCENARIO: sample-python-basic-oci-docker-build-oci-ta PipelineRun has not been created yet for the component build-e2e-sample-python-basic-oci-docker-build-oci-ta/component-sample-python-basic-oci-docker-build-oci-ta << Timeline ------------------------------ • [31.710 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-symlink" triggers a PipelineRun [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:89 Timeline >> Image repository for component component-sample-python-basic-symlink in namespace build-e2e-sample-python-basic-symlink do not have right state ('' != 'ready') yet but it has status { { } { } []}. Created component for scenario: sample-python-basic-symlink RUNNING SCENARIO: sample-python-basic-symlink PipelineRun has not been created yet for the component build-e2e-sample-python-basic-symlink/component-sample-python-basic-symlink << Timeline ------------------------------ • [20.246 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-symlink" the PipelineRun should eventually finish [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:103 Timeline >> current pipelinerun reason: Running << Timeline ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-symlink" [It] should push Dockerfile to registry [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:123 [SKIPPED] Skipping push Dockerfile to registry validation, it is not applicable here In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:125 @ 08/17/26 10:24:05.309 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-symlink" [It] should validate tekton taskrun test results [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:130 [SKIPPED] Skipping tekton task results validation, not applicable In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:132 @ 08/17/26 10:24:05.31 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-symlink" [It] floating tags are created successfully [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:137 [SKIPPED] floating tag validation is not needed for: sample-python-basic-symlink In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:139 @ 08/17/26 10:24:05.31 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-symlink" [It] image manifest mediaType is correct [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:153 [SKIPPED] mediaType validation is not required for scenario: sample-python-basic-symlink In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:155 @ 08/17/26 10:24:05.311 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-symlink" [It] should have Hermeto content in the SBOM in case the build was hermetic [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:180 [SKIPPED] Hermetic build is not enabled, skipping the test In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:182 @ 08/17/26 10:24:05.311 ------------------------------ S [SKIPPED] [2.218 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-symlink" [It] check for source images if enabled in pipeline [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:214 Timeline >> Source build is enabled: false [SKIPPED] in [It] - /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:24:05.312 << Timeline [SKIPPED] Skipping source image check since it is not enabled in the pipeline In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:24:05.312 ------------------------------ • [160.174 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-oci-docker-build" the PipelineRun should eventually finish [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:103 Timeline >> PipelineRun component-sample-python-basic-oci-docker-build-on-pull-reqc7rz6 found for Component build-e2e-sample-python-basic-oci-docker-build/component-sample-python-basic-oci-docker-build PipelineRun component-sample-python-basic-oci-docker-build-on-pull-reqc7rz6 reason: Running PipelineRun component-sample-python-basic-oci-docker-build-on-pull-reqc7rz6 reason: Running PipelineRun component-sample-python-basic-oci-docker-build-on-pull-reqc7rz6 reason: Running PipelineRun component-sample-python-basic-oci-docker-build-on-pull-reqc7rz6 reason: Running PipelineRun component-sample-python-basic-oci-docker-build-on-pull-reqc7rz6 reason: Running PipelineRun component-sample-python-basic-oci-docker-build-on-pull-reqc7rz6 reason: Running PipelineRun component-sample-python-basic-oci-docker-build-on-pull-reqc7rz6 reason: Running PipelineRun component-sample-python-basic-oci-docker-build-on-pull-reqc7rz6 reason: Running PipelineRun component-sample-python-basic-oci-docker-build-on-pull-reqc7rz6 reason: Completed << Timeline ------------------------------ • [4.352 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-oci-docker-build" should push Dockerfile to registry [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:123 ------------------------------ • [0.520 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-oci-docker-build" should validate tekton taskrun test results [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:130 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-oci-docker-build" [It] floating tags are created successfully [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:137 [SKIPPED] floating tag validation is not needed for: sample-python-basic-oci-docker-build In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:139 @ 08/17/26 10:25:41.91 ------------------------------ • [0.263 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-oci-docker-build" image manifest mediaType is correct [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:153 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-oci-docker-build" [It] should have Hermeto content in the SBOM in case the build was hermetic [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:180 [SKIPPED] Hermetic build is not enabled, skipping the test In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:182 @ 08/17/26 10:25:42.174 ------------------------------ S [SKIPPED] [2.681 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-oci-docker-build" [It] check for source images if enabled in pipeline [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:214 Timeline >> Source build is enabled: false [SKIPPED] in [It] - /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:25:42.175 << Timeline [SKIPPED] Skipping source image check since it is not enabled in the pipeline In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:25:42.175 ------------------------------ • [180.187 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-oci-docker-build-oci-ta" the PipelineRun should eventually finish [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:103 Timeline >> PipelineRun component-sample-python-basic-oci-docker-build-oci-ta-on-pnjvkb found for Component build-e2e-sample-python-basic-oci-docker-build-oci-ta/component-sample-python-basic-oci-docker-build-oci-ta PipelineRun component-sample-python-basic-oci-docker-build-oci-ta-on-pnjvkb reason: ResolvingTaskRef PipelineRun component-sample-python-basic-oci-docker-build-oci-ta-on-pnjvkb reason: Running PipelineRun component-sample-python-basic-oci-docker-build-oci-ta-on-pnjvkb reason: Running PipelineRun component-sample-python-basic-oci-docker-build-oci-ta-on-pnjvkb reason: Running PipelineRun component-sample-python-basic-oci-docker-build-oci-ta-on-pnjvkb reason: Running PipelineRun component-sample-python-basic-oci-docker-build-oci-ta-on-pnjvkb reason: Running PipelineRun component-sample-python-basic-oci-docker-build-oci-ta-on-pnjvkb reason: Running PipelineRun component-sample-python-basic-oci-docker-build-oci-ta-on-pnjvkb reason: Running PipelineRun component-sample-python-basic-oci-docker-build-oci-ta-on-pnjvkb reason: Running PipelineRun component-sample-python-basic-oci-docker-build-oci-ta-on-pnjvkb reason: Completed << Timeline ------------------------------ • [1.186 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-oci-docker-build-oci-ta" should push Dockerfile to registry [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:123 ------------------------------ • [0.546 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-oci-docker-build-oci-ta" should validate tekton taskrun test results [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:130 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-oci-docker-build-oci-ta" [It] floating tags are created successfully [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:137 [SKIPPED] floating tag validation is not needed for: sample-python-basic-oci-docker-build-oci-ta In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:139 @ 08/17/26 10:26:20.527 ------------------------------ • [0.317 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-oci-docker-build-oci-ta" image manifest mediaType is correct [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:153 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-oci-docker-build-oci-ta" [It] should have Hermeto content in the SBOM in case the build was hermetic [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:180 [SKIPPED] Hermetic build is not enabled, skipping the test In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:182 @ 08/17/26 10:26:20.845 ------------------------------ S [SKIPPED] [1.850 seconds] [build-service-suite Build pipeline E2E test] Build pipeline scenario "sample-python-basic-oci-docker-build-oci-ta" [It] check for source images if enabled in pipeline [build-pipeline-e2e] /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:214 Timeline >> Source build is enabled: false [SKIPPED] in [It] - /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:26:20.846 << Timeline [SKIPPED] Skipping source image check since it is not enabled in the pipeline In [It] at: /workspace/source/e2e-tests/tests/build/build_pipeline_tests.go:223 @ 08/17/26 10:26:20.846 ------------------------------ [ReportAfterSuite] PASSED [37.873 seconds] [ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report autogenerated by Ginkgo ------------------------------ Ran 86 of 128 Specs in 1748.505 seconds SUCCESS! -- 86 Passed | 0 Failed | 0 Pending | 42 Skipped Ginkgo ran 1 suite in 31m39.026025984s Test Suite Passed