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: 1684119833 - will randomize all specs Will run 496 of 888 specs Running in parallel across 16 processes SSSSSSSSSSSSSSSSSSSSSSSSSSSS•SS••S•••••S•••S ------------------------------ • [23.340 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/943954962 << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [24.391 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/161259535 << Captured StdOut/StdErr Output ------------------------------ SSSSS• ------------------------------ • [20.368 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/1633735376 << Captured StdOut/StdErr Output ------------------------------ S•••S•SS••S ------------------------------ • [22.316 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/2993691980 << Captured StdOut/StdErr Output ------------------------------ •S ------------------------------ • [18.016 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/3986977984 << Captured StdOut/StdErr Output ------------------------------ •S••SSS•S••S••SSS•S•SSSS••S•SSS••S•••S••SSSS•••••SSS•S•S••SS•SS•S••SSSS•••••S•• ------------------------------ • [10.585 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/1859030482 << Captured StdOut/StdErr Output ------------------------------ •••S ------------------------------ • [56.120 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: 17731 << Captured StdOut/StdErr Output ------------------------------ • [7.163 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/1554929163 << Captured StdOut/StdErr Output ------------------------------ •S•S•S••SS•S•S•SSSS••••S•••SS•• ------------------------------ • [80.391 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/1960069629 << Captured StdOut/StdErr Output ------------------------------ S•••••SSSSSS•S•••••SS•SS•S••S•SSS••SSS•••• ------------------------------ • [11.384 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/1661332471 << Captured StdOut/StdErr Output ------------------------------ S•S• ------------------------------ • [20.024 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/2498212841 << Captured StdOut/StdErr Output ------------------------------ •S•S••SSS•S•S••••S•S••S••SS ------------------------------ • [10.174 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/2856325215 << Captured StdOut/StdErr Output ------------------------------ •SS••S••••SSS•S•SS•SS•SS••SS••SS•S•S••SS•SS ------------------------------ • [18.854 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/1104746643 << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [11.920 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/1645004055 << Captured StdOut/StdErr Output ------------------------------ •S••SS•SS••SSS•••SSSSS•SSS•• ------------------------------ • [15.883 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/3341497588 << Captured StdOut/StdErr Output ------------------------------ •S•SSSS•S••••S ------------------------------ • [10.437 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/2291875514 << Captured StdOut/StdErr Output ------------------------------ S••S ------------------------------ • [11.557 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/536036825 << Captured StdOut/StdErr Output ------------------------------ SS• ------------------------------ • [10.178 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/1028971811 << Captured StdOut/StdErr Output ------------------------------ ••SS••S••••••SSSSSS••S•S••• ------------------------------ • [84.026 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/459284417 << Captured StdOut/StdErr Output ------------------------------ ••S• ------------------------------ • [11.869 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/1787919492 << Captured StdOut/StdErr Output ------------------------------ SSS••SS•SSS•S••••SS•SS••S••••••S•SS••SS••SS•••S•S••••SSS•SS ------------------------------ • [3.646 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/492249988 << Captured StdOut/StdErr Output ------------------------------ SS•••S•••••SS••S••••••S•S ------------------------------ • [2.804 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/208464551 << Captured StdOut/StdErr Output ------------------------------ ••••S••••••S•S•SSS•••••SSSS••••S•SSS• ------------------------------ • [2.835 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/1965723898 << Captured StdOut/StdErr Output ------------------------------ •S•S•S••••••S•••S••••••••• ------------------------------ • [11.291 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/4129663238 << Captured StdOut/StdErr Output ------------------------------ ••SSSSS• ------------------------------ • [10.623 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/207256865 << Captured StdOut/StdErr Output ------------------------------ S•S•SS•••SSS••••S•SS•SSS•••••S•S•S••S•••S••••••S•S••S••S•SS••••SS•••••S•S••SSSS••S•••••S• ------------------------------ • [11.339 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/3328807549 << Captured StdOut/StdErr Output ------------------------------ S•••S••S••S••••SS•S•••SS•SS•SSS•S•••SS•S••••••S•S•S••S•S•SS•S•S•S•S•SSS•••••SS•S•••S•S•SSSSSSSS•SS••S•S•S•S ------------------------------ • [10.760 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/2949753246 << Captured StdOut/StdErr Output ------------------------------ SS• ------------------------------ • [80.126 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/3686574080 << Captured StdOut/StdErr Output ------------------------------ •S••SSSSSSSSSS•••S•S•••••••S•S••••S••SS•SS•••SSSS••SSS•••S•SS•S•S•SSSS••SS••S•SS••S• ------------------------------ • [2.545 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/2172158175 << Captured StdOut/StdErr Output ------------------------------ •S••••SSSS••SSSS••••SSSS••S•••••••••••••••• Ran 486 of 888 Specs in 1720.579 seconds SUCCESS! -- 486 Passed | 0 Failed | 0 Pending | 402 Skipped Ginkgo ran 1 suite in 2h6m13.404854338s 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 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-e2e.xml" tests/e2escenarios Running Suite: odo e2e scenarios - /go/odo_1/tests/e2escenarios =============================================================== Random Seed: 1684127413 - will randomize all specs Will run 4 of 4 specs Running in parallel across 16 processes ------------------------------ • [104.999 seconds] E2E Test starting with non-empty Directory test debugging should verify developer workflow from non-empty Directory /go/odo_1/tests/e2escenarios/e2e_test.go:329 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/2173770693 << Captured StdOut/StdErr Output ------------------------------ • [116.811 seconds] E2E Test starting with non-empty Directory add Binding should verify developer workflow of using binding as env in innerloop /go/odo_1/tests/e2escenarios/e2e_test.go:462 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/1745900865 << Captured StdOut/StdErr Output ------------------------------ • [148.724 seconds] E2E Test starting with empty Directory should verify developer workflow from empty Directory /go/odo_1/tests/e2escenarios/e2e_test.go:63 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/67412379 Spawning '/go/bin/odo delete component' from /tmp/67412379 << Captured StdOut/StdErr Output ------------------------------ • [246.908 seconds] E2E Test starting with non-empty Directory should verify developer workflow from non-empty Directory /go/odo_1/tests/e2escenarios/e2e_test.go:197 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/2448007475 Spawning '/go/bin/odo delete component' from /tmp/2448007475 << Captured StdOut/StdErr Output ------------------------------ Ran 4 of 4 Specs in 246.914 seconds SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped Ginkgo ran 1 suite in 4m23.004108003s 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