Using Devfile proxy: 07e90e30-eu-de.lb.appdomain.cloud go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=6e50b8f58" ./cmd/odo/ go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo --randomize-all --slow-spec-threshold=120s -timeout 14400s --no-color -nodes=32 tests/integration Running Suite: Integration Suite - /go/odo_1/tests/integration ============================================================== Random Seed: 1663077593 - will randomize all specs Will run 386 of 386 specs Running in parallel across 32 processes • ------------------------------ • [14.422 seconds] odo init interactive command tests should ask to re-enter the component name when an invalid value is passed /go/odo_1/tests/integration/interactive_init_test.go:68 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/4041367196 << End Captured StdOut/StdErr Output ------------------------------ ••• ------------------------------ • [33.835 seconds] odo deploy interactive command tests when directory is not empty should run alizer to download devfile successfully even with -v flag /go/odo_1/tests/integration/interactive_deploy_test.go:39 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo deploy -v 4' from /tmp/3051278627 << End Captured StdOut/StdErr Output ------------------------------ •••••••••••••••••• ------------------------------ • [79.907 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:376 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3631833241 << End Captured StdOut/StdErr Output ------------------------------ • [82.636 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:309 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3124955676 << End Captured StdOut/StdErr Output ------------------------------ ••• ------------------------------ • [11.885 seconds] odo init interactive command tests should download correct devfile /go/odo_1/tests/integration/interactive_init_test.go:95 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/3550333213 << End Captured StdOut/StdErr Output ------------------------------ ••••••• ------------------------------ • [116.028 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:588 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3066770167 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [42.283 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:376 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3676354461 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [SLOW TEST] [130.257 seconds] odo dev command tests when running odo dev and composite command is used as a run command - without metadata.name should run successfully /go/odo_1/tests/integration/cmd_dev_test.go:1640 ------------------------------ •• ------------------------------ • [SLOW TEST] [131.217 seconds] odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose two endpoints on localhost /go/odo_1/tests/integration/cmd_dev_test.go:572 ------------------------------ • [SLOW TEST] [127.639 seconds] odo logs command tests when component is created and odo logs is executed when running in both Dev and Deploy mode should successfully show logs of the running component /go/odo_1/tests/integration/cmd_logs_test.go:189 ------------------------------ •• ------------------------------ • [SLOW TEST] [128.504 seconds] odo list with devfile when a component created in 'app' application verifying the managedBy Version in the odo list output should show managedBy Version /go/odo_1/tests/integration/cmd_devfile_list_test.go:124 ------------------------------ • ------------------------------ • [SLOW TEST] [132.726 seconds] odo dev command tests when adding local files to gitignore and running odo dev when modifying /testdir/baz.txt file should synchronize it only /go/odo_1/tests/integration/cmd_dev_test.go:1040 ------------------------------ •• ------------------------------ • [33.529 seconds] odo dev interactive command tests when directory is not empty should run alizer to download devfile /go/odo_1/tests/integration/interactive_dev_test.go:70 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports' from /tmp/590345801 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [SLOW TEST] [129.104 seconds] odo describe/list binding command tests when creating a component with a spec binding and envvars (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 ------------------------------ ••• ------------------------------ • [25.923 seconds] odo deploy interactive command tests when directory is not empty should display welcoming messages first /go/odo_1/tests/integration/interactive_deploy_test.go:103 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo deploy' from /tmp/4148051992 << End Captured StdOut/StdErr Output ------------------------------ ••••• ------------------------------ • [52.330 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:130 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/362966288 << End Captured StdOut/StdErr Output ------------------------------ ••••••••• ------------------------------ • [SLOW TEST] [152.991 seconds] odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-yms") 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 ------------------------------ •• ------------------------------ • [SLOW TEST] [185.126 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 expose the endpoint on localhost /go/odo_1/tests/integration/cmd_dev_test.go:524 ------------------------------ • [SLOW TEST] [209.167 seconds] odo dev command tests when node-js application is created and deployed with devfile schema 2.2.0 when Update the devfile.yaml, and waiting synchronization should check cpuLimit, cpuRequests, memoryRequests after restart /go/odo_1/tests/integration/cmd_dev_test.go:2214 ------------------------------ • ------------------------------ • [SLOW TEST] [172.487 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:174 ------------------------------ • ------------------------------ • [SLOW TEST] [130.422 seconds] odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-sxl") 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 ------------------------------ •••••••••••••• ------------------------------ • [SLOW TEST] [130.940 seconds] odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "binding-hwx") 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 ------------------------------ • ------------------------------ • [SLOW TEST] [142.489 seconds] odo describe/list binding command tests when creating a component with a binding as files (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 ------------------------------ • [SLOW TEST] [270.136 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-yut") 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 ------------------------------ • [SLOW TEST] [125.614 seconds] odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev when an endpoint is added after first run of odo dev should expose three endpoints on localhost /go/odo_1/tests/integration/cmd_dev_test.go:644 ------------------------------ • [14.775 seconds] odo init interactive command tests displaying welcoming messages when directory is empty should display appropriate welcoming messages /go/odo_1/tests/integration/interactive_init_test.go:184 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/749175707 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [147.970 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 list the binding /go/odo_1/tests/integration/cmd_describe_list_binding_test.go:581 ------------------------------ • [SLOW TEST] [150.650 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 ------------------------------ •••• ------------------------------ • [SLOW TEST] [142.209 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 list the binding /go/odo_1/tests/integration/cmd_describe_list_binding_test.go:581 ------------------------------ • [SLOW TEST] [127.097 seconds] odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "binding-sdp") 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 ------------------------------ •••••••• ------------------------------ • [SLOW TEST] [165.288 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:271 ------------------------------ ••••• ------------------------------ • [SLOW TEST] [128.575 seconds] odo dev debug command tests when a composite command is used as debug command - without metadata.name should run successfully /go/odo_1/tests/integration/cmd_dev_debug_test.go:109 ------------------------------ • [SLOW TEST] [138.253 seconds] odo dev debug command tests when running build and debug commands as composite in different containers and a shared volume - without metadata.name should run successfully /go/odo_1/tests/integration/cmd_dev_debug_test.go:266 ------------------------------ •• ------------------------------ • [45.504 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:461 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/127108197 << End Captured StdOut/StdErr Output ------------------------------ ••••• ------------------------------ • [SLOW TEST] [128.483 seconds] odo logs command tests when component is created and odo logs is executed when running in both Dev and Deploy mode when --follow flag is specified should successfully follow logs of running component /go/odo_1/tests/integration/cmd_logs_test.go:217 ------------------------------ ••• ------------------------------ • [47.670 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:154 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports --no-watch' from /tmp/4184328136 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [21.200 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:461 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/171469414 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [160.275 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 expose the endpoint on localhost /go/odo_1/tests/integration/cmd_dev_test.go:524 ------------------------------ •• ------------------------------ • [SLOW TEST] [163.597 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:253 ------------------------------ ••• ------------------------------ • [24.614 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:72 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/1494145853 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [SLOW TEST] [127.878 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 describe the binding /go/odo_1/tests/integration/cmd_describe_list_binding_test.go:548 ------------------------------ ••••••••••••••••• ------------------------------ • [6.582 seconds] odo init interactive command tests should not fail when using -v flag /go/odo_1/tests/integration/interactive_init_test.go:40 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init -v 4' from /tmp/632799127 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [8.203 seconds] odo init interactive command tests displaying welcoming messages when directory is not empty should display appropriate welcoming messages /go/odo_1/tests/integration/interactive_init_test.go:220 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/3428800979 << End Captured StdOut/StdErr Output ------------------------------ • [42.055 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:179 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3494299791 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [SLOW TEST] [130.133 seconds] odo dev command tests when running build and run commands as composite in different containers and a shared volume - with metadata.name should run successfully /go/odo_1/tests/integration/cmd_dev_test.go:1705 ------------------------------ • ------------------------------ • [SLOW TEST] [135.116 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-lfk") 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 ------------------------------ •••••••• ------------------------------ • [SLOW TEST] [125.806 seconds] odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-ueo") 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 ------------------------------ •••••••••• ------------------------------ S [SKIPPED] [15.590 seconds] odo dev command tests /go/odo_1/tests/integration/cmd_dev_test.go:30 using Kubernetes cluster [BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:2252 should run odo dev successfully on default namespace /go/odo_1/tests/integration/cmd_dev_test.go:2258 Begin Captured GinkgoWriter Output >> Created dir: /tmp/1086312045 Created dir: /tmp/457561727 Setting KUBECONFIG=/tmp/457561727/config Creating a new project: cmd-dev-test2258dtp Running oc with args [oc new-project cmd-dev-test2258dtp] [oc] Now using project "cmd-dev-test2258dtp" on server "https://c113-e.eu-de.containers.cloud.ibm.com:30152". [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-test2258dtp] [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] [odo] I0913 14:08:36.616490 25810 implem.go:106] The path for preference file is /tmp/457561727/preference.yaml [odo] Successfully removed registry [odo] I0913 14:08:36.618957 25810 odo.go:75] Could not get the latest release information in time. Never mind, exiting gracefully :) Running odo with args [odo preference add registry DefaultDevfileRegistry http://07e90e30-eu-de.lb.appdomain.cloud] [odo] I0913 14:08:38.627455 25898 implem.go:106] The path for preference file is /tmp/457561727/preference.yaml [odo] New registry successfully added [odo] I0913 14:08:38.629529 25898 odo.go:75] Could not get the latest release information in time. Never mind, exiting gracefully :) Setting current dir to: /tmp/1086312045 Deleting project: cmd-dev-test2258dtp Running odo with args [odo delete project cmd-dev-test2258dtp -f --wait=false] [odo] I0913 14:08:40.830698 25966 util.go:767] Cached response used. [odo] I0913 14:08:40.890170 25966 util.go:188] path /tmp/1086312045/devfile.yaml doesn't exist, skipping it [odo] I0913 14:08:40.890263 25966 util.go:188] path /tmp/1086312045/.devfile.yaml doesn't exist, skipping it [odo] I0913 14:08:41.299097 25966 component.go:82] name of component is "1086312045", and sanitized name is "x1086312045" [odo] I0913 14:08:41.299461 25966 kclient.go:207] Checking if "projects" resource is supported [odo] ✓ Project "cmd-dev-test2258dtp" deleted [odo] I0913 14:08:41.374761 25966 odo.go:75] Could not get the latest release information in time. Never mind, exiting gracefully :) Setting current dir to: /go/odo_1/tests/integration Deleting dir: /tmp/1086312045 Deleting dir: /tmp/457561727 << End Captured GinkgoWriter Output This is a Kubernetes specific scenario, skipping In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:2254 ------------------------------ • [SLOW TEST] [196.426 seconds] odo describe/list binding command tests when creating a component with a spec binding and envvars (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 ------------------------------ • [SLOW TEST] [168.896 seconds] odo list with devfile devfile has missing metadata when projectType is missing when the component is pushed in dev mode should show the language for 'Type' in odo list /go/odo_1/tests/integration/cmd_devfile_list_test.go:220 ------------------------------ • [20.457 seconds] odo deploy interactive command tests when directory is not empty should run alizer to download devfile /go/odo_1/tests/integration/interactive_deploy_test.go:71 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo deploy' from /tmp/3028516832 << End Captured StdOut/StdErr Output ------------------------------ ••••••••••••••••• ------------------------------ • [12.749 seconds] odo init interactive command tests should start downloading starter project only after all interactive questions have been asked /go/odo_1/tests/integration/interactive_init_test.go:337 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/2720967432 << End Captured StdOut/StdErr Output ------------------------------ •••••• ------------------------------ • [37.512 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:179 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/2884296134 << End Captured StdOut/StdErr Output ------------------------------ ••••• ------------------------------ • [10.273 seconds] odo init interactive command tests displaying welcoming messages when alizer detection of javascript name should ask to re-enter the component name if invalid value is passed by the user /go/odo_1/tests/integration/interactive_init_test.go:300 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/749478314 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [SLOW TEST] [123.886 seconds] odo dev command tests 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:904 ------------------------------ • [37.365 seconds] odo dev interactive command tests when directory is not empty should display welcoming messages first /go/odo_1/tests/integration/interactive_dev_test.go:101 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports' from /tmp/2344639132 << End Captured StdOut/StdErr Output ------------------------------ •••••• ------------------------------ • [SLOW TEST] [127.174 seconds] odo dev command tests when running build and run commands as composite in different containers and a shared volume - without metadata.name should run successfully /go/odo_1/tests/integration/cmd_dev_test.go:1705 ------------------------------ ••• ------------------------------ • [SLOW TEST] [139.120 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 when changing the current namespace should list the binding with --namespace flag /go/odo_1/tests/integration/cmd_describe_list_binding_test.go:626 ------------------------------ ••• ------------------------------ • [SLOW TEST] [124.609 seconds] odo dev command tests when a component is bootstrapped and pushed when odo dev is executed and Ephemeral is set to false when killing odo dev and running odo delete component --wait should have deleted all resources before returning /go/odo_1/tests/integration/cmd_dev_test.go:290 ------------------------------ • ------------------------------ • [SLOW TEST] [191.686 seconds] odo describe/list binding command tests when creating a component with a spec binding and envvars (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 ------------------------------ ••• ------------------------------ • [50.329 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:179 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/2534791420 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [SLOW TEST] [125.624 seconds] odo dev command tests 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:1360 ------------------------------ •• ------------------------------ • [SLOW TEST] [126.131 seconds] odo dev command tests when adding local files to gitignore and running odo dev when modifying /testdir/baz.txt file should synchronize it only /go/odo_1/tests/integration/cmd_dev_test.go:1040 ------------------------------ • ------------------------------ • [SLOW TEST] [243.611 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:2103 ------------------------------ •••••••••••••••••••••• ------------------------------ • [57.111 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:376 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/921874370 << End Captured StdOut/StdErr Output ------------------------------ ••• ------------------------------ • [SLOW TEST] [149.600 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:972 ------------------------------ •• ------------------------------ • [SLOW TEST] [130.359 seconds] odo dev command tests when Starting a PostgreSQL service when creating local files and dir and running odo dev - without metadata.name should correctly propagate changes to the container /go/odo_1/tests/integration/cmd_dev_test.go:955 ------------------------------ •• ------------------------------ • [SLOW TEST] [121.073 seconds] odo describe/list binding command tests when creating a component with a spec binding (service in namespace "binding-yms") 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 ------------------------------ • [45.180 seconds] odo dev interactive command tests when directory is not empty should run alizer to download devfile successfully even with -v flag /go/odo_1/tests/integration/interactive_dev_test.go:39 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports -v 4' from /tmp/3299762572 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [153.980 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:972 ------------------------------ • ------------------------------ • [56.984 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:100 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/2177403908 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [132.650 seconds] odo dev debug command tests when running build and debug commands as composite in different containers and a shared volume - with metadata.name should run successfully /go/odo_1/tests/integration/cmd_dev_debug_test.go:266 ------------------------------ ••••••• ------------------------------ • [SLOW TEST] [143.277 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:2520 ------------------------------ •• ------------------------------ • [SLOW TEST] [151.212 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:2532 ------------------------------ ••• ------------------------------ • [12.634 seconds] odo init interactive command tests displaying welcoming messages when alizer detection of javascript name should display node-echo name /go/odo_1/tests/integration/interactive_init_test.go:266 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/3343776714 << End Captured StdOut/StdErr Output ------------------------------ •••••••• ------------------------------ • [60.105 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:130 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/1961954507 << End Captured StdOut/StdErr Output ------------------------------ ••••• ------------------------------ • [115.062 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:240 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3390134471 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [152.100 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-kou") 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 ------------------------------ ••••• ------------------------------ • [SLOW TEST] [120.437 seconds] odo dev command tests when running odo dev with devfile contain volume - with metadata.name should create pvc and reuse if it shares the same devfile volume name /go/odo_1/tests/integration/cmd_dev_test.go:1255 ------------------------------ • ------------------------------ • [SLOW TEST] [127.312 seconds] odo dev command tests when running odo dev with alternative commands - without metadata.name should execute the custom non-default build and run commands successfully /go/odo_1/tests/integration/cmd_dev_test.go:2048 ------------------------------ ••••••• ------------------------------ • [99.466 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:255 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3516664056 << End Captured StdOut/StdErr Output ------------------------------ ••••• ------------------------------ • [110.917 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:574 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/4135281410 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [SLOW TEST] [231.484 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-hjr") 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 ------------------------------ ••• ------------------------------ • [SLOW TEST] [123.940 seconds] odo dev debug command tests when a composite command is used as debug command - with metadata.name should run successfully /go/odo_1/tests/integration/cmd_dev_debug_test.go:109 ------------------------------ • [SLOW TEST] [141.842 seconds] odo list with devfile when a component created in 'app' application show an odo deploy or dev in the list /go/odo_1/tests/integration/cmd_devfile_list_test.go:136 ------------------------------ •• ------------------------------ • [SLOW TEST] [178.043 seconds] odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-pmx") 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 ------------------------------ • [SLOW TEST] [131.777 seconds] odo describe/list binding command tests when creating a component with a spec binding and envvars (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 ------------------------------ • [33.997 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:130 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/2590920567 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [31.546 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:461 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/1955475226 << End Captured StdOut/StdErr Output ------------------------------ ••• ------------------------------ • [SLOW TEST] [229.457 seconds] odo add binding command tests when the component is bootstrapped when adding a binding (current 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:271 ------------------------------ ••••• ------------------------------ • [SLOW TEST] [127.269 seconds] odo list with devfile devfile has missing metadata when projectType and language is missing when the component is pushed should show 'nodejs' for 'Type' in odo list /go/odo_1/tests/integration/cmd_devfile_list_test.go:246 ------------------------------ • ------------------------------ • [SLOW TEST] [197.543 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:2154 ------------------------------ Ran 385 of 386 Specs in 965.902 seconds SUCCESS! -- 385 Passed | 0 Failed | 0 Pending | 1 Skipped Ginkgo ran 1 suite in 17m11.271387865s Test Suite Passed go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo --randomize-all --slow-spec-threshold=120s -timeout 14400s --no-color -nodes=32 tests/e2escenarios Running Suite: odo e2e scenarios - /go/odo_1/tests/e2escenarios =============================================================== Random Seed: 1663078630 - will randomize all specs Will run 6 of 6 specs Running in parallel across 32 processes ••• ------------------------------ • [SLOW TEST] [137.774 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] [148.831 seconds] E2E Test starting with non-empty Directory should verify developer workflow from non-empty Directory /go/odo_1/tests/e2escenarios/e2e_test.go:162 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/2946058848 Spawning '/go/bin/odo delete component' from /tmp/2946058848 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [156.741 seconds] E2E Test starting with empty Directory should verify developer workflow from empty Directory /go/odo_1/tests/e2escenarios/e2e_test.go:47 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/1349697611 Spawning '/go/bin/odo delete component' from /tmp/1349697611 << End Captured StdOut/StdErr Output ------------------------------ Ran 6 of 6 Specs in 156.747 seconds SUCCESS! -- 6 Passed | 0 Failed | 0 Pending | 0 Skipped Ginkgo ran 1 suite in 2m59.946820918s Test Suite Passed