Using Devfile proxy: 12659208-eu-de.lb.appdomain.cloud
go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=0c784bb26" ./cmd/odo/
go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo --randomize-all --slow-spec-threshold=120s -timeout 14400s --no-color -nodes=32 --junit-report="test-integration.xml" --label-filter="!nocluster" tests/integration
Running Suite: Integration Suite - /go/odo_1/tests/integration
==============================================================
Random Seed: 1669049801 - will randomize all specs
Will run 349 of 413 specs
Running in parallel across 32 processes
SSSSSS••S••
------------------------------
• [32.586 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/3091282478
<< End Captured StdOut/StdErr Output
------------------------------
••S•••
------------------------------
• [57.008 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/2615981044
<< End Captured StdOut/StdErr Output
------------------------------
•••••SSS
------------------------------
• [65.479 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/4133883609
<< End Captured StdOut/StdErr Output
------------------------------
• [67.215 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/3252187075
<< End Captured StdOut/StdErr Output
------------------------------
•S•••S••••S
------------------------------
• [41.433 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/932563743
<< End Captured StdOut/StdErr Output
------------------------------
••S••••S•••
------------------------------
• [SLOW TEST] [123.497 seconds]
odo describe/list binding command tests when creating a component with a spec binding (service in namespace "binding-wyg") 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
------------------------------
•
------------------------------
• [45.809 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/885049851
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [124.951 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:978
------------------------------
• [SLOW TEST] [126.533 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] [124.036 seconds]
odo dev command tests checking if odo dev matches local Devfile K8s resources and remote resources when odo dev is executed to run a devfile containing a k8s resource without apply command should have deleted the old resource and created the new resource
/go/odo_1/tests/integration/cmd_dev_test.go:513
------------------------------
••••SSS
------------------------------
• [SLOW TEST] [141.700 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
------------------------------
••••••S
------------------------------
• [SLOW TEST] [145.765 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:995
------------------------------
•••S•
------------------------------
• [SLOW TEST] [157.326 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:606
------------------------------
• [SLOW TEST] [127.323 seconds]
odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "binding-kwj") 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] [161.918 seconds]
odo dev command tests when Create and dev java-springboot component should execute default build and run commands correctly
/go/odo_1/tests/integration/cmd_dev_test.go:1843
------------------------------
••
------------------------------
• [51.149 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/3038581210
<< End Captured StdOut/StdErr Output
------------------------------
••••••••S
------------------------------
• [52.385 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/3314793819
<< End Captured StdOut/StdErr Output
------------------------------
• [59.626 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/4140329675
<< End Captured StdOut/StdErr Output
------------------------------
•••
------------------------------
• [SLOW TEST] [126.623 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
------------------------------
•••
------------------------------
• [107.368 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/2639414598
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [127.811 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:1728
------------------------------
• [SLOW TEST] [126.639 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
------------------------------
•S•
------------------------------
• [SLOW TEST] [122.734 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:927
------------------------------
••••••
------------------------------
• [SLOW TEST] [122.052 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
------------------------------
•••••S•
------------------------------
• [SLOW TEST] [122.052 seconds]
odo describe/list binding command tests when creating a component with a spec binding (service in namespace "binding-cfy") 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
------------------------------
•S•S•••••••S•S••
------------------------------
• [SLOW TEST] [141.984 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
------------------------------
• [50.211 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/1930927410
<< End Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [SLOW TEST] [153.919 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:257
------------------------------
••
------------------------------
• [66.538 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/1089171782
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [121.868 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/229490903
<< End Captured StdOut/StdErr Output
------------------------------
• [30.593 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/3249164104
<< End Captured StdOut/StdErr Output
------------------------------
••SS•
------------------------------
• [SLOW TEST] [170.080 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:251
------------------------------
•
------------------------------
• [SLOW TEST] [134.058 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
------------------------------
•••••••••
------------------------------
• [73.770 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/3141369821
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [171.331 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-nbs") 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] [181.935 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:275
------------------------------
SS•••S•S
------------------------------
• [SLOW TEST] [129.282 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
------------------------------
S••S••
------------------------------
• [SLOW TEST] [150.831 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:606
------------------------------
• [SLOW TEST] [177.588 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-add") 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
------------------------------
••S••••
------------------------------
• [SLOW TEST] [132.743 seconds]
odo describe/list binding command tests when creating a component with a spec binding (service in namespace "binding-cdz") 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] [174.395 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-xai") 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] [134.172 seconds]
odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "binding-ccf") 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] [192.002 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-cfy") 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.544 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:2555
------------------------------
•••
------------------------------
• [80.087 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/1947961171
<< End Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [SLOW TEST] [174.717 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-bmv") 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] [122.049 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:1063
------------------------------
S
------------------------------
• [SLOW TEST] [136.071 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:1063
------------------------------
•••S•S
------------------------------
• [SLOW TEST] [122.063 seconds]
odo dev command tests when multiple projects are present - without metadata.name should sync to the correct dir in container
/go/odo_1/tests/integration/cmd_dev_test.go:1217
------------------------------
• [70.009 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/547092956
<< End Captured StdOut/StdErr Output
------------------------------
S•
------------------------------
• [SLOW TEST] [159.147 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:995
------------------------------
••
------------------------------
• [58.718 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/3038930503
<< End Captured StdOut/StdErr Output
------------------------------
••••
------------------------------
• [SLOW TEST] [132.856 seconds]
odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "binding-yot") 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.284 seconds]
odo dev command tests when node-js application is created and deployed with devfile schema 2.2.0 should check cpuLimit, cpuRequests, memoryRequests
/go/odo_1/tests/integration/cmd_dev_test.go:2224
------------------------------
•••
------------------------------
• [SLOW TEST] [141.245 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/2365076129
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [138.283 seconds]
odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "binding-add") 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
------------------------------
SS••
------------------------------
• [SLOW TEST] [143.329 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] [203.331 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:257
------------------------------
•S••••••S••S•S
------------------------------
• [SLOW TEST] [222.118 seconds]
odo remove binding command tests when the component with binding is bootstrapped when odo dev is running when binding is removed should have led odo dev to delete ServiceBinding from the cluster
/go/odo_1/tests/integration/cmd_remove_binding_test.go:61
------------------------------
••••••S••S•
------------------------------
• [SLOW TEST] [124.435 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:2543
------------------------------
•
------------------------------
• [50.046 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/3006737233
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [128.054 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
------------------------------
•S••
------------------------------
• [29.190 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/840424190
<< End Captured StdOut/StdErr Output
------------------------------
••••••••
------------------------------
• [SLOW TEST] [133.560 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
------------------------------
••S•••••••
------------------------------
• [SLOW TEST] [124.809 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] [121.895 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] [162.300 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-pjq") 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
------------------------------
S••
------------------------------
• [SLOW TEST] [142.062 seconds]
odo describe/list binding command tests when creating a component with a spec binding (service in namespace "binding-dhj") 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
------------------------------
• [72.164 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/3702955802
<< End Captured StdOut/StdErr Output
------------------------------
•S
------------------------------
• [SLOW TEST] [135.061 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
------------------------------
•S•S••
------------------------------
• [70.394 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/1899678859
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [162.032 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-nbs") 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
------------------------------
SS••S•S••••••••S••••
------------------------------
• [SLOW TEST] [170.538 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-ccf") 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] [172.674 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-eoc") 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.389 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:138
------------------------------
•••S
------------------------------
• [SLOW TEST] [135.844 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] [165.686 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:2237
------------------------------
S•
------------------------------
• [57.472 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/2903006561
<< End Captured StdOut/StdErr Output
------------------------------
•••SS•
------------------------------
• [SLOW TEST] [125.806 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
------------------------------
••••••••••
------------------------------
• [44.339 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:159
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo dev --random-ports --no-watch' from /tmp/2235169170
<< End Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [SLOW TEST] [126.889 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/3247818102
<< End Captured StdOut/StdErr Output
------------------------------
•••••••••
------------------------------
• [SLOW TEST] [138.454 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-kwj") 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] [121.272 seconds]
odo logs command tests when component is created and odo logs is executed when running in Dev mode when --follow flag is specified should successfully follow logs of running component
/go/odo_1/tests/integration/cmd_logs_test.go:115
------------------------------
••••
------------------------------
• [SLOW TEST] [148.569 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:275
------------------------------
••••
------------------------------
• [SLOW TEST] [180.246 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:2126
------------------------------
•••
------------------------------
• [SLOW TEST] [137.237 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:225
------------------------------
• [SLOW TEST] [204.888 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:2177
------------------------------
Ran 349 of 413 Specs in 933.351 seconds
SUCCESS! -- 349 Passed | 0 Failed | 0 Pending | 64 Skipped
Ginkgo ran 1 suite in 16m39.055403814s
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 --junit-report="test-e2e.xml" tests/e2escenarios
Running Suite: odo e2e scenarios - /go/odo_1/tests/e2escenarios
===============================================================
Random Seed: 1669050807 - will randomize all specs
Will run 6 of 6 specs
Running in parallel across 32 processes
•••
------------------------------
• [SLOW TEST] [122.903 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] [147.414 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/2750597649
Spawning '/go/bin/odo delete component' from /tmp/2750597649
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [152.308 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/3192841457
Spawning '/go/bin/odo delete component' from /tmp/3192841457
<< End Captured StdOut/StdErr Output
------------------------------
Ran 6 of 6 Specs in 152.353 seconds
SUCCESS! -- 6 Passed | 0 Failed | 0 Pending | 0 Skipped
Ginkgo ran 1 suite in 2m53.235976336s
Test Suite Passed