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=33af81b22" ./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: 1685081529 - will randomize all specs

Will run 496 of 888 specs
Running in parallel across 16 processes
SSSSSSSSSSS•S•SS••SS•••SS•SSSSSS•S••••
------------------------------
• [56.730 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: 12826
  << Captured StdOut/StdErr Output
------------------------------
••S•S••S•••••S••SSS•••SS•S••SSS••SSS•S
------------------------------
• [8.301 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/1896950886
  << Captured StdOut/StdErr Output
------------------------------
•S•••
------------------------------
• [3.349 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/1589242534
  << Captured StdOut/StdErr Output
------------------------------
••SSS•
------------------------------
• [9.273 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/127937410
  << Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [8.678 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/3632818719
  << Captured StdOut/StdErr Output
------------------------------
•••S••
------------------------------
• [18.251 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/617078659
  << Captured StdOut/StdErr Output
------------------------------
•S•S•S•SSS•SS•SSS••S•••••S•S•S••S•S•S••••••••••SSS•SS••S••••SS••S•••SS••SSSSSS••••SSS•S•SSS•S•SSSSSS•••S•S•S••••••S•S•SSS•••S•••S•S•S
------------------------------
• [9.861 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/3314523887
  << Captured StdOut/StdErr Output
------------------------------
SS•SSS•S•••••SSS•SSS••SSS•••S•SSS•S
------------------------------
• [3.105 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/1093716535
  << Captured StdOut/StdErr Output
------------------------------
SSS•S•S•SS•S••S•••S••SS•SS•SSS••S••S•SS••SS••••S•S•SSSSS•
------------------------------
• [10.704 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/2198150944
  << Captured StdOut/StdErr Output
------------------------------
••SSS•••SS••SS••S••SSSS•••••S
------------------------------
• [18.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

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo add binding' from /tmp/214284782
  << Captured StdOut/StdErr Output
------------------------------
S••••S•SS••••
------------------------------
• [19.493 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/1695558145
  << Captured StdOut/StdErr Output
------------------------------
•••S•••••••S•SSSS
------------------------------
• [9.285 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/1581434647
  << Captured StdOut/StdErr Output
------------------------------
S••••SS••SS•S••S•
------------------------------
• [11.654 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/90970869
  << Captured StdOut/StdErr Output
------------------------------
S••SSS•••
------------------------------
• [14.398 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/1824602928
  << Captured StdOut/StdErr Output
------------------------------
•••S•••S•SS•••S••S•S••••SS
------------------------------
• [14.851 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/2163555283
  << Captured StdOut/StdErr Output
------------------------------
S•S•
------------------------------
• [11.127 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/98089771
  << Captured StdOut/StdErr Output
------------------------------
•••S•S•S•••••••S•S•
------------------------------
• [12.577 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/2330378000
  << Captured StdOut/StdErr Output
------------------------------
SS••S•••S••••S•S••••SSSSSS•SSS•S••SSSSSSS••S•••SSS•S
------------------------------
• [8.026 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/348098789
  << Captured StdOut/StdErr Output
------------------------------
•••••S•SSS
------------------------------
• [4.899 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/3964560625
  << Captured StdOut/StdErr Output
------------------------------
•SS•••SS•S•S•••S•••••••S
------------------------------
• [82.789 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/390240918
  << Captured StdOut/StdErr Output
------------------------------
•••••S•SS••SSSS•••SSSSSS••S••SS•••••S••••••••SS•SSSSS••SSS•S•SS•S••••S•SS•••SS•••S•••••S•S•S•S•S•SS•SS•••SS•••••SS•S•SSS•S
------------------------------
• [24.214 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/904147331
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [16.260 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/1882758050
  << Captured StdOut/StdErr Output
------------------------------
SS••S••SSS•SS•S•••••SS•SS••••SS•SS•SS•SSSS•••SSSS•S•SS•SS•SSS•••SSSS•S•S•
------------------------------
• [19.889 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/1068381431
  << Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [78.340 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/2737001156
  << Captured StdOut/StdErr Output
------------------------------
SS•S•SS••SS
------------------------------
• [9.129 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/687605038
  << Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [11.270 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/2147777916
  << Captured StdOut/StdErr Output
------------------------------
••SSS•S•SS•S••••S•SS•SS•••S
------------------------------
• [10.679 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/1422949152
  << Captured StdOut/StdErr Output
------------------------------
•••••S••SSS••S•••SS•S•
------------------------------
• [82.056 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/1054221759
  << Captured StdOut/StdErr Output
------------------------------
•S••S•••SS••SS•S•S•S•
------------------------------
• [3.030 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/4056600478
  << Captured StdOut/StdErr Output
------------------------------
•SS•SSS•SSSS•S
------------------------------
• [3.308 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/3341253706
  << Captured StdOut/StdErr Output
------------------------------
SSS••••SS••••••••••••••••

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


Ginkgo ran 1 suite in 25m24.732340306s
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