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=0690c747e" ./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: 1683316879 - will randomize all specs Will run 495 of 885 specs Running in parallel across 16 processes SSSSSSSSSSSSSSSSSSSSSSSS••S•SSSSS•••• ------------------------------ • [24.826 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/900202967 << Captured StdOut/StdErr Output ------------------------------ SS••S•S•S•SSSSS•S•SS ------------------------------ • [40.615 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/494930166 << Captured StdOut/StdErr Output ------------------------------ •••S•••SS•••••••SSS•S••S•• ------------------------------ • [15.300 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/3434150982 << Captured StdOut/StdErr Output ------------------------------ S•SSSS••••SSSSSS••S••S••••••••SSS• ------------------------------ • [18.718 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/2632471899 << Captured StdOut/StdErr Output ------------------------------ S•S••S•S•••••S•• ------------------------------ • [54.337 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:3437 Captured StdOut/StdErr Output >> PID: 17765 << Captured StdOut/StdErr Output ------------------------------ ••SSSS•SS••••••SS•SS• ------------------------------ • [11.811 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/752778103 << Captured StdOut/StdErr Output ------------------------------ SSSSSSS••S•S•S•••S• ------------------------------ • [11.094 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/412399538 << Captured StdOut/StdErr Output ------------------------------ •S•SS•••S••S••S••S••SS•SSSSS• ------------------------------ • [2.833 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/1340840913 << Captured StdOut/StdErr Output ------------------------------ ••S•S••SS•S••SS•S••••SS•••••••S••••••S•SS•S•S•••S••S• ------------------------------ • [3.473 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/1437084709 << Captured StdOut/StdErr Output ------------------------------ • [19.308 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/3015880916 << Captured StdOut/StdErr Output ------------------------------ SSSS••S••••••••S ------------------------------ • [8.782 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/2829592806 << Captured StdOut/StdErr Output ------------------------------ •SS•S•SSS••S••••••SSS•SS•••••S•S•••S•••••••SSS•••SSS•SS•SS••SS•S••••S• ------------------------------ • [7.943 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/962567328 << Captured StdOut/StdErr Output ------------------------------ ••••SS•S•S••SS•SSS•SS••••SSS•SS••S•S•••S•••••••••••S••SSSSSS••SSS•SSS•• ------------------------------ • [3.561 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/1573932931 << Captured StdOut/StdErr Output ------------------------------ SS••S••SSS•••S••S•• ------------------------------ • [8.878 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/254640274 << Captured StdOut/StdErr Output ------------------------------ S•• ------------------------------ • [9.944 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/168122567 << Captured StdOut/StdErr Output ------------------------------ ••S••••S•••••••S•SSS•SS ------------------------------ • [77.758 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/3426104704 << Captured StdOut/StdErr Output ------------------------------ S•S ------------------------------ • [12.173 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/3896737192 << Captured StdOut/StdErr Output ------------------------------ •SS•SSS••S•••S•SS•S•SS••SSS••S•S••••S•SSSSS•••S•S••SSS•SS•SSS••S•S ------------------------------ • [8.738 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/263992497 << Captured StdOut/StdErr Output ------------------------------ S••S•S ------------------------------ • [9.208 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/191264907 << Captured StdOut/StdErr Output ------------------------------ S••SSS••••SS•S•S•S•SSS ------------------------------ • [10.661 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/3085838893 << Captured StdOut/StdErr Output ------------------------------ •S•SSSSSS•SS•• ------------------------------ • [77.906 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/919898591 << Captured StdOut/StdErr Output ------------------------------ S•••SS•S•••••SS•••SS•••S••S•S•••S••S••S•••S•SS•• ------------------------------ • [4.819 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/3453638101 << Captured StdOut/StdErr Output ------------------------------ S••S•S••S•••S•S•S••••S••S••SSSSS••SSS••SS•••SS••SS•••SS••S•SS••S•S•SS•SS••S•S•S•S•S••S•SSSS•••S••••••S•SSS•S•SSSSSSS ------------------------------ • [9.323 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/279444658 << Captured StdOut/StdErr Output ------------------------------ S••S••SS•SS•S• ------------------------------ • [23.955 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/1030441843 << Captured StdOut/StdErr Output ------------------------------ •S ------------------------------ • [13.372 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/1024230993 << Captured StdOut/StdErr Output ------------------------------ SS•S•SSSS••S••S•S•SS•SS•••••SS• ------------------------------ • [11.218 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/1059987528 << Captured StdOut/StdErr Output ------------------------------ SS••SS•S••S•••••SS•S••••SSS•S•S ------------------------------ • [11.582 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/3598069931 << Captured StdOut/StdErr Output ------------------------------ S••••S•S••••SS•SS••SSS ------------------------------ • [10.457 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/1443377574 << Captured StdOut/StdErr Output ------------------------------ •••• ------------------------------ • [3.052 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/510253212 << Captured StdOut/StdErr Output ------------------------------ S•S•S•••••••• ------------------------------ • [79.135 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/299385179 << Captured StdOut/StdErr Output ------------------------------ •••••• Ran 490 of 885 Specs in 1606.341 seconds SUCCESS! -- 490 Passed | 0 Failed | 0 Pending | 395 Skipped Ginkgo ran 1 suite in 27m49.66258266s 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