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=e98f98b8d" ./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: 1684119836 - will randomize all specs Will run 496 of 888 specs Running in parallel across 16 processes SSSSSSS•••••S••SS•S ------------------------------ • [4.230 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/3128229790 << Captured StdOut/StdErr Output ------------------------------ S•SSSS••••S••S••SSSSSS•S•SS•SSS••••SSSSS ------------------------------ • [81.639 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/2303093207 << Captured StdOut/StdErr Output ------------------------------ S••S•••S•S•SS••S•S•S•S••S•••S•SS ------------------------------ • [77.769 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/1075842954 << Captured StdOut/StdErr Output ------------------------------ •••SSSSSS•S•SS••S••S•••SSSS•SS•SSSSSS•• ------------------------------ • [10.046 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/2971878636 << Captured StdOut/StdErr Output ------------------------------ •••S•S•S•S• ------------------------------ • [78.197 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/2882216979 << Captured StdOut/StdErr Output ------------------------------ SS• ------------------------------ • [2.825 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/1179391483 << Captured StdOut/StdErr Output ------------------------------ S••S•••S•SS•S•S ------------------------------ • [9.758 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/2478338834 << Captured StdOut/StdErr Output ------------------------------ S•SS••••S•S•S•• ------------------------------ • [3.949 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/3625535184 << Captured StdOut/StdErr Output ------------------------------ •S• ------------------------------ • [10.883 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/1549894713 << Captured StdOut/StdErr Output ------------------------------ S••••S•SSS•S•••SS•S••SSS•••S••••SS•••S ------------------------------ • [12.298 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/2483544604 << Captured StdOut/StdErr Output ------------------------------ ••S ------------------------------ • [13.596 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/2765965221 << Captured StdOut/StdErr Output ------------------------------ ••••••SS•••S•SSSS•SS•SSSS•S••S••S•SSSS•S••S••S•••S•••S•••SS•S ------------------------------ • [19.985 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/223894983 << Captured StdOut/StdErr Output ------------------------------ •S••S•••S•S••SSS••SSSS••S•••S•SS•S•••••••S•S•• ------------------------------ • [10.935 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/3620575422 << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [55.159 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:3467 Captured StdOut/StdErr Output >> PID: 28120 << Captured StdOut/StdErr Output ------------------------------ •SSSS••SSSS•S•S•S•S ------------------------------ • [3.320 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/1222318849 << Captured StdOut/StdErr Output ------------------------------ S•• ------------------------------ • [9.006 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/3039241923 << Captured StdOut/StdErr Output ------------------------------ S•••••SSSSS•S•S••SSS••SSS•SS••••SS•SS•S•S•SS ------------------------------ • [8.572 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/957315525 << Captured StdOut/StdErr Output ------------------------------ •S•S•••••S••S ------------------------------ • [9.547 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/2296646370 << Captured StdOut/StdErr Output ------------------------------ S•S••••S•SS•••••SS•SSS••SS•SS•S••••••SS•S••••S••S•••••SS•SS•SS•SSS••SS ------------------------------ • [15.733 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/3733203956 << Captured StdOut/StdErr Output ------------------------------ S•S•SS••S•S•••SS•S•SS••S•S•SSS•S•SS•S ------------------------------ • [12.840 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/2591813762 << Captured StdOut/StdErr Output ------------------------------ •••S ------------------------------ • [14.998 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/1959867000 << Captured StdOut/StdErr Output ------------------------------ •SS•SSSS••SS•SSSSS••S•S•••SSSSS•••S•S•S••••SS•SS• ------------------------------ • [2.735 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/3379361445 << Captured StdOut/StdErr Output ------------------------------ •SS•S•SS••SSS••••SSS••S••S ------------------------------ • [8.458 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/2347891519 << Captured StdOut/StdErr Output ------------------------------ ••S•••••S••SSSS•SS•S•SSS•S•••S••••••••SSSSS•S••S ------------------------------ • [11.332 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/392226322 << Captured StdOut/StdErr Output ------------------------------ SS•••S•SS•• ------------------------------ • [14.395 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/3377106915 << Captured StdOut/StdErr Output ------------------------------ •SS•S••S•S•SS ------------------------------ • [11.549 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/1062850236 << Captured StdOut/StdErr Output ------------------------------ ••S•••S•••SS•S•SSS•S•••S••••SS••••••••••S••SS••••SS•••S•••SS•••S••••S•••S•SS•S••S•SSSS•S••S•••S•• ------------------------------ • [12.936 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/3253271598 << Captured StdOut/StdErr Output ------------------------------ • [22.310 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/3278680517 << Captured StdOut/StdErr Output ------------------------------ SSSS••••S•SS•S•••S•SS•SSS•S••• ------------------------------ • [17.198 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/974201199 << Captured StdOut/StdErr Output ------------------------------ •SS•S••S•S•••SS•••S•S••S•S•S••••S•S••SSSSS•S••SS•SS•S ------------------------------ • [17.834 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/3553524453 << Captured StdOut/StdErr Output ------------------------------ •••••••••••••• Ran 491 of 888 Specs in 1700.275 seconds SUCCESS! -- 491 Passed | 0 Failed | 0 Pending | 397 Skipped Ginkgo ran 1 suite in 2h19m11.840991884s 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