go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=4c23ed48b" ./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: 1683017790 - will randomize all specs Will run 112 of 832 specs Running in parallel across 2 processes SSSSSS••SSSS••SSSSSSSSSSSSSS••SSSSS•SSS•SSSSSS••SSSSSSSSSSSSSSSSSSSSSSSSSS•SS•SSSSSSSSSSS•SSSS•SSS•SSSSSSSS•SSSSSSSSSSS•SSSSSSSSS•SSSSSSSSS•S•SSSSSSSSSSSSSSSSSS•SSSS•SSSS•SSSSSSSSSSSSSSS•S••SSSSSS•SSSS•SSS•SSS•SSSSSSSSSSS•SS•S•SS••SS•SSSS•SSSSSSSSSSS•SSS•SSSSSSSSSSSSSSSSSS•S•SSSSSSSSSSS•SSSSSSSSSSSSSSS•SS•SSSSSSSSS•SS ------------------------------ • [2.310 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:482 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/493136238 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSS•SSSSSSSSS ------------------------------ • [1.464 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/77765170 << Captured StdOut/StdErr Output ------------------------------ SS•SSSSSSSS••SSSSSSSSS•SS•S•SSSSSSSSSS•SSSSS ------------------------------ • [1.258 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:196 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/1681654677 << Captured StdOut/StdErr Output ------------------------------ SS•SSSSSSSSSSSSSSSSSSSSSSSSSSSSS•SSSSSSSSS•SSSSSSSS•SSSS ------------------------------ • [1.380 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/3248005951 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSS•SS ------------------------------ • [1.068 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:535 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/4207997242 << Captured StdOut/StdErr Output ------------------------------ SSSSSS•SSS•SSSSSSSSSSSS•SSSSS•SSSSSS ------------------------------ • [1.173 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:409 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/1699708537 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSSSSS•SS•SSSSSSSSSSS•SSS•SSSSSSSSSSSSSS•SSSSSSSSSSSSS•SSSSSSS•SSSS••SSS ------------------------------ • [1.519 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/2547358435 << Captured StdOut/StdErr Output ------------------------------ S•SSSSSSSSSSSSS•SS•SSSSSSS•SSSS•SSSSSSSSSSSSSSSSS•SSSSSSSSSSSSSSSSSSSSS•SS•SSSS ------------------------------ • [1.924 seconds] odo init interactive command tests label nocluster should download correct devfile-starter [nocluster] /go/odo_1/tests/integration/interactive_init_test.go:231 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/2135877671 << Captured StdOut/StdErr Output ------------------------------ SSSSS•SSSSSSSSSS ------------------------------ • [1.562 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:322 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/3064801637 << Captured StdOut/StdErr Output ------------------------------ SSS•SSSSSS••S•SS•S•SS ------------------------------ • [1.052 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:361 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/1520709674 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSS•SSSSSSSSSSSSSSSSSSS ------------------------------ • [1.086 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:444 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/3841828129 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSS•SSSSSSSSSSSS ------------------------------ • [1.458 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/2404342973 << Captured StdOut/StdErr Output ------------------------------ SSS•SSSSSSSSSSSSS•SSS•SSSSSSSSSS•S•SSS•SSS•SSSSSSSS•SSSSSS• ------------------------------ • [0.944 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:578 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/3510934937 << Captured StdOut/StdErr Output ------------------------------ SSS•SSSSSSSSS• Ran 112 of 832 Specs in 52.896 seconds SUCCESS! -- 112 Passed | 0 Failed | 0 Pending | 720 Skipped Ginkgo ran 1 suite in 1m55.053870093s 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