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=9918103dd" ./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: 1683705092 - will randomize all specs Will run 495 of 885 specs Running in parallel across 16 processes SSSSSSSSSSSSSSSSSSS•SSS••SS ------------------------------ • [5.050 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/183884113 << Captured StdOut/StdErr Output ------------------------------ SS•S•S ------------------------------ • [8.479 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/3206248683 << Captured StdOut/StdErr Output ------------------------------ •S••S••••••• ------------------------------ • [9.352 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/3121763631 << Captured StdOut/StdErr Output ------------------------------ ••SS• ------------------------------ • [9.768 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/791413846 << Captured StdOut/StdErr Output ------------------------------ S•SSS•• ------------------------------ • [82.036 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/1645503722 << Captured StdOut/StdErr Output ------------------------------ S•S ------------------------------ • [16.810 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/1541419505 << Captured StdOut/StdErr Output ------------------------------ ••••••SSS••S••S•SS•S••SSSS•••S•S••S ------------------------------ • [3.503 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/4067558996 << Captured StdOut/StdErr Output ------------------------------ ••••S•S•••S ------------------------------ • [18.486 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/540193831 << Captured StdOut/StdErr Output ------------------------------ ••S•S••••SSS••••S•S•••SSS•••S•S•S••••S••S ------------------------------ • [7.671 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/3200446445 << Captured StdOut/StdErr Output ------------------------------ S••••S•SS•••S•S•••••••S•S•••••••••••SS•••SS•SS•SSS•SSS••S•SSS••••S••S••S••SSS•S••S•S•SSSS••SS•••SS•S••S••S••SSS•SSSS•S••SS••••••SS•S•SS•SSSSS•SSSS•S ------------------------------ • [80.902 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/2422099801 << Captured StdOut/StdErr Output ------------------------------ •••••SS•S•SSS••• ------------------------------ • [55.244 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:3427 Captured StdOut/StdErr Output >> PID: 28035 << Captured StdOut/StdErr Output ------------------------------ •••••• ------------------------------ • [11.298 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/4271591466 << Captured StdOut/StdErr Output ------------------------------ SS•••S•S••SS•S•S•S••• ------------------------------ • [9.688 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/1500102846 << Captured StdOut/StdErr Output ------------------------------ •SS••SSS•S•SSS•SS••S•S•SS••SS••S•S••S••S•••S•S•S•S•S•••SS•S•• ------------------------------ • [10.001 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/2767092935 << Captured StdOut/StdErr Output ------------------------------ ••SS••S•SS•SS•••• ------------------------------ • [4.870 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/3832027203 << Captured StdOut/StdErr Output ------------------------------ • [12.947 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/468932831 << Captured StdOut/StdErr Output ------------------------------ S••S•S• ------------------------------ • [22.761 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/2686414964 << Captured StdOut/StdErr Output ------------------------------ S• ------------------------------ • [12.282 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/1064977783 << Captured StdOut/StdErr Output ------------------------------ •••S•S•S•SS•SS••S••SS•S•S ------------------------------ • [9.136 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/264160674 << Captured StdOut/StdErr Output ------------------------------ ••S• ------------------------------ • [9.017 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/2357441131 << Captured StdOut/StdErr Output ------------------------------ •S•SSSS••••SS•S•S•S••S••••••S• ------------------------------ • [15.893 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/3945956805 << Captured StdOut/StdErr Output ------------------------------ •S•••S••S•SS••••S•SSS••SSS ------------------------------ • [9.912 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/3344222758 << Captured StdOut/StdErr Output ------------------------------ SSSSS•••••SS•SS•SS••S••••••S••S•S••S•••S••S••SSS•••SS•S•SSSS•S• ------------------------------ • [3.183 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/2269428299 << Captured StdOut/StdErr Output ------------------------------ ••S•SSS•S•S•S•••SS•SSS•SSSS••••S•••SS•SSS••S•SS••S••••SS••S ------------------------------ • [17.991 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/1575830394 << Captured StdOut/StdErr Output ------------------------------ S•SS••S• ------------------------------ • [11.455 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/356309324 << Captured StdOut/StdErr Output ------------------------------ •S•••SS•• ------------------------------ • [9.862 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/3755662744 << Captured StdOut/StdErr Output ------------------------------ SS••S••SSSS•S•S•SS•SSS•••SS•SS ------------------------------ • [5.774 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/2088282696 << Captured StdOut/StdErr Output ------------------------------ S••S•SS•S• ------------------------------ • [79.526 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/529544463 << Captured StdOut/StdErr Output ------------------------------ •S•••S ------------------------------ • [8.813 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/3184115573 << Captured StdOut/StdErr Output ------------------------------ S•SS••SSS••SSS•SS•SS•S••S••••SSSSS ------------------------------ • [12.571 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/2446935282 << Captured StdOut/StdErr Output ------------------------------ S•••SSS•S•••S•S•S•S••S••S••••••S•S•SS••SSS•SS•S•S•••••SSSSS•••SSS•S•SSSS•S•••SSSS•••SS•SSSS•S••••S••S•••S•S••SS••••••••••••••• Ran 490 of 885 Specs in 1645.726 seconds SUCCESS! -- 490 Passed | 0 Failed | 0 Pending | 395 Skipped Ginkgo ran 1 suite in 28m30.643706558s 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