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=de8deb1b3" ./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: 1670915269 - will randomize all specs
Will run 339 of 542 specs
Running in parallel across 16 processes
SSSSSSSSS••••
------------------------------
• [28.606 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/734808290
<< End Captured StdOut/StdErr Output
------------------------------
••S•S•••S•••SSS•S•••S••SS••••••••S•S•••••S•
------------------------------
• [8.251 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/3153594531
<< End Captured StdOut/StdErr Output
------------------------------
••••S•SS
------------------------------
• [SLOW TEST] [129.304 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:655
------------------------------
S
------------------------------
• [6.202 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/1257831359
<< End Captured StdOut/StdErr Output
------------------------------
• [17.350 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/454239685
<< End Captured StdOut/StdErr Output
------------------------------
• [19.652 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/336077834
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [15.735 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/3924330586
<< End Captured StdOut/StdErr Output
------------------------------
••••SS•S••••••••SS••S•SS•••••••••••S•••S••SS••S•S••S•SS•••S•
------------------------------
• [13.761 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/2674553711
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [32.509 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/364080797
<< End Captured StdOut/StdErr Output
------------------------------
SS•S••S•
------------------------------
• [SLOW TEST] [136.224 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•S•S••S•S•••••••SS•S•••••SSS•SS•S
------------------------------
• [25.335 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/2999473469
<< End Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [SLOW TEST] [120.880 seconds]
odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure
/go/odo_1/tests/integration/cmd_dev_test.go:709
------------------------------
SSSS••SSS••S••SS••
------------------------------
S [SKIPPED] [5.358 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:2350
should run odo dev successfully on default namespace
/go/odo_1/tests/integration/cmd_dev_test.go:2356
Begin Captured GinkgoWriter Output >>
Created dir: /tmp/1075479518
Created dir: /tmp/3988332854
Setting KUBECONFIG=/tmp/3988332854/config
Creating a new project: cmd-dev-test2356mhp
Running oc with args [oc new-project cmd-dev-test2356mhp] and odo env: []
[oc] Now using project "cmd-dev-test2356mhp" 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-test2356mhp] 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] I1213 07:15:29.622312 22785 implem.go:109] The path for preference file is /tmp/3988332854/preference.yaml
[odo] I1213 07:15:29.623065 22785 util.go:767] Cached response used.
[odo] Successfully removed registry
[odo] I1213 07:15:29.624871 22785 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] I1213 07:15:30.178644 22803 util.go:767] Cached response used.
[odo] I1213 07:15:30.178141 22803 implem.go:109] The path for preference file is /tmp/3988332854/preference.yaml
[odo] New registry successfully added
[odo] I1213 07:15:30.179901 22803 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :)
Setting current dir to: /tmp/1075479518
Deleting project: cmd-dev-test2356mhp
Running oc with args [oc delete project cmd-dev-test2356mhp --wait=false] and odo env: []
[oc] project.project.openshift.io "cmd-dev-test2356mhp" deleted
Setting current dir to: /go/odo_1/tests/integration
Deleting dir: /tmp/1075479518
Deleting dir: /tmp/3988332854
<< End Captured GinkgoWriter Output
This is a Kubernetes specific scenario, skipping
In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:2352
------------------------------
S•S••••SS•
------------------------------
• [14.898 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/432030955
<< End Captured StdOut/StdErr Output
------------------------------
S•
------------------------------
• [SLOW TEST] [180.791 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:2643
------------------------------
SSS•S•SSSS•SS•S••SS•S•••SS•SS
------------------------------
• [14.671 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/767410008
<< End Captured StdOut/StdErr Output
------------------------------
S•S•••••S•••
------------------------------
• [14.285 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/631615923
<< End Captured StdOut/StdErr Output
------------------------------
SS•S•S•••••SS••S••S••S•SS•••••S••SS••S•S••SSSSS••S•••••S••S•S•S••S••S•
------------------------------
• [5.186 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/2586352531
<< End Captured StdOut/StdErr Output
------------------------------
S•••S••SSS•••••S••S
------------------------------
• [22.559 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/1396136036
<< End Captured StdOut/StdErr Output
------------------------------
S•
------------------------------
• [22.192 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/775231615
<< End Captured StdOut/StdErr Output
------------------------------
•••
------------------------------
• [34.993 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/4211435856
<< End Captured StdOut/StdErr Output
------------------------------
• [22.351 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/3971836353
<< End Captured StdOut/StdErr Output
------------------------------
•••
------------------------------
• [13.870 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/374766591
<< End Captured StdOut/StdErr Output
------------------------------
•••S••S••••S•S
------------------------------
• [19.605 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/2428255818
<< End Captured StdOut/StdErr Output
------------------------------
•S•••S•S•
------------------------------
• [25.447 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/1938292298
<< End Captured StdOut/StdErr Output
------------------------------
•SSSSS•S•
------------------------------
• [SLOW TEST] [120.590 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:260
------------------------------
•
------------------------------
• [SLOW TEST] [123.114 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•S••S••S••SSSSSS••••S•SS•SSSS•S•S•S••S
------------------------------
• [19.552 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/1939289768
<< End Captured StdOut/StdErr Output
------------------------------
SSS•S•••SSSS•S•••SS••S•
------------------------------
• [29.782 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/2010848213
<< End Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [26.955 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/1149858100
<< End Captured StdOut/StdErr Output
------------------------------
••S••
------------------------------
• [13.724 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/3655864207
<< End Captured StdOut/StdErr Output
------------------------------
•••S••S••S•S•S••S•S•S•••S••S•
------------------------------
• [SLOW TEST] [194.675 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:2201
------------------------------
•S••
------------------------------
• [31.979 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/938580435
<< End Captured StdOut/StdErr Output
------------------------------
S•
------------------------------
• [32.568 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/1688246674
<< End Captured StdOut/StdErr Output
------------------------------
•S•S•
------------------------------
• [SLOW TEST] [124.528 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:2631
------------------------------
••••••••••••••
------------------------------
• [SLOW TEST] [160.950 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:2252
------------------------------
Ran 338 of 542 Specs in 1067.412 seconds
SUCCESS! -- 338 Passed | 0 Failed | 0 Pending | 204 Skipped
Ginkgo ran 1 suite in 18m47.704177242s
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: 1670916404 - will randomize all specs
Will run 7 of 7 specs
Running in parallel across 16 processes
•
------------------------------
• [SLOW TEST] [129.525 seconds]
odo devfile supported tests odo debug support for devfile components Verify output debug information for java-springboot works
/go/odo_1/tests/e2escenarios/e2e_devfile_test.go:71
------------------------------
• [SLOW TEST] [138.831 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] [147.501 seconds]
E2E Test starting with empty Directory should verify developer workflow from empty Directory
/go/odo_1/tests/e2escenarios/e2e_test.go:49
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo init' from /tmp/2918815538
Spawning '/go/bin/odo delete component' from /tmp/2918815538
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [152.482 seconds]
E2E Test starting with non-empty Directory should verify developer workflow from non-empty Directory
/go/odo_1/tests/e2escenarios/e2e_test.go:167
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo init' from /tmp/509259840
Spawning '/go/bin/odo delete component' from /tmp/509259840
<< End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [169.876 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] [171.089 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:321
Begin Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo init' from /tmp/3213720903
<< End Captured StdOut/StdErr Output
------------------------------
Ran 7 of 7 Specs in 171.433 seconds
SUCCESS! -- 7 Passed | 0 Failed | 0 Pending | 0 Skipped
Ginkgo ran 1 suite in 3m6.066190915s
Test Suite Passed