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=d9f25dc60" ./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: 1679401421 - will randomize all specs Will run 435 of 777 specs Running in parallel across 16 processes SSSSSSSSSSSSSSSSSSSS•S•S ------------------------------ • [12.375 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/3041381723 << End Captured StdOut/StdErr Output ------------------------------ ••• ------------------------------ • [23.107 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/2288578713 << End Captured StdOut/StdErr Output ------------------------------ ••S• ------------------------------ S [SKIPPED] [2.470 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/2424906928 Created dir: /tmp/3552293924 Setting KUBECONFIG=/tmp/3552293924/config Creating a new project: cmd-dev-test2632nax Running oc with args [oc new-project cmd-dev-test2632nax] and odo env: [] [oc] Now using project "cmd-dev-test2632nax" 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-test2632nax] 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] I0321 12:25:09.388117 12816 implem.go:110] The path for preference file is /tmp/3552293924/preference.yaml [odo] Successfully removed registry Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: [] [odo] I0321 12:25:09.642242 12829 implem.go:110] The path for preference file is /tmp/3552293924/preference.yaml [odo] New registry successfully added Setting current dir to: /tmp/2424906928 Deleting project: cmd-dev-test2632nax Running oc with args [oc delete project cmd-dev-test2632nax --wait=false] and odo env: [] [oc] project.project.openshift.io "cmd-dev-test2632nax" deleted Setting current dir to: /go/odo_1/tests/integration Deleting dir: /tmp/2424906928 Deleting dir: /tmp/3552293924 << End Captured GinkgoWriter Output This is a Kubernetes specific scenario, skipping In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:2628 ------------------------------ •••SSS•• ------------------------------ • [16.125 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/721007712 << End Captured StdOut/StdErr Output ------------------------------ SS••SS•SSS•SSSSSS••S•SS•• ------------------------------ • [13.562 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/436009186 << End Captured StdOut/StdErr Output ------------------------------ SS•S••• ------------------------------ S [SKIPPED] [4.479 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/2221609296 Created dir: /tmp/3910161795 Setting KUBECONFIG=/tmp/3910161795/config Creating a new project: interactive-init-test600wli Running oc with args [oc new-project interactive-init-test600wli] and odo env: [] [oc] Now using project "interactive-init-test600wli" 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-test600wli] 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] I0321 12:26:03.650305 14398 implem.go:110] The path for preference file is /tmp/3910161795/preference.yaml [odo] Successfully removed registry Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: [] [odo] I0321 12:26:04.402918 14431 implem.go:110] The path for preference file is /tmp/3910161795/preference.yaml [odo] New registry successfully added Setting current dir to: /tmp/2221609296 Deleting project: interactive-init-test600wli Running oc with args [oc delete project interactive-init-test600wli --wait=false] and odo env: [] [oc] project.project.openshift.io "interactive-init-test600wli" deleted Setting current dir to: /go/odo_1/tests/integration Deleting dir: /tmp/2221609296 Deleting dir: /tmp/3910161795 << 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••SS•S•S•S• ------------------------------ S [SKIPPED] [3.050 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/2515499561 Created dir: /tmp/3590139627 Setting KUBECONFIG=/tmp/3590139627/config Creating a new project: cmd-pref-config-test273pqd Running oc with args [oc new-project cmd-pref-config-test273pqd] and odo env: [] [oc] Now using project "cmd-pref-config-test273pqd" 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-test273pqd] 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] I0321 12:26:29.282303 15429 implem.go:110] The path for preference file is /tmp/3590139627/preference.yaml [odo] Successfully removed registry Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: [] [odo] I0321 12:26:29.712126 15454 implem.go:110] The path for preference file is /tmp/3590139627/preference.yaml [odo] New registry successfully added Deleting project: cmd-pref-config-test273pqd Running oc with args [oc delete project cmd-pref-config-test273pqd --wait=false] and odo env: [] [oc] project.project.openshift.io "cmd-pref-config-test273pqd" deleted Setting current dir to: /go/odo_1/tests/integration Deleting dir: /tmp/2515499561 Deleting dir: /tmp/3590139627 << End Captured GinkgoWriter Output skipped on non Kubernetes clusters In [BeforeEach] at: /go/odo_1/tests/integration/cmd_pref_config_test.go:208 ------------------------------ ••S•S••S•S••SSS•SS•S•SS•••S••••••SS ------------------------------ • [15.431 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/3087622401 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [24.181 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/2772103927 << End Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [SLOW TEST] [169.683 seconds] odo remove binding command tests when the component with binding is bootstrapped (bindingName=my-nodejs-app-cluster-sample-ocp) 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•SSS ------------------------------ • [18.176 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/3713719433 << End Captured StdOut/StdErr Output ------------------------------ •S•SS•SS•S ------------------------------ • [17.614 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/1884901531 << End Captured StdOut/StdErr Output ------------------------------ S••S•••S•SSSS••S•S••S• ------------------------------ • [13.237 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/3601570550 << End Captured StdOut/StdErr Output ------------------------------ SSS••SS••S••S••••S•••SS ------------------------------ • [SLOW TEST] [157.697 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-oax") when Starting a Pg service when running dev session should list the binding /go/odo_1/tests/integration/cmd_describe_list_binding_test.go:742 ------------------------------ S•SS•• ------------------------------ • [48.752 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/2305279590 << End Captured StdOut/StdErr Output ------------------------------ S••S•S••S ------------------------------ • [26.588 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/2334869879 << End Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [SLOW TEST] [145.102 seconds] odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "binding-niz") when Starting a Pg service when running dev session should describe the binding /go/odo_1/tests/integration/cmd_describe_list_binding_test.go:701 ------------------------------ • [SLOW TEST] [149.070 seconds] odo dev command tests when devfile has sourcemappings and running odo dev - with metadata.name should sync files to the correct location /go/odo_1/tests/integration/cmd_dev_test.go:1351 ------------------------------ ••S ------------------------------ • [SLOW TEST] [131.964 seconds] odo devfile deploy command tests deploying devfile with exec when using devfile with a long running command in exec should print the tip to run odo logs after 1 minute of execution /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:559 ------------------------------ •S•S•••••S• ------------------------------ • [56.575 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/343802930 << End Captured StdOut/StdErr Output ------------------------------ •S•••S•SS•SS• ------------------------------ • [27.833 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/1222341067 << End Captured StdOut/StdErr Output ------------------------------ S••••••SS••SSS•S•S• ------------------------------ • [6.238 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/1513874513 << End Captured StdOut/StdErr Output ------------------------------ SS•S••SS•SS••S•S•SSS•SS••SSSSSSSS••••••S•S•S•• ------------------------------ S [SKIPPED] [2.546 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/3038722413 Created dir: /tmp/538586931 Setting KUBECONFIG=/tmp/538586931/config Creating a new project: cmd-devfile-registry-test236rpa Running oc with args [oc new-project cmd-devfile-registry-test236rpa] and odo env: [] [oc] Now using project "cmd-devfile-registry-test236rpa" 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-test236rpa] 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] I0321 12:32:58.309613 27670 implem.go:110] The path for preference file is /tmp/538586931/preference.yaml [odo] Successfully removed registry Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: [] [odo] I0321 12:32:58.489023 27682 implem.go:110] The path for preference file is /tmp/538586931/preference.yaml [odo] New registry successfully added Setting current dir to: /tmp/3038722413 Deleting project: cmd-devfile-registry-test236rpa Running oc with args [oc delete project cmd-devfile-registry-test236rpa --wait=false] and odo env: [] [oc] project.project.openshift.io "cmd-devfile-registry-test236rpa" deleted Setting current dir to: /go/odo_1/tests/integration Deleting dir: /tmp/3038722413 Deleting dir: /tmp/538586931 << 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••S••S ------------------------------ • [SLOW TEST] [126.436 seconds] odo dev command tests 1. devfile contains composite apply command when odo dev is running should execute the composite apply commands successfully /go/odo_1/tests/integration/cmd_dev_test.go:1652 ------------------------------ S•SSSS•S•SSSS• ------------------------------ • [SLOW TEST] [130.098 seconds] odo add binding command tests when the component is bootstrapped when adding a binding (current namespace) when odo dev is run should successfully bind component and service /go/odo_1/tests/integration/cmd_add_binding_test.go:260 ------------------------------ •••S••SS•SS•S••SS•SSS•S••S•SSS••••••SSSS•S•••SS•••••S•••S••SS••••SSS•S••••SS••S••SS••• ------------------------------ • [20.147 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/1331689698 << End Captured StdOut/StdErr Output ------------------------------ SSSS•SS••S•••••SS•SS•••SSS••••••••S•SSS•SS•S•S•••••S ------------------------------ • [SLOW TEST] [195.263 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•• ------------------------------ • [SLOW TEST] [123.543 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 [SKIPPED] [2.624 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:570 when CR for devfileregistrieslists is installed in namespace /go/odo_1/tests/integration/cmd_devfile_init_test.go:578 should be able to download devfile from the in-cluster registry /go/odo_1/tests/integration/cmd_devfile_init_test.go:597 Begin Captured GinkgoWriter Output >> Created dir: /tmp/2972802946 Created dir: /tmp/2240760113 Setting KUBECONFIG=/tmp/2240760113/config Creating a new project: cmd-devfile-init-test597lqc Running oc with args [oc new-project cmd-devfile-init-test597lqc] and odo env: [] [oc] Now using project "cmd-devfile-init-test597lqc" 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-test597lqc] 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] I0321 12:37:47.225390 5069 implem.go:110] The path for preference file is /tmp/2240760113/preference.yaml [odo] Successfully removed registry Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: [] [odo] I0321 12:37:47.448686 5090 implem.go:110] The path for preference file is /tmp/2240760113/preference.yaml [odo] New registry successfully added Setting current dir to: /tmp/2972802946 Deleting project: cmd-devfile-init-test597lqc Running oc with args [oc delete project cmd-devfile-init-test597lqc --wait=false] and odo env: [] [oc] project.project.openshift.io "cmd-devfile-init-test597lqc" deleted Setting current dir to: /go/odo_1/tests/integration Deleting dir: /tmp/2972802946 Deleting dir: /tmp/2240760113 << End Captured GinkgoWriter Output skipped on non Kubernetes clusters In [BeforeEach] at: /go/odo_1/tests/integration/cmd_devfile_init_test.go:572 ------------------------------ ••••S•S•SSSSS••S••S•••••SSS ------------------------------ • [SLOW TEST] [121.652 seconds] odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying memoryLimit for container in Devfile should react on the Devfile modification /go/odo_1/tests/integration/cmd_dev_test.go:757 ------------------------------ S•••SSSS•SSSSS••• ------------------------------ S [SKIPPED] [3.179 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/2863017069 Created dir: /tmp/3562450698 Setting KUBECONFIG=/tmp/3562450698/config Creating a new project: cmd-pref-config-test243fnx Running oc with args [oc new-project cmd-pref-config-test243fnx] and odo env: [] [oc] Now using project "cmd-pref-config-test243fnx" 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-test243fnx] 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] I0321 12:38:44.119427 7004 implem.go:110] The path for preference file is /tmp/3562450698/preference.yaml [odo] Successfully removed registry Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: [] [odo] I0321 12:38:44.339170 7017 implem.go:110] The path for preference file is /tmp/3562450698/preference.yaml [odo] New registry successfully added Deleting project: cmd-pref-config-test243fnx Running oc with args [oc delete project cmd-pref-config-test243fnx --wait=false] and odo env: [] [oc] project.project.openshift.io "cmd-pref-config-test243fnx" deleted Setting current dir to: /go/odo_1/tests/integration Deleting dir: /tmp/2863017069 Deleting dir: /tmp/3562450698 << End Captured GinkgoWriter Output skipped on non Kubernetes clusters In [BeforeEach] at: /go/odo_1/tests/integration/cmd_pref_config_test.go:208 ------------------------------ ••••SS•SS• ------------------------------ • [12.731 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/2006962661 << End Captured StdOut/StdErr Output ------------------------------ SS•S• ------------------------------ • [SLOW TEST] [183.470 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••S•S••••S••S• ------------------------------ • [24.089 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/431326908 << End Captured StdOut/StdErr Output ------------------------------ •S ------------------------------ • [15.796 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/1931693517 << End Captured StdOut/StdErr Output ------------------------------ •S•SS••S•SS•••S•S•••••• ------------------------------ • [33.848 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/956639481 << End Captured StdOut/StdErr Output ------------------------------ •SS ------------------------------ • [18.178 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/1454367564 << End Captured StdOut/StdErr Output ------------------------------ •S•SSS• ------------------------------ • [SLOW TEST] [128.636 seconds] odo dev debug command tests when a composite apply command is used as debug command should execute the composite apply commands successfully /go/odo_1/tests/integration/cmd_dev_debug_test.go:243 ------------------------------ • ------------------------------ • [13.513 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/385475231 << End Captured StdOut/StdErr Output ------------------------------ ••SSS ------------------------------ • [13.280 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/3551561111 << End Captured StdOut/StdErr Output ------------------------------ •S•S•S•SS•SS•••S••S•••SSS••S•••S••S•S•••••••SSSSSS ------------------------------ • [12.132 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/3132865236 << End Captured StdOut/StdErr Output ------------------------------ •S• ------------------------------ • [SLOW TEST] [154.966 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 ------------------------------ • [17.238 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/3582954516 << End Captured StdOut/StdErr Output ------------------------------ •S•SSS•SS•SS•S• ------------------------------ • [8.453 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/3567929118 << End Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [18.429 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/3497391349 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [139.553 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 ------------------------------ SS••S ------------------------------ • [SLOW TEST] [157.852 seconds] odo dev command tests when doing odo dev and there is a env variable with spaces - with metadata.name should be able to exec command /go/odo_1/tests/integration/cmd_dev_test.go:1095 ------------------------------ S ------------------------------ • [SLOW TEST] [187.315 seconds] odo dev command tests when running odo dev with devfile containing volume-component - without metadata.name should successfully use the volume components in container components /go/odo_1/tests/integration/cmd_dev_test.go:1613 ------------------------------ • ------------------------------ • [SLOW TEST] [153.212 seconds] odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-xeo") 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:787 ------------------------------ SSS•S•SS•SSS• ------------------------------ • [6.508 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/1593304901 << End Captured StdOut/StdErr Output ------------------------------ S••S••S•S• ------------------------------ • [SLOW TEST] [158.247 seconds] odo dev command tests when a hotReload capable project is used with odo dev should execute the run command /go/odo_1/tests/integration/cmd_dev_test.go:2970 ------------------------------ •S••SS•SSS•SSS•••• ------------------------------ • [15.333 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/3373044602 << End Captured StdOut/StdErr Output ------------------------------ ••••• ------------------------------ • [SLOW TEST] [195.988 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 ------------------------------ •••••• Ran 429 of 777 Specs in 1317.892 seconds SUCCESS! -- 429 Passed | 0 Failed | 0 Pending | 348 Skipped Ginkgo ran 1 suite in 23m1.815463112s 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: 1679402809 - will randomize all specs Will run 7 of 7 specs Running in parallel across 16 processes ••• ------------------------------ • [SLOW TEST] [129.364 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] [143.138 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/2503910704 Spawning '/go/bin/odo delete component' from /tmp/2503910704 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [152.461 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/1677433997 Spawning '/go/bin/odo delete component' from /tmp/1677433997 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [170.836 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/3845799238 << End Captured StdOut/StdErr Output ------------------------------ Ran 7 of 7 Specs in 170.857 seconds SUCCESS! -- 7 Passed | 0 Failed | 0 Pending | 0 Skipped Ginkgo ran 1 suite in 3m8.199730603s Test Suite Passed