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=8b3df06ef" ./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: 1684246753 - will randomize all specs Will run 496 of 888 specs Running in parallel across 16 processes SSSSSSSSSSSSSSSSSSSS••S•SS•S•S••••S•S ------------------------------ • [20.158 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/2958288243 << Captured StdOut/StdErr Output ------------------------------ ••••S•S•••••S•SS•SS•• ------------------------------ • [15.718 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/1990424359 << Captured StdOut/StdErr Output ------------------------------ SSS•••••••S•••SS ------------------------------ • [3.501 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/3880863185 << Captured StdOut/StdErr Output ------------------------------ ••SS•SS•••••SSSS••S•••SSSSS•S•••S•S••••••SSSS••••••••••SS•••S ------------------------------ • [12.265 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/67202039 << Captured StdOut/StdErr Output ------------------------------ •S•SS•••S••S ------------------------------ • [19.030 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/135012012 << Captured StdOut/StdErr Output ------------------------------ •••S•SS••S••SSS••S••SSS•SSSSS•••S••••S ------------------------------ • [5.432 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:712 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/1902509198 << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [9.617 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/469875648 << Captured StdOut/StdErr Output ------------------------------ •SSSSS•••••••S•SS• ------------------------------ • [54.940 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:3470 Captured StdOut/StdErr Output >> PID: 21773 << Captured StdOut/StdErr Output ------------------------------ S•S•••S•SSS•• ------------------------------ • [9.996 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/429334071 << Captured StdOut/StdErr Output ------------------------------ •SS•••SS••••S••SS•SS•S•S•S••••SS•SS•••S•• ------------------------------ • [10.764 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/546722118 << Captured StdOut/StdErr Output ------------------------------ •S•S••SS••SS••S••S•S ------------------------------ • [8.308 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/1179480325 << Captured StdOut/StdErr Output ------------------------------ •SS•S•S•S•SSSS•SSSS••••• ------------------------------ • [8.587 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/111735833 << Captured StdOut/StdErr Output ------------------------------ S•SSS••S••S•SS•SS•S•SS••S•S••SS••S••••S• ------------------------------ • [9.888 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/3595205670 << Captured StdOut/StdErr Output ------------------------------ S•SS•SSSS•S••SS••SS•SS•••S•S••SS••SS•S•••SSS••SSS•SSSSS••••SSS•S••SS•SS•S••S•••••SS•S•SS••S••SS•S••SS•••SS••S••S•SSSS•••• ------------------------------ • [77.620 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/723071182 << Captured StdOut/StdErr Output ------------------------------ ••SS••S•••S•S••SS•SS•SS••S••S••SSS••SS••S••S•• ------------------------------ • [10.070 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/1595952701 << Captured StdOut/StdErr Output ------------------------------ S•S•S•••SS•SSSS••S•••••••SS•SSS•S••SS•SSS•••••SS•S• ------------------------------ • [77.075 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/182607036 << Captured StdOut/StdErr Output ------------------------------ SS•••S•SSS•S•S•••S••S••SS•••S••••S•••••••• ------------------------------ • [8.953 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/2274741622 << Captured StdOut/StdErr Output ------------------------------ SSS•SS•S•SS•SS•••S•••••••SSSSS••S•SS ------------------------------ • [9.425 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/1654254176 << Captured StdOut/StdErr Output ------------------------------ •S••SSS••SSS••• ------------------------------ • [16.524 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/16152858 << Captured StdOut/StdErr Output ------------------------------ •S ------------------------------ • [3.366 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/1111067193 << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [9.574 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/771304684 << Captured StdOut/StdErr Output ------------------------------ ••S•S ------------------------------ • [2.823 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/67884732 << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [10.517 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/96556264 << Captured StdOut/StdErr Output ------------------------------ •S•S•S••SS••SS•S•S••S•SSSS••S•S••S ------------------------------ • [8.468 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/1002610704 << Captured StdOut/StdErr Output ------------------------------ S•••S••S•SS••S•S•S•S•• ------------------------------ • [77.237 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/681676201 << Captured StdOut/StdErr Output ------------------------------ S•••••••S•SS•S••S•S•S• ------------------------------ • [2.622 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/2346045731 << Captured StdOut/StdErr Output ------------------------------ S•S•••S•S•••S•S••SSSS•••• ------------------------------ • [18.063 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/3773775265 << Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [17.190 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/957585841 << Captured StdOut/StdErr Output ------------------------------ SSS• ------------------------------ • [9.397 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/3560639381 << Captured StdOut/StdErr Output ------------------------------ SS•••SS•SS••S••SSS•S•SS•SSS••S••••SSSS•••SSS•S••SSS••S••SS••SSS•S••S••S•• ------------------------------ • [21.757 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/3522426797 << Captured StdOut/StdErr Output ------------------------------ •••••••••••• Ran 491 of 888 Specs in 1625.511 seconds SUCCESS! -- 491 Passed | 0 Failed | 0 Pending | 397 Skipped Ginkgo ran 1 suite in 28m13.774545823s 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.8.0