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=250514951" ./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: 1683785809 - will randomize all specs
Will run 495 of 885 specs
Running in parallel across 16 processes
SSSSSSSSSSSSSSSSSSSSS•••••••••S•••S
------------------------------
• [14.646 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/129573752
<< Captured StdOut/StdErr Output
------------------------------
S•
------------------------------
• [16.891 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/235917570
<< Captured StdOut/StdErr Output
------------------------------
•S••SSSSS•••••SS••SSS•S•
------------------------------
• [9.452 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/3803839461
<< Captured StdOut/StdErr Output
------------------------------
S•••SSS••SS••SS••SS••S••••S•S•S••S•
------------------------------
• [9.183 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/212789686
<< Captured StdOut/StdErr Output
------------------------------
S••SS•••S•S•SS••SSSS•••SS•SS••SS•••SSSSSSS•S•••S•S•SS••S••••••••SS••SS•••SSSSS•SSS•••••SS•SSS••S•SSS•SS••S
------------------------------
• [10.151 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/1612477459
<< Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [6.215 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/4280355769
<< Captured StdOut/StdErr Output
------------------------------
••••••SS••S•SS
------------------------------
• [2.710 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/160785215
<< Captured StdOut/StdErr Output
------------------------------
•SS•••••SSSS•S•S•SS••••S•
------------------------------
• [16.341 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/3922568697
<< Captured StdOut/StdErr Output
------------------------------
SS•SSSS••S•SSS•S•SSS••SSS•S••
------------------------------
• [9.901 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/3976975326
<< Captured StdOut/StdErr Output
------------------------------
S••S•S•SS•SS
------------------------------
• [3.241 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/678947386
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [10.153 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/2588750728
<< Captured StdOut/StdErr Output
------------------------------
SS•SSS•S••SSS••••••S••S•SS•••••••••SS•S•SS•S••••S•••S••••••S•SSS
------------------------------
• [9.816 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/3943109249
<< Captured StdOut/StdErr Output
------------------------------
SSS•SS••SS••S••
------------------------------
• [3.466 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/287184825
<< Captured StdOut/StdErr Output
------------------------------
S•••S•••SSSSSSS•SSSS•S••SS•SS••••SS•••S•S••SS•S•S•••S•••S•SSS••S•S•SSS••S••S•••SS•SS•S•S•S•SS•SSSS•S•S•••SS
------------------------------
• [13.152 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/4209631126
<< Captured StdOut/StdErr Output
------------------------------
•S•SS
------------------------------
• [19.360 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/1097816446
<< Captured StdOut/StdErr Output
------------------------------
S••
------------------------------
• [9.266 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/4037991915
<< Captured StdOut/StdErr Output
------------------------------
S••
------------------------------
• [8.910 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/4081221326
<< Captured StdOut/StdErr Output
------------------------------
••••S•••S••••S•
------------------------------
• [79.361 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/2216424468
<< Captured StdOut/StdErr Output
------------------------------
S••••S•S••••SS•SS••S••S•S••••S••SS•SS•••S•S•••S•••••
------------------------------
• [10.541 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/2874041851
<< Captured StdOut/StdErr Output
------------------------------
• [20.181 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/3074772656
<< Captured StdOut/StdErr Output
------------------------------
SS••S•S•S•S•
------------------------------
• [9.957 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/2250280992
<< Captured StdOut/StdErr Output
------------------------------
•SSS••SS•S••••S••••S•••SSS••SSSS••S•••••S•••••SSS••••••••SS••••SS•SS•
------------------------------
• [78.156 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/820526026
<< Captured StdOut/StdErr Output
------------------------------
SS•
------------------------------
• [9.425 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/3160821375
<< Captured StdOut/StdErr Output
------------------------------
S•SSS•SSSS••SS•S•SS•S•SS•SSS••SSS•S
------------------------------
• [10.710 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/4283092421
<< Captured StdOut/StdErr Output
------------------------------
•S•SS••••••••SSS•S••SS•S••••S••S••SS••
------------------------------
• [3.036 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/3746468899
<< Captured StdOut/StdErr Output
------------------------------
S•SSSS•••SSS•SS•S•••SS••
------------------------------
• [14.807 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/295613677
<< Captured StdOut/StdErr Output
------------------------------
•S•S••SS•S••••••SS•
------------------------------
• [10.810 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/3875966215
<< Captured StdOut/StdErr Output
------------------------------
•SSS•••SSSS•••SS•••SS•S•SSS•SS•••SSS•
------------------------------
• [56.231 seconds]
odo dev command tests when a component with multiple endpoints is run should create state files containing information, including forwarded ports
/go/odo_1/tests/integration/cmd_dev_test.go:3427
Captured StdOut/StdErr Output >>
PID: 18123
<< Captured StdOut/StdErr Output
------------------------------
S••S••SS•S•••S••SS•S•S•S•S•S••S•S••SS••
------------------------------
• [14.208 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/3153390009
<< Captured StdOut/StdErr Output
------------------------------
S•S•••••SS•••••••
------------------------------
• [81.078 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/2467235931
<< Captured StdOut/StdErr Output
------------------------------
•••••••••••
Ran 490 of 885 Specs in 1606.554 seconds
SUCCESS! -- 490 Passed | 0 Failed | 0 Pending | 395 Skipped
Ginkgo ran 1 suite in 27m54.173934945s
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