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=1142929b8" ./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: 1682072217 - will randomize all specs
Will run 460 of 820 specs
Running in parallel across 16 processes
SSSSSSSSS•SSSSS•SS•S••••S•••SS•••••••SSS••SSSS•••SS•SSS•••S•SS
------------------------------
• [17.688 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/3373172852
<< Captured StdOut/StdErr Output
------------------------------
SS•SS•••SS•••SS•S•••S•SS
------------------------------
• [9.239 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/2837493287
<< Captured StdOut/StdErr Output
------------------------------
SSSSS•••SS••
------------------------------
• [8.626 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/4126146830
<< Captured StdOut/StdErr Output
------------------------------
SS••S••••••S•S•••••SS•SSS•SSSSS•SSS•••S••S••••••SS•S•S••SSSSS•S•••••S••S•S•••SSS••SSSS••••SSSS
------------------------------
• [78.492 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/3911657217
<< Captured StdOut/StdErr Output
------------------------------
SSS••••S•S•SS••S•SS
------------------------------
• [10.794 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/342936015
<< Captured StdOut/StdErr Output
------------------------------
•S•SSSS•S••SSS•SSS•••S••SS
------------------------------
• [8.933 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/2811693892
<< Captured StdOut/StdErr Output
------------------------------
SSS••S••••S•••SS•SSS•SS•S••SS••S••S•••SS•S•S••SS••SS
------------------------------
• [9.090 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/3470651684
<< Captured StdOut/StdErr Output
------------------------------
S•SS•S••SSS••SS•••S•S••SSS•S••••••S••S•SSS••••••S•••S••••S•S•SS••SS•S••••••SSSSS•S••S•••SS•S••S•••S•SSS•S•S•SS•SS•SS•S••••S•
------------------------------
• [16.935 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/1914704191
<< Captured StdOut/StdErr Output
------------------------------
•S••
------------------------------
• [9.314 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/981314005
<< Captured StdOut/StdErr Output
------------------------------
S•S•••SSS•S•S•••
------------------------------
• [9.481 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/2180264533
<< Captured StdOut/StdErr Output
------------------------------
•SS••••••
------------------------------
• [78.071 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/3992307498
<< Captured StdOut/StdErr Output
------------------------------
S•S•SSS•SSS
------------------------------
• [4.640 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/3707398468
<< Captured StdOut/StdErr Output
------------------------------
SS•SS
------------------------------
• [11.068 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/2017234955
<< Captured StdOut/StdErr Output
------------------------------
•SSS
------------------------------
• [10.781 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/1765572966
<< Captured StdOut/StdErr Output
------------------------------
••S•SSS•••SSSSSS•S••SS••••••S•SS•••••••S•••S•••S•••
------------------------------
• [3.651 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/2787223076
<< Captured StdOut/StdErr Output
------------------------------
••S••
------------------------------
• [2.959 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/1711041988
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [19.071 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/623278626
<< Captured StdOut/StdErr Output
------------------------------
SSSS•S••••SS••SS
------------------------------
• [9.572 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/3166116616
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [10.633 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/1106269797
<< Captured StdOut/StdErr Output
------------------------------
S•
------------------------------
• [17.567 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/841461555
<< Captured StdOut/StdErr Output
------------------------------
••SS•••S
------------------------------
• [3.338 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/3672074181
<< Captured StdOut/StdErr Output
------------------------------
S••SS••
------------------------------
• [5.434 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/3514447455
<< Captured StdOut/StdErr Output
------------------------------
•S•SSSS
------------------------------
• [17.283 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/2947534315
<< Captured StdOut/StdErr Output
------------------------------
S••SS•••SS•SS•SS•S•S••S•SSS
------------------------------
• [78.336 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/790505750
<< Captured StdOut/StdErr Output
------------------------------
••S•S•••
------------------------------
• [54.570 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:3040
Captured StdOut/StdErr Output >>
PID: 10083
<< Captured StdOut/StdErr Output
------------------------------
S•••S•S••S••S••••••
------------------------------
• [10.619 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/3305217656
<< Captured StdOut/StdErr Output
------------------------------
••SS•••S•••S••••
------------------------------
• [20.682 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/2506930759
<< Captured StdOut/StdErr Output
------------------------------
••••S•S•S••S•S•S•••S•S•••••••••••SS•••••S•SS••SS•S••S••••S•SS••S••
------------------------------
• [11.322 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/2330122751
<< Captured StdOut/StdErr Output
------------------------------
••SS•SS••
------------------------------
• [11.878 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/3715225656
<< Captured StdOut/StdErr Output
------------------------------
S••SSSS
------------------------------
• [12.874 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/4267395284
<< Captured StdOut/StdErr Output
------------------------------
SSSS••S•SSS•S•SSS•••••SSSSSSSS••SS•S•SS••S•SSS•S•S••SS•S•SSS•S•••••••••••••••
Ran 455 of 820 Specs in 1505.647 seconds
SUCCESS! -- 455 Passed | 0 Failed | 0 Pending | 365 Skipped
Ginkgo ran 1 suite in 26m9.332439889s
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