Using Devfile proxy: 07e90e30-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: 1664960497 - will randomize all specs
Will run 386 of 386 specs
Running in parallel across 32 processes
••
------------------------------
• [12.114 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/3670692107
<< End Captured StdOut/StdErr Output
------------------------------
•••••••••
------------------------------
• [50.365 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/1540742915
<< End Captured StdOut/StdErr Output
------------------------------
••••••••••••••••••••••••••••••••
------------------------------
• [SLOW TEST] [121.458 seconds]
odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure
/go/odo_1/tests/integration/cmd_dev_test.go:573
------------------------------
••••
------------------------------
• [SLOW TEST] [128.504 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:846
------------------------------
• [SLOW TEST] [140.042 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] [130.863 seconds]
odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "binding-tza") 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] [153.785 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-dkw") 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
------------------------------
•
------------------------------
• [9.005 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/799560166
<< End Captured StdOut/StdErr Output
------------------------------
••••••
------------------------------
• [62.414 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/3518800293
<< End Captured StdOut/StdErr Output
------------------------------
•••
------------------------------
• [SLOW TEST] [120.957 seconds]
odo describe/list binding command tests when creating a component with a spec binding (service in namespace "binding-hqr") 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.367 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/4001051047
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [60.218 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/3186545876
<< End Captured StdOut/StdErr Output
------------------------------
• [42.750 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/2510588583
<< End Captured StdOut/StdErr Output
------------------------------
•••••••••
------------------------------
• [SLOW TEST] [127.475 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:914
------------------------------
• [SLOW TEST] [212.194 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] [128.180 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] [164.993 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] [171.177 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
------------------------------
••••
------------------------------
• [101.280 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/3177559300
<< End Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [SLOW TEST] [168.255 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:897
------------------------------
••
------------------------------
• [32.918 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/4264967519
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [SLOW TEST] [145.671 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
------------------------------
•
------------------------------
• [59.127 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/3378978302
<< End Captured StdOut/StdErr Output
------------------------------
•••••••••••
------------------------------
• [63.258 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/906335506
<< End Captured StdOut/StdErr Output
------------------------------
••••••••••
------------------------------
• [SLOW TEST] [123.203 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:2143
------------------------------
•••••••••••••••••••••••••••••••
------------------------------
• [SLOW TEST] [121.205 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
------------------------------
••••
------------------------------
• [45.323 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/2249641400
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [SLOW TEST] [131.575 seconds]
odo describe/list binding command tests when creating a component with a spec binding (service in namespace "binding-lzn") 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] [123.120 seconds]
odo describe/list binding command tests when creating a component with a spec binding (service in namespace "") when Starting a Pg service when running dev session when changing the current namespace should list the binding with --namespace flag
/go/odo_1/tests/integration/cmd_describe_list_binding_test.go:626
------------------------------
• [SLOW TEST] [214.777 seconds]
odo describe/list binding command tests when creating a component with a spec binding (service in namespace "binding-hqr") 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 [SKIPPED] [17.926 seconds]
odo dev command tests
/go/odo_1/tests/integration/cmd_dev_test.go:31
using Kubernetes cluster [BeforeEach]
/go/odo_1/tests/integration/cmd_dev_test.go:2194
should run odo dev successfully on default namespace
/go/odo_1/tests/integration/cmd_dev_test.go:2200
Begin Captured GinkgoWriter Output >>
Created dir: /tmp/2354369973
Created dir: /tmp/3686497675
Setting KUBECONFIG=/tmp/3686497675/config
Creating a new project: cmd-dev-test2200trg
Running oc with args [oc new-project cmd-dev-test2200trg]
[oc] Now using project "cmd-dev-test2200trg" on server "https://c113-e.eu-de.containers.cloud.ibm.com:30152".
[oc]
[oc] You can add applications to this project with the 'new-app' command. For example, try:
[oc]
[oc] oc new-app rails-postgresql-example
[oc]
[oc] to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application:
[oc]
[oc] kubectl create deployment hello-node --image=k8s.gcr.io/serve_hostname
[oc]
Running oc with args [oc create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n cmd-dev-test2200trg]
[oc] configmap/config-map-for-cleanup created
Current working dir: /go/odo_1/tests/integration
Running odo with args [odo preference remove registry DefaultDevfileRegistry -f]
[odo] I1005 09:09:21.562928 24085 util.go:767] Cached response used.
[odo] I1005 09:09:21.562213 24085 implem.go:106] The path for preference file is /tmp/3686497675/preference.yaml
[odo] Successfully removed registry
[odo] I1005 09:09:21.565503 24085 odo.go:75] Could not get the latest release information in time. Never mind, exiting gracefully :)
Running odo with args [odo preference add registry DefaultDevfileRegistry http://07e90e30-eu-de.lb.appdomain.cloud]
[odo] I1005 09:09:24.596431 24187 implem.go:106] The path for preference file is /tmp/3686497675/preference.yaml
[odo] I1005 09:09:24.597849 24187 util.go:767] Cached response used.
[odo] New registry successfully added
[odo] I1005 09:09:24.607484 24187 odo.go:75] Could not get the latest release information in time. Never mind, exiting gracefully :)
Setting current dir to: /tmp/2354369973
Deleting project: cmd-dev-test2200trg
Running odo with args [odo delete project cmd-dev-test2200trg -f --wait=false]
[odo] I1005 09:09:27.203470 24276 util.go:188] path /tmp/2354369973/devfile.yaml doesn't exist, skipping it
[odo] I1005 09:09:27.203557 24276 util.go:188] path /tmp/2354369973/.devfile.yaml doesn't exist, skipping it
[odo] I1005 09:09:27.911212 24276 component.go:82] name of component is "2354369973", and sanitized name is "x2354369973"
[odo] I1005 09:09:27.913738 24276 kclient.go:207] Checking if "projects" resource is supported
[odo] ✓ Project "cmd-dev-test2200trg" deleted
[odo] I1005 09:09:28.106429 24276 odo.go:75] Could not get the latest release information in time. Never mind, exiting gracefully :)
Setting current dir to: /go/odo_1/tests/integration
Deleting dir: /tmp/2354369973
Deleting dir: /tmp/3686497675
<< End Captured GinkgoWriter Output
This is a Kubernetes specific scenario, skipping
In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:2196
------------------------------
•••••
------------------------------
• [SLOW TEST] [156.373 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
------------------------------
•
------------------------------
• [18.575 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/1208450158
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [9.075 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/1355879394
<< End Captured StdOut/StdErr Output
------------------------------
• [50.593 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/3918645858
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [183.317 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] [138.806 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
------------------------------
••••••
------------------------------
• [20.135 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/296886483
<< End Captured StdOut/StdErr Output
------------------------------
•••••
------------------------------
• [45.800 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/2633623702
<< End Captured StdOut/StdErr Output
------------------------------
••••
------------------------------
• [SLOW TEST] [146.931 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] [134.123 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] [163.054 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-giz") 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
------------------------------
••••
------------------------------
• [42.639 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/2550496596
<< End Captured StdOut/StdErr Output
------------------------------
••••••
------------------------------
• [10.781 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/2214631911
<< End Captured StdOut/StdErr Output
------------------------------
• [8.853 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/1685386313
<< End Captured StdOut/StdErr Output
------------------------------
••••••
------------------------------
• [49.397 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/381774659
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [129.935 seconds]
odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "binding-zwr") 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
------------------------------
•
------------------------------
• [96.961 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/3112434929
<< End Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [SLOW TEST] [156.932 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] [131.608 seconds]
odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "binding-hqr") when Starting a Pg service when running dev session should list the binding
/go/odo_1/tests/integration/cmd_describe_list_binding_test.go:581
------------------------------
•
------------------------------
• [SLOW TEST] [142.362 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-ktu") 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] [133.706 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] [160.872 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-ejy") 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] [162.873 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-quj") 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.005 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/2045816549
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [SLOW TEST] [152.166 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-kzu") 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] [171.252 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] [124.833 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:1647
------------------------------
••••••••••••••••••••••••
------------------------------
• [42.222 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/320761838
<< End Captured StdOut/StdErr Output
------------------------------
•••
------------------------------
• [SLOW TEST] [121.655 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
------------------------------
•
------------------------------
• [SLOW TEST] [148.131 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-tza") 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
------------------------------
•••
------------------------------
• [12.617 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/729919335
<< End Captured StdOut/StdErr Output
------------------------------
• [23.632 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/4072348684
<< End Captured StdOut/StdErr Output
------------------------------
••••
------------------------------
• [SLOW TEST] [149.171 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] [141.726 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] [154.170 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-fud") 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.430 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] [164.615 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] [132.344 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:1647
------------------------------
••••••
------------------------------
• [SLOW TEST] [205.084 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] [167.476 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-brr") 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
------------------------------
•••••••••
------------------------------
• [9.861 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/2237647236
<< End Captured StdOut/StdErr Output
------------------------------
• [66.083 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/793788502
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [54.415 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/2632355895
<< End Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [SLOW TEST] [125.184 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
------------------------------
•
------------------------------
• [115.377 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/1569253136
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [64.989 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/915441314
<< End Captured StdOut/StdErr Output
------------------------------
••••
------------------------------
• [SLOW TEST] [150.796 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-ead") 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
------------------------------
••
------------------------------
• [37.102 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/1549218661
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [87.631 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/135592768
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [38.165 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/3338304406
<< End Captured StdOut/StdErr Output
------------------------------
••••••
------------------------------
• [SLOW TEST] [129.032 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
------------------------------
•
------------------------------
• [SLOW TEST] [129.961 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] [125.095 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] [200.574 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] [158.260 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:2462
------------------------------
• [SLOW TEST] [122.991 seconds]
odo dev debug command tests when a composite command is used as debug command - with metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_debug_test.go:109
------------------------------
•
------------------------------
• [SLOW TEST] [216.797 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] [130.977 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
------------------------------
Ran 385 of 386 Specs in 869.808 seconds
SUCCESS! -- 385 Passed | 0 Failed | 0 Pending | 1 Skipped
Ginkgo ran 1 suite in 15m33.415421641s
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: 1664961437 - will randomize all specs
Will run 5 of 5 specs
Running in parallel across 32 processes
•••
------------------------------
• [SLOW TEST] [128.271 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/2299100253
Spawning '/go/bin/odo delete component' from /tmp/2299100253
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [140.299 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/375123602
Spawning '/go/bin/odo delete component' from /tmp/375123602
<< End Captured StdOut/StdErr Output
------------------------------
Ran 5 of 5 Specs in 140.353 seconds
SUCCESS! -- 5 Passed | 0 Failed | 0 Pending | 0 Skipped
Ginkgo ran 1 suite in 2m40.986682973s
Test Suite Passed