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=3da82397a" ./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: 1675339303 - will randomize all specs
Will run 419 of 762 specs
Running in parallel across 16 processes
SSSSSSSSSSSSSS•S•••SS•SS••
------------------------------
• [24.899 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/4093103290
<< End Captured StdOut/StdErr Output
------------------------------
S••••SS•S•••S•SS••S••••S•S••S••
------------------------------
• [34.719 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/1354731369
<< End Captured StdOut/StdErr Output
------------------------------
S••S•S••••S•••
------------------------------
• [20.288 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/652413192
<< End Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [22.066 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/10112849
<< End Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [SLOW TEST] [129.332 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:748
------------------------------
•SS•S•S••SSS••••SS•
------------------------------
• [10.880 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/730577766
<< End Captured StdOut/StdErr Output
------------------------------
S•S•S••••SSS••S•••S•••••SS•••S•••SSSS••••••SS••S••••S•SSS•SS•SS•S•S
------------------------------
• [SLOW TEST] [139.153 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:2515
------------------------------
S••S••SS•S•••SSSS•S•SS•S•SS•SSSSSS••SSSS••SS•••S••SS•SS•••SS•S••S••S•SS•••SS•S••S••
------------------------------
• [26.650 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/3148182727
<< End Captured StdOut/StdErr Output
------------------------------
S•••S•••••SSSS•S•SSS•SS•••S•SSS•S••S•••••S••••S
------------------------------
• [SLOW TEST] [144.729 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:1220
------------------------------
•SSSS••••SSSS••SSS•SS••SS•
------------------------------
• [15.439 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/3646494060
<< End Captured StdOut/StdErr Output
------------------------------
S•
------------------------------
• [16.787 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/3383024588
<< End Captured StdOut/StdErr Output
------------------------------
•••••SS•S••SS••S•S•S
------------------------------
• [19.345 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/737014351
<< End Captured StdOut/StdErr Output
------------------------------
••S••SS••S•SSSS•SS•SSS•••
------------------------------
• [22.172 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/597789547
<< End Captured StdOut/StdErr Output
------------------------------
•••S•S•••••••S••SS•S•••••••SSS•SSS•S••
------------------------------
• [17.948 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/1673907914
<< End Captured StdOut/StdErr Output
------------------------------
SS•••••S
------------------------------
• [32.927 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/651502024
<< End Captured StdOut/StdErr Output
------------------------------
SSSS••S••S•
------------------------------
• [4.280 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/2538188066
<< End Captured StdOut/StdErr Output
------------------------------
•SS•SS••S•S
------------------------------
S [SKIPPED] [2.316 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:2635
should run odo dev successfully on default namespace
/go/odo_1/tests/integration/cmd_dev_test.go:2641
Begin Captured GinkgoWriter Output >>
Created dir: /tmp/688959749
Created dir: /tmp/336798395
Setting KUBECONFIG=/tmp/336798395/config
Creating a new project: cmd-dev-test2641mtm
Running oc with args [oc new-project cmd-dev-test2641mtm] and odo env: []
[oc] Now using project "cmd-dev-test2641mtm" 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-test2641mtm] 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] I0202 12:14:17.062713 1667 implem.go:109] The path for preference file is /tmp/336798395/preference.yaml
[odo] I0202 12:14:17.062996 1667 util.go:797] Response will be cached in /tmp/odohttpcache for 1h0m0s
[odo] Successfully removed registry
[odo] I0202 12:14:17.064437 1667 util.go:810] Cached response used.
[odo] I0202 12:14:17.064548 1667 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] I0202 12:14:17.210547 1674 implem.go:109] The path for preference file is /tmp/336798395/preference.yaml
[odo] I0202 12:14:17.210862 1674 util.go:797] Response will be cached in /tmp/odohttpcache for 1h0m0s
[odo] I0202 12:14:17.211847 1674 util.go:810] Cached response used.
[odo] New registry successfully added
[odo] I0202 12:14:17.212544 1674 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :)
Setting current dir to: /tmp/688959749
Deleting project: cmd-dev-test2641mtm
Running oc with args [oc delete project cmd-dev-test2641mtm --wait=false] and odo env: []
[oc] project.project.openshift.io "cmd-dev-test2641mtm" deleted
Setting current dir to: /go/odo_1/tests/integration
Deleting dir: /tmp/688959749
Deleting dir: /tmp/336798395
<< End Captured GinkgoWriter Output
This is a Kubernetes specific scenario, skipping
In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:2637
------------------------------
•••S•
------------------------------
• [27.329 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/2629234063
<< End Captured StdOut/StdErr Output
------------------------------
•••SSS•••SS••SS
------------------------------
• [SLOW TEST] [130.935 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:278
------------------------------
•••S•SS•••S•SS•S•••SSSS••S
------------------------------
• [19.967 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/4070483019
<< End Captured StdOut/StdErr Output
------------------------------
•••S
------------------------------
• [18.172 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/3939659830
<< End Captured StdOut/StdErr Output
------------------------------
SS••SSSS•SS•
------------------------------
• [19.281 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/1021753031
<< End Captured StdOut/StdErr Output
------------------------------
••SSS•SS•S
------------------------------
• [24.506 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/101808441
<< End Captured StdOut/StdErr Output
------------------------------
SSSSSSS•S•S
------------------------------
• [18.842 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/1992041235
<< End Captured StdOut/StdErr Output
------------------------------
•S
------------------------------
• [SLOW TEST] [171.164 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:2460
------------------------------
••S••SSSSS•••S•••S•S•S••S•S•SS••SSS
------------------------------
• [74.005 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/4240761160
<< End Captured StdOut/StdErr Output
------------------------------
S•S•SSSS••SSSSS•••••
------------------------------
• [SLOW TEST] [129.082 seconds]
odo remove binding command tests when the component with binding is bootstrapped when odo dev is running when binding is removed should have led odo dev to delete ServiceBinding from the cluster
/go/odo_1/tests/integration/cmd_remove_binding_test.go:68
------------------------------
S•••S•S••S••••SS•••S•SS•S•S•S••
------------------------------
• [5.366 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/2730349329
<< End Captured StdOut/StdErr Output
------------------------------
S•SSSS•SSSSS•SS•
------------------------------
• [5.455 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/2493877355
<< End Captured StdOut/StdErr Output
------------------------------
SS••••
------------------------------
• [15.015 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/1548245382
<< End Captured StdOut/StdErr Output
------------------------------
•SSS•
------------------------------
• [15.147 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/3030831135
<< End Captured StdOut/StdErr Output
------------------------------
••S••
------------------------------
• [4.457 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/2028554748
<< End Captured StdOut/StdErr Output
------------------------------
•••S•••SS••SSS•••
------------------------------
• [22.698 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/1122491522
<< End Captured StdOut/StdErr Output
------------------------------
•SSSS••SSS•
------------------------------
• [41.821 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/1486418281
<< End Captured StdOut/StdErr Output
------------------------------
•SSS••••S•SS••S•S•••S•S••SS•SSS••SS•••S•S•
------------------------------
• [17.530 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/3465161722
<< End Captured StdOut/StdErr Output
------------------------------
SSSSS••••••
------------------------------
• [SLOW TEST] [131.225 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:260
------------------------------
••••••••••
Ran 418 of 762 Specs in 1232.953 seconds
SUCCESS! -- 418 Passed | 0 Failed | 0 Pending | 344 Skipped
Ginkgo ran 1 suite in 21m36.461971004s
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: 1675340607 - will randomize all specs
Will run 7 of 7 specs
Running in parallel across 16 processes
••
------------------------------
• [SLOW TEST] [128.468 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] [138.566 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.499 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/3788360846
Spawning '/go/bin/odo delete component' from /tmp/3788360846
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [149.563 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/3069055655
Spawning '/go/bin/odo delete component' from /tmp/3069055655
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [168.308 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/1270723737
<< End Captured StdOut/StdErr Output
------------------------------
Ran 7 of 7 Specs in 168.419 seconds
SUCCESS! -- 7 Passed | 0 Failed | 0 Pending | 0 Skipped
Ginkgo ran 1 suite in 3m5.387123414s
Test Suite Passed