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=50cee0219" ./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: 1683012520 - will randomize all specs
Will run 469 of 832 specs
Running in parallel across 16 processes
SSSSSSSSSSSSS•••S
------------------------------
• [25.406 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/124397182
<< Captured StdOut/StdErr Output
------------------------------
••SS••S
------------------------------
• [65.859 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:3204
Captured StdOut/StdErr Output >>
PID: 12634
<< Captured StdOut/StdErr Output
------------------------------
••••••
------------------------------
• [9.813 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/2194364453
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [8.969 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/3452808532
<< Captured StdOut/StdErr Output
------------------------------
•S•
------------------------------
• [91.271 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/50562045
<< Captured StdOut/StdErr Output
------------------------------
S•••SS•••S••S•SSSS•••••S••SS•S•••SS•S••SSS•
------------------------------
• [23.569 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/2457621149
<< Captured StdOut/StdErr Output
------------------------------
••S
------------------------------
• [5.369 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/1802089991
<< Captured StdOut/StdErr Output
------------------------------
S•S••S•S••••S•SS•SS••SSS•••S••••SS••S•S•S•
------------------------------
• [81.879 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/182528055
<< Captured StdOut/StdErr Output
------------------------------
• [80.872 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/3889160378
<< Captured StdOut/StdErr Output
------------------------------
• [9.606 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/2725857822
<< Captured StdOut/StdErr Output
------------------------------
S•S•SS•SS•S•••S••SSS•S••••S•SS••SS•••S•SSS•S••SSS•S•SSSSS•SSS•••SS•S•S•SSSS•SS•••••S••S•SS•••••S•
------------------------------
• [17.160 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/858141861
<< Captured StdOut/StdErr Output
------------------------------
••S••SS••S•S•••S
------------------------------
• [9.693 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/4031779700
<< Captured StdOut/StdErr Output
------------------------------
S•S••SSS••S••S•••SSSSSSSSS•SS•SSSSSSS••SSSS••••S••••S••SS•••S•S•S•S•SSSSSSS•S•••S•S•••S•SS••••S•S•S•SSSSS•SS•••••
------------------------------
• [2.712 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/3794236248
<< Captured StdOut/StdErr Output
------------------------------
SSS•••S•S•S•••S•SSS•••••S••SS•S•S•S••SS•SS••••SSSS••SS
------------------------------
• [3.178 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/3072677735
<< Captured StdOut/StdErr Output
------------------------------
•S
------------------------------
• [2.846 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/1104134071
<< Captured StdOut/StdErr Output
------------------------------
••••S•SSS•S•••••••S••••••S•SSSS••••S•SS•S
------------------------------
• [9.328 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/3744966131
<< Captured StdOut/StdErr Output
------------------------------
S••S•SS•S•S••••••S•S•SS••••SS•S•SSS••S••SS•SS••
------------------------------
• [16.589 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/3957473914
<< Captured StdOut/StdErr Output
------------------------------
••SS•SS•SS•S••
------------------------------
• [9.158 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/35971552
<< Captured StdOut/StdErr Output
------------------------------
•SSS•S•S••S•SS••S•S•SS••S••SS•S•S•••S•S•S•S•S••S•S•S••••SS••
------------------------------
• [8.879 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/1833872568
<< Captured StdOut/StdErr Output
------------------------------
••••SS••S••SSS•
------------------------------
• [6.912 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/2142702775
<< Captured StdOut/StdErr Output
------------------------------
•SSS
------------------------------
• [8.633 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/1777682504
<< Captured StdOut/StdErr Output
------------------------------
•S••SS•S•S•SS
------------------------------
• [6.536 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/3497130272
<< Captured StdOut/StdErr Output
------------------------------
•S••S••••SS••S••SS•S•••S
------------------------------
• [9.797 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/2130599180
<< Captured StdOut/StdErr Output
------------------------------
S••S•••SS••SSS•••••SS•••••S•••S•••••S•••SSS•S••SSSSSS•SSS•S
------------------------------
• [9.263 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/4269558611
<< Captured StdOut/StdErr Output
------------------------------
SSS•
------------------------------
• [8.399 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/4154519182
<< Captured StdOut/StdErr Output
------------------------------
S•SS•S•••S•S••S•
------------------------------
• [10.289 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/2516333648
<< Captured StdOut/StdErr Output
------------------------------
S•••S
------------------------------
• [9.765 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/2095299578
<< Captured StdOut/StdErr Output
------------------------------
•••SS••S•S•••S•SSSS••••SSSSS•••••S•
------------------------------
• [8.827 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/2236396628
<< Captured StdOut/StdErr Output
------------------------------
S•SS•S•••SS
------------------------------
• [19.528 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/4092883855
<< Captured StdOut/StdErr Output
------------------------------
•SS•S•S••SS••S•S•SS••SS•••S••S••••
------------------------------
• [8.377 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/3378571805
<< Captured StdOut/StdErr Output
------------------------------
S•••••••••••••••
Ran 464 of 832 Specs in 1458.931 seconds
SUCCESS! -- 464 Passed | 0 Failed | 0 Pending | 368 Skipped
Ginkgo ran 1 suite in 25m23.0943339s
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