Using Devfile proxy: 12659208-eu-de.lb.appdomain.cloud go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=c5e9c1be2" ./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: 1662565748 - will randomize all specs Will run 372 of 372 specs Running in parallel across 32 processes • ------------------------------ • [10.079 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/87887651 << End Captured StdOut/StdErr Output ------------------------------ • [14.203 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/1623456504 << End Captured StdOut/StdErr Output ------------------------------ •••••••••••• ------------------------------ • [10.181 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/4040662981 << End Captured StdOut/StdErr Output ------------------------------ •••• ------------------------------ • [46.107 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/677247156 << End Captured StdOut/StdErr Output ------------------------------ ••••••••••••• ------------------------------ • [23.079 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/3396715257 << End Captured StdOut/StdErr Output ------------------------------ •••••••••••••••••••••••• ------------------------------ • [SLOW TEST] [132.339 seconds] odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "binding-rtm") 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 ------------------------------ • [11.080 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/284959794 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [SLOW TEST] [142.098 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 ------------------------------ •••••• ------------------------------ • [55.699 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/720075154 << End Captured StdOut/StdErr Output ------------------------------ • [62.535 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/2605709270 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [SLOW TEST] [121.349 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:907 ------------------------------ •••• ------------------------------ • [12.512 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/2058771448 << End Captured StdOut/StdErr Output ------------------------------ ••••••••••••••• ------------------------------ • [SLOW TEST] [127.997 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-bac") 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 ------------------------------ ••••••••• ------------------------------ • [49.936 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/2019508336 << End Captured StdOut/StdErr Output ------------------------------ •••••••••• ------------------------------ • [43.849 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/1310120113 << End Captured StdOut/StdErr Output ------------------------------ • [43.949 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/2653257966 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [145.797 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-ufu") 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.205 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 ------------------------------ •••• ------------------------------ • [55.874 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/2667463841 << End Captured StdOut/StdErr Output ------------------------------ •••••• ------------------------------ • [SLOW TEST] [129.831 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 ------------------------------ •••• ------------------------------ • [48.869 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/2062576037 << End Captured StdOut/StdErr Output ------------------------------ ••••••••••••• ------------------------------ • [SLOW TEST] [139.273 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:481 ------------------------------ ••••• ------------------------------ • [42.406 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/3688965935 << End Captured StdOut/StdErr Output ------------------------------ ••••••••• ------------------------------ • [SLOW TEST] [148.789 seconds] odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-kwz") 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] [154.558 seconds] odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-nnr") 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 ------------------------------ ••• ------------------------------ • [46.935 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/3302572253 << End Captured StdOut/StdErr Output ------------------------------ •••••••••••••••••••• ------------------------------ • [SLOW TEST] [124.484 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:907 ------------------------------ • [SLOW TEST] [154.781 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:264 ------------------------------ ••• ------------------------------ • [57.507 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/2351617434 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [101.601 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/2743689444 << End Captured StdOut/StdErr Output ------------------------------ ••••• ------------------------------ • [SLOW TEST] [200.243 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:2093 ------------------------------ ••••• ------------------------------ • [47.221 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/1168655271 << End Captured StdOut/StdErr Output ------------------------------ ••••• ------------------------------ • [SLOW TEST] [146.421 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-qhh") 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 ------------------------------ ••••• ------------------------------ • [19.243 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/635757258 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [41.748 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/1137827356 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [SLOW TEST] [143.471 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:264 ------------------------------ • [SLOW TEST] [125.660 seconds] odo describe/list binding command tests when creating a component with a spec binding (service in namespace "binding-kwz") 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 ------------------------------ • ------------------------------ • [51.188 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/1972082672 << End Captured StdOut/StdErr Output ------------------------------ ••• ------------------------------ • [12.709 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/4062968374 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [SLOW TEST] [172.906 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 ------------------------------ • [SLOW TEST] [123.284 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] [181.804 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:2042 ------------------------------ ••••••••••• ------------------------------ • [SLOW TEST] [158.741 seconds] odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-zhn") 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 ------------------------------ •••••• ------------------------------ • [53.079 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/1603866332 << End Captured StdOut/StdErr Output ------------------------------ •••••••••• ------------------------------ • [SLOW TEST] [139.562 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:178 ------------------------------ ••••••• ------------------------------ • [12.107 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/2566851520 << End Captured StdOut/StdErr Output ------------------------------ ••••••••• ------------------------------ • [55.660 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/1285853029 << End Captured StdOut/StdErr Output ------------------------------ ••••••••• ------------------------------ • [SLOW TEST] [125.112 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] [131.796 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/1523855332 << End Captured StdOut/StdErr Output ------------------------------ •••• ------------------------------ • [29.202 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/2845792304 << End Captured StdOut/StdErr Output ------------------------------ ••••• ------------------------------ • [SLOW TEST] [158.787 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:2153 ------------------------------ •••••• ------------------------------ • [50.146 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/988224323 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [9.665 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/3503651028 << End Captured StdOut/StdErr Output ------------------------------ ••••• ------------------------------ • [53.918 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/373559293 << End Captured StdOut/StdErr Output ------------------------------ ••••• ------------------------------ • [SLOW TEST] [172.500 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-bnq") 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] [147.801 seconds] odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-plh") 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 ------------------------------ ••••• ------------------------------ • [61.822 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/2473737014 << End Captured StdOut/StdErr Output ------------------------------ • [53.199 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/2012107850 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [SLOW TEST] [127.141 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-qwi") 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.706 seconds] odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-ilt") 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] [145.335 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 ------------------------------ • Ran 372 of 372 Specs in 792.922 seconds SUCCESS! -- 372 Passed | 0 Failed | 0 Pending | 0 Skipped Ginkgo ran 1 suite in 14m11.021131782s 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: 1662566605 - will randomize all specs Will run 6 of 6 specs Running in parallel across 32 processes ••• ------------------------------ • [SLOW TEST] [122.252 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] [140.207 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/2537156994 Spawning '/go/bin/odo delete component' from /tmp/2537156994 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [144.708 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/705126111 Spawning '/go/bin/odo delete component' from /tmp/705126111 << End Captured StdOut/StdErr Output ------------------------------ Ran 6 of 6 Specs in 145.013 seconds SUCCESS! -- 6 Passed | 0 Failed | 0 Pending | 0 Skipped Ginkgo ran 1 suite in 2m45.990397747s Test Suite Passed