Using Devfile proxy: 07e90e30-eu-de.lb.appdomain.cloud
go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=c5e9c1be2" ./cmd/odo/
go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo --randomize-all --slow-spec-threshold=120s -timeout 14400s --no-color -nodes=32 tests/integration
Running Suite: Integration Suite - /go/odo_1/tests/integration
==============================================================
Random Seed: 1662565989 - will randomize all specs
Will run 372 of 372 specs
Running in parallel across 32 processes
------------------------------
• [8.605 seconds]
odo init interactive command tests displaying welcoming messages when alizer detection of javascript name should ask to re-enter the component name if invalid value is passed by the user
/go/odo_1/tests/integration/interactive_init_test.go:300
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo init' from /tmp/3076981443
<< End Captured StdOut/StdErr Output
------------------------------
•••
------------------------------
• [12.849 seconds]
odo init interactive command tests displaying welcoming messages when alizer detection of javascript name should display node-echo name
/go/odo_1/tests/integration/interactive_init_test.go:266
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo init' from /tmp/1518850385
<< End Captured StdOut/StdErr Output
------------------------------
•••••••••••••••••
------------------------------
• [64.158 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/3287564432
<< End Captured StdOut/StdErr Output
------------------------------
• [61.436 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/3948496299
<< End Captured StdOut/StdErr Output
------------------------------
•••••••••••••••
------------------------------
• [89.699 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/2329856777
<< End Captured StdOut/StdErr Output
------------------------------
•••
------------------------------
S [SKIPPED] [9.721 seconds]
odo dev command tests
/go/odo_1/tests/integration/cmd_dev_test.go:29
using Kubernetes cluster [BeforeEach]
/go/odo_1/tests/integration/cmd_dev_test.go:2191
should run odo dev successfully on default namespace
/go/odo_1/tests/integration/cmd_dev_test.go:2197
Begin Captured GinkgoWriter Output >>
Created dir: /tmp/228482333
Created dir: /tmp/2317744707
Setting KUBECONFIG=/tmp/2317744707/config
Creating a new project: cmd-dev-test2197qlw
Running oc with args [oc new-project cmd-dev-test2197qlw]
[oc] Now using project "cmd-dev-test2197qlw" 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-test2197qlw]
[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] I0907 15:55:52.421022 14797 util.go:767] Cached response used.
[odo] I0907 15:55:52.420765 14797 implem.go:106] The path for preference file is /tmp/2317744707/preference.yaml
[odo] Successfully removed registry
[odo] I0907 15:55:52.422336 14797 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] I0907 15:55:53.598732 14885 implem.go:106] The path for preference file is /tmp/2317744707/preference.yaml
[odo] I0907 15:55:53.610929 14885 util.go:767] Cached response used.
[odo] New registry successfully added
[odo] I0907 15:55:53.619960 14885 odo.go:75] Could not get the latest release information in time. Never mind, exiting gracefully :)
Setting current dir to: /tmp/228482333
Deleting project: cmd-dev-test2197qlw
Running odo with args [odo delete project cmd-dev-test2197qlw -f --wait=false]
[odo] I0907 15:55:55.250527 14930 util.go:188] path /tmp/228482333/devfile.yaml doesn't exist, skipping it
[odo] I0907 15:55:55.254351 14930 util.go:188] path /tmp/228482333/.devfile.yaml doesn't exist, skipping it
[odo] I0907 15:55:55.263856 14930 util.go:767] Cached response used.
[odo] I0907 15:55:55.631114 14930 component.go:73] name of component is "228482333", and sanitized name is "x228482333"
[odo] I0907 15:55:55.632648 14930 kclient.go:207] Checking if "projects" resource is supported
[odo] I0907 15:55:55.749903 14930 odo.go:75] Could not get the latest release information in time. Never mind, exiting gracefully :)
[odo] ✓ Project "cmd-dev-test2197qlw" deleted
Setting current dir to: /go/odo_1/tests/integration
Deleting dir: /tmp/228482333
Deleting dir: /tmp/2317744707
<< End Captured GinkgoWriter Output
This is a Kubernetes specific scenario, skipping
In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:2193
------------------------------
•
------------------------------
• [87.570 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/2193692282
<< End Captured StdOut/StdErr Output
------------------------------
•••••
------------------------------
• [SLOW TEST] [128.306 seconds]
odo describe/list binding command tests when creating a component with a spec binding (service in namespace "binding-eop") 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] [125.350 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] [129.144 seconds]
odo describe/list binding command tests when creating a component with a spec binding (service in namespace "binding-rsz") 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.421 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:975
------------------------------
••
------------------------------
• [SLOW TEST] [132.065 seconds]
odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "binding-ftk") 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.861 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:890
------------------------------
• [42.641 seconds]
odo dev interactive command tests when directory is not empty should run alizer to download devfile
/go/odo_1/tests/integration/interactive_dev_test.go:70
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo dev --random-ports' from /tmp/2710135293
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [SLOW TEST] [138.220 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] [159.361 seconds]
odo dev command tests when node-js application is created and deployed with devfile schema 2.2.0 when Update the devfile.yaml, and waiting synchronization should check cpuLimit, cpuRequests, memoryRequests after restart
/go/odo_1/tests/integration/cmd_dev_test.go:2153
------------------------------
••••••
------------------------------
• [SLOW TEST] [130.244 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:87
------------------------------
• [27.752 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/1320761543
<< End Captured StdOut/StdErr Output
------------------------------
•••
------------------------------
• [SLOW TEST] [129.749 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] [152.799 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-biu") 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
------------------------------
•••••
------------------------------
• [24.212 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/4288610184
<< End Captured StdOut/StdErr Output
------------------------------
• [13.216 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/914419687
<< End Captured StdOut/StdErr Output
------------------------------
••••••••
------------------------------
• [SLOW TEST] [157.909 seconds]
odo dev debug command tests when a composite apply command is used as debug command should execute the composite apply commands successfully
/go/odo_1/tests/integration/cmd_dev_debug_test.go:178
------------------------------
•••••••••
------------------------------
• [18.216 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/1831095707
<< End Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [SLOW TEST] [122.412 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-cen") 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] [247.674 seconds]
odo dev command tests when java-springboot application is created and running odo dev when Update the devfile.yaml when compare the local and remote files localFiles and remoteFiles should match
/go/odo_1/tests/integration/cmd_dev_test.go:2093
------------------------------
••
------------------------------
• [3.794 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/2795450807
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [121.783 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-gxy") 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] [125.543 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
------------------------------
•••
------------------------------
• [31.745 seconds]
odo dev interactive command tests when directory is not empty should display welcoming messages first
/go/odo_1/tests/integration/interactive_dev_test.go:101
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo dev --random-ports' from /tmp/357409621
<< End Captured StdOut/StdErr Output
------------------------------
•••
------------------------------
• [13.472 seconds]
odo init interactive command tests should start downloading starter project only after all interactive questions have been asked
/go/odo_1/tests/integration/interactive_init_test.go:337
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo init' from /tmp/1394938481
<< End Captured StdOut/StdErr Output
------------------------------
••••
------------------------------
• [35.656 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/2542308706
<< End Captured StdOut/StdErr Output
------------------------------
••••
------------------------------
• [SLOW TEST] [131.129 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] [131.826 seconds]
odo dev command tests when multiple projects are present - with metadata.name should sync to the correct dir in container
/go/odo_1/tests/integration/cmd_dev_test.go:1129
------------------------------
••••
------------------------------
• [SLOW TEST] [133.826 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
------------------------------
• [6.451 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/3140661764
<< End Captured StdOut/StdErr Output
------------------------------
••••••
------------------------------
• [9.533 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/1214458180
<< End Captured StdOut/StdErr Output
------------------------------
• [63.208 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/4032039098
<< End Captured StdOut/StdErr Output
------------------------------
••••••••••
------------------------------
• [8.737 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/3688119899
<< End Captured StdOut/StdErr Output
------------------------------
••••••••••••
------------------------------
• [SLOW TEST] [126.289 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:270
------------------------------
• [SLOW TEST] [163.453 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying memoryLimit for container in Devfile should expose the endpoint on localhost
/go/odo_1/tests/integration/cmd_dev_test.go:481
------------------------------
•••••••
------------------------------
• [SLOW TEST] [159.525 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:2445
------------------------------
••••••••
------------------------------
• [52.450 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/2845267541
<< End Captured StdOut/StdErr Output
------------------------------
•••
------------------------------
• [29.498 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/2240612736
<< End Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [SLOW TEST] [121.109 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] [121.964 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] [129.192 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:1644
------------------------------
•
------------------------------
• [16.878 seconds]
odo deploy interactive command tests when directory is not empty should display welcoming messages first
/go/odo_1/tests/integration/interactive_deploy_test.go:103
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo deploy' from /tmp/1500208974
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [136.413 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-cgo") 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
------------------------------
••••••••
------------------------------
• [57.060 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/500702060
<< End Captured StdOut/StdErr Output
------------------------------
•••
------------------------------
• [43.066 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/245375215
<< End Captured StdOut/StdErr Output
------------------------------
••••••••••••••
------------------------------
• [37.391 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/4007646071
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [122.654 seconds]
odo dev command tests when Starting a PostgreSQL service when creating local files and dir and running odo dev - without metadata.name when deleting local files and dir and waiting for sync should not list deleted dir and file in container
/go/odo_1/tests/integration/cmd_dev_test.go:907
------------------------------
••••••••••••••••••••••
------------------------------
• [44.325 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/3464338227
<< End Captured StdOut/StdErr Output
------------------------------
•••
------------------------------
• [SLOW TEST] [156.926 seconds]
odo dev command tests when running odo dev with devfile contain volume - without metadata.name check the volume name and mount paths for the containers
/go/odo_1/tests/integration/cmd_dev_test.go:1223
------------------------------
• [SLOW TEST] [127.830 seconds]
odo logs command tests when component is created and odo logs is executed when running in both Dev and Deploy mode should successfully show logs of the running component
/go/odo_1/tests/integration/cmd_logs_test.go:189
------------------------------
••••
------------------------------
• [SLOW TEST] [155.951 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
------------------------------
••••
------------------------------
• [46.966 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/3138411067
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [135.448 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-lyy") when Starting a Pg service when running dev session should list the binding
/go/odo_1/tests/integration/cmd_describe_list_binding_test.go:581
------------------------------
• [SLOW TEST] [123.955 seconds]
odo dev command tests when running odo dev with devfile contain volume - with metadata.name check the volume name and mount paths for the containers
/go/odo_1/tests/integration/cmd_dev_test.go:1223
------------------------------
••••••
------------------------------
• [SLOW TEST] [136.215 seconds]
odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "binding-qjw") 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
------------------------------
••••
------------------------------
• [7.236 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/3356019840
<< End Captured StdOut/StdErr Output
------------------------------
•••
------------------------------
• [SLOW TEST] [126.459 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-upp") 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
------------------------------
••
------------------------------
• [6.010 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/2471860603
<< End Captured StdOut/StdErr Output
------------------------------
•••
------------------------------
• [35.658 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/832091769
<< End Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [28.227 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/3866728077
<< End Captured StdOut/StdErr Output
------------------------------
••••
------------------------------
• [11.854 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/905563754
<< End Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [6.571 seconds]
odo deploy interactive command tests when directory is not empty should run alizer to download devfile
/go/odo_1/tests/integration/interactive_deploy_test.go:71
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo deploy' from /tmp/3970729116
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [130.819 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-zqo") 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] [156.700 seconds]
odo describe/list binding command tests when creating a component with a spec binding (service in namespace "binding-gcw") 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] [231.275 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:2457
------------------------------
•
------------------------------
• [SLOW TEST] [167.389 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] [126.517 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
------------------------------
••••••
------------------------------
• [SLOW TEST] [256.570 seconds]
odo dev command tests when java-springboot application is created and running odo dev when Update the devfile.yaml Should build the application successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2042
------------------------------
••••
------------------------------
• [SLOW TEST] [151.785 seconds]
odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a run command should execute the default run command successfully if specified explicitly
/go/odo_1/tests/integration/cmd_dev_test.go:1975
------------------------------
• [SLOW TEST] [201.236 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] [197.446 seconds]
odo dev command tests when Starting a PostgreSQL service when creating local files and dir and running odo dev - with metadata.name when deleting local files and dir and waiting for sync should not list deleted dir and file in container
/go/odo_1/tests/integration/cmd_dev_test.go:907
------------------------------
Ran 371 of 372 Specs in 786.848 seconds
SUCCESS! -- 371 Passed | 0 Failed | 0 Pending | 1 Skipped
Ginkgo ran 1 suite in 14m6.232717489s
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: 1662566841 - will randomize all specs
Will run 6 of 6 specs
Running in parallel across 32 processes
•••
------------------------------
• [SLOW TEST] [143.065 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] [151.029 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/1105328853
Spawning '/go/bin/odo delete component' from /tmp/1105328853
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [153.275 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/1607169749
Spawning '/go/bin/odo delete component' from /tmp/1607169749
<< End Captured StdOut/StdErr Output
------------------------------
Ran 6 of 6 Specs in 153.286 seconds
SUCCESS! -- 6 Passed | 0 Failed | 0 Pending | 0 Skipped
Ginkgo ran 1 suite in 2m54.396789368s
Test Suite Passed