go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=21614bce8" ./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: 1683815964 - will randomize all specs Will run 116 of 887 specs Running in parallel across 2 processes SSSSSSSS•SSSSSSSS•S•SSSSSSS•SSSSSS•SSSSSSSSSSS ------------------------------ • [1.744 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/2847494675 << Captured StdOut/StdErr Output ------------------------------ S••SSSSSS•S•SS•SS ------------------------------ • [1.062 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/2714521034 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSS••SSSSSSSSSSSSSSSSSSSSSSS•SSSSSSS•SSS•SS ------------------------------ • [0.986 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/3650510488 << Captured StdOut/StdErr Output ------------------------------ SSSSS•S•SSSSSSSSSSS•S•SSSSSSS•SSS••SSSS•SSS•SSSSSSSS•SS••S•SSSSS•SSSSSSSSSSS•SSSSSS••S•SSSSSSS•SSSSSSSSSSSSSSSSSSS•SSSSSS•SSSSSSSSSSSSSSSSSSSS•SSSSSSSSSSSSSSSSSSSSSSSSSSS•SSSSSSSSSSSSSSSSSS•SSSSSS ------------------------------ • [1.493 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/4089605710 << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [0.981 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/3720156197 << Captured StdOut/StdErr Output ------------------------------ SS•SSS•SSSSSSSSSSSSS•SSSSSSSSSSSSSS•SSSSSSSSSSSSSSSSSS••SS•SSSSSSS••SS•SSSSSSS•SSSSSSS•SSSSSSS ------------------------------ • [1.696 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/3811392836 << Captured StdOut/StdErr Output ------------------------------ S•SSSSS•SS•SSSSSSSSSSSSSSSSSSS•SSSSSSSSSSSSSSSSSSSSSSSSSSSS•SS•SSSSSSSSSSSSSS•SS•SSSSSSSSSSSS••• ------------------------------ • [2.267 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/2442232109 << Captured StdOut/StdErr Output ------------------------------ S•SSSSSSSSSSSSS••SSSSSSS••SS•SSSSSSSSSSSSSSSSSS••SSSSSSSSSSSSSSSSSSSSSS••S ------------------------------ • [1.505 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/76159183 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSS ------------------------------ • [2.181 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/293866034 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSS••SSS•SSSSSSSSSS•SSSSSSSSSSSS•SSSS•SSSSSSSSSS ------------------------------ • [1.185 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/352444286 << Captured StdOut/StdErr Output ------------------------------ S•SSS•S•SSSSS•SSSSSSSSSSSS•S•SSSSSS•SSSSSSSSSSSSSSSSSSSSSSS•SSSSSSSSSSSSSSSSSSS•S•SSSSSSSSS•SSSSS ------------------------------ • [2.585 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/2255391119 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSS•SSSSSSSS•SSS•SSSSSSSS•SSSSSS ------------------------------ • [1.532 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/2623043112 << Captured StdOut/StdErr Output ------------------------------ SSS•SSSSSSSSSS•SSSS•SSSSSSSSSS•SSSSSSSSSSSSS•SSSSSSSSSSSSSSSSSSSSSSSSS•SSSS•SSS ------------------------------ • [1.591 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/1341514594 << Captured StdOut/StdErr Output ------------------------------ SSSSS•SSSS•SSSSS ------------------------------ • [0.923 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/1204697752 << Captured StdOut/StdErr Output ------------------------------ Ran 116 of 887 Specs in 54.646 seconds SUCCESS! -- 116 Passed | 0 Failed | 0 Pending | 771 Skipped Ginkgo ran 1 suite in 1m56.112380637s 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