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: 1684226475 - will randomize all specs

Will run 496 of 888 specs
Running in parallel across 16 processes
SSSSSSSSS••••SS•S••S•S••••SSS•SSS••S•S•••
------------------------------
• [90.715 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/3695496868
  << Captured StdOut/StdErr Output
------------------------------
•••S•••SS•••S••S•S•S•••SS•SS•••SS•••SS•S•••SSSS••S••S•••S•••••S•S••••SS••••SS••••S•S•SSS•••••S••S
------------------------------
• [21.720 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/2467015792
  << Captured StdOut/StdErr Output
------------------------------
•••S•••S•SSSSSSS•SSSS•SS
------------------------------
• [3.326 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/2724423826
  << Captured StdOut/StdErr Output
------------------------------
••S•SS••S••SS•••SSSSS•SS••SSSSSS•SS•••••S••S•SS•S••SS
------------------------------
• [84.779 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/1821311739
  << Captured StdOut/StdErr Output
------------------------------
SS•SSSSS•S••
------------------------------
• [12.717 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/4220533258
  << Captured StdOut/StdErr Output
------------------------------
S•
------------------------------
• [18.939 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/2219875881
  << Captured StdOut/StdErr Output
------------------------------
•SS•SS•S•S•S•••S••SS••S•••S•S•••
------------------------------
• [9.464 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/3360333426
  << Captured StdOut/StdErr Output
------------------------------
SSS••SSSS•SSS••••SS•S•SSSSSSS••S••S•SSS•SSSS••S•
------------------------------
• [23.024 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/3676493170
  << Captured StdOut/StdErr Output
------------------------------
••S••SSSSSSSS••S•S•••••S••SS
------------------------------
• [12.767 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/18279799
  << Captured StdOut/StdErr Output
------------------------------
•••S•SSSS••S••••SS•
------------------------------
• [12.560 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/3814162510
  << Captured StdOut/StdErr Output
------------------------------
SSSSSSS•
------------------------------
• [12.073 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/2221666249
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [21.233 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/626414813
  << Captured StdOut/StdErr Output
------------------------------
••S••SS•••S••SS••S••S•SSSSSS•SS••SSS••
------------------------------
• [18.332 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/1058985814
  << Captured StdOut/StdErr Output
------------------------------
S•S•S•SSS••••S••SS••S•S•SSSS•SS•••S
------------------------------
• [11.228 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/3372624720
  << Captured StdOut/StdErr Output
------------------------------
•S•••••S•SSSS••••SSS•S•
------------------------------
• [13.916 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/2209330346
  << Captured StdOut/StdErr Output
------------------------------
S•S•SS•SSS
------------------------------
• [56.705 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: 31980
  << Captured StdOut/StdErr Output
------------------------------
S••SSS•
------------------------------
• [13.939 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/1907673518
  << Captured StdOut/StdErr Output
------------------------------
SS••S••S••••
------------------------------
• [3.946 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/3752911210
  << Captured StdOut/StdErr Output
------------------------------
•SSS•S•SS•SS••S•S•••••S•••S••S•SSS••••••
------------------------------
• [3.183 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/1282961919
  << Captured StdOut/StdErr Output
------------------------------
•••SS•••••S•
------------------------------
• [10.323 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/2491605567
  << Captured StdOut/StdErr Output
------------------------------
SS•S•SSSSS••SSS•SSS•
------------------------------
• [80.361 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/3073579967
  << Captured StdOut/StdErr Output
------------------------------
SS•S•S•S••S••S•S••S•••••S
------------------------------
• [10.850 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/3129730072
  << Captured StdOut/StdErr Output
------------------------------
•S•••SS••S••SSSS••SSS••••SSSS•••S•S•S••SS•S••SSSSS••S•SS•SSS•S•SSSS•••SS•••S••••
------------------------------
• [12.011 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/3723737051
  << Captured StdOut/StdErr Output
------------------------------
SSS•SS•••SS•SSS•S••S•••SS•
------------------------------
• [15.401 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/2060457884
  << Captured StdOut/StdErr Output
------------------------------
•S••••SS••••S•••S•••••SSS•SS•S•SS•SSS••••S••••••S•••••S•SSS••SSS••S•••••S
------------------------------
• [2.780 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/2074307777
  << Captured StdOut/StdErr Output
------------------------------
••SS•SS•SSSSS•S
------------------------------
• [13.174 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/3879572883
  << Captured StdOut/StdErr Output
------------------------------
SS••••SS••SS•••S•••SS•••••••S••S••S••••S
------------------------------
• [11.922 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/3943488784
  << Captured StdOut/StdErr Output
------------------------------
•S•SS••S••••••S••SS
------------------------------
• [13.382 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/2798632559
  << Captured StdOut/StdErr Output
------------------------------
•S••••
------------------------------
• [10.435 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/287238074
  << Captured StdOut/StdErr Output
------------------------------
•••••••••••

Ran 486 of 888 Specs in 1731.101 seconds
SUCCESS! -- 486 Passed | 0 Failed | 0 Pending | 402 Skipped


Ginkgo ran 1 suite in 29m54.422473524s
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

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: 1684228276 - will randomize all specs

Will run 4 of 4 specs
Running in parallel across 16 processes
------------------------------
• [104.578 seconds]
E2E Test starting with non-empty Directory test debugging should verify developer workflow from non-empty Directory
/go/odo_1/tests/e2escenarios/e2e_test.go:329

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo init' from /tmp/2830026925
  << Captured StdOut/StdErr Output
------------------------------
• [149.083 seconds]
E2E Test starting with empty Directory should verify developer workflow from empty Directory
/go/odo_1/tests/e2escenarios/e2e_test.go:63

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo init' from /tmp/832401999
  Spawning '/go/bin/odo delete component' from /tmp/832401999
  << Captured StdOut/StdErr Output
------------------------------
• [165.748 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:462

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo init' from /tmp/322072318
  << Captured StdOut/StdErr Output
------------------------------
• [237.510 seconds]
E2E Test starting with non-empty Directory should verify developer workflow from non-empty Directory
/go/odo_1/tests/e2escenarios/e2e_test.go:197

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo init' from /tmp/2064206092
  Spawning '/go/bin/odo delete component' from /tmp/2064206092
  << Captured StdOut/StdErr Output
------------------------------

Ran 4 of 4 Specs in 237.533 seconds
SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped


Ginkgo ran 1 suite in 4m20.74114961s
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