Using Devfile proxy: 12659208-eu-de.lb.appdomain.cloud go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=dafce5dc8" ./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: 1664960456 - will randomize all specs Will run 386 of 386 specs Running in parallel across 32 processes •••••••• ------------------------------ • [33.809 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:107 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo deploy' from /tmp/800586669 << End Captured StdOut/StdErr Output ------------------------------ ••••••• ------------------------------ • [45.358 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:160 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports --no-watch' from /tmp/1916135330 << End Captured StdOut/StdErr Output ------------------------------ •••••• ------------------------------ • [25.384 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:73 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo deploy' from /tmp/3125679726 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [55.185 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/3577124483 << End Captured StdOut/StdErr Output ------------------------------ •••••• ------------------------------ • [49.682 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/1860072237 << End Captured StdOut/StdErr Output ------------------------------ •••••••••••••••• ------------------------------ • [SLOW TEST] [120.985 seconds] odo describe/list binding command tests when creating a component with a spec binding (service in namespace "binding-nut") 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 ------------------------------ •••••••••••• ------------------------------ • [57.755 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/1050828838 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [SLOW TEST] [120.958 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:89 ------------------------------ •• ------------------------------ • [SLOW TEST] [153.229 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:2156 ------------------------------ •••••••• ------------------------------ • [SLOW TEST] [158.843 seconds] odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-kjr") 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 ------------------------------ •••••• ------------------------------ • [61.943 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/1696609162 << End Captured StdOut/StdErr Output ------------------------------ •••• ------------------------------ • [52.089 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/2778641112 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [160.616 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 ------------------------------ •• ------------------------------ • [13.527 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/3275914992 << End Captured StdOut/StdErr Output ------------------------------ ••••• ------------------------------ • [SLOW TEST] [140.380 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-dyp") 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.564 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/657996123 << End Captured StdOut/StdErr Output ------------------------------ ••• ------------------------------ • [SLOW TEST] [132.084 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] [130.604 seconds] odo describe/list binding command tests when creating a component with a spec binding (service in namespace "binding-pkm") 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 ------------------------------ •••• ------------------------------ • [27.061 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/3282682124 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [9.735 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/1883383841 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [9.632 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:268 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/534824717 << End Captured StdOut/StdErr Output ------------------------------ ••••• ------------------------------ • [52.353 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/1053366433 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [SLOW TEST] [150.165 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-psa") 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] [160.928 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-baq") 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] [142.662 seconds] odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-wve") 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] [198.751 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:2045 ------------------------------ ••••••• ------------------------------ • [SLOW TEST] [136.096 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:525 ------------------------------ ••••••••• ------------------------------ • [SLOW TEST] [169.120 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 ------------------------------ • ------------------------------ • [39.787 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:105 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports' from /tmp/460451313 << End Captured StdOut/StdErr Output ------------------------------ •••••••• ------------------------------ • [SLOW TEST] [124.419 seconds] odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "binding-kjr") 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 ------------------------------ • ------------------------------ • [15.600 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:339 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/127596531 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [10.331 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/2229433452 << End Captured StdOut/StdErr Output ------------------------------ ••• ------------------------------ • [SLOW TEST] [149.990 seconds] odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-wey") 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 ------------------------------ • [113.325 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/957358283 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [170.827 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:897 ------------------------------ •••••• ------------------------------ • [49.237 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/1602782375 << End Captured StdOut/StdErr Output ------------------------------ •••••••••••••••••••••• ------------------------------ • [81.638 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/602067721 << End Captured StdOut/StdErr Output ------------------------------ ••••••••• ------------------------------ • [SLOW TEST] [171.427 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:914 ------------------------------ •••• ------------------------------ • [34.476 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:72 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports' from /tmp/4179959617 << End Captured StdOut/StdErr Output ------------------------------ ••• ------------------------------ • [SLOW TEST] [138.536 seconds] odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-zst") 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 ------------------------------ •••••••• ------------------------------ • [32.701 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/1218861154 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [42.443 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/3671645731 << End Captured StdOut/StdErr Output ------------------------------ ••••• ------------------------------ • [45.960 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/1778058603 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [SLOW TEST] [121.146 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] [120.318 seconds] odo describe/list binding command tests when creating a component with a spec binding (service in namespace "binding-agv") 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] [151.519 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-wve") 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 ------------------------------ • ------------------------------ • [11.452 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:302 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/972510023 << End Captured StdOut/StdErr Output ------------------------------ •••• ------------------------------ • [SLOW TEST] [142.497 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:2474 ------------------------------ •••• ------------------------------ • [SLOW TEST] [132.951 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] [212.906 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:2096 ------------------------------ •••••• ------------------------------ • [SLOW TEST] [163.795 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 ------------------------------ •• ------------------------------ • [47.620 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/2676929058 << End Captured StdOut/StdErr Output ------------------------------ ••••• ------------------------------ • [SLOW TEST] [125.780 seconds] odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-anf") 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 ------------------------------ •• ------------------------------ • [35.719 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/3635703309 << End Captured StdOut/StdErr Output ------------------------------ ••••• ------------------------------ • [35.030 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/1638902870 << End Captured StdOut/StdErr Output ------------------------------ •••••••••••••••••••••••• ------------------------------ • [10.319 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/2053882299 << End Captured StdOut/StdErr Output ------------------------------ ••••••••••• ------------------------------ • [SLOW TEST] [151.124 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 ------------------------------ ••••• ------------------------------ • [45.063 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/1839972197 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [9.186 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/1234944846 << End Captured StdOut/StdErr Output ------------------------------ •• ------------------------------ • [49.498 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/511888555 << End Captured StdOut/StdErr Output ------------------------------ ••••••••••••• ------------------------------ • [SLOW TEST] [131.938 seconds] odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-uqu") 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 ------------------------------ •••• ------------------------------ • [37.013 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/1403691200 << End Captured StdOut/StdErr Output ------------------------------ • [33.503 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/2189863772 << End Captured StdOut/StdErr Output ------------------------------ ••••••••••• ------------------------------ • [SLOW TEST] [124.650 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:525 ------------------------------ • [SLOW TEST] [123.517 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 ------------------------------ • Ran 386 of 386 Specs in 805.792 seconds SUCCESS! -- 386 Passed | 0 Failed | 0 Pending | 0 Skipped Ginkgo ran 1 suite in 14m24.371554748s 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: 1664961327 - will randomize all specs Will run 5 of 5 specs Running in parallel across 32 processes ••• ------------------------------ • [SLOW TEST] [138.383 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/2887534107 Spawning '/go/bin/odo delete component' from /tmp/2887534107 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [144.236 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/2925415395 Spawning '/go/bin/odo delete component' from /tmp/2925415395 << End Captured StdOut/StdErr Output ------------------------------ Ran 5 of 5 Specs in 144.242 seconds SUCCESS! -- 5 Passed | 0 Failed | 0 Pending | 0 Skipped Ginkgo ran 1 suite in 2m45.051185288s Test Suite Passed