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=d800b9417" ./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: 1681398683 - will randomize all specs
Will run 454 of 805 specs
Running in parallel across 16 processes
SSSSSSSSSSSS•S••••••SSSSS••SSS•SSS•••••SSSSS••SSSSSS•SS•••S•S•SS•S•••••S•S•••S•••S••SSSSS••••S•S•SSS•SSSSS•SS••S••••SSS••
------------------------------
• [5.679 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/2651131497
<< Captured StdOut/StdErr Output
------------------------------
S••SSSS•S•SSS••S••SSS••
------------------------------
• [13.091 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/1797185286
<< Captured StdOut/StdErr Output
------------------------------
•SSSS••SSS•S••••
------------------------------
• [84.357 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/1394501229
<< Captured StdOut/StdErr Output
------------------------------
SSSSSS•S••SSSS••••••••••••S••SS•••SS••S••SS••••••S••S•SS•
------------------------------
• [14.678 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/2313132281
<< Captured StdOut/StdErr Output
------------------------------
•••SSSS•S•S•SSSS•SSSSS
------------------------------
• [15.252 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/843183323
<< Captured StdOut/StdErr Output
------------------------------
S•SS•SSS•S
------------------------------
• [16.383 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/2892180227
<< Captured StdOut/StdErr Output
------------------------------
S•••
------------------------------
• [33.562 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/3885425591
<< Captured StdOut/StdErr Output
------------------------------
•••••••S••S•S
------------------------------
• [22.629 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/4214240018
<< Captured StdOut/StdErr Output
------------------------------
•SS
------------------------------
• [26.651 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/3920326245
<< Captured StdOut/StdErr Output
------------------------------
SS•••••••S••S••••••S•S•S•S•SS••••SSSSSSSSS•S•S•SSS•S•••S•S••S•S••S•SS•S•S••••SSS••SS•SSSS••S••••SSS••••••SS•SS
------------------------------
• [12.375 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/814379837
<< Captured StdOut/StdErr Output
------------------------------
S•S••••S•SSSS•SSSS•S•SS
------------------------------
• [3.556 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/4281626214
<< Captured StdOut/StdErr Output
------------------------------
S•S•••S•••SS•S•••••S•••SSS•SSS•S•S••••S•••S••••S
------------------------------
• [88.695 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/2473642148
<< Captured StdOut/StdErr Output
------------------------------
• [11.156 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/2277971966
<< Captured StdOut/StdErr Output
------------------------------
••S•••SS•SS•SSSS•••••
------------------------------
• [15.669 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/3508457344
<< Captured StdOut/StdErr Output
------------------------------
• [26.917 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/2229305199
<< Captured StdOut/StdErr Output
------------------------------
••S•SS•SS•••S•SS••••S
------------------------------
• [37.251 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/1168760140
<< Captured StdOut/StdErr Output
------------------------------
SS•SS••••SSS
------------------------------
• [22.251 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/170669185
<< Captured StdOut/StdErr Output
------------------------------
SSS••SS••SS•S•SS•SS•••••••SSSSS•SSSSSSS•SS••••••SS•••SS•SSS•••••S••••S••••SSS
------------------------------
• [13.542 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/1903308215
<< Captured StdOut/StdErr Output
------------------------------
•••••••SS•S•S••SS•SSS•S•••SSS•
------------------------------
• [83.601 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/322178056
<< Captured StdOut/StdErr Output
------------------------------
S•S••S•SSSSS••••S•SSS•
------------------------------
• [56.757 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/151354727
<< Captured StdOut/StdErr Output
------------------------------
SS••S
------------------------------
• [3.838 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/3280760112
<< Captured StdOut/StdErr Output
------------------------------
•SS•SSS••S•••••S•S•••••S••S••S•
------------------------------
• [12.116 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/4083397099
<< Captured StdOut/StdErr Output
------------------------------
•S•SS•••••SSS•S•••S•••S
------------------------------
• [15.756 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/2159474514
<< Captured StdOut/StdErr Output
------------------------------
•••S
------------------------------
• [19.678 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/2458832709
<< Captured StdOut/StdErr Output
------------------------------
•••
------------------------------
• [5.246 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/2427929742
<< Captured StdOut/StdErr Output
------------------------------
SS•
------------------------------
• [41.554 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/1586380335
<< Captured StdOut/StdErr Output
------------------------------
••••••SS••S•S••••S•
------------------------------
• [16.496 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/1589833920
<< Captured StdOut/StdErr Output
------------------------------
S••SSSS•S•SSS•S••••S••
------------------------------
• [19.825 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/2063076997
<< Captured StdOut/StdErr Output
------------------------------
•S••••SSSSS•••SSS•••••••••••••••••
Ran 444 of 805 Specs in 1902.806 seconds
SUCCESS! -- 444 Passed | 0 Failed | 0 Pending | 361 Skipped
Ginkgo ran 1 suite in 32m48.965155658s
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=16 --junit-report="test-e2e.xml" tests/e2escenarios
Running Suite: odo e2e scenarios - /go/odo_1/tests/e2escenarios
===============================================================
Random Seed: 1681400659 - will randomize all specs
Will run 7 of 7 specs
Running in parallel across 16 processes
•••
------------------------------
• [144.344 seconds]
E2E Test starting with non-empty Directory should verify developer workflow from non-empty Directory
/go/odo_1/tests/e2escenarios/e2e_test.go:193
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo init' from /tmp/2993790195
Spawning '/go/bin/odo delete component' from /tmp/2993790195
<< Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [169.355 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:350
Captured StdOut/StdErr Output >>
Spawning '/go/bin/odo init' from /tmp/3293885937
<< Captured StdOut/StdErr Output
------------------------------
• [171.726 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/2952262984
Spawning '/go/bin/odo delete component' from /tmp/2952262984
<< Captured StdOut/StdErr Output
------------------------------
Ran 7 of 7 Specs in 172.056 seconds
SUCCESS! -- 7 Passed | 0 Failed | 0 Pending | 0 Skipped
Ginkgo ran 1 suite in 3m16.688835794s
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