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=eb575c862" ./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: 1684753488 - will randomize all specs Will run 497 of 890 specs Running in parallel across 16 processes SSSSSSSSSSSSSSSSSSSS•••SS••••SS•• ------------------------------ • [7.963 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/1155756309 << Captured StdOut/StdErr Output ------------------------------ SS•S ------------------------------ • [17.293 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/524973213 << Captured StdOut/StdErr Output ------------------------------ •S•S•••••S••SS•S••••S••S•S•S•••SSS•SSS•••S••SS•SSS•• ------------------------------ • [55.950 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:3471 Captured StdOut/StdErr Output >> PID: 15955 << Captured StdOut/StdErr Output ------------------------------ SSSS•SS• ------------------------------ • [19.425 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/658562176 << Captured StdOut/StdErr Output ------------------------------ •SS••S••S•SSSS•••S•••••S•S•• ------------------------------ • [4.444 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/3516021580 << Captured StdOut/StdErr Output ------------------------------ •••• ------------------------------ • [16.036 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/2929969092 << Captured StdOut/StdErr Output ------------------------------ S••SS••••••S••SSS•SS••SS••••S••S••SS•SS•S•••••• ------------------------------ • [13.717 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/3025300491 << Captured StdOut/StdErr Output ------------------------------ ••••S•S•SS•SSSS•SS•• ------------------------------ • [10.614 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/2461042655 << Captured StdOut/StdErr Output ------------------------------ S•••••SSS••S••S•S••S•••SS•SSSS•S•SSSS•S•S•S• ------------------------------ • [24.027 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/981888758 << Captured StdOut/StdErr Output ------------------------------ SS••S•SS•SSSS••••S•SS•SS•S•••SS•S•••S••S•S••S ------------------------------ • [11.089 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/1069345115 << Captured StdOut/StdErr Output ------------------------------ S••SS•••S•SSS•SS••SSSS••••••S•••S•S•S ------------------------------ • [12.316 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/1600685706 << Captured StdOut/StdErr Output ------------------------------ SSS••••S••SS•S•••S•S• ------------------------------ • [9.033 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/3818618171 << Captured StdOut/StdErr Output ------------------------------ S•S••••••SS•••SSSS•S•SSSS•••S•SS•••SS•SS•SS ------------------------------ • [10.185 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/789697728 << Captured StdOut/StdErr Output ------------------------------ ••S•S•S•S•••• ------------------------------ • [10.152 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/1702253644 << Captured StdOut/StdErr Output ------------------------------ •SS••••SS••• ------------------------------ • [11.846 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/1376641765 << Captured StdOut/StdErr Output ------------------------------ ••SSS•S•SS•S•••SS•S•SS• ------------------------------ • [13.583 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/3355873400 << Captured StdOut/StdErr Output ------------------------------ ••SSSSSS••SSS•••S••SSS•SS•S•••S•SS••••SS••S•SS•SS••S•••••SSS•••SS•SSS•S•S••••••••SSSS••••SSS•S•S•SSSS•S ------------------------------ • [3.030 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/1705015127 << Captured StdOut/StdErr Output ------------------------------ SSS•••S•S•••SSS••SS•••SS•SSS•SS••SSSS••SS••S•••S••S•SS ------------------------------ • [3.096 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/2285287311 << Captured StdOut/StdErr Output ------------------------------ •S•SSS•••S•••S•S• ------------------------------ • [7.488 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/4109195663 << Captured StdOut/StdErr Output ------------------------------ •••S•SS••••••S••••SSSS••S•S•S••SSS ------------------------------ • [8.802 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/3939687319 << Captured StdOut/StdErr Output ------------------------------ •SS••S••SSS•S••SSS•S•S ------------------------------ • [80.922 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/4171800022 << Captured StdOut/StdErr Output ------------------------------ ••••• ------------------------------ • [3.666 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/2194898494 << Captured StdOut/StdErr Output ------------------------------ S•SSS•S• ------------------------------ • [19.863 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/2708871200 << Captured StdOut/StdErr Output ------------------------------ •••S•••••SSSS••SSS• ------------------------------ • [18.393 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/310100043 << Captured StdOut/StdErr Output ------------------------------ •••S•••SSS•S•S••SS••• ------------------------------ • [78.033 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/3057136835 << Captured StdOut/StdErr Output ------------------------------ ••S••SSSS••••••S•SS•••SS••S•S•S•••SSS•• ------------------------------ • [18.344 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/3348670646 << Captured StdOut/StdErr Output ------------------------------ •SSS••S•S•••••S ------------------------------ • [14.028 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/3683373682 << Captured StdOut/StdErr Output ------------------------------ S•••SSSSSSS•S• ------------------------------ • [11.020 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/2471601511 << Captured StdOut/StdErr Output ------------------------------ S•S••SS•S••S••••S•S•S•SS••S•SS••SS•••SSS••SS•••S•S•SS•S ------------------------------ • [79.558 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/4111168465 << Captured StdOut/StdErr Output ------------------------------ •S ------------------------------ • [14.041 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/1081865210 << Captured StdOut/StdErr Output ------------------------------ •S•••••••••••••••• Ran 492 of 890 Specs in 1621.562 seconds SUCCESS! -- 492 Passed | 0 Failed | 0 Pending | 398 Skipped Ginkgo ran 1 suite in 28m5.382340239s 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