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=f423ed0e3" ./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: 1677854288 - will randomize all specs Will run 422 of 771 specs Running in parallel across 16 processes SSSSSSSSSSSSSSSSSSSSSSSS••S•••••SS•••SS•••S••••• ------------------------------ • [20.306 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:206 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports --no-watch' from /tmp/4205910314 << End Captured StdOut/StdErr Output ------------------------------ S••••SS• ------------------------------ • [17.187 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/1555428105 << End Captured StdOut/StdErr Output ------------------------------ S• ------------------------------ S [SKIPPED] [2.959 seconds] odo dev command tests /go/odo_1/tests/integration/cmd_dev_test.go:33 using Kubernetes cluster [BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:2646 should run odo dev successfully on default namespace /go/odo_1/tests/integration/cmd_dev_test.go:2652 Begin Captured GinkgoWriter Output >> Created dir: /tmp/482913817 Created dir: /tmp/3826393992 Setting KUBECONFIG=/tmp/3826393992/config Creating a new project: cmd-dev-test2652cyr Running oc with args [oc new-project cmd-dev-test2652cyr] and odo env: [] [oc] Now using project "cmd-dev-test2652cyr" 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-test2652cyr] 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] I0303 14:40:35.138649 14133 util.go:776] HTTPGetRequest: https://raw.githubusercontent.com/redhat-developer/odo/main/build/VERSION [odo] I0303 14:40:35.154039 14133 implem.go:109] The path for preference file is /tmp/3826393992/preference.yaml [odo] I0303 14:40:35.154710 14133 util.go:797] Response will be cached in /tmp/odohttpcache for 1h0m0s [odo] I0303 14:40:35.155275 14133 util.go:810] Cached response used. [odo] Successfully removed registry [odo] I0303 14:40:35.156028 14133 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] I0303 14:40:35.432233 14159 implem.go:109] The path for preference file is /tmp/3826393992/preference.yaml [odo] I0303 14:40:35.432289 14159 util.go:797] Response will be cached in /tmp/odohttpcache for 1h0m0s [odo] New registry successfully added [odo] I0303 14:40:35.433745 14159 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :) Setting current dir to: /tmp/482913817 Deleting project: cmd-dev-test2652cyr Running oc with args [oc delete project cmd-dev-test2652cyr --wait=false] and odo env: [] [oc] project.project.openshift.io "cmd-dev-test2652cyr" deleted Setting current dir to: /go/odo_1/tests/integration Deleting dir: /tmp/482913817 Deleting dir: /tmp/3826393992 << End Captured GinkgoWriter Output This is a Kubernetes specific scenario, skipping In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:2648 ------------------------------ ••SSS•SS• ------------------------------ • [16.484 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/1779466470 << End Captured StdOut/StdErr Output ------------------------------ S••S•S••S•S• ------------------------------ • [14.715 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/3065492403 << End Captured StdOut/StdErr Output ------------------------------ •SSSS•••S••SS•S•SS•S•••SSSS•• ------------------------------ • [4.668 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/2885921554 << End Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [10.832 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/954697385 << End Captured StdOut/StdErr Output ------------------------------ SSSS••S• ------------------------------ • [SLOW TEST] [121.030 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:759 ------------------------------ •SS••SS••S ------------------------------ • [21.368 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/421702895 << End Captured StdOut/StdErr Output ------------------------------ • [31.313 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:76 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports' from /tmp/1813736966 << End Captured StdOut/StdErr Output ------------------------------ ••••••••S•••S••••SS••••SSS•••SSSSS•S••S•SSS• ------------------------------ • [28.544 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/2873872676 << End Captured StdOut/StdErr Output ------------------------------ •S••SS•SSS•SSS•••SS•••S•S•SSSS••S•S•••S••SSSS•• ------------------------------ • [10.750 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/701410293 << End Captured StdOut/StdErr Output ------------------------------ •S•S•SSSSS•S•SS•S•••SS•SSSS••S••SS•••••S•SSSSSS•SS••S•SSSSS•SS• ------------------------------ • [SLOW TEST] [136.472 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:759 ------------------------------ •••••S•SS••SS•SSS•••S•S••S•• ------------------------------ • [12.170 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/2783716464 << End Captured StdOut/StdErr Output ------------------------------ ••••••••S••S••SS•S•••••SS ------------------------------ • [SLOW TEST] [201.544 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:2530 ------------------------------ S••S•SS•S•S•SS ------------------------------ • [SLOW TEST] [127.175 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:3002 ------------------------------ SS••S•S• ------------------------------ • [12.773 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/2684383867 << End Captured StdOut/StdErr Output ------------------------------ •••SSS ------------------------------ • [14.706 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/1290043653 << End Captured StdOut/StdErr Output ------------------------------ • [14.171 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/277275390 << End Captured StdOut/StdErr Output ------------------------------ ••S•S•SSSSSSS•••••••S ------------------------------ • [4.335 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/1169660680 << End Captured StdOut/StdErr Output ------------------------------ • [11.864 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/3862264689 << End Captured StdOut/StdErr Output ------------------------------ •••SSSS•S•SS ------------------------------ • [SLOW TEST] [125.291 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:787 ------------------------------ •S•S ------------------------------ • [21.591 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:112 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports' from /tmp/3821332515 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [148.987 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:1615 ------------------------------ S• ------------------------------ • [SLOW TEST] [154.713 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:1231 ------------------------------ S•S•••••• ------------------------------ • [17.402 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/3323529636 << End Captured StdOut/StdErr Output ------------------------------ S• ------------------------------ • [29.897 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/457858826 << End Captured StdOut/StdErr Output ------------------------------ SS•S••••S••••S•S•SS•SSSS••SS ------------------------------ • [19.212 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/2439360061 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [160.038 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:2475 ------------------------------ •S••••SS•S••S••SS•SSSSS••SS••S••••SSS ------------------------------ • [SLOW TEST] [148.185 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 ------------------------------ S•SSS• ------------------------------ • [15.495 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/3092483361 << End Captured StdOut/StdErr Output ------------------------------ •S•SS•SS ------------------------------ • [11.805 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:164 Begin Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports' from /tmp/227007879 << End Captured StdOut/StdErr Output ------------------------------ •••SSS••SS••SS••••S•S•S••••S••S•SSSS ------------------------------ • [4.755 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/776833358 << End Captured StdOut/StdErr Output ------------------------------ ••S•••••S•SSSS••S•S••S•SS ------------------------------ • [8.799 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/3308186414 << End Captured StdOut/StdErr Output ------------------------------ S••S•SSS ------------------------------ • [SLOW TEST] [124.476 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:108 ------------------------------ SS••SS•••S•SS••••SS••••••SS••SSS•SSS•S•S••SS••S•••••SS••S•SSS•S••S•S••••SS ------------------------------ • [24.919 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/2490310522 << End Captured StdOut/StdErr Output ------------------------------ •••S•••SS•SSS•SSSS••••SSSSS•SSS•• ------------------------------ • [12.794 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/2103230947 << End Captured StdOut/StdErr Output ------------------------------ •S••S•SS ------------------------------ • [25.572 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/3512557271 << End Captured StdOut/StdErr Output ------------------------------ S•S•S ------------------------------ • [4.656 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/1774595255 << End Captured StdOut/StdErr Output ------------------------------ S••SS•••S••••S•S•••••S•S•S•SS•SSS•••S••••••••••••••• Ran 421 of 771 Specs in 1258.211 seconds SUCCESS! -- 421 Passed | 0 Failed | 0 Pending | 350 Skipped Ginkgo ran 1 suite in 21m59.527346646s 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: 1677855614 - will randomize all specs Will run 7 of 7 specs Running in parallel across 16 processes • ------------------------------ • [SLOW TEST] [139.751 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] [139.821 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.705 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] [152.601 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/395066428 Spawning '/go/bin/odo delete component' from /tmp/395066428 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [153.520 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/24005299 Spawning '/go/bin/odo delete component' from /tmp/24005299 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [169.538 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/2870051246 << End Captured StdOut/StdErr Output ------------------------------ Ran 7 of 7 Specs in 169.592 seconds SUCCESS! -- 7 Passed | 0 Failed | 0 Pending | 0 Skipped Ginkgo ran 1 suite in 3m5.711164271s Test Suite Passed