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=250514951" ./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: 1683785806 - will randomize all specs Will run 495 of 885 specs Running in parallel across 16 processes SSSSSSSSSSSSSSS•SS•S••SSS••S•• ------------------------------ • [24.207 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/1259819683 << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ • [19.015 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/1706386982 << Captured StdOut/StdErr Output ------------------------------ •S••SSS• ------------------------------ • [25.357 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/3234108429 << Captured StdOut/StdErr Output ------------------------------ S•S•••SS•SS••••S••••SS•S•S•S••SSSSSSS•SSSS•SSS•S•S•S•S ------------------------------ • [12.403 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/3764831033 << Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [21.679 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/1461157457 << Captured StdOut/StdErr Output ------------------------------ •SS••SSS•SS••SS•• ------------------------------ • [12.938 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/2470041922 << Captured StdOut/StdErr Output ------------------------------ SSSS•••S•SSS•SS•••••S••••S•S••• ------------------------------ • [10.351 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/317638656 << Captured StdOut/StdErr Output ------------------------------ S•S•••SS•S•SSS•S•S•SSSS•S•••••S•S•••S••SS•S•SSSS••••••SS ------------------------------ • [8.926 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/2616254715 << Captured StdOut/StdErr Output ------------------------------ S•••S••••••SS••SSSS••••SS•SS•S•S•SS•S••S•SS•SS•S• ------------------------------ • [13.701 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/2875660000 << Captured StdOut/StdErr Output ------------------------------ S•••S••••S••S••••SSSSSS••SSSSS••SS•SS ------------------------------ • [15.230 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/1752535286 << Captured StdOut/StdErr Output ------------------------------ •S••S•SS•SSSSS•SS•••S•••S••••S••••SSS ------------------------------ • [3.447 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/3250917373 << Captured StdOut/StdErr Output ------------------------------ •S•SS•S•S••S••SS•••SSS•SS•• ------------------------------ • [11.671 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/2081230327 << Captured StdOut/StdErr Output ------------------------------ S•••S•SSS••SS ------------------------------ • [55.262 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:3427 Captured StdOut/StdErr Output >> PID: 27639 << Captured StdOut/StdErr Output ------------------------------ S•S•S•••••S••••••SSSS•••••S•SSS•••••S•••S•••S•••••••S• ------------------------------ • [11.559 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/3316178702 << Captured StdOut/StdErr Output ------------------------------ •S•S••SS ------------------------------ • [11.548 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/2886345624 << Captured StdOut/StdErr Output ------------------------------ S••••S•••SSS•S••SSS•S•SS ------------------------------ • [12.741 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/1605081764 << Captured StdOut/StdErr Output ------------------------------ SSSS••SS••S•••SSS••••••SS••SS•••SS•••••••SS•SSSS•S•SSS•S•••SSS•••SS•S• ------------------------------ • [22.582 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/150194149 << Captured StdOut/StdErr Output ------------------------------ S•S•S•S•S•••SS•S•••••SS••••S•SSS•••SSS••S•••S•SS••••SS••SSS•SS••SS•S•••SS•SSSS•S•••S••SS••SS•SS•S•S•S ------------------------------ • [3.690 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/3013314566 << Captured StdOut/StdErr Output ------------------------------ S• ------------------------------ • [18.411 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/2215620795 << Captured StdOut/StdErr Output ------------------------------ •S•S•S• ------------------------------ • [10.995 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/656594423 << Captured StdOut/StdErr Output ------------------------------ ••••••S•S ------------------------------ • [82.313 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/2542460228 << Captured StdOut/StdErr Output ------------------------------ •••••••SSS• ------------------------------ • [11.691 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/1443780710 << Captured StdOut/StdErr Output ------------------------------ ••SSS•SS••SS••SSS••S••S•S•• ------------------------------ • [3.298 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/2179720660 << Captured StdOut/StdErr Output ------------------------------ SSS•SS•S•S•SSS••S ------------------------------ • [77.920 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/3908013383 << Captured StdOut/StdErr Output ------------------------------ SSSS••S••••S•S•••S•SS•SSS•S•SSSS•S••S••S ------------------------------ • [22.500 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/3277808034 << Captured StdOut/StdErr Output ------------------------------ S•SS••SSS••S•SS••SS••SS•••S••••S••S••••SS••••SS••••SS•••••SS•S• ------------------------------ • [2.849 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/2348253272 << Captured StdOut/StdErr Output ------------------------------ ••••SS••••S•SS•••SS ------------------------------ • [10.580 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/2942682793 << Captured StdOut/StdErr Output ------------------------------ ••••S•SSS••SS•S••• ------------------------------ • [19.266 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/3091714895 << Captured StdOut/StdErr Output ------------------------------ •SSSS••••••• ------------------------------ • [80.735 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/2597903796 << Captured StdOut/StdErr Output ------------------------------ ••••••• Ran 485 of 885 Specs in 1715.409 seconds SUCCESS! -- 485 Passed | 0 Failed | 0 Pending | 400 Skipped Ginkgo ran 1 suite in 29m42.249615861s 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: 1683787595 - will randomize all specs Will run 4 of 4 specs Running in parallel across 16 processes ------------------------------ • [105.539 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/2602989498 << Captured StdOut/StdErr Output ------------------------------ • [147.918 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/3733444175 Spawning '/go/bin/odo delete component' from /tmp/3733444175 << Captured StdOut/StdErr Output ------------------------------ • [165.521 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/2695470452 << Captured StdOut/StdErr Output ------------------------------ • [247.349 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/1339669780 Spawning '/go/bin/odo delete component' from /tmp/1339669780 << Captured StdOut/StdErr Output ------------------------------ Ran 4 of 4 Specs in 247.364 seconds SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped Ginkgo ran 1 suite in 4m25.162062845s 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