go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=b7eaaebec" ./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: 1684226490 - will randomize all specs Will run 116 of 888 specs Running in parallel across 2 processes SSS•SSSSSSSSSSSSSSSSSSS•SS•SSSSSSSSSSSSSSSSSSS•SS•SSSSSSSSS•SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS•SS•••SSSSSSSSSSSSSSSSSSS•SSSSSS•SSSSSS•SSSS•SSS•SSSS•SSSSS•SSSSSSSSSSSS•S•SSSSSSSSSSSSSSS•SSSSSS•SSSS•SSSSSSSSSSSSSSSSSSSSSS•SSSSSSSS ------------------------------ • [1.512 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/833503890 << Captured StdOut/StdErr Output ------------------------------ SSSSSS•SSSS•SSSSSSSSS•SSSSSSSSSSSS•SSSSSSSSSSSSSSSSSSSS•SSSSSSSSSSSSS•SS•S•SSSSSSSSS•S• ------------------------------ • [1.174 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/913632091 << Captured StdOut/StdErr Output ------------------------------ •SSSSSSSSSSSSSSSSSSSSSS••SSSS•SSSSSSSS•SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS•SSSS••SSSSSSSS ------------------------------ • [1.551 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/3755847941 << Captured StdOut/StdErr Output ------------------------------ SSSSSS••SS•SSSSSSSSSSSS•S•SS•SS•••SSSSS•SSSS•SSS•SSSSS•SSSSSSS•SSSSSSSSSSSSSSSSSS•S ------------------------------ • [2.101 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/1249743463 << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [1.895 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/940780364 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSS•SSSS•SSSSSSSSSSSSS•S•SSSSSSSSSSS ------------------------------ • [1.549 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/1390909786 << Captured StdOut/StdErr Output ------------------------------ SSSSS•SSSSS•SSSSSSSSS•S••SSS•SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ • [0.995 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/3967388459 << Captured StdOut/StdErr Output ------------------------------ SSSSSSS•SSSSSSSSSSSSSSSSSSSSSSS•SSSSSSSSSSSSS•SSSSSS•SSSSS•SS•S•S•S ------------------------------ • [1.124 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/2927482613 << Captured StdOut/StdErr Output ------------------------------ • [3.158 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/1239421087 << Captured StdOut/StdErr Output ------------------------------ •SSS•SSSSSS•S•SSSSSSS••SSSSSSSSSSSS•SSSS•SSS ------------------------------ • [1.607 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/1978546904 << Captured StdOut/StdErr Output ------------------------------ S•SSSS ------------------------------ • [1.636 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/2835487453 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSS•SSSS••SSSSSSSS•SSSSSSS•SSSSS•SS•SSSSSSSSS ------------------------------ • [1.104 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/1661535521 << Captured StdOut/StdErr Output ------------------------------ SSSS•SSS ------------------------------ • [1.533 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/3995507128 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSSSSSS•SS•SSSSSS•S•SS•SSS•SSSSSSS•SSSSSSSSSSSSSSS ------------------------------ • [1.108 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/4259749390 << Captured StdOut/StdErr Output ------------------------------ SS••SSSSSSSSSSSSSS•SS• Ran 116 of 888 Specs in 57.504 seconds SUCCESS! -- 116 Passed | 0 Failed | 0 Pending | 772 Skipped Ginkgo ran 1 suite in 2m4.817026718s 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