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=38f650610" ./cmd/odo/
go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo --randomize-all --slow-spec-threshold=120s -timeout 14400s --no-color -nodes=12 --junit-report="test-integration.xml" --label-filter="!unauth && !nocluster && !podman" tests/integration
Running Suite: Integration Suite - /go/odo_1/tests/integration
==============================================================
Random Seed: 1682447568 - will randomize all specs
Will run 462 of 824 specs
Running in parallel across 12 processes
SSSSSSSSSSSSSSS•SSS••SS••S••SS•••S••••SSSS•••S
------------------------------
• [11.880 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/2407777857
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [2.766 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/2089967255
<< Captured StdOut/StdErr Output
------------------------------
•SS•S
------------------------------
• [10.117 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/1175658067
<< Captured StdOut/StdErr Output
------------------------------
SSSSS••S•••••S•S••••S••S••S••S•S
------------------------------
• [9.497 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/411057043
<< Captured StdOut/StdErr Output
------------------------------
••••••SS••••SSS••SSS•SS••SS•S•S•••••S
------------------------------
• [10.837 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/3206381603
<< Captured StdOut/StdErr Output
------------------------------
S•S•S•
------------------------------
• [10.607 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/1184255265
<< Captured StdOut/StdErr Output
------------------------------
SS•SSSSSS••S••SSS•SS••SS••SSSS••SS•S•••••••
------------------------------
• [79.876 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/1680648272
<< Captured StdOut/StdErr Output
------------------------------
•S•••SSS••S••S•SSS••S•SSSS•S••SSS•••••S••SSS•SSS
------------------------------
• [9.187 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/2965778464
<< Captured StdOut/StdErr Output
------------------------------
• [86.176 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/2548272904
<< Captured StdOut/StdErr Output
------------------------------
SS•••S•S•••S•••SSS•••SS••S••S•SS•S•S•••SS•SS•••
------------------------------
• [11.257 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/490648976
<< Captured StdOut/StdErr Output
------------------------------
S••S••SS••SS•••SSS•••S•SS
------------------------------
• [9.883 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/69651012
<< Captured StdOut/StdErr Output
------------------------------
•••SSSSSS••••SS•SSS•S
------------------------------
• [68.303 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:3170
Captured StdOut/StdErr Output >>
PID: 25398
<< Captured StdOut/StdErr Output
------------------------------
S••••S••••••SSSS••SSSS•SS•••SS••••SS••SSSS•SSS•S
------------------------------
• [11.015 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/2270941382
<< Captured StdOut/StdErr Output
------------------------------
S•S••S••S•S•S••SSSSS•••S•S
------------------------------
• [17.471 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/2061630363
<< Captured StdOut/StdErr Output
------------------------------
S••••••S
------------------------------
• [2.732 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/2558348365
<< Captured StdOut/StdErr Output
------------------------------
SS•••SSSS•S••S•S••SS••S••••S•S
------------------------------
• [10.814 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/2127123449
<< Captured StdOut/StdErr Output
------------------------------
•••••SS••
------------------------------
• [2.902 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/1116925813
<< Captured StdOut/StdErr Output
------------------------------
SSS•••S••S•S••SS••S
------------------------------
• [10.564 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/3147691490
<< Captured StdOut/StdErr Output
------------------------------
•S••S•••••
------------------------------
• [4.149 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/284969612
<< Captured StdOut/StdErr Output
------------------------------
SSSSS••••SSS••SS•••SS•SS•S•SSSSS•SS•SSSS•SSS••SS•••SS
------------------------------
• [9.589 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/794166913
<< Captured StdOut/StdErr Output
------------------------------
••••S•••SS•••••••SSS••S•SSSS••S•••S••••••SS•
------------------------------
• [12.677 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/809739997
<< Captured StdOut/StdErr Output
------------------------------
•••••SSSS••S•S•••SS••••S••S•••SS••SSSS•S•S•SS•••SS
------------------------------
• [85.897 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/1335416506
<< Captured StdOut/StdErr Output
------------------------------
•S••S••S•••S•SSS•S•SSSS••S••••SS•SS••S•S•S
------------------------------
• [20.981 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/1879290682
<< Captured StdOut/StdErr Output
------------------------------
S••S
------------------------------
• [11.030 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/2884318043
<< Captured StdOut/StdErr Output
------------------------------
•SS•S••••SS•S••••••S••••S•••••
------------------------------
• [17.573 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/2982938623
<< Captured StdOut/StdErr Output
------------------------------
S•S•S••••SSSSSS•••S•SSS•S••••SS
------------------------------
• [11.221 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/481340764
<< Captured StdOut/StdErr Output
------------------------------
•••
------------------------------
• [21.413 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/113207228
<< Captured StdOut/StdErr Output
------------------------------
SS•SSSS•
------------------------------
• [20.839 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/1535380933
<< Captured StdOut/StdErr Output
------------------------------
SSSS•S•SS•S•••
------------------------------
• [10.978 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/508026510
<< Captured StdOut/StdErr Output
------------------------------
SS••SSS••S•••S•SSSS••••S••SSS••SS•S•••S•S••••••••••••••
Ran 452 of 824 Specs in 2276.323 seconds
SUCCESS! -- 452 Passed | 0 Failed | 0 Pending | 372 Skipped
Ginkgo ran 1 suite in 39m1.153973759s
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
go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo --randomize-all --slow-spec-threshold=120s -timeout 14400s --no-color -nodes=12 --junit-report="test-e2e.xml" tests/e2escenarios
Running Suite: odo e2e scenarios - /go/odo_1/tests/e2escenarios
===============================================================
Random Seed: 1682449916 - will randomize all specs
Will run 4 of 4 specs
Running in parallel across 12 processes
------------------------------
• [125.630 seconds]
E2E Test starting with non-empty Directory test debugging should verify developer workflow from non-empty Directory
/go/odo_1/tests/e2escenarios/e2e_test.go:329
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo init' from /tmp/4066946201
<< Captured StdOut/StdErr Output
------------------------------
• [149.594 seconds]
E2E Test starting with empty Directory should verify developer workflow from empty Directory
/go/odo_1/tests/e2escenarios/e2e_test.go:63
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo init' from /tmp/1195421569
Spawning '/go/bin/odo delete component' from /tmp/1195421569
<< Captured StdOut/StdErr Output
------------------------------
• [166.862 seconds]
E2E Test starting with non-empty Directory add Binding should verify developer workflow of using binding as env in innerloop
/go/odo_1/tests/e2escenarios/e2e_test.go:462
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo init' from /tmp/2240549221
<< Captured StdOut/StdErr Output
------------------------------
• [280.018 seconds]
E2E Test starting with non-empty Directory should verify developer workflow from non-empty Directory
/go/odo_1/tests/e2escenarios/e2e_test.go:197
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo init' from /tmp/1664917392
Spawning '/go/bin/odo delete component' from /tmp/1664917392
<< Captured StdOut/StdErr Output
------------------------------
Ran 4 of 4 Specs in 280.042 seconds
SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped
Ginkgo ran 1 suite in 5m3.880672771s
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