Error from server (NotFound): namespaces "devfile-proxy" not found
Using Devfile proxy:
go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=d800b9417" ./cmd/odo/
go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo --randomize-all --slow-spec-threshold=120s -timeout 14400s --no-color -nodes=16 --junit-report="test-integration.xml" --label-filter="!unauth && !nocluster && !podman" tests/integration
Running Suite: Integration Suite - /go/odo_1/tests/integration
==============================================================
Random Seed: 1681398676 - will randomize all specs
Will run 454 of 805 specs
Running in parallel across 16 processes
SSSSSSSS••S•S
------------------------------
• [25.781 seconds]
odo add binding interactive command tests when the component is bootstrapped when binding to a service in a different namespace should error out if service is not found in the namespace selected
/go/odo_1/tests/integration/interactive_add_binding_test.go:242
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/1538674585
<< Captured StdOut/StdErr Output
------------------------------
SS•S•••••S•SSS•
------------------------------
• [9.606 seconds]
odo add binding interactive command tests when running a deployment should successfully add binding without devfile (custom naming strategy: "{ .name | upper }")
/go/odo_1/tests/integration/interactive_add_binding_test.go:463
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/3258216390
<< Captured StdOut/StdErr Output
------------------------------
S•SS•S•SSS•••SSS•••S•SSSS••S•S•SS•SSS••••SSSS••••SS•SS•SSSS•S
------------------------------
• [10.244 seconds]
odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile ("uppercase" as naming strategy)
/go/odo_1/tests/integration/interactive_add_binding_test.go:131
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/3989230422
<< Captured StdOut/StdErr Output
------------------------------
S••SSS••SS•S•••••SSS••S•S•
------------------------------
• [10.167 seconds]
odo add binding interactive command tests when running a deployment should successfully add binding without devfile (default naming strategy)
/go/odo_1/tests/integration/interactive_add_binding_test.go:311
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/3116044122
<< Captured StdOut/StdErr Output
------------------------------
•••SS•••
------------------------------
• [8.855 seconds]
odo add binding interactive command tests when running a deployment should successfully add binding without devfile (naming strategy: "uppercase")
/go/odo_1/tests/integration/interactive_add_binding_test.go:378
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/3820909200
<< Captured StdOut/StdErr Output
------------------------------
•••S
------------------------------
• [15.852 seconds]
odo add binding interactive command tests when the component is bootstrapped when binding to a service in a different namespace should successfully add binding to the devfile
/go/odo_1/tests/integration/interactive_add_binding_test.go:257
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/1577966646
<< Captured StdOut/StdErr Output
------------------------------
•SSSSSS••SSS••S•SS••
------------------------------
• [8.252 seconds]
odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile (custom naming strategy: "")
/go/odo_1/tests/integration/interactive_add_binding_test.go:180
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/3369837712
<< Captured StdOut/StdErr Output
------------------------------
SS••SS•
------------------------------
• [77.306 seconds]
odo dev interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile
/go/odo_1/tests/integration/interactive_dev_test.go:76
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo dev --random-ports' from /tmp/3760731067
<< Captured StdOut/StdErr Output
------------------------------
S•S•••S••S••SS
------------------------------
• [8.474 seconds]
odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile (custom naming strategy: "{ .name | upper }")
/go/odo_1/tests/integration/interactive_add_binding_test.go:180
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/411826843
<< Captured StdOut/StdErr Output
------------------------------
SS•SS•S••••SSSS
------------------------------
• [77.670 seconds]
odo dev interactive command tests directory is not empty when there is a match from Alizer should display welcoming messages first
/go/odo_1/tests/integration/interactive_dev_test.go:112
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo dev --random-ports' from /tmp/219813142
<< Captured StdOut/StdErr Output
------------------------------
••SSS
------------------------------
• [11.124 seconds]
odo add binding interactive command tests when running a deployment should successfully add binding without devfile (naming strategy: "lowercase")
/go/odo_1/tests/integration/interactive_add_binding_test.go:378
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/3560498823
<< Captured StdOut/StdErr Output
------------------------------
• [10.760 seconds]
odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile (Bind as Files)
/go/odo_1/tests/integration/interactive_add_binding_test.go:101
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/3480321646
<< Captured StdOut/StdErr Output
------------------------------
•S•S•S
------------------------------
• [11.108 seconds]
odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile ("lowercase" as naming strategy)
/go/odo_1/tests/integration/interactive_add_binding_test.go:131
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/984551567
<< Captured StdOut/StdErr Output
------------------------------
••S•••SSS••SS•••S••••••S•••S•••SS•S••SS••SSS•SS•••••S•SSSSS•••SS•••SS•S••S••SS•S••
------------------------------
• [13.150 seconds]
odo add binding interactive command tests when running a deployment should successfully add binding without devfile (custom naming strategy: "any string")
/go/odo_1/tests/integration/interactive_add_binding_test.go:463
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/3187624293
<< Captured StdOut/StdErr Output
------------------------------
S•
------------------------------
• [12.552 seconds]
odo add binding interactive command tests when running a deployment should successfully add binding without devfile (naming strategy: "none")
/go/odo_1/tests/integration/interactive_add_binding_test.go:378
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/2159070156
<< Captured StdOut/StdErr Output
------------------------------
SSSSSS•S•••S
------------------------------
• [3.517 seconds]
odo deploy interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile successfully even with -v flag
/go/odo_1/tests/integration/interactive_deploy_test.go:40
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo deploy -v 4' from /tmp/1091794576
<< Captured StdOut/StdErr Output
------------------------------
•••SSSSSS•SS••SS•••••SS•••••S•
------------------------------
• [3.810 seconds]
odo deploy interactive command tests directory is not empty when Alizer cannot determine a Devfile based on the current source code should not fail but fallback to the interactive mode
/go/odo_1/tests/integration/interactive_deploy_test.go:159
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo deploy' from /tmp/1594086105
<< Captured StdOut/StdErr Output
------------------------------
•S••S•S•S
------------------------------
• [16.726 seconds]
odo dev interactive command tests when a component is bootstrapped should sync files when p is pressed
/go/odo_1/tests/integration/interactive_dev_test.go:206
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo dev --random-ports --no-watch' from /tmp/1958586639
<< Captured StdOut/StdErr Output
------------------------------
SS••SSS
------------------------------
• [11.287 seconds]
odo add binding interactive command tests when running a deployment should successfully add binding without devfile (custom naming strategy: "")
/go/odo_1/tests/integration/interactive_add_binding_test.go:463
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/2845724381
<< Captured StdOut/StdErr Output
------------------------------
•SS•
------------------------------
• [2.814 seconds]
odo deploy interactive command tests directory is not empty when there is a match from Alizer should display welcoming messages first
/go/odo_1/tests/integration/interactive_deploy_test.go:109
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo deploy' from /tmp/301974496
<< Captured StdOut/StdErr Output
------------------------------
SS•••SSS•••SSSS••••••••SSS
------------------------------
• [3.570 seconds]
odo deploy interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile
/go/odo_1/tests/integration/interactive_deploy_test.go:75
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo deploy' from /tmp/3460378865
<< Captured StdOut/StdErr Output
------------------------------
••SSS•SSS••SS•SS•S•SSSS•S•••S••••S••SS
------------------------------
• [17.933 seconds]
odo add binding interactive command tests when running a deployment when binding to a service in a different namespace should successfully add binding without devfile
/go/odo_1/tests/integration/interactive_add_binding_test.go:591
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/678845419
<< Captured StdOut/StdErr Output
------------------------------
S••S••SSS••S••••S•S•••SSSSSS•••S
------------------------------
• [6.613 seconds]
odo dev interactive command tests directory is not empty when Alizer cannot determine a Devfile based on the current source code should not fail but fallback to the interactive mode
/go/odo_1/tests/integration/interactive_dev_test.go:164
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo dev --random-ports' from /tmp/11142378
<< Captured StdOut/StdErr Output
------------------------------
••S••S•S••S•S•••SSS••SSS•S•••S
------------------------------
• [75.840 seconds]
odo dev interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile successfully even with -v flag
/go/odo_1/tests/integration/interactive_dev_test.go:40
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo dev --random-ports -v 4' from /tmp/2625394993
<< Captured StdOut/StdErr Output
------------------------------
•SS••••S••SS•S•SSS••••S•••S•S•••S••SS••SS••SS••S•S••••••SS•SS•SS••S•S•••
------------------------------
• [5.202 seconds]
odo init interactive command tests when DevfileRegistriesList CRD is installed on cluster when CR for devfileregistrieslists is installed in namespace should download correct devfile from the first in-cluster registry
/go/odo_1/tests/integration/interactive_init_test.go:635
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo init' from /tmp/1670845571
<< Captured StdOut/StdErr Output
------------------------------
•••••••SSS•••S•••S•S•S•SS•••SSSS•SSSSS•SS•••••SSSS••S•SS•SS••••SS•S•SS•••SSSSSS•SS•••S••S••S••SSS•S
------------------------------
• [17.321 seconds]
odo add binding interactive command tests when running a deployment when binding to a service in a different namespace should error out if service is not found in the namespace selected
/go/odo_1/tests/integration/interactive_add_binding_test.go:577
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/4240860860
<< Captured StdOut/StdErr Output
------------------------------
••••S••S••••••SSS•S••S•SSSS•••S••SS•S••SS•••S•••S•••S••••SS•S
------------------------------
• [9.442 seconds]
odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile ("none" as naming strategy)
/go/odo_1/tests/integration/interactive_add_binding_test.go:131
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/333680715
<< Captured StdOut/StdErr Output
------------------------------
S•••••SS••S••
------------------------------
• [9.858 seconds]
odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile (Bind as Environment Variables)
/go/odo_1/tests/integration/interactive_add_binding_test.go:73
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/1098379344
<< Captured StdOut/StdErr Output
------------------------------
•••••S•••••SS•S••S••••••SSS•SS•SSSS•SS••••SS••SS••
------------------------------
• [9.387 seconds]
odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile (custom naming strategy: "any string")
/go/odo_1/tests/integration/interactive_add_binding_test.go:180
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo add binding' from /tmp/2925296405
<< Captured StdOut/StdErr Output
------------------------------
•••••••••••••••
Ran 449 of 805 Specs in 1479.562 seconds
SUCCESS! -- 449 Passed | 0 Failed | 0 Pending | 356 Skipped
Ginkgo ran 1 suite in 25m44.071680423s
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