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=21614bce8" ./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: 1683819273 - will randomize all specs Will run 495 of 887 specs Running in parallel across 16 processes SSSSSSSSSSS•S ------------------------------ • [10.900 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/2517642113 << Captured StdOut/StdErr Output ------------------------------ •SS•S••• ------------------------------ • [24.352 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/169964315 << Captured StdOut/StdErr Output ------------------------------ S••S••SS•S••SSSS•••S••••SS•S ------------------------------ • [23.996 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/1003508426 << Captured StdOut/StdErr Output ------------------------------ S•SS••••••••SS•••SSS••••••S•S•S•••••••SS•• ------------------------------ • [10.664 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/1640521337 << Captured StdOut/StdErr Output ------------------------------ •S•S••S••SSS•S•SSSSSSS••S•S•S•••S••SSSS•SSS•SS••SSSS•S•S••••SSS•S•••••S•SSS••S••SS•SS•S•S•• ------------------------------ • [12.820 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/661103236 << Captured StdOut/StdErr Output ------------------------------ SSS•S ------------------------------ • [2.938 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/717859866 << Captured StdOut/StdErr Output ------------------------------ ••S•SSS•••S•SS•S••S•S•••S••S ------------------------------ • [12.702 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/2005537819 << Captured StdOut/StdErr Output ------------------------------ •S•S•S•S•S•••S•• ------------------------------ • [82.376 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/987048152 << Captured StdOut/StdErr Output ------------------------------ •SSS••S•SSSS•SSS•S•S••••S•S••S•SSS•SSS••S•S••SS•S ------------------------------ • [18.234 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/689795219 << Captured StdOut/StdErr Output ------------------------------ S••S•••SS•••S• ------------------------------ • [12.106 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/3720908295 << Captured StdOut/StdErr Output ------------------------------ S•SSSS•SS••S•SSSSS•SS• ------------------------------ • [3.062 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/3955152938 << Captured StdOut/StdErr Output ------------------------------ •••••SS•S•S••SSSS••• ------------------------------ • [8.521 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/1298693847 << Captured StdOut/StdErr Output ------------------------------ SS••S•S•S ------------------------------ • [12.450 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/4147161190 << Captured StdOut/StdErr Output ------------------------------ •S••• ------------------------------ • [14.947 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/3546370510 << Captured StdOut/StdErr Output ------------------------------ •S•••S•SS•S•••••••••S•S ------------------------------ • [13.887 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/1053052165 << Captured StdOut/StdErr Output ------------------------------ •SS••••S•••S•S•••SS•S•••S•S•••SSSSS••S•SS•SSSS••S•••S•S••SS••S••S••••S ------------------------------ • [55.767 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: 32410 << Captured StdOut/StdErr Output ------------------------------ •••••S•SS••S•S•SSSSS•SS•S•••• ------------------------------ • [14.522 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/3775885157 << Captured StdOut/StdErr Output ------------------------------ ••SS ------------------------------ • [3.097 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/3523354771 << Captured StdOut/StdErr Output ------------------------------ •S•SS•S••S••SS••SSS•SS•SS•S••S••••SSS•S••••S•SS•SSS•SSS••••S• ------------------------------ • [78.944 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/3851070019 << Captured StdOut/StdErr Output ------------------------------ SS••SS•S••S••SS•SS•SS•S ------------------------------ • [10.728 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/1932583735 << Captured StdOut/StdErr Output ------------------------------ ••S•S•S••••S•S•SS•S•••SS••S•S•S••S••SSSS••S••SSS••••SS•SS•SS••S•••••S•SS•••S•SSSS•••SS ------------------------------ • [79.550 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/2788809599 << Captured StdOut/StdErr Output ------------------------------ S•••SSS•SS••SS••S•SS••SS••SS•S• ------------------------------ • [12.417 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/1047950165 << Captured StdOut/StdErr Output ------------------------------ ••••SS•••SS•S••SS•••••S•••SS•S••••SS••SS••SS•S•SS• ------------------------------ • [11.201 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/3802923621 << Captured StdOut/StdErr Output ------------------------------ SSSS••••SSS•••SS ------------------------------ • [21.880 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/1025429824 << Captured StdOut/StdErr Output ------------------------------ •SSSS•••• ------------------------------ • [28.481 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/1476398333 << Captured StdOut/StdErr Output ------------------------------ SS•S• ------------------------------ • [29.852 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/213457194 << Captured StdOut/StdErr Output ------------------------------ S••••S••SSS•S•••SSSS•SS•SSS•••S ------------------------------ • [21.710 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/1571853122 << Captured StdOut/StdErr Output ------------------------------ S•SS•S•S•S•• ------------------------------ • [12.862 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/3177813685 << Captured StdOut/StdErr Output ------------------------------ SSSS•S•SS••SS• ------------------------------ • [10.702 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/2573609040 << Captured StdOut/StdErr Output ------------------------------ •SS••SS•••••••••S••SSSSSSS•S•••••••••••••••• Ran 485 of 887 Specs in 1756.662 seconds SUCCESS! -- 485 Passed | 0 Failed | 0 Pending | 402 Skipped Ginkgo ran 1 suite in 30m23.604471905s 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: 1683821104 - will randomize all specs Will run 4 of 4 specs Running in parallel across 16 processes ------------------------------ • [105.420 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/1390897206 << Captured StdOut/StdErr Output ------------------------------ • [116.717 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/1018113090 << Captured StdOut/StdErr Output ------------------------------ • [149.364 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/1139733146 Spawning '/go/bin/odo delete component' from /tmp/1139733146 << Captured StdOut/StdErr Output ------------------------------ • [258.167 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/3330915199 Spawning '/go/bin/odo delete component' from /tmp/3330915199 << Captured StdOut/StdErr Output ------------------------------ Ran 4 of 4 Specs in 258.178 seconds SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped Ginkgo ran 1 suite in 4m35.688419633s 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