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=c9c4258e3" ./cmd/odo/
go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo --randomize-all --slow-spec-threshold=120s -timeout 14400s --no-color -nodes=8 --junit-report="test-integration.xml" --label-filter="!unauth && !nocluster && !podman" tests/integration
Running Suite: Integration Suite - /go/odo_1/tests/integration
==============================================================
Random Seed: 1682409040 - will randomize all specs
Will run 462 of 824 specs
Running in parallel across 8 processes
SS••SS•S•
------------------------------
• [67.418 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:3146
Captured StdOut/StdErr Output >>
PID: 11976
<< Captured StdOut/StdErr Output
------------------------------
•SSSSSSSSSS
------------------------------
• [2.940 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/4177829207
<< Captured StdOut/StdErr Output
------------------------------
SSSS•••S••S••S•
------------------------------
• [11.459 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/316913557
<< Captured StdOut/StdErr Output
------------------------------
•••S•
------------------------------
• [10.666 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/1990459201
<< Captured StdOut/StdErr Output
------------------------------
•S•SS•SSSS•••••S••
------------------------------
• [21.947 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/1692331745
<< Captured StdOut/StdErr Output
------------------------------
••SS
------------------------------
• [2.665 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/3156020020
<< Captured StdOut/StdErr Output
------------------------------
S••S•••••S••
------------------------------
• [14.195 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/415163757
<< Captured StdOut/StdErr Output
------------------------------
S•••S••S•••S•SSSS•••SS•S••SS••SS•S•S••SSS••SS••S•SS•S•S•SS•SSS•SS•••••S•SSSS•••••SSS••S••S•SSS••SS•S••••••SS•S••S•S•••SSS•••••••SSSSSS••SSSSS•S•SSS••S•••••S•SSS•
------------------------------
• [2.830 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/3114676411
<< Captured StdOut/StdErr Output
------------------------------
S•S•S•S••S•SS•SS•S•S•SS•S•SS••S•SSS••••SS•SSS
------------------------------
• [20.469 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/3716351766
<< Captured StdOut/StdErr Output
------------------------------
SS••••SSS
------------------------------
• [13.074 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/851595747
<< Captured StdOut/StdErr Output
------------------------------
SSS•••SS••S•SS•S••SSS••••SS•••SS•SS•S•S•••SS••••••S••••••••••••••SS•S••••S•SS•S•••SSS••S••SSS
------------------------------
• [23.556 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/3641917373
<< Captured StdOut/StdErr Output
------------------------------
•S••S•••SSS•••S•S••S
------------------------------
• [3.334 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/336956207
<< Captured StdOut/StdErr Output
------------------------------
SS•••S•SSS
------------------------------
• [78.592 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/1136402027
<< Captured StdOut/StdErr Output
------------------------------
•SS•••S•••SS•S••••••
------------------------------
• [11.652 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/2621106634
<< Captured StdOut/StdErr Output
------------------------------
•S•••••SS••S••SS•••S•
------------------------------
• [14.269 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/1117318397
<< Captured StdOut/StdErr Output
------------------------------
•••S•S•SSS
------------------------------
• [22.825 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/2708086683
<< Captured StdOut/StdErr Output
------------------------------
SS•SS••
------------------------------
• [11.016 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/2918001969
<< Captured StdOut/StdErr Output
------------------------------
•SSS•SS•SSSS•S•S••••SSSS•••••S•••SSS
------------------------------
• [11.299 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/549013895
<< Captured StdOut/StdErr Output
------------------------------
S•S•S••S•
------------------------------
• [11.522 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/3850616088
<< Captured StdOut/StdErr Output
------------------------------
••S•SSS••S••S••••S••S•S••S•••••S•SSS•SSSS•SSS••S••S••SS••S
------------------------------
• [81.022 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/739077721
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [10.668 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/2233819900
<< Captured StdOut/StdErr Output
------------------------------
S•S••••S•••S•••SSSSS
------------------------------
• [82.861 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/1839683357
<< Captured StdOut/StdErr Output
------------------------------
•SSSS•SSS•
------------------------------
• [9.770 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/2089215715
<< Captured StdOut/StdErr Output
------------------------------
S••SSS••S•S••S
------------------------------
• [18.998 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/3684424308
<< Captured StdOut/StdErr Output
------------------------------
•••SSS•••••••SS•SS••SS•
------------------------------
• [12.785 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/924353256
<< Captured StdOut/StdErr Output
------------------------------
SSSS•S•SS•S•••S•
------------------------------
• [11.413 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/2618737770
<< Captured StdOut/StdErr Output
------------------------------
S•••S•S•••S•••SSS•SS•SSS•SS••SSS•SSSSSS••••••S•
------------------------------
• [8.672 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/3728772685
<< Captured StdOut/StdErr Output
------------------------------
••S•S••SS••SS•S•••••S•••S•SSSSSSSS••
------------------------------
• [9.493 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/3032212066
<< Captured StdOut/StdErr Output
------------------------------
••••S•S•S•S•S•SSSSSS•
------------------------------
• [9.698 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/388019893
<< Captured StdOut/StdErr Output
------------------------------
•S•••SS••••SSSSS••S•S••S•S••••••••
Ran 452 of 824 Specs in 3411.716 seconds
SUCCESS! -- 452 Passed | 0 Failed | 0 Pending | 372 Skipped
Ginkgo ran 1 suite in 57m58.0359018s
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=8 --junit-report="test-e2e.xml" tests/e2escenarios
Running Suite: odo e2e scenarios - /go/odo_1/tests/e2escenarios
===============================================================
Random Seed: 1682412525 - will randomize all specs
Will run 4 of 4 specs
Running in parallel across 8 processes
------------------------------
• [136.617 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/433708200
<< Captured StdOut/StdErr Output
------------------------------
• [151.184 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/315802801
Spawning '/go/bin/odo delete component' from /tmp/315802801
<< Captured StdOut/StdErr Output
------------------------------
• [167.490 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/428562527
<< Captured StdOut/StdErr Output
------------------------------
• [269.294 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/4112484548
Spawning '/go/bin/odo delete component' from /tmp/4112484548
<< Captured StdOut/StdErr Output
------------------------------
Ran 4 of 4 Specs in 269.313 seconds
SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped
Ginkgo ran 1 suite in 4m52.789656743s
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