go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=eb575c862" ./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: 1684753506 - will randomize all specs Will run 116 of 890 specs Running in parallel across 2 processes SSSSSSSSSSSSSSSSSSSSSSSSSSSSS•S•SSSSS•SSSSSSSSSSSSSSSS•SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS•SSSSSSSS•SSSSSSSSS•SSSS••S•SSSSSSSSS•SSSSS•SSSSSSSSSSSSSS•SSSSSS•S ------------------------------ • [1.769 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/1163955691 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSS•SSSSSS ------------------------------ • [1.163 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/1018803536 << Captured StdOut/StdErr Output ------------------------------ SS•SSSS••SSSSSSSSSSSS ------------------------------ • [1.203 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/3283459464 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSSSS•SSSSSS•SSS•SS••SSS ------------------------------ • [1.558 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/411981232 << Captured StdOut/StdErr Output ------------------------------ S•S•SSSSSSSSS•SSSSSSSSSSSSSSS•SSSSS•SSS ------------------------------ • [1.786 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/3507892393 << Captured StdOut/StdErr Output ------------------------------ ••SSSSS•SSSSS•SSSSS•SSSSSSS ------------------------------ • [1.133 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/941283520 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS•SS•SSSSSSSSSSSS••SSS ------------------------------ • [1.180 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/900811778 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSSSSSSS ------------------------------ • [1.844 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/1155040527 << Captured StdOut/StdErr Output ------------------------------ SSSSSS•SS•S•SS••SSS•SSSS•SSSSSSSS•SSSS•SS•SSSSSSSSSSSSSSSSSSSSSS•SSSS ------------------------------ • [2.286 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/831386849 << Captured StdOut/StdErr Output ------------------------------ •SSSS•SS•SSSSSSSSSS•SSSSSSSSSSS•S•SSS•SSS•SSS•SSSSSS• ------------------------------ • [2.754 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/3630442270 << Captured StdOut/StdErr Output ------------------------------ S•SSSSSS••SS ------------------------------ • [2.342 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/743308887 << Captured StdOut/StdErr Output ------------------------------ SSSSSS•SSSSSS•SSSSSSSSSSSSSSSSSSSS•SSSSSSSSSSSS•SSS ------------------------------ • [1.775 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/3327778084 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSS•SSSSSSSS•SSSSSSSSSSSSSSSS•SSSSSSSS•SSSSSS•S•SSSSSSSS•SSS••S•SSS•SSSSS•SSS•S•SSSSSSSSSSSS•SSSSSSS•SSS•SSS•SS•SSSS••SSSSSSSSSSSSSSS•SSSSSSSSSSSSSSSSSSS•SSSSS• ------------------------------ • [1.703 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/3464176173 << Captured StdOut/StdErr Output ------------------------------ SS•SSSSSS•SSSS•SSSSSS ------------------------------ • [1.183 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/838063523 << Captured StdOut/StdErr Output ------------------------------ SSSS•S•SSSSSSSSSSSSSSS•SSSSS•SSSSSSSS•SSSSSS•SSS•SSSSSSSSSSSSS•SSSSSSSSSSSSSSS•• Ran 116 of 890 Specs in 61.510 seconds SUCCESS! -- 116 Passed | 0 Failed | 0 Pending | 774 Skipped Ginkgo ran 1 suite in 2m9.896390236s 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