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

Will run 496 of 888 specs
Running in parallel across 16 processes
SSSSSSSSS
------------------------------
• [13.848 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/3170590696
  << Captured StdOut/StdErr Output
------------------------------
•S•SS••SSS•SS••S
------------------------------
• [25.812 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/1277381528
  << Captured StdOut/StdErr Output
------------------------------
•SS
------------------------------
• [16.238 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/3919845419
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [24.222 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/2553317794
  << Captured StdOut/StdErr Output
------------------------------
•S•••S••S•••S•••SS•SSSS•S•SS••••S•S•S••SS•SSS•SS••S•S•S••S•••S••SSSS•S•S••SSSSS••••SS•SS•••SS•S••S•SS••SS••SS••SS••SS•••SS•S•SSS••••
------------------------------
• [3.678 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/296328310
  << Captured StdOut/StdErr Output
------------------------------
•SSS•S•S•S••
------------------------------
• [9.585 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/3080934358
  << Captured StdOut/StdErr Output
------------------------------
••S••••••S•SSS••••S•S•S
------------------------------
• [22.626 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/70209603
  << Captured StdOut/StdErr Output
------------------------------
SS•SS
------------------------------
• [11.116 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/2632856368
  << Captured StdOut/StdErr Output
------------------------------
SS•S•SS•SS••SSS•S••S••••SS
------------------------------
• [11.071 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/1395632432
  << Captured StdOut/StdErr Output
------------------------------
•••SS•S•S•S•S•S•S
------------------------------
• [2.804 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/2994196938
  << Captured StdOut/StdErr Output
------------------------------
••SS••
------------------------------
• [17.625 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/1981541769
  << Captured StdOut/StdErr Output
------------------------------
• [11.321 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/2599134979
  << Captured StdOut/StdErr Output
------------------------------
•S•S•S•SSS
------------------------------
• [19.551 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/3004043658
  << Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [9.782 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/608707155
  << Captured StdOut/StdErr Output
------------------------------
SSSSS••••••S•••••SS•••SS••S•S•
------------------------------
• [5.106 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/728324516
  << Captured StdOut/StdErr Output
------------------------------
•S•S•S•S••••SS•
------------------------------
• [55.151 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:3470

  Captured StdOut/StdErr Output >>
  PID: 28260
  << Captured StdOut/StdErr Output
------------------------------
•S••S••S•S•SS•SS•
------------------------------
• [9.909 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/794731827
  << Captured StdOut/StdErr Output
------------------------------
••••S•S•SS•SS•S••S••S•S••S••SS•••••••S•SSS
------------------------------
• [11.205 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/1492764951
  << Captured StdOut/StdErr Output
------------------------------
S•S••
------------------------------
• [13.528 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/4107690927
  << Captured StdOut/StdErr Output
------------------------------
SS•••••S••••S••S••S
------------------------------
• [8.628 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/2370318547
  << Captured StdOut/StdErr Output
------------------------------
SSS••S•
------------------------------
• [78.007 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/2244933655
  << Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [11.943 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/3834146681
  << Captured StdOut/StdErr Output
------------------------------
S•SS••••S•SS
------------------------------
• [7.427 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/2603586242
  << Captured StdOut/StdErr Output
------------------------------
SS•••SS•S•
------------------------------
• [2.811 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/1809424290
  << Captured StdOut/StdErr Output
------------------------------
SSS••SS••S•S•SS••••S•••SS•
------------------------------
• [78.823 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/4046878128
  << Captured StdOut/StdErr Output
------------------------------
•••S•SS•SS••••S•S•SS••S••SS•S
------------------------------
• [10.840 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/1734375787
  << Captured StdOut/StdErr Output
------------------------------
S•••SSS•S••S•SS•••SSS•SS•S•S••••S••••SSSS•SS••S•SS••SSSSS••••SS•••••••SS•S•SS••SS••••S••SS•S
------------------------------
• [78.695 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/1158855384
  << Captured StdOut/StdErr Output
------------------------------
•SS•S•S•••SSS•SSS•S••••SSS•S•••S•••••••S••S••S•SSS••SS•SS••SS•SSSS•SS•••SS•S•S•SSSS••SS••••••SSSS•SSS•
------------------------------
• [9.118 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/366107437
  << Captured StdOut/StdErr Output
------------------------------
••SS•SS•SS•S••S•S••SSS•••S•SSS•••SS•••
------------------------------
• [9.093 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/105951608
  << Captured StdOut/StdErr Output
------------------------------
S••S•SS••SS•••S••••••SSS••••SSSSSSS•SSS••SSSSS•SS••••••S•S••••SS••S•••••S•SSSS•S•••
------------------------------
• [19.955 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/2952106414
  << Captured StdOut/StdErr Output
------------------------------
S•S•••SS••SSS••SSS•S••SSS•SSS•••SS••••S•••S••S•S•••S•••••••••••••••

Ran 491 of 888 Specs in 1620.640 seconds
SUCCESS! -- 491 Passed | 0 Failed | 0 Pending | 397 Skipped


Ginkgo ran 1 suite in 28m8.135706254s
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.8.0