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=17e0292a8" ./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: 1677678409 - will randomize all specs Will run 426 of 778 specs Running in parallel across 16 processes SSSSSSSSSSSSSSSSSSS••S• ------------------------------ • [13.471 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/2434164657 << End Captured StdOut/StdErr Output ------------------------------ SSSS••••S••S ------------------------------ • [25.883 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/556953748 << End Captured StdOut/StdErr Output ------------------------------ • [24.094 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/529519804 << End Captured StdOut/StdErr Output ------------------------------ • [21.030 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/1482826852 << End Captured StdOut/StdErr Output ------------------------------ •SS•••S•••S•••SSS••S•••SS•S•••••SSSS•••S••• ------------------------------ • [26.707 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/2234138443 << End Captured StdOut/StdErr Output ------------------------------ S•S•SS• ------------------------------ • [18.092 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/1194077443 << End Captured StdOut/StdErr Output ------------------------------ S•SSSS••SSS•S ------------------------------ • [33.534 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/1300975386 << End Captured StdOut/StdErr Output ------------------------------ SSSS•SSSS•••S•• ------------------------------ • [SLOW TEST] [166.343 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•S•SSSS•SS• ------------------------------ • [24.106 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/2067371871 << End Captured StdOut/StdErr Output ------------------------------ S••S••••S••••S•••SSS•S••S••••S ------------------------------ • [52.426 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/2788570231 << End Captured StdOut/StdErr Output ------------------------------ •SS• ------------------------------ • [8.348 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/2319405947 << End Captured StdOut/StdErr Output ------------------------------ SS•S••••SSS•• ------------------------------ • [13.733 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/354619330 << End Captured StdOut/StdErr Output ------------------------------ •S••SS•S•SS•SSSSS•••SS•SS••SS•••• ------------------------------ • [SLOW TEST] [149.758 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•SS•S••S••SS•S•S••••••SSSSS•S•SSS•••S•S••••••••SSS•••••S•S••••••••S•••S••••S•SS•S••S ------------------------------ • [25.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/801894586 << End Captured StdOut/StdErr Output ------------------------------ •••S•••SS••••• ------------------------------ • [20.201 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/1135893243 << End Captured StdOut/StdErr Output ------------------------------ ••••S••S•S•SSS••SSS••••SS•SSS•••SSSS ------------------------------ • [14.170 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/2148872682 << End Captured StdOut/StdErr Output ------------------------------ SS•• ------------------------------ • [41.533 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/3325225579 << End Captured StdOut/StdErr Output ------------------------------ S•S••S•••S•S•SS•S••SS•S•••SS••••SSSS ------------------------------ • [16.241 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/3305799573 << End Captured StdOut/StdErr Output ------------------------------ •S ------------------------------ • [SLOW TEST] [134.089 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:109 ------------------------------ •S••• ------------------------------ • [15.342 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/2202226698 << End Captured StdOut/StdErr Output ------------------------------ S•••SS•S ------------------------------ • [16.259 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/292452472 << End Captured StdOut/StdErr Output ------------------------------ ••S•S•••••••SSSSSS••S•SS•SSS••SS•••••S•S•S••••S•SS• ------------------------------ • [SLOW TEST] [139.614 seconds] odo dev debug command tests when a composite apply command is used as debug command should execute the composite apply commands successfully /go/odo_1/tests/integration/cmd_dev_debug_test.go:248 ------------------------------ •S••SSS•••S•SS••S••SSSSSS•••S••SSSS•S••S•S•••S•• ------------------------------ • [SLOW TEST] [120.515 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 ------------------------------ SS••S•SSSSSSSS ------------------------------ • [10.878 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/3036246755 << End Captured StdOut/StdErr Output ------------------------------ S•S ------------------------------ S [SKIPPED] [3.666 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:2647 should run odo dev successfully on default namespace /go/odo_1/tests/integration/cmd_dev_test.go:2653 Begin Captured GinkgoWriter Output >> Created dir: /tmp/3518530828 Created dir: /tmp/3058550935 Setting KUBECONFIG=/tmp/3058550935/config Creating a new project: cmd-dev-test2653pse Running oc with args [oc new-project cmd-dev-test2653pse] and odo env: [] [oc] Now using project "cmd-dev-test2653pse" 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-test2653pse] 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] I0301 14:02:59.871178 7336 implem.go:109] The path for preference file is /tmp/3058550935/preference.yaml [odo] I0301 14:02:59.871911 7336 util.go:810] Cached response used. [odo] Successfully removed registry [odo] I0301 14:02:59.872756 7336 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] I0301 14:03:00.084041 7344 util.go:810] Cached response used. [odo] I0301 14:03:00.083541 7344 implem.go:109] The path for preference file is /tmp/3058550935/preference.yaml [odo] I0301 14:03:00.085002 7344 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :) [odo] New registry successfully added Setting current dir to: /tmp/3518530828 Deleting project: cmd-dev-test2653pse Running oc with args [oc delete project cmd-dev-test2653pse --wait=false] and odo env: [] [oc] project.project.openshift.io "cmd-dev-test2653pse" deleted Setting current dir to: /go/odo_1/tests/integration Deleting dir: /tmp/3518530828 Deleting dir: /tmp/3058550935 << End Captured GinkgoWriter Output This is a Kubernetes specific scenario, skipping In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:2649 ------------------------------ S•SSSSS•S•S•••S ------------------------------ • [45.507 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/897854578 << End Captured StdOut/StdErr Output ------------------------------ •SS•S•SSS•••S ------------------------------ • [5.771 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/1131029822 << End Captured StdOut/StdErr Output ------------------------------ •S•SS••SS•S••SS•S••S•S ------------------------------ • [18.317 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/1792734061 << End Captured StdOut/StdErr Output ------------------------------ S•S••SS•SS•SS•S•••••• ------------------------------ • [21.200 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/3427490226 << End Captured StdOut/StdErr Output ------------------------------ S••S•SS•S••S••••••SSS•S•S•S•S•SS•• ------------------------------ • [24.324 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/3991058908 << End Captured StdOut/StdErr Output ------------------------------ •SSS•S•SSS•SS••S••SS•SSSS•SSSSSSS•••• ------------------------------ • [SLOW TEST] [124.025 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 ------------------------------ •SS••S•• ------------------------------ • [18.302 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/322296160 << End Captured StdOut/StdErr Output ------------------------------ S••SSS•SS•••SSSS•S•S•••S•SSSS•SS••SSS ------------------------------ • [23.145 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/4284061759 << End Captured StdOut/StdErr Output ------------------------------ SS•SS•S ------------------------------ • [24.910 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/1635654639 << End Captured StdOut/StdErr Output ------------------------------ •••• ------------------------------ • [24.190 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/2155439554 << End Captured StdOut/StdErr Output ------------------------------ •••S••••• ------------------------------ • [SLOW TEST] [165.645 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 ------------------------------ ••••••• ------------------------------ • [SLOW TEST] [137.513 seconds] odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-ywj") 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 ------------------------------ ••• Ran 425 of 778 Specs in 1328.245 seconds SUCCESS! -- 425 Passed | 0 Failed | 0 Pending | 353 Skipped Ginkgo ran 1 suite in 23m12.440393871s 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: 1677679808 - will randomize all specs Will run 7 of 7 specs Running in parallel across 16 processes •• ------------------------------ • [SLOW TEST] [129.868 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] [130.102 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] [144.839 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/1188740648 Spawning '/go/bin/odo delete component' from /tmp/1188740648 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [162.787 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/2362296332 Spawning '/go/bin/odo delete component' from /tmp/2362296332 << End Captured StdOut/StdErr Output ------------------------------ • [SLOW TEST] [179.918 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/595277947 << End Captured StdOut/StdErr Output ------------------------------ Ran 7 of 7 Specs in 180.005 seconds SUCCESS! -- 7 Passed | 0 Failed | 0 Pending | 0 Skipped Ginkgo ran 1 suite in 3m16.087548332s Test Suite Passed