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 -p --junit-report="test-integration-nc.xml" --label-filter=nocluster tests/integration Running Suite: Integration Suite - /go/odo_1/tests/integration ============================================================== Random Seed: 1680069986 - will randomize all specs Will run 111 of 783 specs Running in parallel across 2 processes SSSSSSSSSSS••SSSSS••SS•SSSSSSSSSSSSSSSSSSSSSSS•SS•SSSSSSSSSS•S•SSSSSSSS••S•SSSSSSSSSSSSS•SSSSSSSSS••SSSSSSSSSSSSS•SSSSSSSSSSSSSSSSSSSSSSSSSSSS••S•SSSSS•SSSSSSSSSSSSSSS•S•SSSSS•SSSSSS•SSSSSSSSSS ------------------------------ • [6.897 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/360557941 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSS•SSS•SSSSSSSSSSSSSSSS••SSSSSSSSSSSSSSS•S•SSSSS•SSSSSSSSSSSSSSSSSSSSSSS•SSSSSSSSSS•SSSSSSSSSSS•SSSS•SSSSSSSS••SSS ------------------------------ • [2.768 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/547204135 << Captured StdOut/StdErr Output ------------------------------ SSS•SSSSSSSSSS••SSSSSSS•S•S•SSSSSSSSSSSSSSSS•SSSSSSSSSSSS•SSSSS•SSSSSSSSSS ------------------------------ • [2.213 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:374 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/1963798707 << Captured StdOut/StdErr Output ------------------------------ S••SSS•SS•••S•S ------------------------------ • [3.953 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:447 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/3006066924 << Captured StdOut/StdErr Output ------------------------------ S•SSSSSSSSSSSSSSSSSSSSSSS••SSSSSSSS•SSSSSSSSSSSSSSSS•SSSSSSSS•SSSSS••SSSSS••SSSSSS ------------------------------ • [2.633 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:543 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/3811519627 << Captured StdOut/StdErr Output ------------------------------ SSSSSSS••SSSSSSSSSSSSSSSSS•S•SS••SSSSS•SSSSSSSSSSSS•SSS•SSSSSSSSSSSSSSSS ------------------------------ • [2.958 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:287 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/1613942387 << Captured StdOut/StdErr Output ------------------------------ SSSS•SSSSSSSSS•S•SSSSSSSSSSSSSSSSSS•SSSSSSSSSSS•SSSSSSSSSSSS•SSSSS•SSS ------------------------------ • [3.640 seconds] odo init interactive command tests label nocluster should download correct devfile-starter [nocluster] /go/odo_1/tests/integration/interactive_init_test.go:196 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/1062706998 << Captured StdOut/StdErr Output ------------------------------ SSS•SS•SSS•SSSSS ------------------------------ • [2.305 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:326 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/361676858 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSS•SSSSSSSSSSS ------------------------------ • [2.276 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:409 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/3708036329 << Captured StdOut/StdErr Output ------------------------------ SSSSSSS•S••SSSSSSSSSSSSSS•SS ------------------------------ • [2.808 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/2990160657 << Captured StdOut/StdErr Output ------------------------------ •SSSSSSSS•SSSS ------------------------------ • [2.813 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/3031742520 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSS•SSSSSSSS•SS•SSS•SSSS••SS•SSSSSSS ------------------------------ • [2.157 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:500 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/3402828416 << Captured StdOut/StdErr Output ------------------------------ S•S•S• Ran 111 of 783 Specs in 75.941 seconds SUCCESS! -- 111 Passed | 0 Failed | 0 Pending | 672 Skipped Ginkgo ran 1 suite in 2m19.199361399s 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