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=c9c4258e3" ./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: 1682408819 - will randomize all specs
Will run 462 of 824 specs
Running in parallel across 16 processes
SSSSSS••S••SSSSSS
------------------------------
• [19.510 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/2023649717
<< Captured StdOut/StdErr Output
------------------------------
S•••SSS•S•S•SSS••SSS
------------------------------
• [10.464 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/914161421
<< Captured StdOut/StdErr Output
------------------------------
S•S•S••S••SS•S••
------------------------------
• [65.006 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:3146
Captured StdOut/StdErr Output >>
PID: 12484
<< Captured StdOut/StdErr Output
------------------------------
•••S•SS••SS••S
------------------------------
• [11.817 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/3799050105
<< Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [11.288 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/3067959656
<< Captured StdOut/StdErr Output
------------------------------
S••S•S•S•S•••S•S•SSSS••SS•SS•
------------------------------
• [11.264 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/4028346563
<< Captured StdOut/StdErr Output
------------------------------
•••••••••S••S••S••S•S••SS•
------------------------------
• [24.599 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/2119414511
<< Captured StdOut/StdErr Output
------------------------------
SS••••S•••••••
------------------------------
• [12.877 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/2986868185
<< Captured StdOut/StdErr Output
------------------------------
S•••SSS•SSSSS•S••
------------------------------
• [4.389 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/289907178
<< Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [9.790 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/3015983735
<< Captured StdOut/StdErr Output
------------------------------
•••SSSSS•S•
------------------------------
• [19.817 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/281236265
<< Captured StdOut/StdErr Output
------------------------------
S••S••SS•••SS•••••••S•S•S••SS•SSSS•SS•S•••S•SSS••••SS•S••SS•S••SS••SSS•SSSS
------------------------------
• [11.384 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/4141958093
<< Captured StdOut/StdErr Output
------------------------------
•S•SS•SSS•••••SS
------------------------------
• [18.904 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/1141471762
<< Captured StdOut/StdErr Output
------------------------------
•S•••SS•S••S••SSSSSS••••••SSS•••SS•••••SSSSS••••••••SS••S
------------------------------
• [9.780 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/1012926370
<< Captured StdOut/StdErr Output
------------------------------
•S••SS•S•SS••SS•SSSSS•S•S•S•SSS•S•••••
------------------------------
• [5.516 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/931006501
<< Captured StdOut/StdErr Output
------------------------------
••SS••••SS••S•SSS•S••••SS•••••S
------------------------------
• [80.095 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/2737578882
<< Captured StdOut/StdErr Output
------------------------------
S•S••SS••S•••
------------------------------
• [10.539 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/2371444790
<< Captured StdOut/StdErr Output
------------------------------
SS•S••SS••SSS••SSS•S•S••SS••S
------------------------------
• [9.707 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/2967404388
<< Captured StdOut/StdErr Output
------------------------------
S•SS••
------------------------------
• [11.114 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/1556736201
<< Captured StdOut/StdErr Output
------------------------------
•SSSS•S•S•SS•••SS•S•S•S
------------------------------
• [77.729 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/3975686020
<< Captured StdOut/StdErr Output
------------------------------
•S••SS•SS••S••••••SSS•SS•S•S••••
------------------------------
• [9.091 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/3983904234
<< Captured StdOut/StdErr Output
------------------------------
S••••S•SSS•SS••SS••S•S•S
------------------------------
• [21.640 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/688839172
<< Captured StdOut/StdErr Output
------------------------------
S••S•S•S
------------------------------
• [2.869 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/3640741132
<< Captured StdOut/StdErr Output
------------------------------
SSSS•S••S••SSSS•••S•S•••SSSS••SSS••S•S••S••S•••••SSS•
------------------------------
• [10.114 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/3766328973
<< Captured StdOut/StdErr Output
------------------------------
•SS•SSSSSSSS•S•SS•S•S•••SS••SSSS•••S
------------------------------
• [77.164 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/79987338
<< Captured StdOut/StdErr Output
------------------------------
SSS•S•S
------------------------------
• [3.521 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/4279248871
<< Captured StdOut/StdErr Output
------------------------------
SS•S•••S•••S•S•SSS•SSS•SS•••S•S••SSS••S••••SS
------------------------------
• [10.292 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/3229518510
<< Captured StdOut/StdErr Output
------------------------------
•••S•SS••SS•SS•••S•••S••••••S
------------------------------
• [19.910 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/1177586958
<< Captured StdOut/StdErr Output
------------------------------
S•S••S••S•••SS•••S•S••S•••SS••••SS•••S•••S•SSS•S•
------------------------------
• [4.824 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/912619859
<< Captured StdOut/StdErr Output
------------------------------
••••SS
------------------------------
• [9.884 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/2546149843
<< Captured StdOut/StdErr Output
------------------------------
•S••SS•••SS•S•••••SSSSS•••••S•SS•S••••••••••••••••
Ran 457 of 824 Specs in 1517.011 seconds
SUCCESS! -- 457 Passed | 0 Failed | 0 Pending | 367 Skipped
Ginkgo ran 1 suite in 26m24.517767035s
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