Error from server (NotFound): namespaces "devfile-proxy" not found Using Devfile proxy: go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=38f650610" ./cmd/odo/ go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo --randomize-all --slow-spec-threshold=120s -timeout 14400s --no-color -nodes=16 --junit-report="test-integration.xml" --label-filter="!unauth && !nocluster && !podman" tests/integration Running Suite: Integration Suite - /go/odo_1/tests/integration ============================================================== Random Seed: 1682445809 - will randomize all specs Will run 462 of 824 specs Running in parallel across 16 processes SSSSSSSSSSSSSSS••SS••S• ------------------------------ • [23.012 seconds] odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile (custom naming strategy: "{ .name | upper }") /go/odo_1/tests/integration/interactive_add_binding_test.go:180 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/257106077 << Captured StdOut/StdErr Output ------------------------------ • [23.057 seconds] odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile (Bind as Files) /go/odo_1/tests/integration/interactive_add_binding_test.go:101 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/1160648637 << Captured StdOut/StdErr Output ------------------------------ • [23.186 seconds] odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile (custom naming strategy: "any string") /go/odo_1/tests/integration/interactive_add_binding_test.go:180 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/1744576442 << Captured StdOut/StdErr Output ------------------------------ SSS••S ------------------------------ • [21.521 seconds] odo add binding interactive command tests when running a deployment when binding to a service in a different namespace should successfully add binding without devfile /go/odo_1/tests/integration/interactive_add_binding_test.go:591 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/1868122388 << Captured StdOut/StdErr Output ------------------------------ S••••S••S••S•••S•SSSSSSS ------------------------------ • [10.574 seconds] odo add binding interactive command tests when running a deployment should successfully add binding without devfile (naming strategy: "none") /go/odo_1/tests/integration/interactive_add_binding_test.go:378 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/4232896794 << Captured StdOut/StdErr Output ------------------------------ SS•S•SS••SS••S••SS•••SSSS•S•••SS••SS••••S••SSSSSS•S•••SS•S•••S••••••••S••••S• ------------------------------ • [54.964 seconds] odo dev command tests when a component with multiple endpoints is run should create state files containing information, including forwarded ports /go/odo_1/tests/integration/cmd_dev_test.go:3170 Captured StdOut/StdErr Output >> PID: 17513 << Captured StdOut/StdErr Output ------------------------------ •SSS•SS•SS••S•••••S•••SSS•S•SS••••SSS• ------------------------------ • [18.893 seconds] odo dev interactive command tests when a component is bootstrapped should sync files when p is pressed /go/odo_1/tests/integration/interactive_dev_test.go:206 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports --no-watch' from /tmp/2237328353 << Captured StdOut/StdErr Output ------------------------------ •SSS•S• ------------------------------ • [3.418 seconds] odo deploy interactive command tests directory is not empty when Alizer cannot determine a Devfile based on the current source code should not fail but fallback to the interactive mode /go/odo_1/tests/integration/interactive_deploy_test.go:159 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo deploy' from /tmp/2384384082 << Captured StdOut/StdErr Output ------------------------------ S••SS•S•• ------------------------------ • [10.870 seconds] odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile ("none" as naming strategy) /go/odo_1/tests/integration/interactive_add_binding_test.go:131 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3440146784 << Captured StdOut/StdErr Output ------------------------------ ••••SS•••SSSSS•••SSS••S•S••SS•••SS••SS•••S••S•S••••S••••SSSS•SS•SSSS••S•S•••• ------------------------------ • [9.330 seconds] odo add binding interactive command tests when running a deployment should successfully add binding without devfile (naming strategy: "lowercase") /go/odo_1/tests/integration/interactive_add_binding_test.go:378 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/4068493654 << Captured StdOut/StdErr Output ------------------------------ ••••SS••••••SS•SSSSS•SSS• ------------------------------ • [8.513 seconds] odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile ("lowercase" as naming strategy) /go/odo_1/tests/integration/interactive_add_binding_test.go:131 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3941553614 << Captured StdOut/StdErr Output ------------------------------ S•••S••••••S• ------------------------------ • [9.947 seconds] odo add binding interactive command tests when running a deployment should successfully add binding without devfile (custom naming strategy: "") /go/odo_1/tests/integration/interactive_add_binding_test.go:463 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3014552541 << Captured StdOut/StdErr Output ------------------------------ S••SS••SS•SS•S••S•S•••S•S••SS ------------------------------ • [13.281 seconds] odo add binding interactive command tests when running a deployment should successfully add binding without devfile (custom naming strategy: "any string") /go/odo_1/tests/integration/interactive_add_binding_test.go:463 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3562045567 << Captured StdOut/StdErr Output ------------------------------ •SS•S•S•••••••••S••S•S• ------------------------------ • [78.759 seconds] odo dev interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile successfully even with -v flag /go/odo_1/tests/integration/interactive_dev_test.go:40 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports -v 4' from /tmp/3547106270 << Captured StdOut/StdErr Output ------------------------------ SS•SSSSS•SSSS•••SS• ------------------------------ • [11.439 seconds] odo add binding interactive command tests when running a deployment should successfully add binding without devfile (naming strategy: "uppercase") /go/odo_1/tests/integration/interactive_add_binding_test.go:378 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/1687050942 << Captured StdOut/StdErr Output ------------------------------ S•••••SS••••SSSS••SSSS••••S••••S•••S•SS•SSS•S ------------------------------ • [17.539 seconds] odo add binding interactive command tests when running a deployment when binding to a service in a different namespace should error out if service is not found in the namespace selected /go/odo_1/tests/integration/interactive_add_binding_test.go:577 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/2353385676 << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [77.518 seconds] odo dev interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile /go/odo_1/tests/integration/interactive_dev_test.go:76 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports' from /tmp/316170570 << Captured StdOut/StdErr Output ------------------------------ SSS••••SSS•S ------------------------------ • [80.052 seconds] odo dev interactive command tests directory is not empty when there is a match from Alizer should display welcoming messages first /go/odo_1/tests/integration/interactive_dev_test.go:112 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports' from /tmp/421370487 << Captured StdOut/StdErr Output ------------------------------ •S••S•S••••S•••SS•SS•SS•SSSS•SS•S•••SSS•••• ------------------------------ • [14.383 seconds] odo add binding interactive command tests when running a deployment should successfully add binding without devfile (default naming strategy) /go/odo_1/tests/integration/interactive_add_binding_test.go:311 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/2060171212 << Captured StdOut/StdErr Output ------------------------------ S•SSSSSS•SSSSS•S•SSS•SS•••••• ------------------------------ • [19.560 seconds] odo add binding interactive command tests when the component is bootstrapped when binding to a service in a different namespace should successfully add binding to the devfile /go/odo_1/tests/integration/interactive_add_binding_test.go:257 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/1091481377 << Captured StdOut/StdErr Output ------------------------------ SS•S•S•S• ------------------------------ • [8.488 seconds] odo add binding interactive command tests when running a deployment should successfully add binding without devfile (custom naming strategy: "{ .name | upper }") /go/odo_1/tests/integration/interactive_add_binding_test.go:463 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/1930614822 << Captured StdOut/StdErr Output ------------------------------ •S••SSS•SS•SS•SS•SSSS•SS••••••••SSS••• ------------------------------ • [10.575 seconds] odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile ("uppercase" as naming strategy) /go/odo_1/tests/integration/interactive_add_binding_test.go:131 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/1028152678 << Captured StdOut/StdErr Output ------------------------------ S•• ------------------------------ • [2.884 seconds] odo deploy interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile successfully even with -v flag /go/odo_1/tests/integration/interactive_deploy_test.go:40 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo deploy -v 4' from /tmp/2065483935 << Captured StdOut/StdErr Output ------------------------------ •••••• ------------------------------ • [8.387 seconds] odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile (custom naming strategy: "") /go/odo_1/tests/integration/interactive_add_binding_test.go:180 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3623671817 << Captured StdOut/StdErr Output ------------------------------ ••••SSS•••••S••••S•SS•S•••S•SS•••SSSS••SS••SS••SSS•S•• ------------------------------ • [7.133 seconds] odo dev interactive command tests directory is not empty when Alizer cannot determine a Devfile based on the current source code should not fail but fallback to the interactive mode /go/odo_1/tests/integration/interactive_dev_test.go:164 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports' from /tmp/1309784055 << Captured StdOut/StdErr Output ------------------------------ ••••SSSSSS•••••••SSS••S•••••SSSSSS•SS••••••S•S•S•••• ------------------------------ • [4.332 seconds] odo deploy interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile /go/odo_1/tests/integration/interactive_deploy_test.go:75 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo deploy' from /tmp/2009849905 << Captured StdOut/StdErr Output ------------------------------ ••S••••S•••S••SS•••SS•S•SS••SSS••SSSSSS•••••••••SS••••••SS•SSSS••S•SS••S••S• ------------------------------ • [19.355 seconds] odo add binding interactive command tests when the component is bootstrapped when binding to a service in a different namespace should error out if service is not found in the namespace selected /go/odo_1/tests/integration/interactive_add_binding_test.go:242 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/2766789477 << Captured StdOut/StdErr Output ------------------------------ S•SS•S•S•S•••SSS•••SSSS•SS••S• ------------------------------ • [5.305 seconds] odo deploy interactive command tests directory is not empty when there is a match from Alizer should display welcoming messages first /go/odo_1/tests/integration/interactive_deploy_test.go:109 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo deploy' from /tmp/3126014781 << Captured StdOut/StdErr Output ------------------------------ • [11.723 seconds] odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile (Bind as Environment Variables) /go/odo_1/tests/integration/interactive_add_binding_test.go:73 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/376522663 << Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [5.139 seconds] odo init interactive command tests when DevfileRegistriesList CRD is installed on cluster when CR for devfileregistrieslists is installed in namespace should download correct devfile from the first in-cluster registry /go/odo_1/tests/integration/interactive_init_test.go:635 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/1447359743 << Captured StdOut/StdErr Output ------------------------------ SSSS•S•S••••••••••••••• Ran 457 of 824 Specs in 1496.268 seconds SUCCESS! -- 457 Passed | 0 Failed | 0 Pending | 367 Skipped Ginkgo ran 1 suite in 26m1.063788782s Test Suite Passed You're using deprecated Ginkgo functionality: ============================================= --slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck. To silence deprecations that can be silenced set the following environment variable: ACK_GINKGO_DEPRECATIONS=2.6.0