go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=33af81b22" ./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: 1685081519 - will randomize all specs Will run 116 of 888 specs Running in parallel across 2 processes SSSSSSSSSS••SSSSSSSS•SSSSS•SSSS ------------------------------ • [1.706 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/1081161598 << Captured StdOut/StdErr Output ------------------------------ •SSSS ------------------------------ • [1.027 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/2488982087 << Captured StdOut/StdErr Output ------------------------------ SSSSSS•SSSSSSSSSSSSSSSSS•SSS•S•SSSSSSSSSSS•SSSSSSSSSSS•SS•SSSSSSSSSS•SSSSSSS•S•SSSSSS•SSSSS ------------------------------ • [1.401 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/2764863681 << Captured StdOut/StdErr Output ------------------------------ • ------------------------------ • [0.950 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/2759732072 << Captured StdOut/StdErr Output ------------------------------ SSS•S•SSSSSSSS•SS•SSSSSS•SS•SSSSSSS•SSSSSSSS•SSSS•SSS•SSSSSSSSSSSSSSSSSSSSS•SS•SSSSSSSSS•SSSSSSSSSSSSSSSSSSSSSS•SSSS ------------------------------ • [1.556 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/575397569 << Captured StdOut/StdErr Output ------------------------------ SS•S•SSSSSSSSSSSSSSS••SSSSSSSSSSSS••SSS•SS•SSSSSSSSSSSSSSSSSSSS•SSS•SS•SSS•SSSSS••SSSSSSSSSSSSSSSSSS•SSSSSSSSS•S•SSSSSSS•S ------------------------------ • [1.308 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/806032227 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSS ------------------------------ • [1.779 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/815596839 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSS•SSSSSSSSSSSSSSSSSSSS•S ------------------------------ • [1.055 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/2853462197 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSS••SSSSSSSSSSSSSSSSSSSS•SSSSSSSSS•SSSSSSSS•SSSSSSSSSSSSSSSSSS•SSSSSSSSS•SSSSSSSSSSSSSSSSSSSSS•SSS•SSSS•••SSS•SS•SSSSSSSSS•SSSSSSSSSSSSSSSSS ------------------------------ • [2.008 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/3421866420 << Captured StdOut/StdErr Output ------------------------------ SS•S•SSSSSSSSSS•SSSSSS•S ------------------------------ • [1.242 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/962975570 << Captured StdOut/StdErr Output ------------------------------ SS•SS•SSSSSSSSSSSS•SSSSSSS•SSSSSSSSSSSSSS••S•SSSSSSSSSS•SSSSSSSSSSSS•SSS ------------------------------ • [1.025 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/2026624125 << Captured StdOut/StdErr Output ------------------------------ SS•SS ------------------------------ • [2.246 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/852268216 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSS•SS•SSS•SSSSSSSS•SSSSSSSSSSSSSSSSSSSS••SS•SSSSSSSS•S•SSSSSSSS•SSSSSSSSSSSSSSSSSSS•SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS•SSSSSSSSS•SSSSSSS•S•S•SSSSSSSSS•SSSSSSSS•SSSS••SSSSSSS•SSSSSSSSSSSSSS ------------------------------ • [1.391 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/183138536 << Captured StdOut/StdErr Output ------------------------------ •SSS ------------------------------ • [1.491 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/2885788249 << Captured StdOut/StdErr Output ------------------------------ Ran 116 of 888 Specs in 54.674 seconds SUCCESS! -- 116 Passed | 0 Failed | 0 Pending | 772 Skipped Ginkgo ran 1 suite in 1m57.76875349s 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.8.0