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=21614bce8" ./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: 1683819296 - will randomize all specs

Will run 495 of 887 specs
Running in parallel across 16 processes
SSSSSSSSSSSS•S••S•SSS•••S••SS•••SSS•SS••S
------------------------------
• [17.994 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/1892593202
  << Captured StdOut/StdErr Output
------------------------------
•SSSSS
------------------------------
• [41.065 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/1158414218
  << Captured StdOut/StdErr Output
------------------------------
S•S••S••••••S••S•SS•••SSSSSSSS••S••S••SSSS•SSS••S
------------------------------
• [10.527 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/1986336555
  << Captured StdOut/StdErr Output
------------------------------
SSS•S••SS•SSSS••••SSS•
------------------------------
• [78.026 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/1250026754
  << Captured StdOut/StdErr Output
------------------------------
••••S•SSS••S••S
------------------------------
• [78.124 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/1667624299
  << Captured StdOut/StdErr Output
------------------------------
•••S•••S•S••S•••••S••S•••••SSSSS•SS••S••S••SSSS•SS••SS••S•S•S••SS•S•••SS••S••S•S••S•SS••S•••••S••S••S••S••SSSSS•S•S••S•••SS•S••SS••SS•S••••SS••
------------------------------
• [2.937 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/2444569481
  << Captured StdOut/StdErr Output
------------------------------
•S••SS•S
------------------------------
• [17.959 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/2213430873
  << Captured StdOut/StdErr Output
------------------------------
• [9.688 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/2536762072
  << Captured StdOut/StdErr Output
------------------------------
SSSSSS••S••
------------------------------
• [8.487 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/3946390595
  << Captured StdOut/StdErr Output
------------------------------
••S•S•S•S•••S••S•••••••S••SSSSS
------------------------------
• [19.006 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/1467408377
  << Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [10.414 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/568802682
  << Captured StdOut/StdErr Output
------------------------------
S•S••SS•SSS••SSSS••S••S•S•S•S•••••••S
------------------------------
• [17.542 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/3211821312
  << Captured StdOut/StdErr Output
------------------------------
S•S•••••SSSS••S
------------------------------
• [10.815 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/391406333
  << Captured StdOut/StdErr Output
------------------------------
••SSS•S•S••SS••S•SS•••••S•SSS•••SS•S••••SS•SS••••SS•S•••S•SS•SS•S•S••
------------------------------
• [5.804 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:712

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo init' from /tmp/2062185013
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [77.320 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/4292371195
  << Captured StdOut/StdErr Output
------------------------------
••SS•••S••SS•S•SSSSS••SS••SS•S•S••••••S•SSS••S••S•••••••SSS••••
------------------------------
• [54.759 seconds]
odo dev command tests when a component with multiple endpoints is run should create state files containing information, including forwarded ports
/go/odo_1/tests/integration/cmd_dev_test.go:3427

  Captured StdOut/StdErr Output >>
  PID: 4900
  << Captured StdOut/StdErr Output
------------------------------
SSSSS•
------------------------------
• [17.677 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/3096060390
  << Captured StdOut/StdErr Output
------------------------------
S••S•S••••••SS•••••••SS••S•S•S•S••S•S••SS•SS••
------------------------------
• [10.036 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/3228590617
  << Captured StdOut/StdErr Output
------------------------------
SSSS••S•••SS•••SSSS•S•S•••S••••SSSS
------------------------------
• [3.421 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/4033541163
  << Captured StdOut/StdErr Output
------------------------------
•SS•S••
------------------------------
• [15.285 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/1817454838
  << Captured StdOut/StdErr Output
------------------------------
•S••SSS•S•S•SS•SS••SS•S••S•S••••SS
------------------------------
• [11.209 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/1306501971
  << Captured StdOut/StdErr Output
------------------------------
••SSSS••S•••S••SS•••S••SSS•S•
------------------------------
• [9.673 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/364800582
  << Captured StdOut/StdErr Output
------------------------------
SS•
------------------------------
• [11.146 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/1729472951
  << Captured StdOut/StdErr Output
------------------------------
••S••S•S•••SSSSS•S•SS••SSS•••SS•S•S•S•S
------------------------------
• [2.930 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/1674423583
  << Captured StdOut/StdErr Output
------------------------------
••SS•••S•S••••SS••S•••••SS•SSS•S•SSS•S••SS••••S•SSS
------------------------------
• [10.791 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/4104779869
  << Captured StdOut/StdErr Output
------------------------------
•SS••S
------------------------------
• [8.436 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/3150006409
  << Captured StdOut/StdErr Output
------------------------------
S•••S•S••
------------------------------
• [8.620 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/2161945484
  << Captured StdOut/StdErr Output
------------------------------
SSSSS•SSS••••SS
------------------------------
• [10.136 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/3172736186
  << Captured StdOut/StdErr Output
------------------------------
•••SS•••••••
------------------------------
• [2.748 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/3626018257
  << Captured StdOut/StdErr Output
------------------------------
•SSS••
------------------------------
• [14.941 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/848577944
  << Captured StdOut/StdErr Output
------------------------------
•••••SS•SS•SSSSS••SS••••SS•SS•••••••••••••••

Ran 490 of 887 Specs in 1640.206 seconds
SUCCESS! -- 490 Passed | 0 Failed | 0 Pending | 397 Skipped


Ginkgo ran 1 suite in 28m25.836937568s
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