Error from server (NotFound): namespaces "devfile-proxy" not found
Using Devfile proxy:
go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=11c02cdac" ./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="!unauth && !nocluster && !podman" tests/integration
Running Suite: Integration Suite - /go/odo_1/tests/integration
==============================================================
Random Seed: 1675722225 - will randomize all specs
Will run 421 of 769 specs
Running in parallel across 16 processes
SSSSSSS•SSSSSSSSSS•SSSS•S••S•
------------------------------
• [21.948 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:180
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/2167327592
<< End Captured StdOut/StdErr Output
------------------------------
•SSS•S••SS•S•••S•SSS
------------------------------
• [17.833 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:378
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/2176331708
<< End Captured StdOut/StdErr Output
------------------------------
SS•SS••S••SS••SSS••••SS••••S••S••S•S••S•••S
------------------------------
• [10.136 seconds]
odo dev interactive command tests directory is not empty when Alizer cannot determine a Devfile based on the current source code should not fail but fallback to the interactive mode
/go/odo_1/tests/integration/interactive_dev_test.go:155
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo dev --random-ports' from /tmp/3679427923
<< End Captured StdOut/StdErr Output
------------------------------
•S•SS••••••S•SSSSSS•S•
------------------------------
• [32.956 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:257
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/3181577546
<< End Captured StdOut/StdErr Output
------------------------------
S••S
------------------------------
• [SLOW TEST] [120.469 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 react on the Devfile modification
/go/odo_1/tests/integration/cmd_dev_test.go:760
------------------------------
•SSS••S•SSSSS•••••S•••S••SSSS•S•SSSS
------------------------------
• [25.298 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:577
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/1114713657
<< End Captured StdOut/StdErr Output
------------------------------
•••SS
------------------------------
• [18.667 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:463
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/2967470220
<< End Captured StdOut/StdErr Output
------------------------------
•S••S•S•S•SSSSSS•SS••••••SSS•S•SSS•S•SS•S••SSSS
------------------------------
• [24.613 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:378
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/1793955466
<< End Captured StdOut/StdErr Output
------------------------------
•S•S•S
------------------------------
• [29.888 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:463
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/1549561651
<< End Captured StdOut/StdErr Output
------------------------------
S••SSS•S
------------------------------
• [22.446 seconds]
odo dev interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile successfully even with -v flag
/go/odo_1/tests/integration/interactive_dev_test.go:40
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo dev --random-ports -v 4' from /tmp/3553087624
<< End Captured StdOut/StdErr Output
------------------------------
SS•••S
------------------------------
• [5.582 seconds]
odo deploy interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile
/go/odo_1/tests/integration/interactive_deploy_test.go:75
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo deploy' from /tmp/1570090303
<< End Captured StdOut/StdErr Output
------------------------------
SS•
------------------------------
• [26.174 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:180
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/1891304091
<< End Captured StdOut/StdErr Output
------------------------------
••••SS•SSS•S••SS••SS•S•S••SSSS•••SS••S•SS••S•S•S••SS•SSS•SSS•S•S•S••S•S•••S•SS••S•
------------------------------
• [SLOW TEST] [169.053 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:1232
------------------------------
•SS
------------------------------
• [22.524 seconds]
odo dev interactive command tests directory is not empty when there is a match from Alizer should display welcoming messages first
/go/odo_1/tests/integration/interactive_dev_test.go:106
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo dev --random-ports' from /tmp/4070035610
<< End Captured StdOut/StdErr Output
------------------------------
SS••SSSSSS•SSSSSSSSS•••S•S•S•
------------------------------
• [4.876 seconds]
odo deploy interactive command tests directory is not empty when Alizer cannot determine a Devfile based on the current source code should not fail but fallback to the interactive mode
/go/odo_1/tests/integration/interactive_deploy_test.go:159
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo deploy' from /tmp/1117772836
<< End Captured StdOut/StdErr Output
------------------------------
•••SSS••••S•SS••SS••••••••••••S••S••••SS•S•••S•S•S••••••••SSSSS••S••
------------------------------
• [20.012 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:311
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/2423991474
<< End Captured StdOut/StdErr Output
------------------------------
•••••••S••S•S•••S•••SS•S•S•S•
------------------------------
• [21.361 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:131
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/1005155622
<< End Captured StdOut/StdErr Output
------------------------------
S••
------------------------------
• [20.120 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:378
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/3987715919
<< End Captured StdOut/StdErr Output
------------------------------
SS•••••SSS•SSS••S••S••SS•SSSSS••SS••
------------------------------
• [13.075 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:463
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/2489304796
<< End Captured StdOut/StdErr Output
------------------------------
•SSS•S
------------------------------
• [17.573 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:194
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo dev --random-ports --no-watch' from /tmp/3270799939
<< End Captured StdOut/StdErr Output
------------------------------
•SSS••S••••SSS•S••SSSSSS•SS•••••
------------------------------
• [13.242 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:73
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/4241356192
<< End Captured StdOut/StdErr Output
------------------------------
•••••SS•SSSS•
------------------------------
• [3.938 seconds]
odo deploy interactive command tests directory is not empty when there is a match from Alizer should display welcoming messages first
/go/odo_1/tests/integration/interactive_deploy_test.go:109
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo deploy' from /tmp/1865194000
<< End Captured StdOut/StdErr Output
------------------------------
••SS
------------------------------
• [SLOW TEST] [147.089 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:2531
------------------------------
•S•S•S•SS••SS•S•••••SS•SS•••S••••SS•
------------------------------
• [SLOW TEST] [168.340 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:2476
------------------------------
•S•SS
------------------------------
• [14.129 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:101
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/2197864288
<< End Captured StdOut/StdErr Output
------------------------------
S•S•
------------------------------
• [SLOW TEST] [148.148 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:1232
------------------------------
SS••SSS•SSS•••
------------------------------
• [32.209 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:591
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/3200710783
<< End Captured StdOut/StdErr Output
------------------------------
•SSS•S•SSS•S
------------------------------
• [4.109 seconds]
odo deploy interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile successfully even with -v flag
/go/odo_1/tests/integration/interactive_deploy_test.go:40
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo deploy -v 4' from /tmp/3483608648
<< End Captured StdOut/StdErr Output
------------------------------
S•S•S•••••••••••S•S••••SS•S
------------------------------
S [SKIPPED] [1.942 seconds]
odo dev command tests
/go/odo_1/tests/integration/cmd_dev_test.go:34
using Kubernetes cluster [BeforeEach]
/go/odo_1/tests/integration/cmd_dev_test.go:2651
should run odo dev successfully on default namespace
/go/odo_1/tests/integration/cmd_dev_test.go:2657
Begin Captured GinkgoWriter Output >>
Created dir: /tmp/1897613904
Created dir: /tmp/2403198764
Setting KUBECONFIG=/tmp/2403198764/config
Creating a new project: cmd-dev-test2657gmd
Running oc with args [oc new-project cmd-dev-test2657gmd] and odo env: []
[oc] Now using project "cmd-dev-test2657gmd" 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/e2e-test-images/agnhost:2.33 -- /agnhost 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-test2657gmd] 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] I0206 22:40:42.713560 10893 implem.go:109] The path for preference file is /tmp/2403198764/preference.yaml
[odo] I0206 22:40:42.713701 10893 util.go:797] Response will be cached in /tmp/odohttpcache for 1h0m0s
[odo] Successfully removed registry
[odo] I0206 22:40:42.714737 10893 util.go:810] Cached response used.
[odo] I0206 22:40:42.715170 10893 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 https://registry.stage.devfile.io] and odo env: []
[odo] I0206 22:40:42.853038 10900 implem.go:109] The path for preference file is /tmp/2403198764/preference.yaml
[odo] I0206 22:40:42.853475 10900 util.go:810] Cached response used.
[odo] New registry successfully added
[odo] I0206 22:40:42.854416 10900 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :)
Setting current dir to: /tmp/1897613904
Deleting project: cmd-dev-test2657gmd
Running oc with args [oc delete project cmd-dev-test2657gmd --wait=false] and odo env: []
[oc] project.project.openshift.io "cmd-dev-test2657gmd" deleted
Setting current dir to: /go/odo_1/tests/integration
Deleting dir: /tmp/1897613904
Deleting dir: /tmp/2403198764
<< End Captured GinkgoWriter Output
This is a Kubernetes specific scenario, skipping
In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:2653
------------------------------
••SS•SSS•S
------------------------------
• [11.556 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:180
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/1507864525
<< End Captured StdOut/StdErr Output
------------------------------
•S••S•••SS••S••SSS•S
------------------------------
• [22.567 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:131
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/3207512325
<< End Captured StdOut/StdErr Output
------------------------------
S•S•
------------------------------
• [15.257 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:131
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/2296238221
<< End Captured StdOut/StdErr Output
------------------------------
••••S•S•••S•S••••••••••SSS•••••SS••S••S•••S•S•
------------------------------
• [21.396 seconds]
odo dev interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile
/go/odo_1/tests/integration/interactive_dev_test.go:73
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo dev --random-ports' from /tmp/2258596008
<< End Captured StdOut/StdErr Output
------------------------------
SS•SS••
------------------------------
• [22.136 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:242
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/4044725415
<< End Captured StdOut/StdErr Output
------------------------------
S•••••••••••••••
Ran 420 of 769 Specs in 1178.240 seconds
SUCCESS! -- 420 Passed | 0 Failed | 0 Pending | 349 Skipped
Ginkgo ran 1 suite in 20m42.149938354s
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: 1675723474 - will randomize all specs
Will run 7 of 7 specs
Running in parallel across 16 processes
•
------------------------------
• [118.321 seconds]
E2E Test starting with non-empty Directory add Binding should verify developer workflow of using binding as env in innerloop
/go/odo_1/tests/e2escenarios/e2e_test.go:337
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo init' from /tmp/2472783789
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [SLOW TEST] [128.004 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] [128.397 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] [141.714 seconds]
E2E Test starting with non-empty Directory should verify developer workflow from non-empty Directory
/go/odo_1/tests/e2escenarios/e2e_test.go:180
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo init' from /tmp/2949706176
Spawning '/go/bin/odo delete component' from /tmp/2949706176
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [149.846 seconds]
E2E Test starting with empty Directory should verify developer workflow from empty Directory
/go/odo_1/tests/e2escenarios/e2e_test.go:55
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo init' from /tmp/1818723287
Spawning '/go/bin/odo delete component' from /tmp/1818723287
<< End Captured StdOut/StdErr Output
------------------------------
Ran 7 of 7 Specs in 149.899 seconds
SUCCESS! -- 7 Passed | 0 Failed | 0 Pending | 0 Skipped
Ginkgo ran 1 suite in 2m46.689975606s
Test Suite Passed