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=75db52cd3" ./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: 1684724689 - will randomize all specs
Will run 496 of 888 specs
Running in parallel across 16 processes
SSSSSSSSSSS••S•S•S••
------------------------------
• [21.859 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/3305452910
<< Captured StdOut/StdErr Output
------------------------------
•S•S•S••••SSS•
------------------------------
• [9.432 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/1451832542
<< Captured StdOut/StdErr Output
------------------------------
•S•SS••••••S•
------------------------------
• [8.988 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/2047323693
<< Captured StdOut/StdErr Output
------------------------------
•SSSSS••S••••SS•S•••SSS•S••SSSSSS•S••••S••S•••SSS•S••••••SS•SS
------------------------------
• [24.675 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/2561150201
<< Captured StdOut/StdErr Output
------------------------------
•SS•SSS•SSSSSSSSS•S•••SSSSS•SS••SS•••SSSSS
------------------------------
• [8.878 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/2920173811
<< Captured StdOut/StdErr Output
------------------------------
S••SS•S•S•SS•S•S•S•SSSS••••S••SSS•••SSSS••••S•S•S•SSSS•S•S••SS•••
------------------------------
• [2.964 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/3217118655
<< Captured StdOut/StdErr Output
------------------------------
•SS•S••S••••S•••S••
------------------------------
• [8.934 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/1311148543
<< Captured StdOut/StdErr Output
------------------------------
•••S••••••
------------------------------
• [9.434 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/1040648313
<< Captured StdOut/StdErr Output
------------------------------
•••S•••S••S•S•SS•SSS••S
------------------------------
• [10.248 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/2353608826
<< Captured StdOut/StdErr Output
------------------------------
SS••••S•SS•S•SS•••S•••S•••SSSS•••S••S•••
------------------------------
• [79.113 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/2467805465
<< Captured StdOut/StdErr Output
------------------------------
• [2.971 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/2208006199
<< Captured StdOut/StdErr Output
------------------------------
S•SS••S••••••S•SS•S•S•SS•SS•S
------------------------------
• [55.529 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:3470
Captured StdOut/StdErr Output >>
PID: 28908
<< Captured StdOut/StdErr Output
------------------------------
SSS•SS•••••S•••S•••••SSS•S•••
------------------------------
• [10.873 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/1429880291
<< Captured StdOut/StdErr Output
------------------------------
S•••SS•SS••SSSSSS•
------------------------------
• [3.673 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/1221847918
<< Captured StdOut/StdErr Output
------------------------------
••SSS•
------------------------------
• [8.663 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/3753783425
<< Captured StdOut/StdErr Output
------------------------------
S•S•SS•••••SS•S••SS••S•••S•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 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/3865440498
<< Captured StdOut/StdErr Output
------------------------------
••••SS•S••••S••••S•SS•S•••S••S
------------------------------
• [11.301 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/1638212069
<< Captured StdOut/StdErr Output
------------------------------
•SS•••SSS••••••••••••S•SSSSS•S••••SS•S••••SSS•SSS••••SSS•S•••S••••S••SS••SS•S•••SSSS•S•SS•S•S•••SSS•S•SS•••SS
------------------------------
• [21.407 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/1405349980
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [5.103 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:712
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo init' from /tmp/2119987275
<< Captured StdOut/StdErr Output
------------------------------
•SS••••SSS•SS•SS•S••S•SSS•SSS••SSS•S••••SSS•SS•S•S•SSS•••S••SSSS•
------------------------------
• [9.499 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/628677841
<< Captured StdOut/StdErr Output
------------------------------
•SS••••S•S••S••••••••SSSSS••SS•S•SSS•••SSSS•S•S•SSSS•S•S•S••••SSS••S•S•••S••••••SSS••••SSSS•SSSS••S•S•
------------------------------
• [19.370 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/2422096487
<< Captured StdOut/StdErr Output
------------------------------
••S•SSS•••SSS•SS••S•S••SSSS••
------------------------------
• [17.946 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/3546886414
<< Captured StdOut/StdErr Output
------------------------------
••S•SSSSSS
------------------------------
• [78.492 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/3282179788
<< Captured StdOut/StdErr Output
------------------------------
•SSSS•••S•SS•S•
------------------------------
• [3.000 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/2495032877
<< Captured StdOut/StdErr Output
------------------------------
•S•S•S••
------------------------------
• [11.299 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/1197449100
<< Captured StdOut/StdErr Output
------------------------------
• [10.549 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/4267679647
<< Captured StdOut/StdErr Output
------------------------------
SSSS••SS•S•S••••••••S••••S••S•SS•SS•
------------------------------
• [14.345 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/1675714663
<< Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [13.809 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/1486735759
<< Captured StdOut/StdErr Output
------------------------------
•SS•SS•••
------------------------------
• [11.373 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/546438539
<< Captured StdOut/StdErr Output
------------------------------
•••••••••••••
------------------------------
• [79.486 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/2892334398
<< Captured StdOut/StdErr Output
------------------------------
•
Ran 491 of 888 Specs in 1618.181 seconds
SUCCESS! -- 491 Passed | 0 Failed | 0 Pending | 397 Skipped
Ginkgo ran 1 suite in 28m1.070539383s
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.8.0