go: downloading github.com/konflux-ci/build-service v0.0.0-20240611083846-2dee6cfe6fe4 go: downloading github.com/konflux-ci/application-api v0.0.0-20260312190025-5154ad273e17 go: downloading k8s.io/apimachinery v0.34.2 go: downloading github.com/devfile/library/v2 v2.2.1-0.20230418160146-e75481b7eebd go: downloading github.com/google/go-github/v66 v66.0.0 go: downloading github.com/konflux-ci/e2e-tests v0.0.0-20260428105747-f0b222ad8cb6 go: downloading github.com/openshift/oc v0.0.0-alpha.0.0.20220614012638-35c7eeb5274e go: downloading github.com/onsi/gomega v1.39.1 go: downloading github.com/tektoncd/pipeline v1.7.0 go: downloading k8s.io/api v0.34.2 go: downloading github.com/konflux-ci/release-service v0.0.0-20260127184035-c36c56a3c440 go: downloading github.com/go-logr/logr v1.4.3 go: downloading golang.org/x/sys v0.42.0 go: downloading golang.org/x/exp v0.0.0-20260312153236-7ab1446f8b90 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/openshift/api v0.0.0-20260320151444-324a1bcb9f55 go: downloading github.com/google/go-containerregistry v0.20.7 go: downloading k8s.io/client-go v0.34.2 go: downloading k8s.io/utils v0.0.0-20251002143259-bc988d571ff4 go: downloading knative.dev/pkg v0.0.0-20250424013628-d5e74d29daa3 go: downloading sigs.k8s.io/controller-runtime v0.20.2 go: downloading github.com/bradleyfalzon/ghinstallation/v2 v2.17.0 go: downloading sigs.k8s.io/yaml v1.6.0 go: downloading github.com/google/go-github/v45 v45.2.0 go: downloading github.com/prometheus/client_golang v1.23.2 go: downloading golang.org/x/oauth2 v0.34.0 go: downloading k8s.io/apiextensions-apiserver v0.34.2 go: downloading github.com/google/go-cmp v0.7.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/gregjones/httpcache v0.0.0-20190611155906-901d90724c79 go: downloading github.com/gobwas/glob v0.2.3 go: downloading github.com/pkg/errors v0.9.1 go: downloading k8s.io/klog v1.0.0 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/konflux-ci/operator-toolkit v0.0.0-20260312101100-d4e398191a68 go: downloading github.com/google/go-querystring v1.2.0 go: downloading github.com/docker/cli v29.0.3+incompatible go: downloading github.com/magefile/mage v1.14.0 go: downloading github.com/mitchellh/go-homedir v1.1.0 go: downloading k8s.io/klog/v2 v2.130.1 go: downloading github.com/avast/retry-go/v4 v4.3.3 go: downloading github.com/konflux-ci/image-controller v0.0.0-20240530145826-3296e4996f6f go: downloading github.com/xanzy/go-gitlab v0.114.0 go: downloading github.com/moby/buildkit v0.12.5 go: downloading github.com/openshift/library-go v0.0.0-20220525173854-9b950a41acdc go: downloading k8s.io/cli-runtime v0.34.2 go: downloading github.com/golang-jwt/jwt/v4 v4.5.2 go: downloading github.com/google/go-github/v75 v75.0.0 go: downloading go.yaml.in/yaml/v2 v2.4.4 go: downloading go.yaml.in/yaml/v3 v3.0.4 go: downloading golang.org/x/net v0.52.0 go: downloading github.com/fsnotify/fsnotify v1.9.0 go: downloading github.com/spf13/afero v1.15.0 go: downloading github.com/evanphx/json-patch/v5 v5.9.11 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 google.golang.org/protobuf v1.36.11 go: downloading github.com/mattn/go-colorable v0.1.14 go: downloading github.com/mattn/go-isatty v0.0.20 go: downloading github.com/peterbourgon/diskv v2.0.1+incompatible go: downloading github.com/hashicorp/errwrap v1.1.0 go: downloading github.com/opencontainers/go-digest v1.0.0 go: downloading github.com/bmatcuk/doublestar/v4 v4.7.1 go: downloading github.com/gogo/protobuf v1.3.2 go: downloading sigs.k8s.io/structured-merge-diff/v6 v6.3.2 go: downloading gopkg.in/inf.v0 v0.9.1 go: downloading sigs.k8s.io/randfill v1.0.0 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/codeready-toolchain/api v0.0.0-20231217224957-34f7cb3fcbf7 go: downloading github.com/conforma/crds/api v0.1.7 go: downloading github.com/konflux-ci/integration-service v0.0.0-20260330012634-6190adb9bbce 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/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/opencontainers/image-spec v1.1.1 go: downloading oras.land/oras-go/v2 v2.5.0 go: downloading github.com/tektoncd/cli v0.43.0 go: downloading golang.org/x/crypto v0.49.0 go: downloading github.com/docker/distribution v2.8.2+incompatible go: downloading github.com/docker/go-units v0.5.0 go: downloading github.com/spf13/cobra v1.10.2 go: downloading k8s.io/kubectl v0.34.2 go: downloading github.com/docker/docker v23.0.7+incompatible go: downloading github.com/aws/aws-sdk-go v1.55.8 go: downloading github.com/containers/image/v5 v5.29.3 go: downloading gomodules.xyz/jsonpatch/v2 v2.5.0 go: downloading sigs.k8s.io/json v0.0.0-20250730193827-2d320260d730 go: downloading k8s.io/kube-openapi v0.0.0-20260330154417-16be699c7b31 go: downloading github.com/google/uuid v1.6.0 go: downloading github.com/spf13/pflag v1.0.10 go: downloading gopkg.in/evanphx/json-patch.v4 v4.13.0 go: downloading golang.org/x/text v0.35.0 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/hashicorp/go-cleanhttp v0.5.2 go: downloading github.com/hashicorp/go-retryablehttp v0.7.8 go: downloading golang.org/x/time v0.15.0 go: downloading github.com/google/btree v1.1.3 go: downloading github.com/munnerz/goautoneg v0.0.0-20191010083416-a7dc8b61c822 go: downloading github.com/json-iterator/go v1.1.12 go: downloading github.com/go-fed/httpsig v1.1.1-0.20201223112313-55836744818e go: downloading github.com/42wim/httpsig v1.2.3 go: downloading github.com/hashicorp/go-version v1.7.0 go: downloading github.com/google/cel-go v0.26.1 go: downloading github.com/santhosh-tekuri/jsonschema/v5 v5.3.1 go: downloading github.com/sirupsen/logrus v1.9.3 go: downloading github.com/docker/libtrust v0.0.0-20160708172513-aabc10ec26b7 go: downloading golang.org/x/term v0.41.0 go: downloading github.com/google/gnostic-models v0.7.1 go: downloading sigs.k8s.io/kustomize/api v0.20.1 go: downloading sigs.k8s.io/kustomize/kyaml v0.20.1 go: downloading github.com/liggitt/tabwriter v0.0.0-20181228230101-89fcab3d43de go: downloading github.com/moby/term v0.5.2 go: downloading github.com/pjbgf/sha1cd v0.5.0 go: downloading github.com/go-git/gcfg v1.5.1-0.20230307220236-3a3c6141e376 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/cyphar/filepath-securejoin v0.3.6 go: downloading github.com/fxamacker/cbor/v2 v2.9.0 go: downloading github.com/containerd/typeurl/v2 v2.2.2 go: downloading github.com/klauspost/compress v1.18.2 go: downloading github.com/containerd/stargz-snapshotter/estargz v0.18.1 go: downloading github.com/docker/docker-credential-helpers v0.9.3 go: downloading github.com/gorilla/mux v1.8.0 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/davecgh/go-spew v1.1.2-0.20180830191138-d8f796af33cc go: downloading gopkg.in/warnings.v0 v0.1.2 go: downloading cel.dev/expr v0.25.1 go: downloading google.golang.org/genproto/googleapis/api v0.0.0-20260406210006-6f92a3bedf2d 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 k8s.io/component-base v0.34.2 go: downloading github.com/MakeNowJust/heredoc v1.0.0 go: downloading github.com/mitchellh/go-wordwrap v1.0.1 go: downloading github.com/russross/blackfriday/v2 v2.1.0 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/containers/libtrust v0.0.0-20230121012942-c1716e8a8d01 go: downloading github.com/containers/ocicrypt v1.1.10 go: downloading github.com/containers/storage v1.51.0 go: downloading github.com/x448/float16 v0.8.4 go: downloading github.com/vbatts/tar-split v0.12.2 go: downloading github.com/pmezard/go-difflib v1.0.1-0.20181226105442-5d4384ee4fb2 go: downloading github.com/docker/go-metrics v0.0.1 go: downloading github.com/go-openapi/jsonreference v0.21.5 go: downloading github.com/go-openapi/swag v0.25.5 go: downloading github.com/emicklei/go-restful/v3 v3.13.0 go: downloading github.com/cloudflare/circl v1.6.3 go: downloading github.com/stoewer/go-strcase v1.3.1 go: downloading github.com/antlr4-go/antlr/v4 v4.13.1 go: downloading github.com/exponent-io/jsonpath v0.0.0-20210407135951-1de76d718b3f go: downloading google.golang.org/genproto/googleapis/rpc v0.0.0-20260401024825-9d38bb4040a9 go: downloading github.com/prometheus/statsd_exporter v0.28.0 go: downloading github.com/chai2010/gettext-go v1.0.3 go: downloading github.com/klauspost/cpuid/v2 v2.3.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/blendle/zapdriver v1.3.1 go: downloading github.com/blang/semver/v4 v4.0.0 go: downloading github.com/go-errors/errors v1.5.1 go: downloading github.com/BurntSushi/toml v1.4.0 go: downloading go.uber.org/multierr v1.11.0 go: downloading github.com/blang/semver v3.5.1+incompatible 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/gorilla/websocket v1.5.4-0.20250319132907-e064f32e3674 go: downloading github.com/grpc-ecosystem/grpc-gateway/v2 v2.27.6 go: downloading github.com/monochromegane/go-gitignore v0.0.0-20200626010858-205db1a8cc00 go: downloading github.com/xlab/treeprint v1.2.0 go: downloading github.com/opencontainers/runtime-spec v1.2.0 go: downloading github.com/syndtr/gocapability v0.0.0-20200815063812-42c35b437635 go: downloading github.com/moby/spdystream v0.5.0 go: downloading github.com/opencontainers/runc v1.1.14 go: downloading github.com/moby/sys/mountinfo v0.7.2 go: downloading github.com/mxk/go-flowrate v0.0.0-20140419014527-cca7078d478f go: downloading github.com/moby/sys/sequential v0.5.0 go: downloading github.com/docker/go-connections v0.5.0 go: downloading github.com/moby/patternmatcher v0.5.0 go: downloading github.com/containerd/containerd v1.7.25 go: downloading github.com/morikuni/aec v1.0.0 go: downloading github.com/moby/sys/userns v0.1.0 go: downloading github.com/jmespath/go-jmespath v0.4.1-0.20220621161143-b0104c826a24 Running Suite: Build Service E2E - /workspace/source/test/e2e ============================================================= Random Seed: 1777527608 Will run 147 of 154 specs Running in parallel across 10 processes ------------------------------ • [14.885 seconds] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace creates component with context directory go-component [build-service, github, pac-build, multi-component] /workspace/source/test/e2e/multi_component.go:106 Timeline >> Image repository for component go-component-rnhknv in namespace build-e2e-semp do not have right state ('' != 'ready') yet but it has status { { } { } []}. << Timeline ------------------------------ • [15.631 seconds] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created creates first component [build-service, github, pac-build, secret-lookup] /workspace/source/test/e2e/secret_lookup.go:123 Timeline >> Image repository for component component-one-tebz in namespace build-e2e-xrsj do not have right state ('' != 'ready') yet but it has status { { } { } []}. << Timeline ------------------------------ • [30.341 seconds] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created creates second component [build-service, github, pac-build, secret-lookup] /workspace/source/test/e2e/secret_lookup.go:140 Timeline >> Image repository for component component-two-svrv in namespace build-e2e-xrsj do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component component-two-svrv in namespace build-e2e-xrsj do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component component-two-svrv in namespace build-e2e-xrsj do not have right state ('' != 'ready') yet but it has status { { } { } []}. << Timeline ------------------------------ • [40.325 seconds] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace triggers a PipelineRun for component go-component-rnhknv [build-service, github, pac-build, multi-component] /workspace/source/test/e2e/multi_component.go:125 Timeline >> PipelineRun has not been created yet for the component build-e2e-semp/go-component-rnhknv PipelineRun has not been created yet for the component build-e2e-semp/go-component-rnhknv << Timeline ------------------------------ • [0.526 seconds] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace should lead to a PaC PR creation for component go-component-rnhknv [build-service, github, pac-build, multi-component] /workspace/source/test/e2e/multi_component.go:140 ------------------------------ • [57.616 seconds] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace creates component with nudges [build-service, renovate, multi-component, github] /workspace/source/test/e2e/renovate.go:235 Timeline >> ReleaseAdmissionPlan data: {"Mapping":{"Components":[{"Name":"gh-multi-component-parent-cgit","Repository":"quay.io/redhat-appstudio-qe/release-repository"}]}}Image repository for component gh-multi-component-child-cgit in namespace build-e2e-aupf do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component gh-multi-component-child-cgit in namespace build-e2e-aupf do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component gh-multi-component-parent-cgit in namespace build-e2e-aupf do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component gh-multi-component-parent-cgit in namespace build-e2e-aupf do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component gh-multi-component-parent-cgit in namespace build-e2e-aupf do not have right state ('' != 'ready') yet but it has status { { } { } []}. << Timeline ------------------------------ • [58.351 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private 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] /workspace/source/test/e2e/pac_build.go:137 Timeline >> Image repository for component gh-test-custom-default-fwxhuw in namespace build-e2e-oakw do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component gh-test-custom-default-fwxhuw in namespace build-e2e-oakw do not have right state ('' != 'ready') yet but it has status { { } { } []}. << Timeline ------------------------------ • [0.128 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private workspace parameter is set correctly in PaC repository CR [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:154 ------------------------------ • [72.359 seconds] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace creates component with nudges [build-service, renovate, multi-component, forgejo] /workspace/source/test/e2e/renovate.go:235 Timeline >> ReleaseAdmissionPlan data: {"Mapping":{"Components":[{"Name":"fj-multi-component-parent-agzw","Repository":"quay.io/redhat-appstudio-qe/release-repository"}]}}Image repository for component fj-multi-component-child-agzw in namespace build-e2e-oovz do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component fj-multi-component-child-agzw in namespace build-e2e-oovz do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component fj-multi-component-child-agzw in namespace build-e2e-oovz do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component fj-multi-component-parent-agzw in namespace build-e2e-oovz do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component fj-multi-component-parent-agzw in namespace build-e2e-oovz do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component fj-multi-component-parent-agzw in namespace build-e2e-oovz do not have right state ('' != 'ready') yet but it has status { { } { } []}. << Timeline ------------------------------ • [74.150 seconds] [build-service-suite Build service E2E tests] test build annotations when component is created with invalid build request annotations handles invalid request annotation [build-service, github, annotations] /workspace/source/test/e2e/annotations.go:89 Timeline >> Image repository for component test-annotations-lzqfyn in namespace build-e2e-ldxh do not have right state ('' != 'ready') yet but it has status { { } { } []}. build status annotation value: {"message":"unexpected build request: foo"} << Timeline ------------------------------ • [78.413 seconds] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace creates component with nudges [build-service, renovate, multi-component, gitlab] /workspace/source/test/e2e/renovate.go:235 Timeline >> ReleaseAdmissionPlan data: {"Mapping":{"Components":[{"Name":"gl-multi-component-parent-hspp","Repository":"quay.io/redhat-appstudio-qe/release-repository"}]}}Image repository for component gl-multi-component-child-hspp in namespace build-e2e-edkp do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component gl-multi-component-child-hspp in namespace build-e2e-edkp do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component gl-multi-component-child-hspp in namespace build-e2e-edkp do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component gl-multi-component-child-hspp in namespace build-e2e-edkp do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component gl-multi-component-parent-hspp in namespace build-e2e-edkp do not have right state ('' != 'ready') yet but it has status { { } { } []}. << Timeline ------------------------------ • [20.239 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:176 Timeline >> PipelineRun has not been created yet for the component build-e2e-oakw/gh-test-custom-branch-xkxfnj << Timeline ------------------------------ • [0.000 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private build pipeline uses the correct serviceAccount [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:191 ------------------------------ • [0.064 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private component build status is set correctly [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:195 Timeline >> build status annotation value: {"pac":{"state":"enabled","merge-url":"https://github.com/redhat-appstudio-qe/devfile-sample-hello-world-mlqbkr/pull/1","configuration-time":"Thu, 30 Apr 2026 05:45:46 UTC"},"message":"done"} state: enabled mergeUrl: https://github.com/redhat-appstudio-qe/devfile-sample-hello-world-mlqbkr/pull/1 errId: 0 errMessage: configurationTime: Thu, 30 Apr 2026 05:45:46 UTC << Timeline ------------------------------ • [1.017 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:225 ------------------------------ • [0.286 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private created image repo is private [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:243 ------------------------------ • [95.324 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 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] /workspace/source/test/e2e/pac_build.go:137 Timeline >> Image repository for component fj-test-custom-default-hyxmjm in namespace build-e2e-yaqs do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component fj-test-custom-default-hyxmjm in namespace build-e2e-yaqs do not have right state ('' != 'ready') yet but it has status { { } { } []}. << Timeline ------------------------------ • [0.132 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 workspace parameter is set correctly in PaC repository CR [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:154 ------------------------------ • [20.332 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private a related PipelineRun should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:249 ------------------------------ • [0.160 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private PR branch should not exist in the repo [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:264 ------------------------------ • [0.889 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private related image repo and the robot account should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:277 ------------------------------ • [58.568 seconds] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created check first component annotation has errors [build-service, github, pac-build, secret-lookup] /workspace/source/test/e2e/secret_lookup.go:158 Timeline >> build status annotation value: {"message":"waiting for spec.containerImage to be set by ImageRepository with annotation image-controller.appstudio.redhat.com/update-component-image"} build status annotation value: {"message":"waiting for spec.containerImage to be set by ImageRepository with annotation image-controller.appstudio.redhat.com/update-component-image"} build status annotation value: {"message":"waiting for spec.containerImage to be set by ImageRepository with annotation image-controller.appstudio.redhat.com/update-component-image"} build status annotation value: {"message":"waiting for spec.containerImage to be set by ImageRepository with annotation image-controller.appstudio.redhat.com/update-component-image"} build status annotation value: {"message":"waiting for spec.containerImage to be set by ImageRepository with annotation image-controller.appstudio.redhat.com/update-component-image"} build status annotation value: {"message":"waiting for spec.containerImage to be set by ImageRepository with annotation image-controller.appstudio.redhat.com/update-component-image"} build status annotation value: {"message":"waiting for spec.containerImage to be set by ImageRepository with annotation image-controller.appstudio.redhat.com/update-component-image"} build status annotation value: {"message":"waiting for spec.containerImage to be set by ImageRepository with annotation image-controller.appstudio.redhat.com/update-component-image"} build status annotation value: {"message":"waiting for spec.containerImage to be set by ImageRepository with annotation image-controller.appstudio.redhat.com/update-component-image"} build status annotation value: {"message":"waiting for spec.containerImage to be set by ImageRepository with annotation image-controller.appstudio.redhat.com/update-component-image"} build status annotation value: {"message":"waiting for spec.containerImage to be set by ImageRepository with annotation image-controller.appstudio.redhat.com/update-component-image"} build status annotation value: {"pac":{"state":"error","error-id":74,"error-message":"74: Access token is unrecognizable by GitHub"},"message":"done"} << Timeline ------------------------------ • [114.984 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 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] /workspace/source/test/e2e/pac_build.go:137 Timeline >> Image repository for component gl-test-custom-default-wpfkqi in namespace build-e2e-moue do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component gl-test-custom-default-wpfkqi in namespace build-e2e-moue do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component gl-test-custom-default-wpfkqi in namespace build-e2e-moue do not have right state ('' != 'ready') yet but it has status { { } { } []}. << Timeline ------------------------------ • [0.129 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 workspace parameter is set correctly in PaC repository CR [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:154 ------------------------------ • [20.240 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 triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:176 Timeline >> PipelineRun has not been created yet for the component build-e2e-yaqs/fj-test-custom-branch-ildcfr << Timeline ------------------------------ • [0.000 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 build pipeline uses the correct serviceAccount [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:191 ------------------------------ • [0.066 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 component build status is set correctly [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:195 Timeline >> build status annotation value: {"pac":{"state":"enabled","merge-url":"https://codeberg.org/konflux-qe/devfile-sample-hello-world-zunait/pulls/1","configuration-time":"Thu, 30 Apr 2026 05:46:22 UTC"},"message":"done"} state: enabled mergeUrl: https://codeberg.org/konflux-qe/devfile-sample-hello-world-zunait/pulls/1 errId: 0 errMessage: configurationTime: Thu, 30 Apr 2026 05:46:22 UTC << Timeline ------------------------------ • [1.322 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 image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:225 ------------------------------ • [0.287 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 created image repo is private [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:243 ------------------------------ • [20.669 seconds] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created triggered PipelineRun is for component [build-service, github, pac-build, secret-lookup] /workspace/source/test/e2e/secret_lookup.go:178 Timeline >> PipelineRun has not been created yet for the component build-e2e-xrsj/component-two-svrv << Timeline ------------------------------ • [62.348 seconds] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace triggers a PipelineRun for parent component [build-service, renovate, multi-component, forgejo] /workspace/source/test/e2e/renovate.go:259 Timeline >> PipelineRun has not been created yet for the component build-e2e-oovz/fj-multi-component-parent-agzw PipelineRun has not been created yet for the component build-e2e-oovz/fj-multi-component-parent-agzw PipelineRun has not been created yet for the component build-e2e-oovz/fj-multi-component-parent-agzw << Timeline ------------------------------ • [20.196 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 triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:176 Timeline >> PipelineRun has not been created yet for the component build-e2e-moue/gl-test-custom-branch-ervavi << Timeline ------------------------------ • [0.000 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 build pipeline uses the correct serviceAccount [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:191 ------------------------------ • [0.064 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 component build status is set correctly [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:195 Timeline >> build status annotation value: {"pac":{"state":"enabled","merge-url":"https://gitlab.com/konflux-qe/devfile-sample-hello-world-cydtia/-/merge_requests/1","configuration-time":"Thu, 30 Apr 2026 05:46:44 UTC"},"message":"done"} state: enabled mergeUrl: https://gitlab.com/konflux-qe/devfile-sample-hello-world-cydtia/-/merge_requests/1 errId: 0 errMessage: configurationTime: Thu, 30 Apr 2026 05:46:44 UTC << Timeline ------------------------------ • [1.106 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 image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:225 ------------------------------ • [0.293 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 created image repo is private [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:243 ------------------------------ • [81.079 seconds] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace triggers a PipelineRun for parent component [build-service, renovate, multi-component, github] /workspace/source/test/e2e/renovate.go:259 Timeline >> PipelineRun has not been created yet for the component build-e2e-aupf/gh-multi-component-parent-cgit PipelineRun has not been created yet for the component build-e2e-aupf/gh-multi-component-parent-cgit PipelineRun has not been created yet for the component build-e2e-aupf/gh-multi-component-parent-cgit PipelineRun has not been created yet for the component build-e2e-aupf/gh-multi-component-parent-cgit << Timeline ------------------------------ • [5.480 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 a related PipelineRun should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:249 ------------------------------ • [0.118 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 PR branch should not exist in the repo [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:264 ------------------------------ • [0.943 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 related image repo and the robot account should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:277 ------------------------------ • [42.205 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 a related PipelineRun should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:249 ------------------------------ • [0.119 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 PR branch should not exist in the repo [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:264 ------------------------------ • [0.829 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 related image repo and the robot account should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch] /workspace/source/test/e2e/pac_build.go:277 ------------------------------ • [70.621 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /workspace/source/test/e2e/pac_build.go:327 Timeline >> Image repository for component gh-test-custom-branch-xkxfnj in namespace build-e2e-oakw do not have right state ('' != 'ready') yet but it has status { { } { } []}. PipelineRun has not been created yet for the component build-e2e-oakw/gh-test-custom-branch-xkxfnj PipelineRun has not been created yet for the component build-e2e-oakw/gh-test-custom-branch-xkxfnj PipelineRun has not been created yet for the component build-e2e-oakw/gh-test-custom-branch-xkxfnj << Timeline ------------------------------ • [0.264 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created should lead to a PaC init PR creation [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /workspace/source/test/e2e/pac_build.go:342 ------------------------------ • [33.970 seconds] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /workspace/source/test/e2e/pac_build.go:327 Timeline >> Image repository for component gl-test-custom-branch-ervavi in namespace build-e2e-moue do not have right state ('' != 'ready') yet but it has status { { } { } []}. PipelineRun has not been created yet for the component build-e2e-moue/gl-test-custom-branch-ervavi << Timeline ------------------------------ • [0.198 seconds] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created should lead to a PaC init PR creation [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /workspace/source/test/e2e/pac_build.go:342 ------------------------------ • [100.647 seconds] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace triggers a PipelineRun for parent component [build-service, renovate, multi-component, gitlab] /workspace/source/test/e2e/renovate.go:259 Timeline >> PipelineRun has not been created yet for the component build-e2e-edkp/gl-multi-component-parent-hspp PipelineRun has not been created yet for the component build-e2e-edkp/gl-multi-component-parent-hspp PipelineRun has not been created yet for the component build-e2e-edkp/gl-multi-component-parent-hspp PipelineRun has not been created yet for the component build-e2e-edkp/gl-multi-component-parent-hspp PipelineRun has not been created yet for the component build-e2e-edkp/gl-multi-component-parent-hspp << Timeline ------------------------------ • [30.386 seconds] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /workspace/source/test/e2e/pac_build.go:327 Timeline >> Image repository for component fj-test-custom-branch-ildcfr in namespace build-e2e-yaqs do not have right state ('' != 'ready') yet but it has status { { } { } []}. PipelineRun has not been created yet for the component build-e2e-yaqs/fj-test-custom-branch-ildcfr << Timeline ------------------------------ • [0.208 seconds] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created should lead to a PaC init PR creation [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /workspace/source/test/e2e/pac_build.go:342 ------------------------------ • [124.036 seconds] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created check only one pipelinerun should be triggered [build-service, github, pac-build, secret-lookup] /workspace/source/test/e2e/secret_lookup.go:193 ------------------------------ 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] /workspace/source/test/e2e/secret_lookup.go:206 ------------------------------ • [680.191 seconds] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /workspace/source/test/e2e/pac_build.go:360 Timeline >> PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c found for Component build-e2e-moue/gl-test-custom-branch-ervavi PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: ResolvingTaskRef PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: ResolvingTaskRef PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: ResolvingTaskRef PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: ResolvingTaskRef PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: ResolvingTaskRef PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-sbr6c reason: Completed << Timeline ------------------------------ • [1.124 seconds] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /workspace/source/test/e2e/pac_build.go:365 ------------------------------ • [0.286 seconds] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created created image repo is public [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /workspace/source/test/e2e/pac_build.go:384 ------------------------------ • [680.198 seconds] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for parent component [build-service, renovate, multi-component, gitlab] /workspace/source/test/e2e/renovate.go:274 Timeline >> PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc found for Component build-e2e-edkp/gl-multi-component-parent-hspp PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun has not been created yet for the Component build-e2e-edkp/gl-multi-component-parent-hspp PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Running PipelineRun gl-multi-component-parent-hspp-on-pull-request-mxdzc reason: Completed << Timeline ------------------------------ • [0.503 seconds] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created image tag is updated successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /workspace/source/test/e2e/pac_build.go:390 Timeline >> Image tag quay.io/redhat-appstudio-qe/build-e2e-moue/gl-test-custom-branch-ervavi:on-pr-1c27e02910383a7f617b590d0296225c841b4a8a successfully found in Quay << Timeline ------------------------------ • [0.500 seconds] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created should ensure pruning labels are set [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /workspace/source/test/e2e/pac_build.go:416 ------------------------------ • [0.417 seconds] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created eventually leads to the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /workspace/source/test/e2e/pac_build.go:433 ------------------------------ • [680.190 seconds] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /workspace/source/test/e2e/pac_build.go:360 Timeline >> PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 found for Component build-e2e-yaqs/fj-test-custom-branch-ildcfr PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: ResolvingTaskRef PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: ResolvingTaskRef PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: ResolvingTaskRef PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: ResolvingTaskRef PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: ResolvingTaskRef PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: ResolvingTaskRef PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun has not been created yet for the Component build-e2e-yaqs/fj-test-custom-branch-ildcfr PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-h6zf5 reason: Completed << Timeline ------------------------------ • [1.188 seconds] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /workspace/source/test/e2e/pac_build.go:365 ------------------------------ • [0.325 seconds] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created created image repo is public [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /workspace/source/test/e2e/pac_build.go:384 ------------------------------ • [0.617 seconds] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created image tag is updated successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /workspace/source/test/e2e/pac_build.go:390 Timeline >> Image tag quay.io/redhat-appstudio-qe/build-e2e-yaqs/fj-test-custom-branch-ildcfr:on-pr-3ce7b7e94c5b6d534a62b818b6761601fab00b9e successfully found in Quay << Timeline ------------------------------ • [0.486 seconds] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created should ensure pruning labels are set [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /workspace/source/test/e2e/pac_build.go:416 ------------------------------ • [0.531 seconds] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created eventually leads to the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /workspace/source/test/e2e/pac_build.go:433 ------------------------------ • [820.291 seconds] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace the PipelineRun should eventually finish successfully for component go-component-rnhknv [build-service, github, pac-build, multi-component] /workspace/source/test/e2e/multi_component.go:159 Timeline >> PipelineRun go-component-rnhknv-on-pull-request-nzkfc found for Component build-e2e-semp/go-component-rnhknv PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: ResolvingTaskRef PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Running PipelineRun go-component-rnhknv-on-pull-request-nzkfc reason: Completed << Timeline ------------------------------ • [1.847 seconds] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace merging the PR should be successful [build-service, github, pac-build, multi-component] /workspace/source/test/e2e/multi_component.go:164 Timeline >> merged result sha: b6b0e0d281bc1b99c7b73bbf8520469ac0c99c97 for PR #32746 << Timeline ------------------------------ • [21.055 seconds] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is updated eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /workspace/source/test/e2e/pac_build.go:458 Timeline >> created file sha: d598ab17cb65801a2396abd2f6c2c2e5501e2013 PipelineRun has not been created yet for the component build-e2e-moue/gl-test-custom-branch-ervavi << Timeline ------------------------------ • [0.243 seconds] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is updated should lead to a PaC init PR update [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /workspace/source/test/e2e/pac_build.go:473 ------------------------------ • [21.441 seconds] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /workspace/source/test/e2e/pac_build.go:458 Timeline >> created file sha: 169a0040754c4c65f393a2cd1738a71db568d1d2 PipelineRun has not been created yet for the component build-e2e-yaqs/fj-test-custom-branch-ildcfr << Timeline ------------------------------ • [0.195 seconds] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated should lead to a PaC init PR update [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /workspace/source/test/e2e/pac_build.go:473 ------------------------------ • [20.214 seconds] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace leads to triggering on push PipelineRun [build-service, github, pac-build, multi-component] /workspace/source/test/e2e/multi_component.go:174 Timeline >> Push PipelineRun has not been created yet for the component build-e2e-semp/go-component-rnhknv << Timeline ------------------------------ • [10.217 seconds] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace creates component with context directory python-component [build-service, github, pac-build, multi-component] /workspace/source/test/e2e/multi_component.go:106 Timeline >> Image repository for component python-component-uxmsdf in namespace build-e2e-semp do not have right state ('' != 'ready') yet but it has status { { } { } []}. << Timeline ------------------------------ • [20.204 seconds] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace triggers a PipelineRun for component python-component-uxmsdf [build-service, github, pac-build, multi-component] /workspace/source/test/e2e/multi_component.go:125 Timeline >> PipelineRun has not been created yet for the component build-e2e-semp/python-component-uxmsdf << Timeline ------------------------------ • [0.450 seconds] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace should lead to a PaC PR creation for component python-component-uxmsdf [build-service, github, pac-build, multi-component] /workspace/source/test/e2e/multi_component.go:140 ------------------------------ • [952.573 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /workspace/source/test/e2e/pac_build.go:360 Timeline >> PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp found for Component build-e2e-oakw/gh-test-custom-branch-xkxfnj PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: ResolvingTaskRef PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: ResolvingTaskRef PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: ResolvingTaskRef PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: ResolvingTaskRef PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: ResolvingTaskRef PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp reason: Failed attempt 1/3: PipelineRun "gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp" failed: pod: gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp-init-pod | init container: prepare 2026/04/30 05:49:22 Entrypoint initialization pod: gh-test-custom-branch-xkxfnj-on-pull-request-dxzxp-init-pod | container step-init: time="2026-04-30T05:49:26Z" level=info msg="[param] enable: false" time="2026-04-30T05:49:26Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-30T05:49:26Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-30T05:49:26Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-30T05:49:26Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-30T05:49:26Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-30T05:49:26Z" level=info msg="Cache proxy is disabled via param" time="2026-04-30T05:49:26Z" level=info msg="[result] HTTP PROXY: " time="2026-04-30T05:49:26Z" level=info msg="[result] NO PROXY: " New PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 found after retrigger for component build-e2e-oakw/gh-test-custom-branch-xkxfnj PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 found for Component build-e2e-oakw/gh-test-custom-branch-xkxfnj PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: ResolvingTaskRef PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: ResolvingTaskRef PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun has not been created yet for the Component build-e2e-oakw/gh-test-custom-branch-xkxfnj PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-w9f97 reason: Completed << Timeline ------------------------------ • [1.247 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /workspace/source/test/e2e/pac_build.go:365 ------------------------------ • [1.044 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created created image repo is public [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /workspace/source/test/e2e/pac_build.go:384 ------------------------------ • [0.794 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created image tag is updated successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /workspace/source/test/e2e/pac_build.go:390 Timeline >> Image tag quay.io/redhat-appstudio-qe/build-e2e-oakw/gh-test-custom-branch-xkxfnj:on-pr-8c331722e965cdcf7d8bacfe8ff08e1c372f8bb2 successfully found in Quay << Timeline ------------------------------ • [0.557 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created should ensure pruning labels are set [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /workspace/source/test/e2e/pac_build.go:416 ------------------------------ • [0.668 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created eventually leads to the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /workspace/source/test/e2e/pac_build.go:433 ------------------------------ • [20.860 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /workspace/source/test/e2e/pac_build.go:458 Timeline >> created file sha: 24544312f4b8cd91aebe6aec343e5e36d3ae371a PipelineRun has not been created yet for the component build-e2e-oakw/gh-test-custom-branch-xkxfnj << Timeline ------------------------------ • [0.228 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated should lead to a PaC init PR update [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /workspace/source/test/e2e/pac_build.go:473 ------------------------------ • [460.262 seconds] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is updated PipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /workspace/source/test/e2e/pac_build.go:492 Timeline >> PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv found for Component build-e2e-moue/gl-test-custom-branch-ervavi PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: ResolvingTaskRef PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: ResolvingTaskRef PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Running PipelineRun gl-test-custom-branch-ervavi-on-pull-request-zvxcv reason: Completed << Timeline ------------------------------ • [0.364 seconds] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is updated eventually leads to another update of a PR about the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /workspace/source/test/e2e/pac_build.go:497 ------------------------------ • [22.644 seconds] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /workspace/source/test/e2e/pac_build.go:523 Timeline >> merged result sha: 6e3c664a9c724d6d84ed65b39c95fff6de136e26 PipelineRun has not been created yet for the component build-e2e-moue/gl-test-custom-branch-ervavi << Timeline ------------------------------ • [500.621 seconds] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated PipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /workspace/source/test/e2e/pac_build.go:492 Timeline >> PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt found for Component build-e2e-yaqs/fj-test-custom-branch-ildcfr PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: ResolvingTaskRef PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: ResolvingTaskRef PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: ResolvingTaskRef PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-pull-request-m2skt reason: Completed << Timeline ------------------------------ • [0.000 seconds] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated eventually leads to another update of a PR about the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /workspace/source/test/e2e/pac_build.go:497 ------------------------------ • [23.973 seconds] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /workspace/source/test/e2e/pac_build.go:523 Timeline >> merged result sha: 5725fc9734f13d0c67acddf2d857c1dca099915f PipelineRun has not been created yet for the component build-e2e-yaqs/fj-test-custom-branch-ildcfr << Timeline ------------------------------ • [FAILED] [1326.403 seconds] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace [It] the PipelineRun should eventually finish successfully for parent component [build-service, renovate, multi-component, forgejo] /workspace/source/test/e2e/renovate.go:274 Timeline >> PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 found for Component build-e2e-oovz/fj-multi-component-parent-agzw PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: ResolvingTaskRef PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: ResolvingTaskRef PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: ResolvingTaskRef PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: ResolvingTaskRef PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: PipelineRunStopping PipelineRun fj-multi-component-parent-agzw-on-pull-request-pw9f2 reason: Failed attempt 1/3: PipelineRun "fj-multi-component-parent-agzw-on-pull-request-pw9f2" failed: pod: fj-multi-component-parent-agzw-on-pull-request-pw9f2-init-pod | init container: prepare 2026/04/30 05:48:25 Entrypoint initialization pod: fj-multi-component-parent-agzw-on-pull-request-pw9f2-init-pod | container step-init: time="2026-04-30T05:48:29Z" level=info msg="[param] enable: false" time="2026-04-30T05:48:29Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-30T05:48:29Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-30T05:48:29Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-30T05:48:29Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-30T05:48:29Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-30T05:48:29Z" level=info msg="Cache proxy is disabled via param" time="2026-04-30T05:48:29Z" level=info msg="[result] HTTP PROXY: " time="2026-04-30T05:48:29Z" level=info msg="[result] NO PROXY: " New PipelineRun fj-multi-component-parent-agzw-on-pull-request-ggcf9 found after retrigger for component build-e2e-oovz/fj-multi-component-parent-agzw PipelineRun fj-multi-component-parent-agzw-on-pull-request-ggcf9 found for Component build-e2e-oovz/fj-multi-component-parent-agzw PipelineRun fj-multi-component-parent-agzw-on-pull-request-ggcf9 reason: ResolvingTaskRef PipelineRun fj-multi-component-parent-agzw-on-pull-request-ggcf9 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-ggcf9 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-ggcf9 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-ggcf9 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-ggcf9 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-ggcf9 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-ggcf9 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-ggcf9 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-ggcf9 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-ggcf9 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-ggcf9 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-ggcf9 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-ggcf9 reason: Failed attempt 2/3: PipelineRun "fj-multi-component-parent-agzw-on-pull-request-ggcf9" failed: pod: fj-multi-component-parent-agzw-on-pull-request-ggcf9-init-pod | init container: prepare 2026/04/30 05:57:46 Entrypoint initialization pod: fj-multi-component-parent-agzw-on-pull-request-ggcf9-init-pod | container step-init: time="2026-04-30T05:58:24Z" level=info msg="[param] enable: false" time="2026-04-30T05:58:24Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-30T05:58:24Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-30T05:58:24Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-30T05:58:24Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-30T05:58:24Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-30T05:58:24Z" level=info msg="Cache proxy is disabled via param" time="2026-04-30T05:58:24Z" level=info msg="[result] HTTP PROXY: " time="2026-04-30T05:58:24Z" level=info msg="[result] NO PROXY: " New PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 found after retrigger for component build-e2e-oovz/fj-multi-component-parent-agzw PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 found for Component build-e2e-oovz/fj-multi-component-parent-agzw PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: ResolvingTaskRef PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: ResolvingTaskRef PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: ResolvingTaskRef PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: ResolvingTaskRef PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: ResolvingTaskRef PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: Running PipelineRun fj-multi-component-parent-agzw-on-pull-request-bdst6 reason: Failed attempt 3/3: PipelineRun "fj-multi-component-parent-agzw-on-pull-request-bdst6" failed: pod: fj-multi-component-parent-agzw-on-pull-request-bdst6-init-pod | init container: prepare 2026/04/30 06:03:34 Entrypoint initialization pod: fj-multi-component-parent-agzw-on-pull-request-bdst6-init-pod | container step-init: time="2026-04-30T06:03:39Z" level=info msg="[param] enable: false" time="2026-04-30T06:03:39Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-30T06:03:39Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-30T06:03:39Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-30T06:03:39Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-30T06:03:39Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-30T06:03:39Z" level=info msg="Cache proxy is disabled via param" time="2026-04-30T06:03:39Z" level=info msg="[result] HTTP PROXY: " time="2026-04-30T06:03:39Z" level=info msg="[result] NO PROXY: " [FAILED] in [It] - /workspace/source/test/e2e/renovate.go:276 @ 04/30/26 06:08:35.795 << Timeline [FAILED] Expected success, but got an error: <*errors.errorString | 0xc001b981b0>: pod: fj-multi-component-parent-agzw-on-pull-request-bdst6-init-pod | init container: prepare 2026/04/30 06:03:34 Entrypoint initialization pod: fj-multi-component-parent-agzw-on-pull-request-bdst6-init-pod | container step-init: time="2026-04-30T06:03:39Z" level=info msg="[param] enable: false" time="2026-04-30T06:03:39Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-30T06:03:39Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-30T06:03:39Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-30T06:03:39Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-30T06:03:39Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-30T06:03:39Z" level=info msg="Cache proxy is disabled via param" time="2026-04-30T06:03:39Z" level=info msg="[result] HTTP PROXY: " time="2026-04-30T06:03:39Z" level=info msg="[result] NO PROXY: " { s: "\n pod: fj-multi-component-parent-agzw-on-pull-request-bdst6-init-pod | init container: prepare\n2026/04/30 06:03:34 Entrypoint initialization\n\npod: fj-multi-component-parent-agzw-on-pull-request-bdst6-init-pod | container step-init: \ntime=\"2026-04-30T06:03:39Z\" level=info msg=\"[param] enable: false\"\ntime=\"2026-04-30T06:03:39Z\" level=info msg=\"[param] default-http-proxy: squid.caching.svc.cluster.local:3128\"\ntime=\"2026-04-30T06:03:39Z\" level=info msg=\"[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai\"\ntime=\"2026-04-30T06:03:39Z\" level=info msg=\"[param] http-proxy-result-path: /tekton/results/http-proxy\"\ntime=\"2026-04-30T06:03:39Z\" level=info msg=\"[param] no-proxy-result-path: /tekton/results/no-proxy\"\ntime=\"2026-04-30T06:03:39Z\" level=info msg=\"Using in-cluster config\" logger=KubeClient\ntime=\"2026-04-30T06:03:39Z\" level=info msg=\"Cache proxy is disabled via param\"\ntime=\"2026-04-30T06:03:39Z\" level=info msg=\"[result] HTTP PROXY: \"\ntime=\"2026-04-30T06:03:39Z\" level=info msg=\"[result] NO PROXY: \"\n", } In [It] at: /workspace/source/test/e2e/renovate.go:276 @ 04/30/26 06:08:35.795 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace [It] the PipelineRun should eventually finish successfully for child component [build-service, renovate, multi-component, forgejo] /workspace/source/test/e2e/renovate.go:285 [SKIPPED] Spec skipped because an earlier spec in an ordered container failed In [It] at: /workspace/source/test/e2e/renovate.go:285 @ 04/30/26 06:09:12.475 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace [It] should lead to a PaC PR creation for child component [build-service, renovate, multi-component, forgejo] /workspace/source/test/e2e/renovate.go:289 [SKIPPED] Spec skipped because an earlier spec in an ordered container failed In [It] at: /workspace/source/test/e2e/renovate.go:289 @ 04/30/26 06:09:12.475 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace [It] Merging the PaC PR should be successful for child component [build-service, renovate, multi-component, forgejo] /workspace/source/test/e2e/renovate.go:307 [SKIPPED] Spec skipped because an earlier spec in an ordered container failed In [It] at: /workspace/source/test/e2e/renovate.go:307 @ 04/30/26 06:09:12.476 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace [It] create dockerfile and yaml manifest that references build and distribution repositories [build-service, renovate, multi-component, forgejo] /workspace/source/test/e2e/renovate.go:318 [SKIPPED] Spec skipped because an earlier spec in an ordered container failed In [It] at: /workspace/source/test/e2e/renovate.go:318 @ 04/30/26 06:09:12.476 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace [It] should lead to a PaC PR creation for parent component [build-service, renovate, multi-component, forgejo] /workspace/source/test/e2e/renovate.go:358 [SKIPPED] Spec skipped because an earlier spec in an ordered container failed In [It] at: /workspace/source/test/e2e/renovate.go:358 @ 04/30/26 06:09:12.476 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace [It] Merging the PaC PR should be successful for parent component [build-service, renovate, multi-component, forgejo] /workspace/source/test/e2e/renovate.go:375 [SKIPPED] Spec skipped because an earlier spec in an ordered container failed In [It] at: /workspace/source/test/e2e/renovate.go:375 @ 04/30/26 06:09:12.476 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace [It] PR merge triggers PAC PipelineRun for parent component [build-service, renovate, multi-component, forgejo] /workspace/source/test/e2e/renovate.go:385 [SKIPPED] Spec skipped because an earlier spec in an ordered container failed In [It] at: /workspace/source/test/e2e/renovate.go:385 @ 04/30/26 06:09:12.477 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace [It] PAC PipelineRun for parent component is successful [build-service, renovate, multi-component, forgejo] /workspace/source/test/e2e/renovate.go:401 [SKIPPED] Spec skipped because an earlier spec in an ordered container failed In [It] at: /workspace/source/test/e2e/renovate.go:401 @ 04/30/26 06:09:12.477 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace [It] should lead to a nudge PR creation for child component [build-service, renovate, multi-component, forgejo] /workspace/source/test/e2e/renovate.go:412 [SKIPPED] Spec skipped because an earlier spec in an ordered container failed In [It] at: /workspace/source/test/e2e/renovate.go:412 @ 04/30/26 06:09:12.477 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace [It] merging the PR should be successful for child component [build-service, renovate, multi-component, forgejo] /workspace/source/test/e2e/renovate.go:429 [SKIPPED] Spec skipped because an earlier spec in an ordered container failed In [It] at: /workspace/source/test/e2e/renovate.go:429 @ 04/30/26 06:09:12.478 ------------------------------ S [SKIPPED] [0.000 seconds] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace [It] Verify the nudge updated the contents [build-service, renovate, multi-component, forgejo] /workspace/source/test/e2e/renovate.go:440 [SKIPPED] Spec skipped because an earlier spec in an ordered container failed In [It] at: /workspace/source/test/e2e/renovate.go:440 @ 04/30/26 06:09:12.478 ------------------------------ • [752.845 seconds] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace the PipelineRun should eventually finish successfully for component python-component-uxmsdf [build-service, github, pac-build, multi-component] /workspace/source/test/e2e/multi_component.go:159 Timeline >> PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 found for Component build-e2e-semp/python-component-uxmsdf PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: ResolvingTaskRef PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: ResolvingTaskRef PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: ResolvingTaskRef PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: ResolvingTaskRef PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: ResolvingTaskRef PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Running PipelineRun python-component-uxmsdf-on-pull-request-wz4c2 reason: Completed << Timeline ------------------------------ • [1.777 seconds] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace merging the PR should be successful [build-service, github, pac-build, multi-component] /workspace/source/test/e2e/multi_component.go:164 Timeline >> merged result sha: 8728232f61addbc80419e1bd1aa4a6888afc5b7a for PR #32747 << Timeline ------------------------------ • [20.891 seconds] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace leads to triggering on push PipelineRun [build-service, github, pac-build, multi-component] /workspace/source/test/e2e/multi_component.go:174 Timeline >> Push PipelineRun has not been created yet for the component build-e2e-semp/python-component-uxmsdf << Timeline ------------------------------ • [4.045 seconds] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace only one component is changed [build-service, github, pac-build, multi-component] /workspace/source/test/e2e/multi_component.go:190 Timeline >> PR #32749 got created with sha 58194a421501e1d97a13130dd76f47d302dbea6f << Timeline ------------------------------ • [1577.867 seconds] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for parent component [build-service, renovate, multi-component, github] /workspace/source/test/e2e/renovate.go:274 Timeline >> PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 found for Component build-e2e-aupf/gh-multi-component-parent-cgit PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: PipelineRunStopping PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: PipelineRunStopping PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: PipelineRunStopping PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: PipelineRunStopping PipelineRun has not been created yet for the Component build-e2e-aupf/gh-multi-component-parent-cgit PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: PipelineRunStopping PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: PipelineRunStopping PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: PipelineRunStopping PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: PipelineRunStopping PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: PipelineRunStopping PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: PipelineRunStopping PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: PipelineRunStopping PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: PipelineRunStopping PipelineRun gh-multi-component-parent-cgit-on-pull-request-rxx55 reason: Failed attempt 1/3: PipelineRun "gh-multi-component-parent-cgit-on-pull-request-rxx55" failed: pod: gh-multi-component-parent-cgit-on-pull-request-rxx55-init-pod | init container: prepare 2026/04/30 05:48:31 Entrypoint initialization pod: gh-multi-component-parent-cgit-on-pull-request-rxx55-init-pod | container step-init: time="2026-04-30T05:48:33Z" level=info msg="[param] enable: false" time="2026-04-30T05:48:33Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-30T05:48:33Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-30T05:48:33Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-30T05:48:33Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-30T05:48:33Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-30T05:48:33Z" level=info msg="Cache proxy is disabled via param" time="2026-04-30T05:48:33Z" level=info msg="[result] HTTP PROXY: " time="2026-04-30T05:48:33Z" level=info msg="[result] NO PROXY: " New PipelineRun gh-multi-component-parent-cgit-on-pull-request-h24mg found after retrigger for component build-e2e-aupf/gh-multi-component-parent-cgit PipelineRun gh-multi-component-parent-cgit-on-pull-request-h24mg found for Component build-e2e-aupf/gh-multi-component-parent-cgit PipelineRun gh-multi-component-parent-cgit-on-pull-request-h24mg reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-cgit-on-pull-request-h24mg reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-h24mg reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-h24mg reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-h24mg reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-h24mg reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-h24mg reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-h24mg reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-h24mg reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-h24mg reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-h24mg reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-h24mg reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-h24mg reason: Failed attempt 2/3: PipelineRun "gh-multi-component-parent-cgit-on-pull-request-h24mg" failed: pod: gh-multi-component-parent-cgit-on-pull-request-h24mg-init-pod | init container: prepare 2026/04/30 05:59:23 Entrypoint initialization pod: gh-multi-component-parent-cgit-on-pull-request-h24mg-init-pod | container step-init: time="2026-04-30T05:59:28Z" level=info msg="[param] enable: false" time="2026-04-30T05:59:28Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-30T05:59:28Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-30T05:59:28Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-30T05:59:28Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-30T05:59:28Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-30T05:59:28Z" level=info msg="Cache proxy is disabled via param" time="2026-04-30T05:59:28Z" level=info msg="[result] HTTP PROXY: " time="2026-04-30T05:59:28Z" level=info msg="[result] NO PROXY: " New PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr found after retrigger for component build-e2e-aupf/gh-multi-component-parent-cgit PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr found for Component build-e2e-aupf/gh-multi-component-parent-cgit PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Running PipelineRun gh-multi-component-parent-cgit-on-pull-request-htswr reason: Completed << Timeline ------------------------------ • [21.127 seconds] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace only related pipelinerun should be triggered [build-service, github, pac-build, multi-component] /workspace/source/test/e2e/multi_component.go:205 Timeline >> on pull PiplelineRun has not been created yet for the PR << Timeline ------------------------------ • [580.190 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated PipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /workspace/source/test/e2e/pac_build.go:492 Timeline >> PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 found for Component build-e2e-oakw/gh-test-custom-branch-xkxfnj PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: ResolvingTaskRef PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: ResolvingTaskRef PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-pull-request-7ftt8 reason: Completed << Timeline ------------------------------ • [0.410 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated eventually leads to another update of a PR about the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /workspace/source/test/e2e/pac_build.go:497 ------------------------------ • [19.597 seconds] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when a components is created with same git url in different namespace should fail to configure PaC for the component [build-service, github, pac-build, multi-component] /workspace/source/test/e2e/multi_component.go:264 Timeline >> Image repository for component go-component-xelmgg in namespace build-e2e-fxje do not have right state ('' != 'ready') yet but it has status { { } { } []}. build status annotation value: {"pac":{"state":"error","error-id":53,"error-message":"53: Git repository is already handled by Pipelines as Code"},"message":"done"} build status: &{State:error MergeUrl: ConfigurationTime: ErrorInfo:{ErrId:53 ErrMessage:53: Git repository is already handled by Pipelines as Code}} << Timeline ------------------------------ • [22.057 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /workspace/source/test/e2e/pac_build.go:523 Timeline >> merged result sha: d16d3d4be1f680fe803b75a65f5fd3da520814cc PipelineRun has not been created yet for the component build-e2e-oakw/gh-test-custom-branch-xkxfnj << Timeline ------------------------------ • [480.201 seconds] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /workspace/source/test/e2e/pac_build.go:539 Timeline >> PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 found for Component build-e2e-moue/gl-test-custom-branch-ervavi PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: ResolvingTaskRef PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Running PipelineRun gl-test-custom-branch-ervavi-on-push-hg7z8 reason: Completed << Timeline ------------------------------ • [0.253 seconds] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged does not have expiration set [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /workspace/source/test/e2e/pac_build.go:545 ------------------------------ • [1025.511 seconds] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for child component [build-service, renovate, multi-component, gitlab] /workspace/source/test/e2e/renovate.go:285 Timeline >> PipelineRun gl-multi-component-child-hspp-on-pull-request-rxd4j found for Component build-e2e-edkp/gl-multi-component-child-hspp PipelineRun gl-multi-component-child-hspp-on-pull-request-rxd4j reason: Failed attempt 1/3: PipelineRun "gl-multi-component-child-hspp-on-pull-request-rxd4j" failed: pod: gl-multi-component-child-hspp-on-pull-request-rxd4j-init-pod | init container: prepare 2026/04/30 05:48:19 Entrypoint initialization pod: gl-multi-component-child-hspp-on-pull-request-rxd4j-init-pod | container step-init: time="2026-04-30T05:48:23Z" level=info msg="[param] enable: false" time="2026-04-30T05:48:23Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-30T05:48:23Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-30T05:48:23Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-30T05:48:23Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-30T05:48:23Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-30T05:48:23Z" level=info msg="Cache proxy is disabled via param" time="2026-04-30T05:48:23Z" level=info msg="[result] HTTP PROXY: " time="2026-04-30T05:48:23Z" level=info msg="[result] NO PROXY: " New PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s found after retrigger for component build-e2e-edkp/gl-multi-component-child-hspp PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s found for Component build-e2e-edkp/gl-multi-component-child-hspp PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: ResolvingTaskRef PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: ResolvingTaskRef PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: ResolvingTaskRef PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-mfx6s reason: Failed attempt 2/3: PipelineRun "gl-multi-component-child-hspp-on-pull-request-mfx6s" failed: pod: gl-multi-component-child-hspp-on-pull-request-mfx6s-init-pod | init container: prepare 2026/04/30 06:00:08 Entrypoint initialization pod: gl-multi-component-child-hspp-on-pull-request-mfx6s-init-pod | container step-init: time="2026-04-30T06:00:12Z" level=info msg="[param] enable: false" time="2026-04-30T06:00:12Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-30T06:00:12Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-30T06:00:12Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-30T06:00:12Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-30T06:00:12Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-30T06:00:12Z" level=info msg="Cache proxy is disabled via param" time="2026-04-30T06:00:12Z" level=info msg="[result] HTTP PROXY: " time="2026-04-30T06:00:12Z" level=info msg="[result] NO PROXY: " New PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v found after retrigger for component build-e2e-edkp/gl-multi-component-child-hspp PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v found for Component build-e2e-edkp/gl-multi-component-child-hspp PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: ResolvingTaskRef PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: ResolvingTaskRef PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Running PipelineRun gl-multi-component-child-hspp-on-pull-request-7vx5v reason: Completed << Timeline ------------------------------ • [0.205 seconds] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace should lead to a PaC PR creation for child component [build-service, renovate, multi-component, gitlab] /workspace/source/test/e2e/renovate.go:289 ------------------------------ • [2.460 seconds] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace Merging the PaC PR should be successful for child component [build-service, renovate, multi-component, gitlab] /workspace/source/test/e2e/renovate.go:307 Timeline >> merged result sha: 2d94768342d451ccd4dc25603cc829a9550309ad for PR #1 << Timeline ------------------------------ • [500.495 seconds] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /workspace/source/test/e2e/pac_build.go:539 Timeline >> PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v found for Component build-e2e-yaqs/fj-test-custom-branch-ildcfr PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: ResolvingTaskRef PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: ResolvingTaskRef PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: ResolvingTaskRef PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: ResolvingTaskRef PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: ResolvingTaskRef PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Running PipelineRun fj-test-custom-branch-ildcfr-on-push-52f6v reason: Completed << Timeline ------------------------------ • [0.295 seconds] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged does not have expiration set [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /workspace/source/test/e2e/pac_build.go:545 ------------------------------ • [66.938 seconds] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace create dockerfile and yaml manifest that references build and distribution repositories [build-service, renovate, multi-component, gitlab] /workspace/source/test/e2e/renovate.go:318 ------------------------------ • [0.218 seconds] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace should lead to a PaC PR creation for parent component [build-service, renovate, multi-component, gitlab] /workspace/source/test/e2e/renovate.go:358 ------------------------------ • [0.970 seconds] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace Merging the PaC PR should be successful for parent component [build-service, renovate, multi-component, gitlab] /workspace/source/test/e2e/renovate.go:375 Timeline >> merged result sha: 55c151b8aec3b66a8f49049bea436ce14bfe973e for PR #1 << Timeline ------------------------------ • [128.697 seconds] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged After updating image visibility to private, it should not trigger another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /workspace/source/test/e2e/pac_build.go:560 Timeline >> found pipelinerun: gl-test-custom-branch-ervavi-on-push-hg7z8 waiting for one minute and expecting to not trigger a PipelineRun << Timeline ------------------------------ • [0.296 seconds] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged image repo is updated to private [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /workspace/source/test/e2e/pac_build.go:590 ------------------------------ 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] /workspace/source/test/e2e/pac_build.go:595 ------------------------------ 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] /workspace/source/test/e2e/pac_build.go:631 ------------------------------ • [20.289 seconds] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace PR merge triggers PAC PipelineRun for parent component [build-service, renovate, multi-component, gitlab] /workspace/source/test/e2e/renovate.go:385 Timeline >> Push PipelineRun has not been created yet for the component build-e2e-edkp/gl-multi-component-parent-hspp << Timeline ------------------------------ • [30.132 seconds] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the component is removed and recreated (with the same name in the same namespace) should no longer lead to a creation of a PaC PR [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch] /workspace/source/test/e2e/pac_build.go:701 Timeline >> Image repository for component gl-test-custom-branch-ervavi in namespace build-e2e-moue do not have right state ('' != 'ready') yet but it has status { { } { } []}. Found purge PR with id: 3 << Timeline ------------------------------ • [121.036 seconds] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged After updating image visibility to private, it should not trigger another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /workspace/source/test/e2e/pac_build.go:560 Timeline >> waiting for one minute and expecting to not trigger a PipelineRun << Timeline ------------------------------ • [0.349 seconds] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged image repo is updated to private [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /workspace/source/test/e2e/pac_build.go:590 ------------------------------ 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] /workspace/source/test/e2e/pac_build.go:595 ------------------------------ 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] /workspace/source/test/e2e/pac_build.go:631 ------------------------------ • [332.820 seconds] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for child component [build-service, renovate, multi-component, github] /workspace/source/test/e2e/renovate.go:285 Timeline >> PipelineRun gh-multi-component-child-cgit-on-pull-request-shppz found for Component build-e2e-aupf/gh-multi-component-child-cgit PipelineRun gh-multi-component-child-cgit-on-pull-request-shppz reason: Failed attempt 1/3: PipelineRun "gh-multi-component-child-cgit-on-pull-request-shppz" failed: pod: gh-multi-component-child-cgit-on-pull-request-shppz-init-pod | init container: prepare 2026/04/30 05:46:12 Entrypoint initialization pod: gh-multi-component-child-cgit-on-pull-request-shppz-init-pod | container step-init: time="2026-04-30T05:46:27Z" level=info msg="[param] enable: false" time="2026-04-30T05:46:27Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128" time="2026-04-30T05:46:27Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai" time="2026-04-30T05:46:27Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy" time="2026-04-30T05:46:27Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy" time="2026-04-30T05:46:27Z" level=info msg="Using in-cluster config" logger=KubeClient time="2026-04-30T05:46:27Z" level=info msg="Cache proxy is disabled via param" time="2026-04-30T05:46:27Z" level=info msg="[result] HTTP PROXY: " time="2026-04-30T05:46:27Z" level=info msg="[result] NO PROXY: " New PipelineRun gh-multi-component-child-cgit-on-pull-request-rv88v found after retrigger for component build-e2e-aupf/gh-multi-component-child-cgit PipelineRun gh-multi-component-child-cgit-on-pull-request-rv88v found for Component build-e2e-aupf/gh-multi-component-child-cgit PipelineRun gh-multi-component-child-cgit-on-pull-request-rv88v reason: ResolvingTaskRef PipelineRun gh-multi-component-child-cgit-on-pull-request-rv88v reason: Running PipelineRun gh-multi-component-child-cgit-on-pull-request-rv88v reason: Running PipelineRun gh-multi-component-child-cgit-on-pull-request-rv88v reason: Running PipelineRun gh-multi-component-child-cgit-on-pull-request-rv88v reason: Running PipelineRun gh-multi-component-child-cgit-on-pull-request-rv88v reason: Running PipelineRun gh-multi-component-child-cgit-on-pull-request-rv88v reason: Running PipelineRun gh-multi-component-child-cgit-on-pull-request-rv88v reason: Running PipelineRun gh-multi-component-child-cgit-on-pull-request-rv88v reason: Running PipelineRun gh-multi-component-child-cgit-on-pull-request-rv88v reason: Running PipelineRun gh-multi-component-child-cgit-on-pull-request-rv88v reason: Running PipelineRun gh-multi-component-child-cgit-on-pull-request-rv88v reason: Running PipelineRun gh-multi-component-child-cgit-on-pull-request-rv88v reason: Running PipelineRun gh-multi-component-child-cgit-on-pull-request-rv88v reason: Running PipelineRun gh-multi-component-child-cgit-on-pull-request-rv88v reason: Running PipelineRun gh-multi-component-child-cgit-on-pull-request-rv88v reason: Running PipelineRun gh-multi-component-child-cgit-on-pull-request-rv88v reason: Completed << Timeline ------------------------------ • [0.231 seconds] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace should lead to a PaC PR creation for child component [build-service, renovate, multi-component, github] /workspace/source/test/e2e/renovate.go:289 ------------------------------ • [1.948 seconds] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace Merging the PaC PR should be successful for child component [build-service, renovate, multi-component, github] /workspace/source/test/e2e/renovate.go:307 Timeline >> merged result sha: ce6de5d4bd93e01bd91043155eee07b84a1eb607 for PR #1 << Timeline ------------------------------ • [5.394 seconds] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace create dockerfile and yaml manifest that references build and distribution repositories [build-service, renovate, multi-component, github] /workspace/source/test/e2e/renovate.go:318 ------------------------------ • [0.209 seconds] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace should lead to a PaC PR creation for parent component [build-service, renovate, multi-component, github] /workspace/source/test/e2e/renovate.go:358 ------------------------------ • [1.968 seconds] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace Merging the PaC PR should be successful for parent component [build-service, renovate, multi-component, github] /workspace/source/test/e2e/renovate.go:375 Timeline >> merged result sha: 12a1750b4d86fcc76753c5c73945a2f93bad2bf9 for PR #1 << Timeline ------------------------------ • [31.392 seconds] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the component is removed and recreated (with the same name in the same namespace) should no longer lead to a creation of a PaC PR [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch] /workspace/source/test/e2e/pac_build.go:701 Timeline >> Image repository for component fj-test-custom-branch-ildcfr in namespace build-e2e-yaqs do not have right state ('' != 'ready') yet but it has status { { } { } []}. Found purge PR with id: 3 << Timeline ------------------------------ • [21.332 seconds] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace PR merge triggers PAC PipelineRun for parent component [build-service, renovate, multi-component, github] /workspace/source/test/e2e/renovate.go:385 Timeline >> Push PipelineRun has not been created yet for the component build-e2e-aupf/gh-multi-component-parent-cgit << Timeline ------------------------------ • [380.292 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /workspace/source/test/e2e/pac_build.go:539 Timeline >> PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 found for Component build-e2e-oakw/gh-test-custom-branch-xkxfnj PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 reason: ResolvingTaskRef PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 reason: Running PipelineRun gh-test-custom-branch-xkxfnj-on-push-5f8c9 reason: Completed << Timeline ------------------------------ • [0.282 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged does not have expiration set [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /workspace/source/test/e2e/pac_build.go:545 ------------------------------ • [129.065 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged After updating image visibility to private, it should not trigger another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /workspace/source/test/e2e/pac_build.go:560 Timeline >> found pipelinerun: gh-test-custom-branch-xkxfnj-on-push-5f8c9 waiting for one minute and expecting to not trigger a PipelineRun << Timeline ------------------------------ • [0.304 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged image repo is updated to private [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /workspace/source/test/e2e/pac_build.go:590 ------------------------------ 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] /workspace/source/test/e2e/pac_build.go:595 ------------------------------ 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] /workspace/source/test/e2e/pac_build.go:631 ------------------------------ • [40.217 seconds] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the component is removed and recreated (with the same name in the same namespace) should no longer lead to a creation of a PaC PR [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch] /workspace/source/test/e2e/pac_build.go:701 Timeline >> Image repository for component gh-test-custom-branch-xkxfnj in namespace build-e2e-oakw do not have right state ('' != 'ready') yet but it has status { { } { } []}. Image repository for component gh-test-custom-branch-xkxfnj in namespace build-e2e-oakw do not have right state ('' != 'ready') yet but it has status { { } { } []}. Found purge PR with id: 3 << Timeline ------------------------------ • [480.200 seconds] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace PAC PipelineRun for parent component is successful [build-service, renovate, multi-component, gitlab] /workspace/source/test/e2e/renovate.go:401 Timeline >> PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 found for Component build-e2e-edkp/gl-multi-component-parent-hspp PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: ResolvingTaskRef PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Running PipelineRun gl-multi-component-parent-hspp-on-push-nk4m6 reason: Completed << Timeline ------------------------------ • [273.774 seconds] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace should lead to a nudge PR creation for child component [build-service, renovate, multi-component, gitlab] /workspace/source/test/e2e/renovate.go:412 ------------------------------ • [1.388 seconds] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace merging the PR should be successful for child component [build-service, renovate, multi-component, gitlab] /workspace/source/test/e2e/renovate.go:429 Timeline >> merged result sha: 7bb15477a6e1da7d63b410944b587159b0677b23 for PR #3 << Timeline ------------------------------ • [18.273 seconds] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace Verify the nudge updated the contents [build-service, renovate, multi-component, gitlab] /workspace/source/test/e2e/renovate.go:440 Timeline >> Verifying Dockerfile.tmp updated to sha sha256:6781e843134795be97a606617d0c0857e2b9c96709f1178518ef0e915513dab5content: FROM quay.io/redhat-appstudio-qe/build-e2e-edkp/gl-multi-component-parent-hspp@sha256:6781e843134795be97a606617d0c0857e2b9c96709f1178518ef0e915513dab5 RUN echo hello << Timeline ------------------------------ • [720.208 seconds] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace PAC PipelineRun for parent component is successful [build-service, renovate, multi-component, github] /workspace/source/test/e2e/renovate.go:401 Timeline >> PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm found for Component build-e2e-aupf/gh-multi-component-parent-cgit PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: ResolvingTaskRef PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Running PipelineRun gh-multi-component-parent-cgit-on-push-t8dlm reason: Completed << Timeline ------------------------------ • [20.563 seconds] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace should lead to a nudge PR creation for child component [build-service, renovate, multi-component, github] /workspace/source/test/e2e/renovate.go:412 ------------------------------ • [2.093 seconds] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace merging the PR should be successful for child component [build-service, renovate, multi-component, github] /workspace/source/test/e2e/renovate.go:429 Timeline >> merged result sha: 46676487a72c5333ce4e06aa85a9ea474da5a0f4 for PR #3 << Timeline ------------------------------ • [14.210 seconds] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace Verify the nudge updated the contents [build-service, renovate, multi-component, github] /workspace/source/test/e2e/renovate.go:440 Timeline >> Verifying Dockerfile.tmp updated to sha sha256:dabff7e3fdd42e087fc8214a3d578ef1673faa62717576d5953052fa0383e209content: FROM quay.io/redhat-appstudio-qe/build-e2e-aupf/gh-multi-component-parent-cgit@sha256:dabff7e3fdd42e087fc8214a3d578ef1673faa62717576d5953052fa0383e209 RUN echo hello << Timeline ------------------------------ [ReportAfterSuite] PASSED [2763.421 seconds] [ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report autogenerated by Ginkgo ------------------------------ Summarizing 1 Failure: [FAIL] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace [It] the PipelineRun should eventually finish successfully for parent component [build-service, renovate, multi-component, forgejo] /workspace/source/test/e2e/renovate.go:276 Ran 136 of 154 Specs in 2837.642 seconds FAIL! -- 135 Passed | 1 Failed | 7 Pending | 11 Skipped Ginkgo ran 1 suite in 52m0.439474429s Test Suite Failed