go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=75db52cd3" ./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: 1684724678 - will randomize all specs Will run 116 of 888 specs Running in parallel across 2 processes SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS•SSSSSSSSSSSSSS••SSSSSS•SSSSSSSSSSSSSSSSSSS•SSSSSSSSS•SSSSSSS ------------------------------ • [0.970 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/548317134 << Captured StdOut/StdErr Output ------------------------------ SSSS•SSS ------------------------------ • [1.077 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/185404861 << Captured StdOut/StdErr Output ------------------------------ S•SSS•SSSSSSSSSSS•SSSSSSSS•SS•SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ • [0.978 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/1279678662 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSS•SSSSSS•SSS•SSSSSS•S•SSS•SS•SSSSSSS•SS••SSSSSSS•SSSSS•SSSSSS•SSSSSSSSSS•SSSSSSSSS•SSSSSSSS•SSSSSSSSS•SSSSSSSSSSSSSSSSSSS•SSSSSSSSSSSSSSS•SSSSS•SS•SSSS•SSSSSSSSSSSSSSS ------------------------------ • [1.932 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/3317332088 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSS•SSS•SSSSSSSSS•SSSS••SS ------------------------------ • [2.167 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/3708919671 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSSSSSS ------------------------------ • [1.359 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/891218320 << Captured StdOut/StdErr Output ------------------------------ SS•SSS•SSSSSSSSSSS•SSSSSSSS•SSSSSSSSSS ------------------------------ • [0.908 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/139475678 << Captured StdOut/StdErr Output ------------------------------ SS•S•SSSSSSSSSSSSSSSSSSS ------------------------------ • [1.386 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/3422843691 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSS•SSSSSSSSSSSSSSSSSSSSS•SS•SSSSSSSSSSSSSSSSSSSSSSSSSSSSSS••SSSSSSSS ------------------------------ • [1.284 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/3652478662 << Captured StdOut/StdErr Output ------------------------------ •SSSSSSS•SSSS•SSSSS•SSSSSSSS•SSSS•SSSSSSSSSSSSSSSSSSS••SSSSS•SSSSSSSS•SSSSSS•SS•SSSSSSSSSSSS•SS ------------------------------ • [1.073 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/3586334325 << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [1.538 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/2519067545 << Captured StdOut/StdErr Output ------------------------------ SSS•SSSSSSSSSS•SSSSS•SS•••SSSSSSSSS•SS•SSSS•SS ------------------------------ • [1.404 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/1866523751 << Captured StdOut/StdErr Output ------------------------------ ••SSSS•SSSSSS ------------------------------ • [1.424 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/3496660560 << Captured StdOut/StdErr Output ------------------------------ SSS•SSSSSS•SSS•SSSSSS•SSS•SSSSSSSSSSSSS•SS•S•S•SS•SSSSSSSSS•SS•SSSSSS•SSSSSSSSS•SSSSSSSSSS ------------------------------ • [2.043 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/3478182188 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSS••SSSS•SSSSSSSSSSSS•SSSSS•SS••SSSSSSS•SSS•SSS•SSSSSSSSSSSSSSSSS•S•SSSSS• Ran 116 of 888 Specs in 52.399 seconds SUCCESS! -- 116 Passed | 0 Failed | 0 Pending | 772 Skipped Ginkgo ran 1 suite in 1m52.876153842s 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