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=e48e03cf2" ./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: 1681824520 - will randomize all specs

Will run 457 of 816 specs
Running in parallel across 16 processes
SSSSSSSSSSSSSSS
------------------------------
• [14.458 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo deploy' from /tmp/2147042069
  << Captured StdOut/StdErr Output
------------------------------
•S•S
------------------------------
• [15.646 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo deploy -v 4' from /tmp/779994374
  << Captured StdOut/StdErr Output
------------------------------
•SS•S•SS••SSSSSS•S••S•
------------------------------
• [32.689 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo add binding' from /tmp/1087526516
  << Captured StdOut/StdErr Output
------------------------------
S•S••SS•••S
------------------------------
• [19.831 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo add binding' from /tmp/2964402015
  << Captured StdOut/StdErr Output
------------------------------
SS•
------------------------------
• [19.621 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo add binding' from /tmp/619265081
  << Captured StdOut/StdErr Output
------------------------------
•••SSS••S••••••
------------------------------
• [16.503 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo dev --random-ports --no-watch' from /tmp/255790382
  << Captured StdOut/StdErr Output
------------------------------
S••SSSSSS•••••••••S•S•S•S••S••••S•S•S••S•SS•SSS••S•••SS•S•••••S•SSSSS•••S•S••S•S••SS•S
------------------------------
• [19.079 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo dev --random-ports -v 4' from /tmp/1811786340
  << Captured StdOut/StdErr Output
------------------------------
•S
------------------------------
• [15.847 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo add binding' from /tmp/1836195782
  << Captured StdOut/StdErr Output
------------------------------
S••SS•S
------------------------------
• [10.438 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo dev --random-ports' from /tmp/410006778
  << Captured StdOut/StdErr Output
------------------------------
•S•S•S•
------------------------------
• [12.504 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo add binding' from /tmp/424444242
  << Captured StdOut/StdErr Output
------------------------------
• [11.019 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo add binding' from /tmp/649566344
  << Captured StdOut/StdErr Output
------------------------------
••S•SS•S•SS••••••S•S
------------------------------
• [11.408 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo add binding' from /tmp/1704446061
  << Captured StdOut/StdErr Output
------------------------------
• [10.442 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo add binding' from /tmp/2088834886
  << Captured StdOut/StdErr Output
------------------------------
••SS••S••••S•S•SS•••S•SS•S•SSS•S•S••••••••••S•SSSS•SS••••S•SSS••S••S•SS•••SSS•SSSSSS•S•SS••S•SS
------------------------------
• [20.015 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo dev --random-ports' from /tmp/394625874
  << Captured StdOut/StdErr Output
------------------------------
SS••S••S••SSS••••S•S•S••SS•••S•S•
------------------------------
• [10.162 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo add binding' from /tmp/35392168
  << Captured StdOut/StdErr Output
------------------------------
•••SS•S••SSS••SSS••S•••SS••SSS•S••S•••••S•••S•S•••S•SS••SSS
------------------------------
• [27.939 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo add binding' from /tmp/584696645
  << Captured StdOut/StdErr Output
------------------------------
•••S•SSS••S•••
------------------------------
• [20.174 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo add binding' from /tmp/3877941272
  << Captured StdOut/StdErr Output
------------------------------
S•••SS••S•••••
------------------------------
• [8.669 seconds]
odo init interactive command tests when DevfileRegistriesList CRD is installed on cluster when CR for devfileregistrieslists is installed in namespace should download correct devfile from the first in-cluster registry
/go/odo_1/tests/integration/interactive_init_test.go:635

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo init' from /tmp/881089020
  << Captured StdOut/StdErr Output
------------------------------
S••SSSS••
------------------------------
• [12.471 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo add binding' from /tmp/269683573
  << Captured StdOut/StdErr Output
------------------------------
••S•
------------------------------
• [12.139 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo add binding' from /tmp/4039927276
  << Captured StdOut/StdErr Output
------------------------------
••SSSSS••••S•S••SS•S••S••S••••SSSS••S•SS•SS•SS••SS••••S•S•••SS••S•S•S•SS••S•S•S•S••SSS•SS•SSSS•SS••SS•
------------------------------
• [24.718 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo add binding' from /tmp/3993566486
  << Captured StdOut/StdErr Output
------------------------------
•SS
------------------------------
• [15.874 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo add binding' from /tmp/1576177965
  << Captured StdOut/StdErr Output
------------------------------
•••••SS••••SSS•SSS•S••S•••S•••S•SSS•SS••••SSS
------------------------------
• [13.466 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo add binding' from /tmp/2701584712
  << Captured StdOut/StdErr Output
------------------------------
•SS•••SSS
------------------------------
• [12.100 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo add binding' from /tmp/1059617912
  << Captured StdOut/StdErr Output
------------------------------
•S•••S••S•SSSSSSS•S•••••S••S•••SSSSSS•••S••S••••••SSS••S•••SSSSSSS
------------------------------
• [12.619 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo add binding' from /tmp/2045437156
  << Captured StdOut/StdErr Output
------------------------------
S•SS•SS••••S•••SS•••
------------------------------
• [3.179 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo deploy' from /tmp/3965838383
  << Captured StdOut/StdErr Output
------------------------------
•S•SS•S•S•S•S•••S•S••S•S•••••SSS•S•S•••S•••SS••SSS••S••SS
------------------------------
• [2.925 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo deploy' from /tmp/790221382
  << Captured StdOut/StdErr Output
------------------------------
•••S••••S••S•SS••••S••S
------------------------------
• [22.635 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo add binding' from /tmp/4123838973
  << Captured StdOut/StdErr Output
------------------------------
••SS•SS•SSSS
------------------------------
• [16.437 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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo dev --random-ports' from /tmp/3859387804
  << Captured StdOut/StdErr Output
------------------------------
S•SSS••SSSSS•S••••••••••••••••

Ran 452 of 816 Specs in 1184.738 seconds
SUCCESS! -- 452 Passed | 0 Failed | 0 Pending | 364 Skipped


Ginkgo ran 1 suite in 20m51.484372442s
Test Suite Passed
You're using deprecated Ginkgo functionality:
=============================================
  --slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.

To silence deprecations that can be silenced set the following environment variable:
  ACK_GINKGO_DEPRECATIONS=2.6.0