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=9918103dd" ./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: 1683705094 - will randomize all specs

Will run 495 of 885 specs
Running in parallel across 16 processes
SSSSSSSSSSSSSSSS••SS•S••SS•
------------------------------
• [23.161 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/100899709
  << Captured StdOut/StdErr Output
------------------------------
•SSSS•••••
------------------------------
• [34.983 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/186599380
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [16.591 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/2881886483
  << Captured StdOut/StdErr Output
------------------------------
•SSSS••S••S••••S•S•••S•••
------------------------------
• [80.752 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/351815256
  << Captured StdOut/StdErr Output
------------------------------
S•SS••SS••S•S
------------------------------
• [2.664 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/3700511197
  << Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [12.239 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/4126993268
  << Captured StdOut/StdErr Output
------------------------------
•••S••S••S••S•S•SS•SSSS•S•••S••S•SS•••SS•••
------------------------------
• [2.905 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/1066786861
  << Captured StdOut/StdErr Output
------------------------------
S••••SS•••••••S•SS•S•S
------------------------------
• [15.117 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/452454222
  << Captured StdOut/StdErr Output
------------------------------
S••S•S•SS••SS•S•S••
------------------------------
• [12.803 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/2306316231
  << Captured StdOut/StdErr Output
------------------------------
•S•S•SSSSS•S••S••SS••S•••S•S•S
------------------------------
• [13.706 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/1575966965
  << Captured StdOut/StdErr Output
------------------------------
SS•
------------------------------
• [16.437 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/2090047135
  << Captured StdOut/StdErr Output
------------------------------
S•••••S•SSS•S•S••••S•S•••SS•SSSS•••S•S•S•••SSS•••S•SSS••SS•SS•SS•S•S•••
------------------------------
• [11.175 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/3189900868
  << Captured StdOut/StdErr Output
------------------------------
••S•S•S••S•••S•
------------------------------
• [22.929 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/3222073462
  << Captured StdOut/StdErr Output
------------------------------
SS•••SS••••SSS•••
------------------------------
• [21.875 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/1929363729
  << Captured StdOut/StdErr Output
------------------------------
SSS••S•••S••SSSSSSSS••SS•S••S•S••S•••S••S•••SS••S•••S••SSS•S•••SSS•SS••••••SSS•SSSSS•S•SSSSS•S••SS•••••SS•S•S••SSSS••••S•••••SS•S
------------------------------
• [8.246 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/3812293481
  << Captured StdOut/StdErr Output
------------------------------
SSS•S•••S••S•SSS•••••SSS••S••S•S•SS•S••SS••SSS••S•••••••SSS••S••••
------------------------------
• [20.188 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/675011767
  << Captured StdOut/StdErr Output
------------------------------
SSS••SS•S•SS•SSSSSS••SSS•S•S•SSS••SS•SSSSSSSSSS••S••S•••••SSSS•••••S••••S•••••SS•••S•S••SSS
------------------------------
• [11.438 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/459129565
  << Captured StdOut/StdErr Output
------------------------------
•S••S•S•••S•S
------------------------------
• [56.345 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:3427

  Captured StdOut/StdErr Output >>
  PID: 6312
  << Captured StdOut/StdErr Output
------------------------------
SSSSSS•SS••
------------------------------
• [2.968 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/3669865244
  << Captured StdOut/StdErr Output
------------------------------
••SS•S•••S•S••SSSS••••SS•••
------------------------------
• [13.894 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/2680653388
  << Captured StdOut/StdErr Output
------------------------------
••S•S•SS•SSS•••S
------------------------------
• [20.678 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/255769713
  << Captured StdOut/StdErr Output
------------------------------
••••••S•S•S••S•SS••SS••
------------------------------
• [79.794 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/1127293973
  << Captured StdOut/StdErr Output
------------------------------
SS•SS
------------------------------
• [13.143 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/1953475388
  << Captured StdOut/StdErr Output
------------------------------
S••••SSS•
------------------------------
• [16.151 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/3710584807
  << Captured StdOut/StdErr Output
------------------------------
S••••SS•S•S••SSS••S•SS••S•SS•SS•SSS•S•••SSSS•••SSS••••S•••••SS•S
------------------------------
• [80.110 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/704267688
  << Captured StdOut/StdErr Output
------------------------------
••SSSS••••S••SSSS•••SSS•S••••S••
------------------------------
• [3.436 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/3413243627
  << Captured StdOut/StdErr Output
------------------------------
S••SS•SSSS•S•S•
------------------------------
• [17.040 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/1587265585
  << Captured StdOut/StdErr Output
------------------------------
•S••••S••••S••••S•
------------------------------
• [12.514 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/2795029424
  << Captured StdOut/StdErr Output
------------------------------
•S•S•S•S•SS•SSS•••SSS•S
------------------------------
• [10.484 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/736914527
  << Captured StdOut/StdErr Output
------------------------------
••••••••••••••

Ran 485 of 885 Specs in 1717.692 seconds
SUCCESS! -- 485 Passed | 0 Failed | 0 Pending | 400 Skipped


Ginkgo ran 1 suite in 29m43.233787609s
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: 1683706884 - will randomize all specs

Will run 4 of 4 specs
Running in parallel across 16 processes
------------------------------
• [105.223 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/1491156852
  << Captured StdOut/StdErr Output
------------------------------
• [148.770 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/970658334
  Spawning '/go/bin/odo delete component' from /tmp/970658334
  << Captured StdOut/StdErr Output
------------------------------
• [215.469 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/2106841629
  << Captured StdOut/StdErr Output
------------------------------
• [258.612 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/2767061517
  Spawning '/go/bin/odo delete component' from /tmp/2767061517
  << Captured StdOut/StdErr Output
------------------------------

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


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