Using Devfile proxy: 7acd6132-eu-de.lb.appdomain.cloud
go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=0c784bb26" ./cmd/odo/
go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo --randomize-all --slow-spec-threshold=120s -timeout 14400s --no-color -nodes=16 --junit-report="test-integration.xml" --label-filter="!nocluster" tests/integration
Running Suite: Integration Suite - /go/odo_1/tests/integration
==============================================================
Random Seed: 1669050151 - will randomize all specs
Will run 349 of 413 specs
Running in parallel across 16 processes
S•SSS••••
------------------------------
• [28.723 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/4219069520
<< End Captured StdOut/StdErr Output
------------------------------
• [34.290 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/943884378
<< End Captured StdOut/StdErr Output
------------------------------
•S
------------------------------
• [24.795 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/1811139017
<< End Captured StdOut/StdErr Output
------------------------------
•••••S•••S•••S•S••••••S•S••••••S••••••
------------------------------
• [26.486 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/3010072826
<< End Captured StdOut/StdErr Output
------------------------------
S•••••••S••••••••••
------------------------------
• [12.454 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/4174539722
<< End Captured StdOut/StdErr Output
------------------------------
•••S•••S•S•
------------------------------
• [SLOW TEST] [141.459 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:978
------------------------------
•
------------------------------
• [19.349 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/2414068917
<< End Captured StdOut/StdErr Output
------------------------------
••••••S•••
------------------------------
S [SKIPPED] [2.756 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:2275
should run odo dev successfully on default namespace
/go/odo_1/tests/integration/cmd_dev_test.go:2281
Begin Captured GinkgoWriter Output >>
Created dir: /tmp/720630877
Created dir: /tmp/3288014875
Setting KUBECONFIG=/tmp/3288014875/config
Creating a new project: cmd-dev-test2281ihv
Running oc with args [oc new-project cmd-dev-test2281ihv] and odo env: []
[oc] Now using project "cmd-dev-test2281ihv" on server "https://c100-e.eu-de.containers.cloud.ibm.com:31988".
[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-test2281ihv] and odo env: []
[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] and odo env: []
[odo] I1121 17:07:48.164194 18224 implem.go:109] The path for preference file is /tmp/3288014875/preference.yaml
[odo] Successfully removed registry
[odo] I1121 17:07:48.165913 18224 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :)
Running odo with args [odo preference add registry DefaultDevfileRegistry http://7acd6132-eu-de.lb.appdomain.cloud] and odo env: []
[odo] I1121 17:07:48.417500 18239 util.go:767] Cached response used.
[odo] I1121 17:07:48.416993 18239 implem.go:109] The path for preference file is /tmp/3288014875/preference.yaml
[odo] New registry successfully added
[odo] I1121 17:07:48.418632 18239 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :)
Setting current dir to: /tmp/720630877
Deleting project: cmd-dev-test2281ihv
Running odo with args [odo delete project cmd-dev-test2281ihv -f --wait=false] and odo env: []
[odo] I1121 17:07:48.600195 18252 util.go:754] Response will be cached in /tmp/odohttpcache for 1h0m0s
[odo] I1121 17:07:48.601075 18252 util.go:767] Cached response used.
[odo] I1121 17:07:48.604515 18252 kclient.go:209] Checking if "projects" resource is supported
[odo] ✓ Project "cmd-dev-test2281ihv" deleted
[odo] I1121 17:07:48.824189 18252 odo.go:88] 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/720630877
Deleting dir: /tmp/3288014875
<< End Captured GinkgoWriter Output
This is a Kubernetes specific scenario, skipping
In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:2277
------------------------------
••••S••••S•••••
------------------------------
• [24.740 seconds]
odo dev interactive command tests when a component is bootstrapped should sync files when p is pressed
/go/odo_1/tests/integration/interactive_dev_test.go:159
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo dev --random-ports --no-watch' from /tmp/1793539885
<< End Captured StdOut/StdErr Output
------------------------------
S•
------------------------------
• [9.804 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/2397603612
<< End Captured StdOut/StdErr Output
------------------------------
••••S••
------------------------------
• [10.484 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/208914683
<< End Captured StdOut/StdErr Output
------------------------------
•••••••S••••S
------------------------------
• [7.073 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/2443200021
<< End Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [SLOW TEST] [130.403 seconds]
odo dev command tests when running odo dev with devfile containing volume-component - with metadata.name should successfully use the volume components in container components
/go/odo_1/tests/integration/cmd_dev_test.go:1350
------------------------------
• [SLOW TEST] [129.305 seconds]
odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy when running and stopping odo dev should not delete the resources created with odo deploy
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:114
------------------------------
SS••
------------------------------
• [SLOW TEST] [129.071 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name and namespace from another directory when odo delete command is run again with nothing deployed on the cluster should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:140
------------------------------
•
------------------------------
• [13.700 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/712172831
<< End Captured StdOut/StdErr Output
------------------------------
••••
------------------------------
• [26.672 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/3568015284
<< End Captured StdOut/StdErr Output
------------------------------
•••••••••
------------------------------
• [SLOW TEST] [189.260 seconds]
odo dev command tests when a component is bootstrapped and pushed ensure that index information is updated
/go/odo_1/tests/integration/cmd_dev_test.go:89
------------------------------
•S•S•••••••
------------------------------
• [SLOW TEST] [127.281 seconds]
odo dev command tests when Create and dev java-springboot component should execute default build and run commands correctly
/go/odo_1/tests/integration/cmd_dev_test.go:1843
------------------------------
•SS•••S••••
------------------------------
• [9.317 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/1438389208
<< End Captured StdOut/StdErr Output
------------------------------
S•••SS•S•••S•S••S
------------------------------
• [15.241 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/1308171403
<< End Captured StdOut/StdErr Output
------------------------------
•S•••S•••SS•••••••
------------------------------
• [22.275 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/493534243
<< End Captured StdOut/StdErr Output
------------------------------
S•••••••
------------------------------
• [51.795 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/676244859
<< End Captured StdOut/StdErr Output
------------------------------
••S•S
------------------------------
• [10.432 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/1396164877
<< End Captured StdOut/StdErr Output
------------------------------
••••••••••
------------------------------
• [SLOW TEST] [213.352 seconds]
odo dev command tests when java-springboot application is created and running odo dev when Update the devfile.yaml when compare the local and remote files localFiles and remoteFiles should match
/go/odo_1/tests/integration/cmd_dev_test.go:2177
------------------------------
•••••••••••S••••••••
------------------------------
• [18.847 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/972810895
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [140.111 seconds]
odo dev command tests when Starting a PostgreSQL service when creating local files and dir and running odo dev - without metadata.name when deleting local files and dir and waiting for sync should not list deleted dir and file in container
/go/odo_1/tests/integration/cmd_dev_test.go:995
------------------------------
••
------------------------------
• [7.966 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/3832227649
<< End Captured StdOut/StdErr Output
------------------------------
•••••••••S•••••S•••
------------------------------
• [20.545 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/1318004807
<< End Captured StdOut/StdErr Output
------------------------------
•••••••
------------------------------
• [10.746 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/2514080662
<< End Captured StdOut/StdErr Output
------------------------------
•••••••••S•••••
------------------------------
• [SLOW TEST] [218.188 seconds]
odo dev command tests when java-springboot application is created and running odo dev when Update the devfile.yaml Should build the application successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2126
------------------------------
••••
------------------------------
• [16.893 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/3784329478
<< End Captured StdOut/StdErr Output
------------------------------
SSSS•
------------------------------
• [SLOW TEST] [137.799 seconds]
odo dev command tests when Starting a PostgreSQL service when creating local files and dir and running odo dev - without metadata.name should correctly propagate changes to the container
/go/odo_1/tests/integration/cmd_dev_test.go:978
------------------------------
•S•
------------------------------
• [3.102 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/2969768174
<< End Captured StdOut/StdErr Output
------------------------------
•••S••S•••S•S••••••••
------------------------------
• [4.261 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/1641413321
<< End Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [SLOW TEST] [127.301 seconds]
odo dev command tests when a component with multiple endpoints is run when odo dev is stopped should remove forwarded ports from state file
/go/odo_1/tests/integration/cmd_dev_test.go:2447
------------------------------
••S•••••••••••S••••••••S••SS
------------------------------
• [23.526 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/1916152265
<< End Captured StdOut/StdErr Output
------------------------------
•••••S•
------------------------------
• [9.499 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/3964885604
<< End Captured StdOut/StdErr Output
------------------------------
•••••••••••••••
Ran 348 of 413 Specs in 1028.793 seconds
SUCCESS! -- 348 Passed | 0 Failed | 0 Pending | 65 Skipped
Ginkgo ran 1 suite in 18m22.934570284s
Test Suite Passed
go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo --randomize-all --slow-spec-threshold=120s -timeout 14400s --no-color -nodes=16 --junit-report="test-e2e.xml" tests/e2escenarios
Running Suite: odo e2e scenarios - /go/odo_1/tests/e2escenarios
===============================================================
Random Seed: 1669051260 - will randomize all specs
Will run 6 of 6 specs
Running in parallel across 16 processes
••
------------------------------
• [SLOW TEST] [130.767 seconds]
odo devfile supported tests odo debug support for devfile components Verify output debug information for java-maven debug works
/go/odo_1/tests/e2escenarios/e2e_devfile_test.go:77
------------------------------
• [SLOW TEST] [130.779 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] [142.801 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/3181095141
Spawning '/go/bin/odo delete component' from /tmp/3181095141
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [148.704 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/1906217740
Spawning '/go/bin/odo delete component' from /tmp/1906217740
<< End Captured StdOut/StdErr Output
------------------------------
Ran 6 of 6 Specs in 148.767 seconds
SUCCESS! -- 6 Passed | 0 Failed | 0 Pending | 0 Skipped
Ginkgo ran 1 suite in 2m52.618629415s
Test Suite Passed