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=18892a83d" ./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: 1680069976 - will randomize all specs

Will run 438 of 783 specs
Running in parallel across 16 processes
SSSSSSSSSSSSSSSS•S••SS•S•
------------------------------
• [22.925 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/1189173449
  << Captured StdOut/StdErr Output
------------------------------
S•••S••SSS••SS•SS•S••••SSSSSSSS••S•••••S••SS••••SS•SSS•••SS••S••••••S•SS•••S•SS
------------------------------
• [21.772 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/3924011121
  << Captured StdOut/StdErr Output
------------------------------
S•SSS••••
------------------------------
• [10.804 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/3826407354
  << Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [16.548 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/3023988252
  << Captured StdOut/StdErr Output
------------------------------
•S•••S•••SS••••SS•SS•S•SSSS•••SSSS••SS••S••S•S••••S••S•SSSS
------------------------------
• [17.454 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/727697231
  << Captured StdOut/StdErr Output
------------------------------
SSSSS•SS•SSS••S•SSSS•••S•S•••
------------------------------
• [11.903 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/1699938316
  << Captured StdOut/StdErr Output
------------------------------
•••S••SS•••••S••SSS••S•S•SS•SS•••S••SS••••S••••••••S••SS••SSS•SSS•
------------------------------
• [16.674 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/239890060
  << Captured StdOut/StdErr Output
------------------------------
•••S••S••
------------------------------
• [23.038 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/3333710222
  << Captured StdOut/StdErr Output
------------------------------
••S••••S•S•S•••S•SS•••••••SSS•S•S•S•S••SSS••SS•S•S•••••••S••••SS
------------------------------
• [13.874 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/918401766
  << Captured StdOut/StdErr Output
------------------------------
S•SSS••S•
------------------------------
• [4.574 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/3920874579
  << Captured StdOut/StdErr Output
------------------------------
SS••S
------------------------------
• [25.905 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/2230672016
  << Captured StdOut/StdErr Output
------------------------------
SS••S••••••S•SS••SS••SSS•SS••S•••••••••SSSS
------------------------------
• [15.591 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/3931025105
  << Captured StdOut/StdErr Output
------------------------------
S•S•S•SS•
------------------------------
• [30.537 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/2681821380
  << Captured StdOut/StdErr Output
------------------------------
S•SS•S•
------------------------------
• [15.387 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/2997225967
  << Captured StdOut/StdErr Output
------------------------------
•SS••••••S•S•S••S•••••SSSS•S
------------------------------
• [7.898 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/2850721368
  << Captured StdOut/StdErr Output
------------------------------
••S•••••SSS•SS•SSS••SS•S•SS•SSSS•S•S••••••S•S•SS••S•SS••S••
------------------------------
• [30.790 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/2593062739
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [27.448 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/1904475460
  << Captured StdOut/StdErr Output
------------------------------
•S••
------------------------------
• [17.770 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/2834528605
  << Captured StdOut/StdErr Output
------------------------------
S•••S•S••
------------------------------
• [6.571 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/1350541251
  << Captured StdOut/StdErr Output
------------------------------
•S••S
------------------------------
• [18.430 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/1523151509
  << Captured StdOut/StdErr Output
------------------------------
S•••S•S•S••S•SS•SSSS•SSSS••••SS•••SS•S•S•SS•SS••••••S••SS•SSS
------------------------------
• [21.920 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/4073586659
  << Captured StdOut/StdErr Output
------------------------------
S•SSSS•S•S•S•S•S•S•••S••S•SS•S•SSSSS•••SSS•
------------------------------
• [14.391 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/1014048740
  << Captured StdOut/StdErr Output
------------------------------
•S••S•SSSSSS•S••SS•••••SS••SS••S•SSSSS•••SS•••SSS•SSS
------------------------------
• [11.141 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/1104217633
  << Captured StdOut/StdErr Output
------------------------------
•SSS•
------------------------------
• [19.007 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/1448613286
  << Captured StdOut/StdErr Output
------------------------------
•S••SSSS•SS
------------------------------
• [13.745 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/3397988844
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [4.611 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/2593711521
  << Captured StdOut/StdErr Output
------------------------------
SSS•••SS••••S••••S•SS••••
------------------------------
• [17.874 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/3608590490
  << Captured StdOut/StdErr Output
------------------------------
SS••SS••SS•••
------------------------------
• [12.336 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/3124172048
  << Captured StdOut/StdErr Output
------------------------------
•S•S•••••••••••••••••

Ran 431 of 783 Specs in 1195.971 seconds
SUCCESS! -- 431 Passed | 0 Failed | 0 Pending | 352 Skipped


Ginkgo ran 1 suite in 20m56.903512337s
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

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

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

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

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

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

Ran 7 of 7 Specs in 167.549 seconds
SUCCESS! -- 7 Passed | 0 Failed | 0 Pending | 0 Skipped


Ginkgo ran 1 suite in 3m3.602430664s
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