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=18892a83d" ./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: 1680069977 - will randomize all specs
Will run 438 of 783 specs
Running in parallel across 16 processes
SSSSSSSSSSSSS•S••S••
------------------------------
• [24.766 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/2062699928
<< Captured StdOut/StdErr Output
------------------------------
S•S
------------------------------
• [30.615 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/2846593981
<< Captured StdOut/StdErr Output
------------------------------
•S•••S••SSSS•SS••S•SSS•S•SSSS•S•••••S
------------------------------
• [16.013 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/2171513374
<< Captured StdOut/StdErr Output
------------------------------
S•••
------------------------------
• [17.823 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/466912516
<< Captured StdOut/StdErr Output
------------------------------
•••S••S••S•SS•S•S•SSS•SS•••••SSS••SSSS••
------------------------------
• [16.959 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/2379299997
<< Captured StdOut/StdErr Output
------------------------------
SS••SSS•SS•SS••••SS••
------------------------------
• [4.084 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/663108424
<< Captured StdOut/StdErr Output
------------------------------
SS•
------------------------------
• [4.690 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/1426312645
<< Captured StdOut/StdErr Output
------------------------------
S•SSSSS•••S
------------------------------
• [8.861 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/301320699
<< Captured StdOut/StdErr Output
------------------------------
S••S•••S••S•••S
------------------------------
• [8.779 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/261159777
<< Captured StdOut/StdErr Output
------------------------------
•S••S•S••SS••••S••SS••SSSS•S•SS••SS
------------------------------
• [9.863 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/1477441453
<< Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [9.758 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/4125196982
<< Captured StdOut/StdErr Output
------------------------------
••S•••SS••S•SS••••S•SSSSS•SS•S••SS•••SS•SS•SS••••••S••••••S
------------------------------
• [10.123 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/646559944
<< Captured StdOut/StdErr Output
------------------------------
••S•••SS•••••S••SSSSSS•
------------------------------
• [10.389 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/2266765900
<< Captured StdOut/StdErr Output
------------------------------
SS••••
------------------------------
• [20.639 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/2731681309
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [9.870 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/283935723
<< Captured StdOut/StdErr Output
------------------------------
SS•S•S••SS•S••SS••••SS•S
------------------------------
• [4.950 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/4286481560
<< Captured StdOut/StdErr Output
------------------------------
••S•••••SSS•S••S•
------------------------------
• [11.936 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/1727161022
<< Captured StdOut/StdErr Output
------------------------------
•••SSS•••SS••S•S•S••SSS•S•S••SS•••S•S••S•S•
------------------------------
• [22.363 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/3714259508
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [10.897 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/335145796
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [9.608 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/2870419305
<< Captured StdOut/StdErr Output
------------------------------
SSS••SSSSS•••S•S
------------------------------
• [18.533 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/3473473008
<< Captured StdOut/StdErr Output
------------------------------
••SSSS•SSS•S••••SS••S•••••
------------------------------
• [21.758 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/421518534
<< Captured StdOut/StdErr Output
------------------------------
••S•••S•S••••••S•S••••SSS•S•••SSSSS•S•SSSS••SS•S•S
------------------------------
• [17.859 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/69401414
<< Captured StdOut/StdErr Output
------------------------------
••SS••S•••S•S••S•SS••S•SS•••S•••••••••SS•S•SSS•S••S••SSS••SS•••••••S••S••SS•
------------------------------
• [4.875 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/2362660578
<< Captured StdOut/StdErr Output
------------------------------
•S••••••••S•SSSSS•SS•SS•SSS•S••••
------------------------------
• [15.912 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/3949156668
<< Captured StdOut/StdErr Output
------------------------------
SSS•S••••SS•
------------------------------
• [32.205 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/4247130183
<< Captured StdOut/StdErr Output
------------------------------
••S
------------------------------
• [26.322 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/4290998910
<< Captured StdOut/StdErr Output
------------------------------
•S•S•S•S•••••S•••••••••S••S•••••••••SSS•S•SS•S•SSS•SS•••SS•SSSS•••SSS••S•S•S••••SSSSSSS••SSSS
------------------------------
• [21.842 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/2967338049
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [15.182 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:600
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo init' from /tmp/2129935776
<< Captured StdOut/StdErr Output
------------------------------
•SSS•SS•S••SSSSS••SS••SS•••S•••SSSSSS••••S•SSS•S•S•S••SS•SSSS•••••••••••••••
Ran 433 of 783 Specs in 1098.227 seconds
SUCCESS! -- 433 Passed | 0 Failed | 0 Pending | 350 Skipped
Ginkgo ran 1 suite in 19m21.245889357s
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