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

Will run 496 of 888 specs
Running in parallel across 16 processes
SSSSSSSSSSSS•••
------------------------------
• [29.450 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/1662829072
  << Captured StdOut/StdErr Output
------------------------------
•SSS•SSS
------------------------------
• [19.280 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/4210233011
  << Captured StdOut/StdErr Output
------------------------------
•••S••S••S•SS•••SSS••S•••S
------------------------------
• [16.817 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/2642412203
  << Captured StdOut/StdErr Output
------------------------------
••••••••S••SSSSSSS•••S•••SS•S••SS•S•••••S•
------------------------------
• [57.327 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: 15906
  << Captured StdOut/StdErr Output
------------------------------
•S•S
------------------------------
• [34.549 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/2481102470
  << Captured StdOut/StdErr Output
------------------------------
SS•••SSSS
------------------------------
• [36.259 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/1422773379
  << Captured StdOut/StdErr Output
------------------------------
SSSSS••S••••SSS
------------------------------
• [33.150 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/1240872322
  << Captured StdOut/StdErr Output
------------------------------
S•S•SS••••S•S••S••S•••••S•S•SSS•S•
------------------------------
• [3.501 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/4232933071
  << Captured StdOut/StdErr Output
------------------------------
SSS••SS•S•••S•••SS
------------------------------
• [11.064 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/4089749145
  << Captured StdOut/StdErr Output
------------------------------
••S
------------------------------
• [12.434 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/443653417
  << Captured StdOut/StdErr Output
------------------------------
S•••SS••S•S••S•••SSS•
------------------------------
• [14.110 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/3415682276
  << Captured StdOut/StdErr Output
------------------------------
•••S•••
------------------------------
• [10.582 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/2559821670
  << Captured StdOut/StdErr Output
------------------------------
•S•SSSSSS••SS••••S•SSS•SS•S•SS••
------------------------------
• [9.056 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/2709840667
  << Captured StdOut/StdErr Output
------------------------------
•••S•S•S
------------------------------
• [2.793 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/1169555199
  << Captured StdOut/StdErr Output
------------------------------
S•SS•••S••S••SSS••SS••SS•••••S•S•S••S••SS•SS••S•S
------------------------------
• [12.793 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/4122295593
  << Captured StdOut/StdErr Output
------------------------------
SSS••S•••••SS••••••S•••
------------------------------
• [11.817 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/1476397362
  << Captured StdOut/StdErr Output
------------------------------
••SS•••••••S••S••S••••
------------------------------
• [4.649 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/4133490115
  << Captured StdOut/StdErr Output
------------------------------
•S••••S•••S•SS•••SSS•S••S•S
------------------------------
• [2.861 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/3919784343
  << Captured StdOut/StdErr Output
------------------------------
•S•S
------------------------------
• [10.618 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/4063079190
  << Captured StdOut/StdErr Output
------------------------------
•••••SSSS•••S••SSS
------------------------------
• [14.472 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/1122106640
  << Captured StdOut/StdErr Output
------------------------------
•SSS
------------------------------
• [16.851 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/3161568401
  << Captured StdOut/StdErr Output
------------------------------
••SS•SS•S•SSS•SS•S••SSSSSS•••SSS••SSS••••S•S•S•S••••S•SS•SSS••S•SSSS•SS••SS•S••S••SS••SS•SSS••••S•••••••S••SSSSS•S•S•SSS•S••S•••S
------------------------------
• [22.307 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/736727037
  << Captured StdOut/StdErr Output
------------------------------
•••SS•SS••S•SSSSS•SSS•SS•SSS••S•SSSS•SS•••SS••••S•••S•S••S•••••S••SSSSS••SS•••••SSSSS•SSS••SS•S••S•••S•S•SS••S•S•SSS•SS•SS•SS•S
------------------------------
• [15.049 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/2291421005
  << Captured StdOut/StdErr Output
------------------------------
S•
------------------------------
• [79.881 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/3283099805
  << Captured StdOut/StdErr Output
------------------------------
•SS•S•••••••S••S•S•••S
------------------------------
• [17.004 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/4212865185
  << Captured StdOut/StdErr Output
------------------------------
S•••••••SS••S•S•S•••S•SSSSS••••SSS•S•SSSSS•SSS•S•S••SS•S••••••SSSS••
------------------------------
• [21.325 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/3337904880
  << Captured StdOut/StdErr Output
------------------------------
•••
------------------------------
• [10.147 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/4209333778
  << Captured StdOut/StdErr Output
------------------------------
••S•S••S•S•SS•••••SS•SS•S•SSS••••S•S•SS
------------------------------
• [80.852 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/3211941732
  << Captured StdOut/StdErr Output
------------------------------
••SSSS•S•SSS•SSS••••••SSSS•S•S•••S••SSS•S••S•••S••••SS•SSSSSS•SSSS•••
------------------------------
• [81.020 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/486763134
  << Captured StdOut/StdErr Output
------------------------------
•••••••••••

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


Ginkgo ran 1 suite in 29m8.95536882s
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: 1685083299 - will randomize all specs

Will run 4 of 4 specs
Running in parallel across 16 processes
------------------------------
• [105.782 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/1466268739
  << Captured StdOut/StdErr Output
------------------------------
• [148.767 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/1877104597
  Spawning '/go/bin/odo delete component' from /tmp/1877104597
  << Captured StdOut/StdErr Output
------------------------------
• [166.760 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/1370327788
  << Captured StdOut/StdErr Output
------------------------------
• [258.052 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/1902633350
  Spawning '/go/bin/odo delete component' from /tmp/1902633350
  << Captured StdOut/StdErr Output
------------------------------

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


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