go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=0b8878efa" ./cmd/odo/
Using Devfile Registry https://devfile-registry-ci-devfile-registry.odo-test-kubernetes-clust-49529fc6e6a4a9fe7ebba9a3db5b55c4-0000.eu-de.containers.appdomain.cloud/
go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo  --randomize-all --slow-spec-threshold=120s -timeout 14400s --no-color -p  --junit-report="test-integration-nc.xml" --label-filter=nocluster tests/integration
Running Suite: Integration Suite - /go/odo_1/tests/integration
==============================================================
Random Seed: 1684160205 - will randomize all specs

Will run 116 of 888 specs
Running in parallel across 2 processes
SSSSSS••SSSS•SSS•SSSSSSSSS•SSS•SSS•SS•SS•SSS•SSSSSSSSSSSS•S
------------------------------
• [1.469 seconds]
odo init interactive command tests label nocluster should not fail when using -v flag [nocluster]
/go/odo_1/tests/integration/interactive_init_test.go:51

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo init -v 4' from /tmp/4225760920
  << Captured StdOut/StdErr Output
------------------------------
S•S•S•SSSSS
------------------------------
• [1.439 seconds]
odo init interactive command tests label nocluster should download correct devfile [nocluster]
/go/odo_1/tests/integration/interactive_init_test.go:237

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo init' from /tmp/1753113183
  << Captured StdOut/StdErr Output
------------------------------
S•S
------------------------------
• [1.110 seconds]
odo init interactive command tests label nocluster displaying welcoming messages when alizer detection of javascript name should display node-echo name [nocluster]
/go/odo_1/tests/integration/interactive_init_test.go:486

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo init' from /tmp/1920245065
  << Captured StdOut/StdErr Output
------------------------------
S•SSSSSSSSSSS•SSS•SSSSSSSSSSSSSS•SSSSSSS•SSS••SSS•SSSSSSSSSSSSS•SSSS•S•SSSS••SSSS•S•SSSSSSSSSSSSSSSSSS
------------------------------
• [1.959 seconds]
odo init interactive command tests label nocluster should download correct devfile-starter [nocluster]
/go/odo_1/tests/integration/interactive_init_test.go:308

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo init' from /tmp/2665207176
  << Captured StdOut/StdErr Output
------------------------------
•SS•SSSSSSSSSSSSSSSSSSSS
------------------------------
• [2.019 seconds]
odo init interactive command tests label nocluster personalizing Devfile configuration should allow for personalizing configurations [nocluster]
/go/odo_1/tests/integration/interactive_init_test.go:95

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo init' from /tmp/3382664645
  << Captured StdOut/StdErr Output
------------------------------
SSS•SSSSSSSSS•SSSSSSSSSSSS•SSSSS•SSS•SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS•SSSS•SSSS•SSSSSS•SSSS•SSSS•SSSSSSS•SSSSSSSSSSSSSSSSSSSSSSSSS•SS•SSSSSSSS•SSSSSSSSSS•SSSSS•S
------------------------------
• [1.405 seconds]
odo init interactive command tests label nocluster should print automation command with proper values [nocluster]
/go/odo_1/tests/integration/interactive_init_test.go:193

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo init' from /tmp/2857277954
  << Captured StdOut/StdErr Output
------------------------------
SSSSSSSS•SSSSS•SSSSSSSSSSSSSSSSSSSSSSSSSSS•••SSSSSSSS
------------------------------
• [1.110 seconds]
odo init interactive command tests label nocluster displaying welcoming messages when directory is not empty should display appropriate welcoming messages [nocluster]
/go/odo_1/tests/integration/interactive_init_test.go:438

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo init' from /tmp/580709033
  << Captured StdOut/StdErr Output
------------------------------
SSSSSSS•SS•SSSSSS•SSS
------------------------------
• [1.101 seconds]
odo init interactive command tests label nocluster Automatic port detection via Alizer when starting with an existing project should display ports detected [nocluster]
/go/odo_1/tests/integration/interactive_init_test.go:612

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo init' from /tmp/3490695604
  << Captured StdOut/StdErr Output
------------------------------
SSSSSSS•SSSSSSSSSSSSSSSSSSSSSSSSSSS•SSSSS
------------------------------
• [2.391 seconds]
odo init interactive command tests label nocluster should start downloading starter project only after all interactive questions have been asked [nocluster]
/go/odo_1/tests/integration/interactive_init_test.go:559

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo init' from /tmp/918951008
  << Captured StdOut/StdErr Output
------------------------------
SSSSS•SS•SSSS•SSS•SSSSSSS•SS•SSSSSSSSSSSSSSSSSSSSSSS•SSSSSSSSSSSSSSSSSSS•SSSSSSSSSSSS•SSSSSS•SSSSSSSSSSSSSSSSSS••SSSSSSSSSSSSSSSS•SSS
------------------------------
• [1.630 seconds]
odo init interactive command tests label nocluster should ask to re-enter the component name when an invalid value is passed [nocluster]
/go/odo_1/tests/integration/interactive_init_test.go:160

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo init' from /tmp/3586386789
  << Captured StdOut/StdErr Output
------------------------------
SSSS•SS•SSSSS•SSSSS••SSSSSS•SSS•SSS•SSSSSSS•S•SS
------------------------------
• [1.126 seconds]
odo init interactive command tests label nocluster when Alizer cannot determine a Devfile based on the current source code should not fail but fallback to the interactive mode [nocluster]
/go/odo_1/tests/integration/interactive_init_test.go:655

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo init' from /tmp/3123231510
  << Captured StdOut/StdErr Output
------------------------------
SSSSSS•SS•SSSSSS•SSSSS•SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS•SSSSSSSSSSSSSSSSSSSS•SSSSSSSSSSSSSSSSSSSSSSS
------------------------------
• [1.789 seconds]
odo init interactive command tests label nocluster should ask to download the starter project when the devfile stack has extra files [nocluster]
/go/odo_1/tests/integration/interactive_init_test.go:273

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo init' from /tmp/1153303949
  << Captured StdOut/StdErr Output
------------------------------
SSSSSSSSSSSS•SSSSSSSSSSSSSSSS••
------------------------------
• [1.788 seconds]
odo init interactive command tests label nocluster displaying welcoming messages when directory is empty should display appropriate welcoming messages [nocluster]
/go/odo_1/tests/integration/interactive_init_test.go:399

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo init' from /tmp/1828144219
  << Captured StdOut/StdErr Output
------------------------------
S•SSSSSSSSSSSSSSSSSSSS•SSSSSSS
------------------------------
• [1.075 seconds]
odo init interactive command tests label nocluster displaying welcoming messages when alizer detection of javascript name should ask to re-enter the component name if invalid value is passed by the user [nocluster]
/go/odo_1/tests/integration/interactive_init_test.go:521

  Captured StdOut/StdErr Output >>
  Spawning '/go/bin/odo init' from /tmp/2994561096
  << Captured StdOut/StdErr Output
------------------------------
S•SSS•SSSSSSSSSSSSSSSS•SSS•SSSSS••SSSSSS•S•SSSSSSSSSSSSSS•

Ran 116 of 888 Specs in 57.022 seconds
SUCCESS! -- 116 Passed | 0 Failed | 0 Pending | 772 Skipped


Ginkgo ran 1 suite in 1m58.60990957s
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