Using Devfile proxy: 12659208-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: 1663077595 - will randomize all specs Will run 386 of 386 specs Running in parallel across 32 processes ••••••••••••••••• ------------------------------ • [60.308 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/3857070130 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [70.515 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/1054332733 << End Captured StdOut/StdErr Output ------------------------------ ••••••••••• ------------------------------ • [19.158 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/2195400229 << End Captured StdOut/StdErr Output ------------------------------ • [46.741 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/1496302538 << End Captured StdOut/StdErr Output ------------------------------ •••••••• ------------------------------ • [39.491 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/2042499997 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [SLOW TEST] [121.794 seconds] odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "binding-uqr") 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] [123.753 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/4112263396 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [126.403 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] [127.482 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] [127.052 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] [132.928 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] [135.138 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 ------------------------------ • ------------------------------ • [SLOW TEST] [141.835 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 ------------------------------ •• ------------------------------ • [14.303 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/4149185279 << End Captured StdOut/StdErr Output ------------------------------ •••••••••••••• ------------------------------ • [49.039 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/761963495 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [SLOW TEST] [204.893 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 ------------------------------ • [SLOW TEST] [168.608 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 ------------------------------ ••• ------------------------------ • [42.076 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/3651551079 << End Captured StdOut/StdErr Output ------------------------------ ••••••••• ------------------------------ • [43.854 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/1240317376 << End Captured StdOut/StdErr Output ------------------------------ ••••••• ------------------------------ • [25.122 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/856903735 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [SLOW TEST] [124.384 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] [120.497 seconds] odo dev command tests when running odo dev and composite command is used as a run command - with metadata.name should run successfully /go/odo_1/tests/integration/cmd_dev_test.go:1640 ------------------------------ • [SLOW TEST] [128.092 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 ------------------------------ •• ------------------------------ • [SLOW TEST] [148.574 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:253 ------------------------------ •• ------------------------------ • [58.055 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/1080074131 << End Captured StdOut/StdErr Output ------------------------------ ••• ------------------------------ • [13.764 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/273401359 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [SLOW TEST] [128.626 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 list the binding /go/odo_1/tests/integration/cmd_describe_list_binding_test.go:581 ------------------------------ • [SLOW TEST] [151.878 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-uqr") 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 ------------------------------ • [14.059 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/200727258 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [66.709 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/2952198086 << End Captured StdOut/StdErr Output ------------------------------ ••••••••••••••• ------------------------------ • [10.702 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/123533739 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [SLOW TEST] [144.356 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-fsj") 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] [128.497 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "") when Starting a Pg service when running dev session when changing the current namespace should list the binding with --namespace flag /go/odo_1/tests/integration/cmd_describe_list_binding_test.go:626 ------------------------------ • ------------------------------ • [SLOW TEST] [122.818 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:88 ------------------------------ • ------------------------------ • [SLOW TEST] [148.368 seconds] odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-nwu") 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] [132.359 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] [124.400 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] [148.186 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] [121.542 seconds] odo describe/list binding command tests when creating a component with a spec binding (service in namespace "binding-eje") 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 ------------------------------ •••••••••••••••• ------------------------------ • [11.831 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/961158722 << End Captured StdOut/StdErr Output ------------------------------ ••• ------------------------------ • [SLOW TEST] [156.333 seconds] odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-kyv") 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 ------------------------------ •• ------------------------------ • [42.666 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/648263800 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [126.571 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 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] [133.475 seconds] odo describe/list binding command tests when creating a component with a spec binding (service in namespace "binding-aqv") 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] [138.612 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 ------------------------------ •••• ------------------------------ • [SLOW TEST] [161.505 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-eea") 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 ------------------------------ •••• ------------------------------ • [67.899 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/1196592698 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [SLOW TEST] [134.718 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-otm") 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 ------------------------------ ••••• ------------------------------ • [38.120 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/4111374063 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [SLOW TEST] [144.283 seconds] odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-ijj") 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 ------------------------------ •••• ------------------------------ • [58.310 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/2094072080 << End Captured StdOut/StdErr Output ------------------------------ • [16.583 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/601654647 << End Captured StdOut/StdErr Output ------------------------------ •••••••••••• ------------------------------ • [7.234 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/948609109 << End Captured StdOut/StdErr Output ------------------------------ •••• ------------------------------ • [42.070 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/2476173952 << End Captured StdOut/StdErr Output ------------------------------ •••••••••••• ------------------------------ • [SLOW TEST] [125.553 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] [182.182 seconds] odo dev command tests when Starting a PostgreSQL service when creating local files and dir and running odo dev - with metadata.name should correctly propagate changes to the container /go/odo_1/tests/integration/cmd_dev_test.go:955 ------------------------------ • ------------------------------ • [SLOW TEST] [152.873 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 ------------------------------ ••••••••••• ------------------------------ • [58.316 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/1017518751 << End Captured StdOut/StdErr Output ------------------------------ ••••••••• ------------------------------ • [99.061 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/1839712601 << End Captured StdOut/StdErr Output ------------------------------ • [102.281 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/1308271099 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [SLOW TEST] [159.125 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 ------------------------------ • ------------------------------ • [55.102 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/3131204861 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [SLOW TEST] [125.007 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] [136.942 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] [190.788 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] [130.289 seconds] odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "binding-eje") 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 ------------------------------ • ------------------------------ • [60.105 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/2009201147 << End Captured StdOut/StdErr Output ------------------------------ ••••••••• ------------------------------ • [SLOW TEST] [213.384 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 ------------------------------ •• ------------------------------ • [11.288 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/3147413416 << End Captured StdOut/StdErr Output ------------------------------ ••••••• ------------------------------ • [SLOW TEST] [272.946 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 ------------------------------ ••••••••••••• ------------------------------ • [SLOW TEST] [127.916 seconds] odo describe/list binding command tests when creating a component with a spec binding (service in namespace "binding-fdj") 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] [183.360 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] [131.685 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 ------------------------------ • [SLOW TEST] [126.659 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 ------------------------------ • ------------------------------ • [61.574 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/625033836 << End Captured StdOut/StdErr Output ------------------------------ ••• ------------------------------ • [67.738 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/4142267758 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [SLOW TEST] [137.576 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/2415546071 << End Captured StdOut/StdErr Output ------------------------------ •••••••• ------------------------------ • [41.672 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/4164899948 << End Captured StdOut/StdErr Output ------------------------------ ••••••••••••••••••••• ------------------------------ • [SLOW TEST] [129.220 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 ------------------------------ •• Ran 386 of 386 Specs in 847.426 seconds SUCCESS! -- 386 Passed | 0 Failed | 0 Pending | 0 Skipped Ginkgo ran 1 suite in 15m13.973197034s 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: 1663078515 - will randomize all specs Will run 6 of 6 specs Running in parallel across 32 processes ••• ------------------------------ • [SLOW TEST] [133.156 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] [138.840 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/231602531 Spawning '/go/bin/odo delete component' from /tmp/231602531 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [145.369 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/1565764789 Spawning '/go/bin/odo delete component' from /tmp/1565764789 << End Captured StdOut/StdErr Output ------------------------------ Ran 6 of 6 Specs in 145.386 seconds SUCCESS! -- 6 Passed | 0 Failed | 0 Pending | 0 Skipped Ginkgo ran 1 suite in 2m48.287726579s Test Suite Passed