go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=1142929b8" ./cmd/odo/ 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: 1682070806 - will randomize all specs Will run 112 of 820 specs Running in parallel across 2 processes SSSSSSSSSSSS•SSS•SSSSSSSSSS•SSSSSS•SSSSSSSSS•SSS•SSSSSSSSSS ------------------------------ • [1.641 seconds] odo init interactive command tests label nocluster should download correct devfile [nocluster] /go/odo_1/tests/integration/interactive_init_test.go:160 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/2297237260 << Captured StdOut/StdErr Output ------------------------------ SSSS••SSSSSSSSSS•SSSSSSSSSSSSSSSSSSSSSSSSS•S•SSSSSSS•S•SSSSSSSSSSSSSSS••SSSSSSSSS•••SSSSSS•SSS•SS••SSSSSSSSSSSSSSSSSSSS ------------------------------ • [1.026 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:409 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/3322757898 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSSSSSS•SSSSSSSSSSSSSSS•SSSS ------------------------------ • [1.751 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:84 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/3977669594 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSS•S•S•SS•SSSSSSSSSSSSSSSSSSSSS•SSSSSSSSS•SSSSSSSSSSS••S•SSSSSSSSSSSSSSSSSSSSS•SSSSSSS ------------------------------ • [1.087 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:535 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/1550801924 << Captured StdOut/StdErr Output ------------------------------ SSSSSS••S•S•SSSSSSSSSSSS•SSSSS•SSSSSSSSSSSSSSS•SS•S•SSS•SSSSSSS•SSSSSSSSSSSSSSSSSSSSSSSS•SSSSS•S•SSSSSSS•SSSSSSSSSSSSSSS•SSS•SSSSSSSSSSSSSSSSSSSSS•S•SSSSSSSS•SSSSSSSSSSSSSSSS•S•SSS•S•SSSS•S ------------------------------ • [1.124 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:361 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/3897046928 << Captured StdOut/StdErr Output ------------------------------ SSS•SSSS•SSSSSSS•SSSSSSSSSSSSS•S ------------------------------ • [1.534 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:322 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/2264221767 << Captured StdOut/StdErr Output ------------------------------ • [0.958 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:578 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/291564367 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSS ------------------------------ • [1.780 seconds] odo init interactive command tests label nocluster should download correct devfile-starter [nocluster] /go/odo_1/tests/integration/interactive_init_test.go:231 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/214475130 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSS•SSSS•SS•SSS•SSS•SSSS•S•SSSSSSSSSSSSSS•SSSSSSSSSSSS•SS ------------------------------ • [1.663 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:117 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/2606476152 << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ • [1.407 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:196 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/1674049031 << Captured StdOut/StdErr Output ------------------------------ SSSS•SSSSSSSSS•S•••SS•SSSS•SSS••SSSS•SSSSSSSS•S•SSSSSSSSSSSS ------------------------------ • [1.003 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:444 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/2011219551 << Captured StdOut/StdErr Output ------------------------------ SSSSS•SSS ------------------------------ • [1.522 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:50 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init -v 4' from /tmp/432627805 << Captured StdOut/StdErr Output ------------------------------ •S••SS•SSSSSSSSSS••SSSS•SSSSSSSSSSS•SSSSSSS•SSSSSSSSSSSSSSS•SSSS•SSSSSSSS•SSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ • [2.555 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:482 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/631688682 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSS•SSSSSS• Ran 112 of 820 Specs in 52.173 seconds SUCCESS! -- 112 Passed | 0 Failed | 0 Pending | 708 Skipped Ginkgo ran 1 suite in 1m51.974294118s 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