Using Devfile proxy: 07e90e30-eu-de.lb.appdomain.cloud
go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=b9311835f" ./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: 1663056266 - will randomize all specs
Will run 380 of 380 specs
Running in parallel across 32 processes
•
------------------------------
• [12.353 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/976048268
<< End Captured StdOut/StdErr Output
------------------------------
••••••
------------------------------
• [52.688 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/1004115431
<< End Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [14.417 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/3286030953
<< End Captured StdOut/StdErr Output
------------------------------
• [50.649 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/1870286815
<< End Captured StdOut/StdErr Output
------------------------------
••••
------------------------------
S [SKIPPED] [24.218 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:2251
should run odo dev successfully on default namespace
/go/odo_1/tests/integration/cmd_dev_test.go:2257
Begin Captured GinkgoWriter Output >>
Created dir: /tmp/1033523320
Created dir: /tmp/771547864
Setting KUBECONFIG=/tmp/771547864/config
Creating a new project: cmd-dev-test2257xfb
Running oc with args [oc new-project cmd-dev-test2257xfb]
[oc] Now using project "cmd-dev-test2257xfb" 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-test2257xfb]
[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] I0913 08:06:39.765676 12914 implem.go:106] The path for preference file is /tmp/771547864/preference.yaml
[odo] Successfully removed registry
[odo] I0913 08:06:39.809406 12914 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] I0913 08:06:42.604546 13052 implem.go:106] The path for preference file is /tmp/771547864/preference.yaml
[odo] New registry successfully added
[odo] I0913 08:06:42.672725 13052 odo.go:75] Could not get the latest release information in time. Never mind, exiting gracefully :)
Setting current dir to: /tmp/1033523320
Deleting project: cmd-dev-test2257xfb
Running odo with args [odo delete project cmd-dev-test2257xfb -f --wait=false]
[odo] I0913 08:06:46.129400 13133 util.go:188] path /tmp/1033523320/devfile.yaml doesn't exist, skipping it
[odo] I0913 08:06:46.130141 13133 util.go:188] path /tmp/1033523320/.devfile.yaml doesn't exist, skipping it
[odo] I0913 08:06:46.199158 13133 util.go:733] HTTPGetRequest: https://raw.githubusercontent.com/redhat-developer/odo/main/build/VERSION
[odo] I0913 08:06:46.200148 13133 util.go:754] Response will be cached in /tmp/odohttpcache for 1h0m0s
[odo] I0913 08:06:46.204595 13133 util.go:767] Cached response used.
[odo] I0913 08:06:46.628202 13133 component.go:73] name of component is "1033523320", and sanitized name is "x1033523320"
[odo] I0913 08:06:46.628578 13133 kclient.go:207] Checking if "projects" resource is supported
[odo] I0913 08:06:46.695591 13133 odo.go:75] Could not get the latest release information in time. Never mind, exiting gracefully :)
[odo] ✓ Project "cmd-dev-test2257xfb" deleted
Setting current dir to: /go/odo_1/tests/integration
Deleting dir: /tmp/1033523320
Deleting dir: /tmp/771547864
<< End Captured GinkgoWriter Output
This is a Kubernetes specific scenario, skipping
In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:2253
------------------------------
•••••••••••••••••••••••
------------------------------
• [110.703 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/4188131416
<< End Captured StdOut/StdErr Output
------------------------------
••••
------------------------------
• [SLOW TEST] [123.506 seconds]
odo dev command tests when project and clonePath is present in devfile and running odo dev - without metadata.name should sync to the correct dir in container
/go/odo_1/tests/integration/cmd_dev_test.go:1126
------------------------------
•••
------------------------------
• [48.611 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/489178671
<< End Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [SLOW TEST] [152.563 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
------------------------------
••
------------------------------
• [18.620 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/443622520
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [157.771 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:971
------------------------------
• [9.101 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/3699607870
<< End Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [15.303 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/3966212248
<< End Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [SLOW TEST] [173.575 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
------------------------------
••
------------------------------
• [9.419 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/3447354957
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [179.830 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-prz") 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] [182.643 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-mlx") 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] [185.817 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:2213
------------------------------
•
------------------------------
• [SLOW TEST] [137.612 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:2519
------------------------------
••••
------------------------------
• [SLOW TEST] [137.575 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:136
------------------------------
•••••
------------------------------
• [SLOW TEST] [123.967 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] [122.331 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] [160.719 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
------------------------------
•
------------------------------
• [SLOW TEST] [134.640 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] [120.448 seconds]
odo dev command tests when a component is bootstrapped and pushed when odo dev is executed and Ephemeral is set to false when stopping odo dev normally should have deleted all resources before returning
/go/odo_1/tests/integration/cmd_dev_test.go:311
------------------------------
••••
------------------------------
• [SLOW TEST] [268.475 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:2153
------------------------------
•••
------------------------------
• [SLOW TEST] [179.191 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] [127.486 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
------------------------------
•
------------------------------
• [71.707 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/3666979002
<< End Captured StdOut/StdErr Output
------------------------------
••••
------------------------------
• [SLOW TEST] [128.975 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/1647789046
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [SLOW TEST] [133.195 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:1039
------------------------------
•••••••••
------------------------------
• [SLOW TEST] [135.786 seconds]
odo dev command tests when running odo dev and composite command is used as a run command - without metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_test.go:1639
------------------------------
•••
------------------------------
• [67.807 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/2884285447
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [135.564 seconds]
odo list with devfile when a component created in 'app' application verifying the managedBy Version in the odo list output should show managedBy Version
/go/odo_1/tests/integration/cmd_devfile_list_test.go:124
------------------------------
••••••••••••••••••••••••••••••
------------------------------
• [62.814 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/960790588
<< End Captured StdOut/StdErr Output
------------------------------
•••••••••••
------------------------------
• [69.347 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/4226108459
<< End Captured StdOut/StdErr Output
------------------------------
•••••••
------------------------------
• [SLOW TEST] [142.896 seconds]
odo dev command tests 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:903
------------------------------
•••••••
------------------------------
• [SLOW TEST] [138.570 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-roz") 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] [137.750 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
------------------------------
• [SLOW TEST] [176.458 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-yzu") 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] [157.449 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-bgt") 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] [127.502 seconds]
odo dev command tests when a component is bootstrapped and pushed when odo dev is executed and Ephemeral is set to false when killing odo dev and running odo delete component --wait should have deleted all resources before returning
/go/odo_1/tests/integration/cmd_dev_test.go:289
------------------------------
••
------------------------------
• [81.710 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/1390632492
<< End Captured StdOut/StdErr Output
------------------------------
•••
------------------------------
• [SLOW TEST] [123.812 seconds]
odo dev command tests when running odo dev with devfile containing volume-component - without metadata.name should successfully use the volume components in container components
/go/odo_1/tests/integration/cmd_dev_test.go:1326
------------------------------
• [SLOW TEST] [148.100 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/3629537491
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [130.474 seconds]
odo dev command tests when adding local files to gitignore and running odo dev should not sync ignored files to the container
/go/odo_1/tests/integration/cmd_dev_test.go:1029
------------------------------
••
------------------------------
• [SLOW TEST] [132.751 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
------------------------------
•••••
------------------------------
• [21.032 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/1414176829
<< End Captured StdOut/StdErr Output
------------------------------
•••••••
------------------------------
• [SLOW TEST] [138.964 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:1704
------------------------------
•••
------------------------------
• [14.894 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/2538398588
<< End Captured StdOut/StdErr Output
------------------------------
• [54.561 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/3057464932
<< End Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [SLOW TEST] [133.280 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:2531
------------------------------
••••••••••
------------------------------
• [56.772 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/1454492746
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [166.769 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-lpp") when Starting a Pg service when running dev session when changing the current namespace should list the binding with --namespace flag
/go/odo_1/tests/integration/cmd_describe_list_binding_test.go:626
------------------------------
• [SLOW TEST] [198.086 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] [146.979 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:954
------------------------------
•••
------------------------------
• [SLOW TEST] [140.104 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:903
------------------------------
•
------------------------------
• [SLOW TEST] [128.901 seconds]
odo dev command tests when creating nodejs component, doing odo dev and run command has dev.odo.push.path attribute should sync only the mentioned files at the appropriate remote destination
/go/odo_1/tests/integration/cmd_dev_test.go:2239
------------------------------
•
------------------------------
• [SLOW TEST] [124.148 seconds]
odo describe/list binding command tests when creating a component with a spec binding (service in namespace "binding-bxb") 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.773 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:2102
------------------------------
•••••
------------------------------
• [97.636 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/1264852909
<< End Captured StdOut/StdErr Output
------------------------------
• [13.883 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/3044053583
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [63.287 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/2880489685
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [224.569 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
------------------------------
• [62.990 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/2075268653
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [SLOW TEST] [178.292 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:523
------------------------------
• [SLOW TEST] [152.332 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.650 seconds]
odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "binding-tmo") 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] [153.665 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:971
------------------------------
•••
------------------------------
• [SLOW TEST] [126.029 seconds]
odo dev debug command tests when a composite command is used as debug command - without metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_debug_test.go:109
------------------------------
• [SLOW TEST] [147.334 seconds]
odo dev command tests devfile contains composite apply command when odo dev is running should execute the composite apply commands successfully
/go/odo_1/tests/integration/cmd_dev_test.go:1359
------------------------------
•••••••
------------------------------
• [SLOW TEST] [126.543 seconds]
odo dev command tests when running odo dev and composite command is used as a run command - with metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_test.go:1639
------------------------------
• [SLOW TEST] [128.204 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
------------------------------
•••••
------------------------------
• [66.190 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/1766083402
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [67.415 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/3346081671
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [166.727 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:523
------------------------------
• [SLOW TEST] [134.866 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] [133.034 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 describe the binding
/go/odo_1/tests/integration/cmd_describe_list_binding_test.go:548
------------------------------
••
------------------------------
• [24.801 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/1389337600
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [204.740 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
------------------------------
•••
------------------------------
• [56.916 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/504937130
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [140.931 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:954
------------------------------
•••
------------------------------
• [14.793 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/1462625202
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [SLOW TEST] [136.808 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
------------------------------
•••••••••••
------------------------------
• [SLOW TEST] [135.416 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] [128.428 seconds]
odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose two endpoints on localhost
/go/odo_1/tests/integration/cmd_dev_test.go:571
------------------------------
•••••••••••••
------------------------------
• [47.182 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/4128223262
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [39.939 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:154
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo dev --random-ports --no-watch' from /tmp/184477013
<< End Captured StdOut/StdErr Output
------------------------------
•••••
------------------------------
• [SLOW TEST] [152.861 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-ali") 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
------------------------------
• [41.842 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/1001049758
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [SLOW TEST] [120.702 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
------------------------------
• [SLOW TEST] [201.848 seconds]
odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "binding-mij") 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.168 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-hmc") 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] [158.544 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-prz") 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
------------------------------
• [46.815 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/2084489047
<< End Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [SLOW TEST] [134.625 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-ymj") 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] [245.578 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] [127.021 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] [183.825 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
------------------------------
••••
Ran 379 of 380 Specs in 929.600 seconds
SUCCESS! -- 379 Passed | 0 Failed | 0 Pending | 1 Skipped
Ginkgo ran 1 suite in 16m34.857200322s
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: 1663057269 - will randomize all specs
Will run 6 of 6 specs
Running in parallel across 32 processes
•••
------------------------------
• [SLOW TEST] [141.638 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] [148.203 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/3712354668
Spawning '/go/bin/odo delete component' from /tmp/3712354668
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [154.576 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/1077373936
Spawning '/go/bin/odo delete component' from /tmp/1077373936
<< End Captured StdOut/StdErr Output
------------------------------
Ran 6 of 6 Specs in 154.581 seconds
SUCCESS! -- 6 Passed | 0 Failed | 0 Pending | 0 Skipped
Ginkgo ran 1 suite in 2m59.396611425s
Test Suite Passed