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=1142929b8" ./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: 1682073247 - will randomize all specs
Will run 460 of 820 specs
Running in parallel across 16 processes
SSSSSSSSSSSSSSS•S••••S•••••SS•SSS•SSSS••S
------------------------------
• [25.479 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/2574017751
<< Captured StdOut/StdErr Output
------------------------------
SS••S••
------------------------------
• [28.950 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/2687673254
<< Captured StdOut/StdErr Output
------------------------------
SSSSS•SSS•SSSS••••S••S•••
------------------------------
• [11.866 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/4081059751
<< Captured StdOut/StdErr Output
------------------------------
S•SS•S•SS•S••SSSSS•S•••••
------------------------------
• [18.734 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/317095033
<< Captured StdOut/StdErr Output
------------------------------
•SS••••S•
------------------------------
• [3.416 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/3634001317
<< Captured StdOut/StdErr Output
------------------------------
SSS•S•••••••••S••S•
------------------------------
• [15.905 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/592115258
<< Captured StdOut/StdErr Output
------------------------------
••
------------------------------
• [3.060 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/1991632271
<< Captured StdOut/StdErr Output
------------------------------
•••S•S•SSSSSS•S
------------------------------
• [13.834 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/1544835429
<< Captured StdOut/StdErr Output
------------------------------
S••••••••S•••SS••S••S
------------------------------
• [4.021 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/1297008282
<< Captured StdOut/StdErr Output
------------------------------
•••SS••SSSS••S•••S•SSS••••S••••
------------------------------
• [13.233 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/3946398660
<< Captured StdOut/StdErr Output
------------------------------
SSS••••••••
------------------------------
• [16.312 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/656628870
<< Captured StdOut/StdErr Output
------------------------------
•S•S•SSSSS••SS•SS•S••SS•S•••S••S••
------------------------------
• [20.653 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/4100436837
<< Captured StdOut/StdErr Output
------------------------------
SS•••S
------------------------------
• [18.247 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/2404623536
<< Captured StdOut/StdErr Output
------------------------------
S•SSS••••SSS•SS•••S••S•S••S••••S••SS••SSS••••SSS••SSS•••S•SS••••S•S•S
------------------------------
• [35.862 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/513406263
<< Captured StdOut/StdErr Output
------------------------------
S•S•S••S••••SS•SS••••S
------------------------------
• [3.900 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/1992303313
<< Captured StdOut/StdErr Output
------------------------------
S•S••SS
------------------------------
• [10.544 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/2324581285
<< Captured StdOut/StdErr Output
------------------------------
••S•SSSS••••••
------------------------------
• [12.692 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/4001815262
<< Captured StdOut/StdErr Output
------------------------------
SSSS•••••••SS•SSS••SSSSS•••SS••SSSS
------------------------------
• [17.274 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/3941503333
<< Captured StdOut/StdErr Output
------------------------------
•SS•••S••SSS••S••SSSSS••SS•S•SSS•SS••SSSSSSS•••SSS•SSSSS•S••••SSSS•••S•SS
------------------------------
• [55.838 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:3040
Captured StdOut/StdErr Output >>
PID: 2498
<< Captured StdOut/StdErr Output
------------------------------
•SSS••••••••S••SSSSS•••SSSSSS•••S•
------------------------------
• [85.174 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/2292666849
<< Captured StdOut/StdErr Output
------------------------------
•S•S
------------------------------
• [17.405 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/141657067
<< Captured StdOut/StdErr Output
------------------------------
•S•••S••SS••••••S••••S••SS••SSS•SSS••
------------------------------
• [103.812 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/2326675332
<< Captured StdOut/StdErr Output
------------------------------
SS•
------------------------------
• [13.578 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/2497111713
<< Captured StdOut/StdErr Output
------------------------------
•••S••S•S•••S••S•SSS•S••S•SSSS•••SS•S
------------------------------
• [11.275 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/1032638488
<< Captured StdOut/StdErr Output
------------------------------
••S•••S•SSS
------------------------------
• [14.178 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/211511948
<< Captured StdOut/StdErr Output
------------------------------
•SSS••SS
------------------------------
• [89.588 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/932485664
<< Captured StdOut/StdErr Output
------------------------------
••SS••••••S•S•••S•S•••SSS••S••S••SS•S•SSSSSS••SSS•S•S•••••S•S•SS•
------------------------------
• [19.963 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/3604534044
<< Captured StdOut/StdErr Output
------------------------------
•S•S•S••SS•••••S•S••S••••S•S•S•SS•S•SS•SSS••••••S•SS•S
------------------------------
• [22.926 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/32086980
<< Captured StdOut/StdErr Output
------------------------------
••SS•SS••••S•S••SSSSS•••SSS••SSS•••SSS•S••SS•
------------------------------
• [8.910 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/3352770102
<< Captured StdOut/StdErr Output
------------------------------
••S•S••SSSS••••••••••••••••
Ran 450 of 820 Specs in 2203.324 seconds
SUCCESS! -- 450 Passed | 0 Failed | 0 Pending | 370 Skipped
Ginkgo ran 1 suite in 37m50.288005375s
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: 1682075524 - will randomize all specs
Will run 7 of 7 specs
Running in parallel across 16 processes
••
------------------------------
• [149.866 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/3089807403
Spawning '/go/bin/odo delete component' from /tmp/3089807403
<< Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [160.599 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/3192546160
Spawning '/go/bin/odo delete component' from /tmp/3192546160
<< Captured StdOut/StdErr Output
------------------------------
•
------------------------------
• [179.390 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/1720327798
<< Captured StdOut/StdErr Output
------------------------------
Ran 7 of 7 Specs in 179.441 seconds
SUCCESS! -- 7 Passed | 0 Failed | 0 Pending | 0 Skipped
Ginkgo ran 1 suite in 3m15.761050492s
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