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=f72a8cf00" ./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: 1678817185 - will randomize all specs Will run 435 of 779 specs Running in parallel across 16 processes SSSSSSSSSSSSSS••SS•S•••SSS••S••S••SSSSS•••S•••••S•SSS••SS•SS••••S••••••S•S•S•••S ------------------------------ • [13.608 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/578644862 << End Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [16.862 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/4036547104 << End Captured StdOut/StdErr Output ------------------------------ ••S•••••S•SS•S••SS•S•S•••• ------------------------------ • [11.730 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/2681079181 << End Captured StdOut/StdErr Output ------------------------------ SSSS•S•SS••• ------------------------------ • [SLOW TEST] [147.278 seconds] odo dev command tests when Starting a PostgreSQL service when creating local files and dir and running odo dev - without 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:1229 ------------------------------ ••S•SS••SSSS••SS ------------------------------ • [25.637 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/3561713414 << End Captured StdOut/StdErr Output ------------------------------ •S•••SS••S••SSSS ------------------------------ • [9.611 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/1019184884 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [8.693 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/1321475491 << End Captured StdOut/StdErr Output ------------------------------ ••S•••S•• ------------------------------ S [SKIPPED] [2.944 seconds] odo devfile init command tests /go/odo_1/tests/integration/cmd_devfile_init_test.go:24 when DevfileRegistriesList CRD is installed on cluster [BeforeEach] /go/odo_1/tests/integration/cmd_devfile_init_test.go:581 when CR for devfileregistrieslists is installed in namespace /go/odo_1/tests/integration/cmd_devfile_init_test.go:589 should be able to download devfile from the in-cluster registry /go/odo_1/tests/integration/cmd_devfile_init_test.go:608 Begin Captured GinkgoWriter Output >> Created dir: /tmp/874372759 Created dir: /tmp/3293394898 Setting KUBECONFIG=/tmp/3293394898/config Creating a new project: cmd-devfile-init-test608rcu Running oc with args [oc new-project cmd-devfile-init-test608rcu] and odo env: [] [oc] Now using project "cmd-devfile-init-test608rcu" 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/e2e-test-images/agnhost:2.33 -- /agnhost serve-hostname [oc] Running oc with args [oc create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n cmd-devfile-init-test608rcu] 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] I0314 18:11:26.956018 20084 implem.go:110] The path for preference file is /tmp/3293394898/preference.yaml [odo] Successfully removed registry Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: [] [odo] I0314 18:11:27.397284 20103 implem.go:110] The path for preference file is /tmp/3293394898/preference.yaml [odo] New registry successfully added Setting current dir to: /tmp/874372759 Deleting project: cmd-devfile-init-test608rcu Running oc with args [oc delete project cmd-devfile-init-test608rcu --wait=false] and odo env: [] [oc] project.project.openshift.io "cmd-devfile-init-test608rcu" deleted Setting current dir to: /go/odo_1/tests/integration Deleting dir: /tmp/874372759 Deleting dir: /tmp/3293394898 << End Captured GinkgoWriter Output skipped on non Kubernetes clusters In [BeforeEach] at: /go/odo_1/tests/integration/cmd_devfile_init_test.go:583 ------------------------------ •S••••••••• ------------------------------ • [11.897 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/1961147516 << End Captured StdOut/StdErr Output ------------------------------ S••S••SSSS••SSS ------------------------------ • [SLOW TEST] [192.460 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:1229 ------------------------------ • ------------------------------ • [13.292 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/4075271765 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [6.447 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/1604230340 << End Captured StdOut/StdErr Output ------------------------------ S•••S•SSSSSS••SSS••SS••SS•S••SS•SSS•S••SSS•SS••• ------------------------------ • [SLOW TEST] [167.390 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:2510 ------------------------------ S•SS•SSSS•SS••SSSS• ------------------------------ • [25.338 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports' from /tmp/365151787 << End Captured StdOut/StdErr Output ------------------------------ SS• ------------------------------ S [SKIPPED] [2.849 seconds] odo preference and config command tests /go/odo_1/tests/integration/cmd_pref_config_test.go:17 when DevfileRegistriesList CRD is installed on cluster [BeforeEach] /go/odo_1/tests/integration/cmd_pref_config_test.go:206 when CR for devfileregistrieslists is installed in namespace /go/odo_1/tests/integration/cmd_pref_config_test.go:218 should fail to delete the in-cluster registry /go/odo_1/tests/integration/cmd_pref_config_test.go:273 Begin Captured GinkgoWriter Output >> Created dir: /tmp/3035699035 Created dir: /tmp/2013433475 Setting KUBECONFIG=/tmp/2013433475/config Creating a new project: cmd-pref-config-test273nxn Running oc with args [oc new-project cmd-pref-config-test273nxn] and odo env: [] [oc] Now using project "cmd-pref-config-test273nxn" 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/e2e-test-images/agnhost:2.33 -- /agnhost serve-hostname [oc] Running oc with args [oc create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n cmd-pref-config-test273nxn] 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] I0314 18:13:45.309740 24825 implem.go:110] The path for preference file is /tmp/2013433475/preference.yaml [odo] Successfully removed registry Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: [] [odo] I0314 18:13:45.608456 24847 implem.go:110] The path for preference file is /tmp/2013433475/preference.yaml [odo] New registry successfully added Deleting project: cmd-pref-config-test273nxn Running oc with args [oc delete project cmd-pref-config-test273nxn --wait=false] and odo env: [] [oc] project.project.openshift.io "cmd-pref-config-test273nxn" deleted Setting current dir to: /go/odo_1/tests/integration Deleting dir: /tmp/3035699035 Deleting dir: /tmp/2013433475 << End Captured GinkgoWriter Output skipped on non Kubernetes clusters In [BeforeEach] at: /go/odo_1/tests/integration/cmd_pref_config_test.go:208 ------------------------------ •S••SSS•SS••SS••SSS•S•••S•S••S ------------------------------ • [10.476 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/698440745 << End Captured StdOut/StdErr Output ------------------------------ S••SS•SSSS••SS•S ------------------------------ • [13.050 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/87078816 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ S [SKIPPED] [2.405 seconds] odo preference and config command tests /go/odo_1/tests/integration/cmd_pref_config_test.go:17 when DevfileRegistriesList CRD is installed on cluster [BeforeEach] /go/odo_1/tests/integration/cmd_pref_config_test.go:206 when CR for devfileregistrieslists is installed in namespace /go/odo_1/tests/integration/cmd_pref_config_test.go:218 registry list should return registry listed in CR /go/odo_1/tests/integration/cmd_pref_config_test.go:243 Begin Captured GinkgoWriter Output >> Created dir: /tmp/764846938 Created dir: /tmp/4196500174 Setting KUBECONFIG=/tmp/4196500174/config Creating a new project: cmd-pref-config-test243ysh Running oc with args [oc new-project cmd-pref-config-test243ysh] and odo env: [] [oc] Now using project "cmd-pref-config-test243ysh" 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/e2e-test-images/agnhost:2.33 -- /agnhost serve-hostname [oc] Running oc with args [oc create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n cmd-pref-config-test243ysh] 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] I0314 18:14:41.410433 27044 implem.go:110] The path for preference file is /tmp/4196500174/preference.yaml [odo] Successfully removed registry Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: [] [odo] I0314 18:14:41.638863 27057 implem.go:110] The path for preference file is /tmp/4196500174/preference.yaml [odo] New registry successfully added Deleting project: cmd-pref-config-test243ysh Running oc with args [oc delete project cmd-pref-config-test243ysh --wait=false] and odo env: [] [oc] project.project.openshift.io "cmd-pref-config-test243ysh" deleted Setting current dir to: /go/odo_1/tests/integration Deleting dir: /tmp/764846938 Deleting dir: /tmp/4196500174 << End Captured GinkgoWriter Output skipped on non Kubernetes clusters In [BeforeEach] at: /go/odo_1/tests/integration/cmd_pref_config_test.go:208 ------------------------------ SSSS••S•SSSSSS• ------------------------------ • [23.100 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports' from /tmp/2119846293 << End Captured StdOut/StdErr Output ------------------------------ •••SS•SS•SS••SSSSSS•SS•S••S•S ------------------------------ • [22.136 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/1679426743 << End Captured StdOut/StdErr Output ------------------------------ •S•SSS•S••••S•S•• ------------------------------ S [SKIPPED] [4.625 seconds] odo devfile registry command tests /go/odo_1/tests/integration/cmd_devfile_registry_test.go:15 when DevfileRegistriesList CRD is installed on cluster [BeforeEach] /go/odo_1/tests/integration/cmd_devfile_registry_test.go:208 when CR for devfileregistrieslists is installed in namespace /go/odo_1/tests/integration/cmd_devfile_registry_test.go:217 should list detailed information regarding nodejs when using an in-cluster registry /go/odo_1/tests/integration/cmd_devfile_registry_test.go:236 Begin Captured GinkgoWriter Output >> Created dir: /tmp/1140677010 Created dir: /tmp/1606986540 Setting KUBECONFIG=/tmp/1606986540/config Creating a new project: cmd-devfile-registry-test236yqh Running oc with args [oc new-project cmd-devfile-registry-test236yqh] and odo env: [] [oc] Now using project "cmd-devfile-registry-test236yqh" 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/e2e-test-images/agnhost:2.33 -- /agnhost serve-hostname [oc] Running oc with args [oc create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n cmd-devfile-registry-test236yqh] 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] I0314 18:15:46.151181 29270 implem.go:110] The path for preference file is /tmp/1606986540/preference.yaml [odo] Successfully removed registry Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: [] [odo] I0314 18:15:46.666339 29290 implem.go:110] The path for preference file is /tmp/1606986540/preference.yaml [odo] New registry successfully added Setting current dir to: /tmp/1140677010 Deleting project: cmd-devfile-registry-test236yqh Running oc with args [oc delete project cmd-devfile-registry-test236yqh --wait=false] and odo env: [] [oc] project.project.openshift.io "cmd-devfile-registry-test236yqh" deleted Setting current dir to: /go/odo_1/tests/integration Deleting dir: /tmp/1140677010 Deleting dir: /tmp/1606986540 << End Captured GinkgoWriter Output skipped on non Kubernetes clusters In [BeforeEach] at: /go/odo_1/tests/integration/cmd_devfile_registry_test.go:210 ------------------------------ S•••S ------------------------------ • [20.015 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/1776327368 << End Captured StdOut/StdErr Output ------------------------------ S•S ------------------------------ • [14.147 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports' from /tmp/822974181 << End Captured StdOut/StdErr Output ------------------------------ ••S•S•SSSS••S••• ------------------------------ • [26.834 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/852569875 << End Captured StdOut/StdErr Output ------------------------------ S•S•S••S•••S•••S• ------------------------------ • [25.146 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/3971573740 << End Captured StdOut/StdErr Output ------------------------------ •S•••••SSSS•SS••••SS•SSSS••••S••••S•S•S•SS•••S• ------------------------------ S [SKIPPED] [3.761 seconds] odo init interactive command tests /go/odo_1/tests/integration/interactive_init_test.go:26 when DevfileRegistriesList CRD is installed on cluster [BeforeEach] /go/odo_1/tests/integration/interactive_init_test.go:571 when CR for devfileregistrieslists is installed in namespace /go/odo_1/tests/integration/interactive_init_test.go:579 should download correct devfile from the first in-cluster registry /go/odo_1/tests/integration/interactive_init_test.go:600 Begin Captured GinkgoWriter Output >> Created dir: /tmp/3777477596 Created dir: /tmp/2034419090 Setting KUBECONFIG=/tmp/2034419090/config Creating a new project: interactive-init-test600vcj Running oc with args [oc new-project interactive-init-test600vcj] and odo env: [] [oc] Now using project "interactive-init-test600vcj" 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/e2e-test-images/agnhost:2.33 -- /agnhost serve-hostname [oc] Running oc with args [oc create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n interactive-init-test600vcj] 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] I0314 18:18:01.131623 1551 implem.go:110] The path for preference file is /tmp/2034419090/preference.yaml [odo] Successfully removed registry Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: [] [odo] I0314 18:18:01.651672 1576 implem.go:110] The path for preference file is /tmp/2034419090/preference.yaml [odo] New registry successfully added Setting current dir to: /tmp/3777477596 Deleting project: interactive-init-test600vcj Running oc with args [oc delete project interactive-init-test600vcj --wait=false] and odo env: [] [oc] project.project.openshift.io "interactive-init-test600vcj" deleted Setting current dir to: /go/odo_1/tests/integration Deleting dir: /tmp/3777477596 Deleting dir: /tmp/2034419090 << End Captured GinkgoWriter Output skipped on non Kubernetes clusters In [BeforeEach] at: /go/odo_1/tests/integration/interactive_init_test.go:573 ------------------------------ S•S••S••••••••SSSS•••••S•S ------------------------------ • [18.474 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/33571150 << End Captured StdOut/StdErr Output ------------------------------ •••••SSSS•S•••S••SS•S••SS••S•S•••SSS•S••S•••••••SSSS••S•••SSS••S••••SS•••S•S•SS•S••SS•••S••••SS•SSSS•SSSSSS ------------------------------ • [SLOW TEST] [121.311 seconds] odo dev command tests when a component is bootstrapped and pushed ensure that index information is updated /go/odo_1/tests/integration/cmd_dev_test.go:109 ------------------------------ •S•••SSS ------------------------------ • [6.284 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/3112629340 << End Captured StdOut/StdErr Output ------------------------------ SS•••SSS•S•• ------------------------------ • [14.120 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/4225165198 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [172.694 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:2455 ------------------------------ ••••••S••••S••S•S••S ------------------------------ S [SKIPPED] [4.567 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:2626 should run odo dev successfully on default namespace /go/odo_1/tests/integration/cmd_dev_test.go:2632 Begin Captured GinkgoWriter Output >> Created dir: /tmp/1584916588 Created dir: /tmp/3252914279 Setting KUBECONFIG=/tmp/3252914279/config Creating a new project: cmd-dev-test2632kwm Running oc with args [oc new-project cmd-dev-test2632kwm] and odo env: [] [oc] Now using project "cmd-dev-test2632kwm" 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/e2e-test-images/agnhost:2.33 -- /agnhost 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-test2632kwm] 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] I0314 18:23:03.795059 11126 implem.go:110] The path for preference file is /tmp/3252914279/preference.yaml [odo] Successfully removed registry Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: [] [odo] I0314 18:23:04.327781 11211 implem.go:110] The path for preference file is /tmp/3252914279/preference.yaml [odo] New registry successfully added Setting current dir to: /tmp/1584916588 Deleting project: cmd-dev-test2632kwm Running oc with args [oc delete project cmd-dev-test2632kwm --wait=false] and odo env: [] [oc] project.project.openshift.io "cmd-dev-test2632kwm" deleted Setting current dir to: /go/odo_1/tests/integration Deleting dir: /tmp/1584916588 Deleting dir: /tmp/3252914279 << End Captured GinkgoWriter Output This is a Kubernetes specific scenario, skipping In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:2628 ------------------------------ • ------------------------------ • [19.915 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 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports --no-watch' from /tmp/1646728744 << End Captured StdOut/StdErr Output ------------------------------ ••SS••••SSS ------------------------------ • [12.022 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/161578574 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [191.128 seconds] odo remove binding command tests when the component with binding is bootstrapped (bindingName=my-nodejs-app-cluster-sample-k8s) 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:71 ------------------------------ SS••S•SS•••S•SSSSS ------------------------------ • [6.885 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/2559455115 << End Captured StdOut/StdErr Output ------------------------------ •S••S••••S•S••S•••SS ------------------------------ • [11.243 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/115294135 << End Captured StdOut/StdErr Output ------------------------------ SS•SSS•••S•SS ------------------------------ • [10.170 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/75587771 << End Captured StdOut/StdErr Output ------------------------------ S•S•S•S••SS••S• ------------------------------ • [11.896 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/3218147382 << End Captured StdOut/StdErr Output ------------------------------ •SS•S• ------------------------------ • [18.695 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/4222779965 << End Captured StdOut/StdErr Output ------------------------------ •S•S••S•••••••••••••••• ------------------------------ • [SLOW TEST] [155.726 seconds] odo dev command tests when a hotReload capable project is used with odo dev when a source file is modified should not re-execute the run command /go/odo_1/tests/integration/cmd_dev_test.go:2982 ------------------------------ • Ran 429 of 779 Specs in 1165.168 seconds SUCCESS! -- 429 Passed | 0 Failed | 0 Pending | 350 Skipped Ginkgo ran 1 suite in 20m27.310776213s 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: 1678818419 - will randomize all specs Will run 7 of 7 specs Running in parallel across 16 processes ••• ------------------------------ • [SLOW TEST] [130.265 seconds] odo devfile supported tests odo debug support for devfile components Verify output debug information for java-quarkus debug works /go/odo_1/tests/e2escenarios/e2e_devfile_test.go:74 ------------------------------ • [SLOW TEST] [144.459 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/1442551154 Spawning '/go/bin/odo delete component' from /tmp/1442551154 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [151.630 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/2579353202 Spawning '/go/bin/odo delete component' from /tmp/2579353202 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [169.490 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/706091314 << End Captured StdOut/StdErr Output ------------------------------ Ran 7 of 7 Specs in 169.671 seconds SUCCESS! -- 7 Passed | 0 Failed | 0 Pending | 0 Skipped Ginkgo ran 1 suite in 3m6.119842393s Test Suite Passed