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=e11c63fb6" ./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: 1674839156 - will randomize all specs Will run 411 of 742 specs Running in parallel across 16 processes SSSSSSSSS ------------------------------ S [SKIPPED] [12.316 seconds] odo dev command tests /go/odo_1/tests/integration/cmd_dev_test.go:34 using Kubernetes cluster [BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:2619 should run odo dev successfully on default namespace /go/odo_1/tests/integration/cmd_dev_test.go:2625 Begin Captured GinkgoWriter Output >> Created dir: /tmp/2246042064 Created dir: /tmp/765990250 Setting KUBECONFIG=/tmp/765990250/config Creating a new project: cmd-dev-test2625cgn Running oc with args [oc new-project cmd-dev-test2625cgn] and odo env: [] [oc] Now using project "cmd-dev-test2625cgn" on server "https://c100-e.eu-de.containers.cloud.ibm.com:31988". [oc] [oc] You can add applications to this project with the 'new-app' command. For example, try: [oc] [oc] oc new-app rails-postgresql-example [oc] [oc] to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: [oc] [oc] kubectl create deployment hello-node --image=k8s.gcr.io/serve_hostname [oc] Running oc with args [oc create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n cmd-dev-test2625cgn] and odo env: [] [oc] configmap/config-map-for-cleanup created Current working dir: /go/odo_1/tests/integration Running odo with args [odo preference remove registry DefaultDevfileRegistry -f] and odo env: [] [odo] I0127 17:07:03.169298 11435 implem.go:109] The path for preference file is /tmp/765990250/preference.yaml [odo] I0127 17:07:03.169736 11435 util.go:797] Response will be cached in /tmp/odohttpcache for 1h0m0s [odo] Successfully removed registry [odo] I0127 17:07:03.204179 11435 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :) Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: [] [odo] I0127 17:07:04.707221 11559 implem.go:109] The path for preference file is /tmp/765990250/preference.yaml [odo] New registry successfully added [odo] I0127 17:07:04.755175 11559 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :) Setting current dir to: /tmp/2246042064 Deleting project: cmd-dev-test2625cgn Running oc with args [oc delete project cmd-dev-test2625cgn --wait=false] and odo env: [] [oc] project.project.openshift.io "cmd-dev-test2625cgn" deleted Setting current dir to: /go/odo_1/tests/integration Deleting dir: /tmp/2246042064 Deleting dir: /tmp/765990250 << End Captured GinkgoWriter Output This is a Kubernetes specific scenario, skipping In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:2621 ------------------------------ SSS•SSS••S••SS•SS••••••S ------------------------------ • [23.794 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3488066056 << End Captured StdOut/StdErr Output ------------------------------ ••S•SSS•S•SS•S•SS•••••SS•S•S•S•S•S•••••••••S••SSSS••SSSSS ------------------------------ • [18.309 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3995785814 << End Captured StdOut/StdErr Output ------------------------------ •S••S•••S•SS•S•SS•SSSSSS•SSS•SSSS••SS•• ------------------------------ • [SLOW TEST] [196.261 seconds] odo remove binding command tests when the component with binding is bootstrapped when odo dev is running when binding is removed should have led odo dev to delete ServiceBinding from the cluster /go/odo_1/tests/integration/cmd_remove_binding_test.go:68 ------------------------------ ••••S ------------------------------ • [29.071 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/614301969 << End Captured StdOut/StdErr Output ------------------------------ •S•SSS•S••S ------------------------------ • [22.473 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/1284191625 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [24.873 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3870632935 << End Captured StdOut/StdErr Output ------------------------------ S••••SSS• ------------------------------ • [19.038 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/2322179395 << End Captured StdOut/StdErr Output ------------------------------ S•SS•S•SSS ------------------------------ • [23.287 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/43466787 << End Captured StdOut/StdErr Output ------------------------------ SS•S•S•S••SSS ------------------------------ • [18.442 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/2524016734 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [34.017 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/484543517 << End Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [6.572 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo deploy' from /tmp/1213737068 << End Captured StdOut/StdErr Output ------------------------------ SSSSS•S ------------------------------ • [7.411 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo deploy -v 4' from /tmp/133390265 << End Captured StdOut/StdErr Output ------------------------------ S• ------------------------------ • [20.839 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3745307614 << End Captured StdOut/StdErr Output ------------------------------ S••S••S••SS•S ------------------------------ • [17.366 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/2154799068 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [SLOW TEST] [125.514 seconds] odo add binding command tests when the component is bootstrapped when adding a binding (other namespace) when odo dev is run should successfully bind component and service /go/odo_1/tests/integration/cmd_add_binding_test.go:260 ------------------------------ ••SS•••S•S••SS ------------------------------ • [24.828 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/1493771590 << End Captured StdOut/StdErr Output ------------------------------ •S•S•S•S ------------------------------ • [97.330 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports -v 4' from /tmp/4078572478 << End Captured StdOut/StdErr Output ------------------------------ •S••SS•••S••SSS•S•SS ------------------------------ • [SLOW TEST] [148.648 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "") when Starting a Pg service when running dev session when changing the current namespace should list the binding with --namespace flag /go/odo_1/tests/integration/cmd_describe_list_binding_test.go:626 ------------------------------ ••• ------------------------------ • [18.871 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:194 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports --no-watch' from /tmp/3204014094 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [SLOW TEST] [153.233 seconds] odo dev command tests devfile contains composite apply command the devfile contains an image component that uses a remote Dockerfile when [PODMAN_CMD=echo] remote server returns a valid file when odo dev is run should build and push image when odo dev is run /go/odo_1/tests/integration/cmd_dev_test.go:1721 ------------------------------ S• ------------------------------ • [SLOW TEST] [231.698 seconds] odo dev command tests when java-springboot application is created and running odo dev when Update the devfile.yaml when compare the local and remote files localFiles and remoteFiles should match /go/odo_1/tests/integration/cmd_dev_test.go:2499 ------------------------------ S• ------------------------------ • [16.194 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/2951917851 << End Captured StdOut/StdErr Output ------------------------------ •S•SSSSS• ------------------------------ • [SLOW TEST] [134.604 seconds] odo describe/list binding command tests when creating a component with a spec binding (service in namespace "") when Starting a Pg service when running dev session should list the binding /go/odo_1/tests/integration/cmd_describe_list_binding_test.go:581 ------------------------------ •SS•••S•S•••••S ------------------------------ • [11.850 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:155 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports' from /tmp/2334492876 << End Captured StdOut/StdErr Output ------------------------------ SS••••S••••SS••SSS••S•SSS•••SS••SS•••••••SSS•S••SS•S•S•••••• ------------------------------ • [22.538 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/2990799963 << End Captured StdOut/StdErr Output ------------------------------ ••S•S• ------------------------------ • [SLOW TEST] [140.910 seconds] odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-sze") when Starting a Pg service when running dev session should list the binding /go/odo_1/tests/integration/cmd_describe_list_binding_test.go:581 ------------------------------ •SS•SS•SS•••S•S••SS•S•S• ------------------------------ • [SLOW TEST] [131.161 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "") when Starting a Pg service when running dev session should describe the binding /go/odo_1/tests/integration/cmd_describe_list_binding_test.go:548 ------------------------------ SSSS••S•SS•SSS ------------------------------ • [8.003 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo deploy' from /tmp/3120404020 << End Captured StdOut/StdErr Output ------------------------------ •SSSS••S•• ------------------------------ • [16.535 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/1430287182 << End Captured StdOut/StdErr Output ------------------------------ •S••S•SSS•SSS••S•SSS•••••••••S ------------------------------ • [30.350 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:106 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports' from /tmp/472908979 << End Captured StdOut/StdErr Output ------------------------------ S••SS• ------------------------------ • [SLOW TEST] [123.556 seconds] odo add binding command tests when the component is bootstrapped when adding a binding (other namespace) when odo dev is run when odo dev command is stopped should have successfully delete the binding /go/odo_1/tests/integration/cmd_add_binding_test.go:278 ------------------------------ S••SSS••SS••S ------------------------------ • [SLOW TEST] [152.448 seconds] odo dev command tests when java-springboot application is created and running odo dev when Update the devfile.yaml Should build the application successfully /go/odo_1/tests/integration/cmd_dev_test.go:2444 ------------------------------ S•SSS• ------------------------------ • [5.943 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo deploy' from /tmp/3582835216 << End Captured StdOut/StdErr Output ------------------------------ •••S•S•••S•SS•SS••••SS••S••SS••••SS•S•SS•••••SS•••••S•S••••••S•••S••SS••S•••S••••••••S ------------------------------ • [12.431 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/2062443172 << End Captured StdOut/StdErr Output ------------------------------ •SS••SS••••S•S•SS••S•SSSS•••SS••••SS•• ------------------------------ • [SLOW TEST] [147.520 seconds] odo dev command tests when Starting a PostgreSQL service when creating local files and dir and running odo dev - with metadata.name when deleting local files and dir and waiting for sync should not list deleted dir and file in container /go/odo_1/tests/integration/cmd_dev_test.go:1204 ------------------------------ • [16.842 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/2219166009 << End Captured StdOut/StdErr Output ------------------------------ SS••••SS•S••SS•SS•••S• ------------------------------ • [37.519 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/732391429 << End Captured StdOut/StdErr Output ------------------------------ ••S•SSSS•S•SS•SSSSS•S•SS••••••SSSS•••S••SS•• ------------------------------ • [23.146 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:73 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports' from /tmp/1545024602 << End Captured StdOut/StdErr Output ------------------------------ •SSS•S••SS•SSS•S•••SSSS••S•SS••SSS ------------------------------ • [23.569 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/4151417039 << End Captured StdOut/StdErr Output ------------------------------ S••S•SS•S•SS••••••••••••••• Ran 410 of 742 Specs in 1250.109 seconds SUCCESS! -- 410 Passed | 0 Failed | 0 Pending | 332 Skipped Ginkgo ran 1 suite in 21m53.085958782s Test Suite Passed 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: 1674840476 - will randomize all specs Will run 7 of 7 specs Running in parallel across 16 processes •••• ------------------------------ • [SLOW TEST] [147.009 seconds] E2E Test starting with non-empty Directory should verify developer workflow from non-empty Directory /go/odo_1/tests/e2escenarios/e2e_test.go:180 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/2427667217 Spawning '/go/bin/odo delete component' from /tmp/2427667217 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [153.947 seconds] E2E Test starting with empty Directory should verify developer workflow from empty Directory /go/odo_1/tests/e2escenarios/e2e_test.go:55 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/1461833809 Spawning '/go/bin/odo delete component' from /tmp/1461833809 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [170.307 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:337 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/2526585725 << End Captured StdOut/StdErr Output ------------------------------ Ran 7 of 7 Specs in 170.321 seconds SUCCESS! -- 7 Passed | 0 Failed | 0 Pending | 0 Skipped Ginkgo ran 1 suite in 3m7.019904857s Test Suite Passed