cp ododevapispec.yaml pkg/apiserver-impl/swagger-ui/swagger.yaml
go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=5250cdf85" ./cmd/odo/
go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo --randomize-all --poll-progress-after=120s --poll-progress-interval=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: 1701420955 - will randomize all specs
Will run 504 of 956 specs
Running in parallel across 16 processes
SSSSSSSSSSSSSSSSSS
------------------------------
• [19.129 seconds]
odo devfile deploy command tests using a Devfile with an image component using a remote Dockerfile when remote server returns a valid file should run odo deploy
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:538
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36687"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [18.890 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an Image component with a build context should build image via Docker if build context references PROJECT_SOURCE env var
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:326
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37895"
<< Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [21.895 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=false --running-in=dev should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35721"
<< Captured StdOut/StdErr Output
------------------------------
• [23.863 seconds]
odo devfile deploy command tests deploying devfile with exec when using devfile that works; with component name of at max(63) characters length should complete the command execution successfully
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:576
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44121"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [8.285 seconds]
odo create/delete/list/set namespace/project tests set project should successfully set the project
/go/odo_1/tests/integration/cmd_namespace_test.go:147
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35905"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [29.051 seconds]
odo create/delete/list/set namespace/project tests delete namespace when force-deleting a valid namespace should successfully delete the namespace synchronously with --wait
/go/odo_1/tests/integration/cmd_namespace_test.go:115
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40651"
<< Captured StdOut/StdErr Output
------------------------------
• [4.810 seconds]
odo devfile deploy command tests using a Devfile with an image component using a remote Dockerfile when remote server returns an error should not build images
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:502
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:32997"
<< Captured StdOut/StdErr Output
------------------------------
• [40.880 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="dev") when odo delete command is run again with nothing deployed on the cluster should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:151
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36909"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [41.667 seconds]
odo logs command tests when component is created and odo logs is executed when running in Deploy mode when --follow flag is specified should successfully follow logs of running component
/go/odo_1/tests/integration/cmd_logs_test.go:291
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35967"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [6.092 seconds]
odo logs command tests when directory is empty should error
/go/odo_1/tests/integration/cmd_logs_test.go:86
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40337"
<< Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [62.928 seconds]
odo dev command tests when using a Devfile with no commands should start the Dev Session with --no-commands=false
/go/odo_1/tests/integration/cmd_dev_test.go:4921
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39835"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [62.935 seconds]
odo dev command tests when a component is bootstrapped when odo is executed with --no-watch flag and with --no-commands when a file in component directory is modified should not trigger a push
/go/odo_1/tests/integration/cmd_dev_test.go:736
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43547"
<< Captured StdOut/StdErr Output
------------------------------
SSSSSS
------------------------------
• [63.565 seconds]
odo dev command tests when a component is bootstrapped when running with --no-commands (debug=false) should start the dev session
/go/odo_1/tests/integration/cmd_dev_test.go:268
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33363"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [69.366 seconds]
odo dev command tests when a container component defines a Command or Args - with metadata.name should run odo dev successfully (#5620)
/go/odo_1/tests/integration/cmd_dev_test.go:3538
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39401"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [70.876 seconds]
odo dev command tests when a component is bootstrapped should use the index information from previous push operation
/go/odo_1/tests/integration/cmd_dev_test.go:200
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43655"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [73.690 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43581"
<< Captured StdOut/StdErr Output
------------------------------
• [9.435 seconds]
odo create/delete/list/set namespace/project tests create namespace should successfully create the namespace
/go/odo_1/tests/integration/cmd_namespace_test.go:54
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46595"
<< Captured StdOut/StdErr Output
------------------------------
• [60.877 seconds]
odo dev command tests when no project is present - with metadata.name should sync to the correct dir in container
/go/odo_1/tests/integration/cmd_dev_test.go:2164
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42597"
<< Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [53.349 seconds]
odo dev command tests when using a Devfile with no commands should start the Dev Session with --no-commands=true
/go/odo_1/tests/integration/cmd_dev_test.go:4921
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33219"
<< Captured StdOut/StdErr Output
------------------------------
• [61.067 seconds]
odo dev command tests when a component is bootstrapped when recording telemetry data should record the telemetry data correctly
/go/odo_1/tests/integration/cmd_dev_test.go:458
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41343"
<< Captured StdOut/StdErr Output
------------------------------
• [64.281 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped the component is deleted while having access to the devfile.yaml when the component is deleted with --files should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:178
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42869"
<< Captured StdOut/StdErr Output
------------------------------
• [10.945 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44183"
<< Captured StdOut/StdErr Output
------------------------------
• [48.044 seconds]
odo dev command tests when running odo dev --no-watch and build command throws an error should error out with some log
/go/odo_1/tests/integration/cmd_dev_test.go:2898
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35351"
<< Captured StdOut/StdErr Output
------------------------------
• [3.877 seconds]
odo create/delete/list/set namespace/project tests list namespace should successfully list all the namespaces
/go/odo_1/tests/integration/cmd_namespace_test.go:221
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46241"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [60.986 seconds]
odo dev command tests when multiple projects are present - with metadata.name should sync to the correct dir in container
/go/odo_1/tests/integration/cmd_dev_test.go:2130
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43777"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
S [3.763 seconds]
odo dev command tests when Starting a PostgreSQL service [BeforeEach] when creating local files and dir and running odo dev - without metadata.name should correctly propagate changes to the container
[BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:1815
[It] /go/odo_1/tests/integration/cmd_dev_test.go:1865
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44947"
<< Captured StdOut/StdErr Output
[SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true
In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:1818 @ 12/01/23 08:58:46.525
------------------------------
• [106.025 seconds]
odo logs command tests when component is created and odo logs is executed when running in Dev mode should successfully show logs of the running component
/go/odo_1/tests/integration/cmd_logs_test.go:140
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33871"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [5.848 seconds]
odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy with image build extra args should succeed
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:143
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34617"
<< Captured StdOut/StdErr Output
------------------------------
• [7.529 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44881"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
S [5.453 seconds]
odo devfile deploy command tests when deploying a ServiceBinding k8s resource [BeforeEach] when odo deploy is run should successfully deploy the ServiceBinding resource
[BeforeEach] /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:387
[It] /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:412
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41593"
<< Captured StdOut/StdErr Output
[SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true
In [BeforeEach] at: /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:390 @ 12/01/23 08:58:55.433
------------------------------
• [6.937 seconds]
odo generic executing odo version command should only print client info when using --client flag
/go/odo_1/tests/integration/generic_test.go:201
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40267"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [59.808 seconds]
odo dev debug command tests when a component is bootstrapped when running odo dev with debug flag and custom port mapping for port forwarding should connect to relevant custom ports forwarded
/go/odo_1/tests/integration/cmd_dev_debug_test.go:76
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33239"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [89.083 seconds]
odo dev command with api server tests when the component is bootstrapped when odo is executed with --no-watch and --api-server flags when a file in component directory is modified when /component/command endpoint is POSTed should trigger a push
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:282
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41121"
<< Captured StdOut/StdErr Output
------------------------------
• [19.419 seconds]
odo create/delete/list/set namespace/project tests delete project when force-deleting a valid project should successfully delete the project synchronously with --wait
/go/odo_1/tests/integration/cmd_namespace_test.go:115
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35827"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [58.895 seconds]
odo dev command tests when running odo dev and devfile with composite command - without metadata.name should execute all commands in composite command
/go/odo_1/tests/integration/cmd_dev_test.go:2610
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34929"
<< Captured StdOut/StdErr Output
------------------------------
• [7.153 seconds]
odo create/delete/list/set namespace/project tests set namespace should successfully set the namespace
/go/odo_1/tests/integration/cmd_namespace_test.go:147
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33747"
<< Captured StdOut/StdErr Output
------------------------------
SSSSSS
------------------------------
• [58.619 seconds]
odo dev command tests when a component is bootstrapped when odo is executed with --no-watch flag and with --no-commands when a file in component directory is modified when p is pressed should trigger a push
/go/odo_1/tests/integration/cmd_dev_test.go:754
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44231"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
Progress Report for Ginkgo Process #4
Automatically polling progress:
odo dev command tests when running odo dev and multiple env variables are set - without metadata.name should be able to exec command (Spec Runtime: 2m14.338s)
/go/odo_1/tests/integration/cmd_dev_test.go:1717
In [It] (Node Runtime: 2m0.001s)
/go/odo_1/tests/integration/cmd_dev_test.go:1717
Begin Captured GinkgoWriter Output >>
...
[odo] read: read /dev/stdin: input/output error
[odo] I1201 08:58:50.602319 12991 watch.go:333] Dev mode interrupted by user
[odo] I1201 08:58:50.624816 12991 implem.go:114] The path for preference file is /tmp/112040142/preference.yaml
[odo] I1201 08:58:50.625907 12991 segment.go:268] Checking telemetry enable status
[odo] I1201 08:58:50.625917 12991 segment.go:286] Sending telemetry disabled by env variable
[odo] Cleaning resources, please wait
[odo] I1201 08:58:50.728898 12991 all.go:46] starting to concurrently query 201 APIs
[odo] I1201 08:58:50.730063 12991 all.go:62] fired up all goroutines to query APIs
[odo] I1201 08:58:51.804139 12991 all.go:67] all goroutines have returned in 1.075730287s
[odo] I1201 08:58:51.804227 12991 all.go:76] query result: objects=627
<< End Captured GinkgoWriter Output
Spec Goroutine
goroutine 70 [select]
github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0005700e0, {0x314b5d8?, 0xc0008442a0}, 0x1, {0x0, 0x0, 0x0})
/go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538
github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0005700e0, {0x314b5d8, 0xc0008442a0}, {0x0, 0x0, 0x0})
/go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145
github.com/onsi/gomega/gexec.(*Session).Wait(0xc000f67d70?, {0xc001250150?, 0x2d36b12?, 0x3?})
/go/odo_1/vendor/github.com/onsi/gomega/gexec/session.go:144
github.com/redhat-developer/odo/tests/helper.DevSession.WaitEnd(...)
/go/odo_1/tests/helper/helper_dev.go:263
github.com/redhat-developer/odo/tests/helper.RunDevMode.func1()
/go/odo_1/tests/helper/helper_dev.go:334
github.com/redhat-developer/odo/tests/helper.RunDevMode({{0x0, 0x0, 0x0}, {0x0, 0x0, 0x0}, 0x0, 0x0, 0x0, 0x0, ...}, ...)
/go/odo_1/tests/helper/helper_dev.go:337
> github.com/redhat-developer/odo/tests/integration.glob..func7.12.2()
/go/odo_1/tests/integration/cmd_dev_test.go:1718
|
| It("should be able to exec command", func() {
> err := helper.RunDevMode(helper.DevSessionOpts{
| RunOnPodman: podman,
| }, func(session *gexec.Session, out, err string, ports map[string]string) {
github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x2d64db8, 0x0})
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463
github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3()
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865
github.com/onsi/ginkgo/v2/internal.(*Suite).runNode
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852
------------------------------
• [140.138 seconds]
odo dev command tests when running odo dev and multiple env variables are set - without metadata.name should be able to exec command
/go/odo_1/tests/integration/cmd_dev_test.go:1717
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36049"
<< Captured StdOut/StdErr Output
------------------------------
• [12.279 seconds]
odo logs command tests when component is created and odo logs is executed when running in Deploy mode should successfully show logs of the running component
/go/odo_1/tests/integration/cmd_logs_test.go:267
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39689"
<< Captured StdOut/StdErr Output
------------------------------
• [59.800 seconds]
odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag (custom api server port=false) should describe the API Server port (JSON)
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:123
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41051"
<< Captured StdOut/StdErr Output
------------------------------
• [59.875 seconds]
odo dev command tests when odo dev is executed to run a devfile containing multiple k8s resource defined under a single Devfile component should have created the necessary k8s resources
/go/odo_1/tests/integration/cmd_dev_test.go:1127
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40335"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [4.496 seconds]
odo dev command tests when running applications listening on the container loopback interface should error out if using --forward-localhost on any platform other than Podman
/go/odo_1/tests/integration/cmd_dev_test.go:4220
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45853"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [6.794 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=true --running-in=deploy should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46357"
<< Captured StdOut/StdErr Output
------------------------------
• [48.811 seconds]
odo dev command tests when running odo dev and build command throws an error should error out with some log
/go/odo_1/tests/integration/cmd_dev_test.go:2898
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44171"
<< Captured StdOut/StdErr Output
------------------------------
• [38.098 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped the component is deleted while having access to the devfile.yaml when the component is deleted with --files should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:178
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38193"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [54.933 seconds]
odo run command tests when a component is bootstrapped when odo dev is executed with --no-commands=true and ready should execute commands
/go/odo_1/tests/integration/cmd_run_test.go:100
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45043"
<< Captured StdOut/StdErr Output
------------------------------
• [89.752 seconds]
odo dev command tests when hotReload capable Build and Run commands are used with odo dev should execute the build and run commands
/go/odo_1/tests/integration/cmd_dev_test.go:3818
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41013"
<< Captured StdOut/StdErr Output
------------------------------
• [4.950 seconds]
odo dev command tests when Devfile contains neither metadata.language nor metadata.projectType when odo deploy is executed should set the correct value in labels of deployed resources
/go/odo_1/tests/integration/cmd_dev_test.go:4105
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36535"
<< Captured StdOut/StdErr Output
------------------------------
• [116.956 seconds]
odo dev command tests when a devfile with a local parent is used for odo dev and the parent is not synced when updating the parent should update the component
/go/odo_1/tests/integration/cmd_dev_test.go:3697
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34419"
<< Captured StdOut/StdErr Output
------------------------------
• [7.754 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=true --running-in= should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35691"
<< Captured StdOut/StdErr Output
------------------------------
• [120.866 seconds]
odo dev command tests when running odo dev with devfile contain volume - with metadata.name check the volume name and mount paths for the containers
/go/odo_1/tests/integration/cmd_dev_test.go:2230
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:32793"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [60.483 seconds]
odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag (custom api server port=true) should describe the API Server port
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:108
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37921"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [68.987 seconds]
odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag when /component/command endpoint is POSTed should trigger a push
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:221
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34357"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [118.941 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=true, customPortForwarding=false, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1379
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42353"
<< Captured StdOut/StdErr Output
------------------------------
• [8.769 seconds]
odo dev command tests when Devfile contains metadata.language when odo deploy is executed should set the correct value in labels of deployed resources
/go/odo_1/tests/integration/cmd_dev_test.go:4105
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41875"
<< Captured StdOut/StdErr Output
------------------------------
• [4.923 seconds]
odo dev command tests when running odo dev and prestart events are defined should not correctly execute PreStart commands
/go/odo_1/tests/integration/cmd_dev_test.go:2823
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41663"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [79.497 seconds]
odo dev command tests when devfile project field is present and running odo dev - without metadata.name should sync to the correct dir in container
/go/odo_1/tests/integration/cmd_dev_test.go:2097
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39107"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [130.072 seconds]
odo describe component command tests checking for remote source code location when using devfile with containers that has mountSource set to false and starting an odo dev session should show remote source code location in odo describe component output
/go/odo_1/tests/integration/cmd_describe_component_test.go:642
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44381"
<< Captured StdOut/StdErr Output
------------------------------
• [30.739 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted using its name and namespace from another directory should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:473
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45715"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [59.022 seconds]
odo dev command tests when a component is bootstrapped should add annotation to use ImageStreams
/go/odo_1/tests/integration/cmd_dev_test.go:147
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38569"
<< Captured StdOut/StdErr Output
------------------------------
Progress Report for Ginkgo Process #12
Automatically polling progress:
odo dev debug command tests when a composite apply command is used as debug command should execute the composite apply commands successfully (Spec Runtime: 3m42.134s)
/go/odo_1/tests/integration/cmd_dev_debug_test.go:288
In [It] (Node Runtime: 2m0s)
/go/odo_1/tests/integration/cmd_dev_debug_test.go:288
At [By Step] cleaning up the resources on ending the session (Step Runtime: 26.369s)
/go/odo_1/tests/integration/cmd_dev_debug_test.go:326
Begin Captured GinkgoWriter Output >>
...
[odo] stderr: []
[odo] I1201 09:00:21.478938 12916 execute_run.go:36] error while running background command: unable to exec command [/bin/sh -c echo $$ > /opt/odo/.odo_cmd_start-debug.pid && cd /projects && (npm run debug) 1>>/proc/1/fd/1 2>>/proc/1/fd/2; echo $? >> /opt/odo/.odo_cmd_start-debug.pid]: error while streaming command: context canceled
[odo] I1201 09:00:21.479260 12916 implem.go:114] The path for preference file is /tmp/3132305192/preference.yaml
[odo] Cleaning resources, please wait
[odo] I1201 09:00:21.480076 12916 segment.go:268] Checking telemetry enable status
[odo] I1201 09:00:21.480086 12916 segment.go:286] Sending telemetry disabled by env variable
[odo] I1201 09:00:21.631922 12916 all.go:46] starting to concurrently query 201 APIs
[odo] I1201 09:00:21.634576 12916 all.go:62] fired up all goroutines to query APIs
[odo] I1201 09:00:24.116370 12916 all.go:67] all goroutines have returned in 2.484711344s
[odo] I1201 09:00:24.116531 12916 all.go:76] query result: objects=669
<< End Captured GinkgoWriter Output
Spec Goroutine
goroutine 76 [select]
github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc00037e000, {0x314b5d8?, 0xc00140a738}, 0x1, {0x0, 0x0, 0x0})
/go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538
github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc00037e000, {0x314b5d8, 0xc00140a738}, {0x0, 0x0, 0x0})
/go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145
github.com/onsi/gomega/gexec.(*Session).Wait(0xc00045c840?, {0xc00089aa50?, 0x0?, 0x0?})
/go/odo_1/vendor/github.com/onsi/gomega/gexec/session.go:144
github.com/redhat-developer/odo/tests/helper.DevSession.WaitEnd(...)
/go/odo_1/tests/helper/helper_dev.go:263
> github.com/redhat-developer/odo/tests/integration.glob..func6.7.2.8()
/go/odo_1/tests/integration/cmd_dev_debug_test.go:328
| By("cleaning up the resources on ending the session", func() {
| devSession.Stop()
> devSession.WaitEnd()
| out := commonVar.CliRunner.Run("get", "deployments").Out.Contents()
| helper.DontMatchAllInOutput(string(out), deploymentNames)
github.com/onsi/ginkgo/v2/internal.(*Suite).By(0xc000130000, {0x2d9d9e7, 0x2f}, {0xc00068be70, 0x1, 0x1?})
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:309
github.com/onsi/ginkgo/v2.By({0x2d9d9e7?, 0x0?}, {0xc00068be70?, 0xc0006f7938?, 0xc000088640?})
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/core_dsl.go:547
> github.com/redhat-developer/odo/tests/integration.glob..func6.7.2()
/go/odo_1/tests/integration/cmd_dev_debug_test.go:326
| })
|
> By("cleaning up the resources on ending the session", func() {
| devSession.Stop()
| devSession.WaitEnd()
github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x10a5e65, 0xc0001d45a0})
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463
github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3()
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865
github.com/onsi/ginkgo/v2/internal.(*Suite).runNode
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852
------------------------------
• [32.419 seconds]
odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted using its name and namespace from another directory should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:473
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:32797"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [6.102 seconds]
odo dev command tests when running applications listening on the container loopback interface should error out if using --forward-localhost on any platform other than Podman
/go/odo_1/tests/integration/cmd_dev_test.go:4220
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41319"
<< Captured StdOut/StdErr Output
------------------------------
• [61.255 seconds]
odo dev command tests when Devfile contains neither metadata.language nor metadata.projectType when running odo dev should set the correct value in labels of resources
/go/odo_1/tests/integration/cmd_dev_test.go:4089
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44961"
<< Captured StdOut/StdErr Output
------------------------------
• [81.082 seconds]
odo dev debug command tests when running build and debug commands as composite in different containers and a shared volume - with metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_debug_test.go:388
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40581"
<< Captured StdOut/StdErr Output
------------------------------
• [11.815 seconds]
odo devfile deploy command tests deploying devfile with exec when using devfile that works; with component name of a normal character length should complete the command execution successfully
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:576
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37913"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [237.212 seconds]
odo dev debug command tests when a composite apply command is used as debug command should execute the composite apply commands successfully
/go/odo_1/tests/integration/cmd_dev_debug_test.go:288
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44767"
<< Captured StdOut/StdErr Output
------------------------------
• [58.971 seconds]
odo dev command tests when running odo dev with alternative commands - with metadata.name when running odo dev with a build command should execute the custom non-default build command successfully
/go/odo_1/tests/integration/cmd_dev_test.go:3112
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:32979"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [5.365 seconds]
odo create/delete/list/set namespace/project tests create namespace should fail to create namespace
/go/odo_1/tests/integration/cmd_namespace_test.go:63
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33231"
<< Captured StdOut/StdErr Output
------------------------------
• [5.274 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when running odo deploy with image build extra args should succeed
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:143
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40565"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [78.616 seconds]
odo dev command tests when creating local files and dir and running odo dev - without metadata.name when deleting local files and dir and waiting for sync should not list deleted dir and file in container
/go/odo_1/tests/integration/cmd_dev_test.go:1805
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34885"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [29.362 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped the component is deleted while having access to the devfile.yaml when the component is deleted with --files should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:178
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37347"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [60.211 seconds]
odo dev command tests when creating local files and dir and running odo dev - without metadata.name should correctly propagate changes to the container
/go/odo_1/tests/integration/cmd_dev_test.go:1788
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33951"
<< Captured StdOut/StdErr Output
------------------------------
• [7.122 seconds]
odo describe component command tests when creating a component should not describe the component from another directory, with default cluster mode
/go/odo_1/tests/integration/cmd_describe_component_test.go:264
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37927"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [112.565 seconds]
odo logs command tests when component is created and odo logs is executed when running in Dev mode when --follow flag is specified should successfully follow logs of running component
/go/odo_1/tests/integration/cmd_logs_test.go:172
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46733"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [9.114 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=false --running-in=deploy should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39273"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [9.078 seconds]
odo devfile deploy command tests when using a devfile.yaml containing two deploy commands should run odo deploy
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:244
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44765"
<< Captured StdOut/StdErr Output
------------------------------
• [122.187 seconds]
odo describe component command tests checking for remote source code location when using devfile with no sourceMapping, defaults to /projects and starting an odo dev session should show remote source code location in odo describe component output
/go/odo_1/tests/integration/cmd_describe_component_test.go:642
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43001"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [7.444 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=true --running-in=dev should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40415"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [27.973 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="dev") when odo delete command is run again with nothing deployed on the cluster should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:151
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39285"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [71.774 seconds]
odo dev debug command tests when running build and debug commands as composite in different containers and a shared volume - without metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_debug_test.go:388
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42809"
<< Captured StdOut/StdErr Output
------------------------------
• [9.217 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34775"
<< Captured StdOut/StdErr Output
------------------------------
• [139.851 seconds]
odo dev command tests when running odo dev with devfile containing volume-component - without metadata.name should successfully use the volume components in container components
/go/odo_1/tests/integration/cmd_dev_test.go:2278
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33573"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [78.523 seconds]
odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=true, customPortForwarding=true, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1463
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42129"
<< Captured StdOut/StdErr Output
------------------------------
• [72.813 seconds]
odo devfile deploy command tests deploying devfile with exec when using devfile with a long running command in exec should print the tip to run odo logs after 1 minute of execution
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:636
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36517"
<< Captured StdOut/StdErr Output
------------------------------
• [29.457 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="dev") should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:128
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34701"
<< Captured StdOut/StdErr Output
------------------------------
• [59.697 seconds]
odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a run command should execute the default run command successfully if specified explicitly
/go/odo_1/tests/integration/cmd_dev_test.go:3195
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41055"
<< Captured StdOut/StdErr Output
------------------------------
• [28.416 seconds]
odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33565"
<< Captured StdOut/StdErr Output
------------------------------
• [61.458 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37785"
<< Captured StdOut/StdErr Output
------------------------------
• [8.631 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45071"
<< Captured StdOut/StdErr Output
------------------------------
• [108.942 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=true, customPortForwarding=false, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1379
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36667"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [7.581 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=true --running-in=dev should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44401"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [87.319 seconds]
odo dev command tests when a component with endpoints is bootstrapped and pushed should not create Ingress or Route resources in the cluster
/go/odo_1/tests/integration/cmd_dev_test.go:3463
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43071"
<< Captured StdOut/StdErr Output
------------------------------
SSSSSSS
------------------------------
• [87.205 seconds]
odo dev command tests 1. devfile contains composite apply command when odo dev is running with container run extra args should execute the composite apply commands successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2388
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41891"
<< Captured StdOut/StdErr Output
------------------------------
S [5.510 seconds]
odo devfile deploy command tests deploying devfile with long-running exec when pod security is enforced as restricted [It] should set securitycontext for podsecurity admission on job's pod template
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:676
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40057"
<< Captured StdOut/StdErr Output
[SKIPPED] This is a Kubernetes specific scenario, skipping
In [It] at: /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:678 @ 12/01/23 09:02:29.582
------------------------------
S
------------------------------
• [117.689 seconds]
odo dev command tests when running odo dev and single env var is set - without metadata.name should be able to exec command
/go/odo_1/tests/integration/cmd_dev_test.go:1691
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37671"
<< Captured StdOut/StdErr Output
------------------------------
• [92.837 seconds]
odo logs command tests when component is created and odo logs is executed when running in Dev mode with --logs 1. should successfully show logs of the running component
/go/odo_1/tests/integration/cmd_logs_test.go:249
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45467"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [65.240 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="deploy") when odo delete command is run again with nothing deployed on the cluster should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:151
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43227"
<< Captured StdOut/StdErr Output
------------------------------
• [70.270 seconds]
odo dev command tests when devfile project field is present and running odo dev - with metadata.name should sync to the correct dir in container
/go/odo_1/tests/integration/cmd_dev_test.go:2097
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36061"
<< Captured StdOut/StdErr Output
------------------------------
• [5.781 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 >>
Using Devfile Registry URL at: "http://127.0.0.1:32793"
Spawning '/go/bin/odo deploy -v 4' from /tmp/1761964543
<< Captured StdOut/StdErr Output
------------------------------
• [8.531 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted using its name and namespace from another directory should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:241
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41549"
<< Captured StdOut/StdErr Output
------------------------------
• [84.576 seconds]
odo dev command tests when starting with Devfile with autoBuild or deployByDefault components when running odo dev with some components not referenced in the Devfile should create the appropriate resources
/go/odo_1/tests/integration/cmd_dev_test.go:4466
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42523"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [59.905 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped the component is deleted while having access to the devfile.yaml when the component is deleted with --files should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:178
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36907"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [118.548 seconds]
odo dev command tests when doing odo dev and there is a env variable with spaces - with metadata.name should be able to exec command
/go/odo_1/tests/integration/cmd_dev_test.go:1743
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33539"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [66.867 seconds]
odo dev command tests when adding local files to gitignore and running odo dev when modifying /testdir/foobar.txt file should not synchronize it
/go/odo_1/tests/integration/cmd_dev_test.go:1987
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39695"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [57.877 seconds]
odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag should serve endpoints
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:171
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37673"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [93.694 seconds]
odo logs command tests when component is created and odo logs is executed when logs --follow is started when running in Dev mode should successfully follow logs of running component
/go/odo_1/tests/integration/cmd_logs_test.go:219
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33117"
<< Captured StdOut/StdErr Output
------------------------------
• [119.717 seconds]
odo dev command tests when a hotReload capable Run command is used with odo dev when a source file is modified should not re-execute the run command
/go/odo_1/tests/integration/cmd_dev_test.go:3787
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42327"
<< Captured StdOut/StdErr Output
------------------------------
• [118.504 seconds]
odo dev command tests when doing odo dev and there is a env variable with spaces - without metadata.name should be able to exec command
/go/odo_1/tests/integration/cmd_dev_test.go:1743
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39739"
<< Captured StdOut/StdErr Output
------------------------------
• [5.952 seconds]
odo dev command tests when a component is bootstrapped should fail when using --no-commands and --build-command and/or --run-command together
/go/odo_1/tests/integration/cmd_dev_test.go:233
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33461"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [62.922 seconds]
odo dev command tests when project and clonePath is present in devfile and running odo dev - without metadata.name should sync to the correct dir in container
/go/odo_1/tests/integration/cmd_dev_test.go:2058
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34777"
<< Captured StdOut/StdErr Output
------------------------------
• [12.307 seconds]
odo describe component command tests when creating a component should not describe the component from another directory, with cluster
/go/odo_1/tests/integration/cmd_describe_component_test.go:289
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37509"
<< Captured StdOut/StdErr Output
------------------------------
• [34.076 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="") when odo delete command is run again with nothing deployed on the cluster should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:151
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33203"
<< Captured StdOut/StdErr Output
------------------------------
• [31.207 seconds]
odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46511"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [14.075 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted using its name and namespace from another directory should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:241
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40419"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [52.782 seconds]
odo dev command tests when a component is bootstrapped when running with --no-commands (debug=true) should start the dev session
/go/odo_1/tests/integration/cmd_dev_test.go:268
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35273"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [8.819 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an Image component with no build context should build image via Podman by defaulting build context to devfile path
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:450
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41319"
<< Captured StdOut/StdErr Output
------------------------------
SSSSSSSS
------------------------------
• [61.522 seconds]
odo dev command tests when Devfile contains metadata.projectType when running odo dev should set the correct value in labels of resources
/go/odo_1/tests/integration/cmd_dev_test.go:4089
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:32829"
<< Captured StdOut/StdErr Output
------------------------------
• [8.055 seconds]
odo dev command with api server tests when the component is bootstrapped should fail if --api-server is false but --api-server-port is true
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:46
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46557"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [122.221 seconds]
odo dev command tests when running odo dev with devfile contain volume - without metadata.name should create pvc and reuse if it shares the same devfile volume name
/go/odo_1/tests/integration/cmd_dev_test.go:2197
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34511"
<< Captured StdOut/StdErr Output
------------------------------
• [7.684 seconds]
odo devfile deploy command tests deploying devfile with exec when using a devfile name with length more than 63 should fail with invalid component name error
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:622
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37405"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [61.714 seconds]
odo dev command tests when adding local files to gitignore and running odo dev should not sync ignored files to the container
/go/odo_1/tests/integration/cmd_dev_test.go:1955
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36223"
<< Captured StdOut/StdErr Output
------------------------------
• [132.449 seconds]
odo dev command tests when running odo dev and composite command is used as a run command - without metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2709
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41141"
<< Captured StdOut/StdErr Output
------------------------------
• [4.533 seconds]
odo dev command tests when a component is bootstrapped should fail when using --no-commands and --build-command and/or --run-command together
/go/odo_1/tests/integration/cmd_dev_test.go:233
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38825"
<< Captured StdOut/StdErr Output
------------------------------
• [111.016 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=false, customPortForwarding=true, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1379
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:32947"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [63.130 seconds]
odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted using its name and namespace from another directory should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:473
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44567"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [66.629 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="deploy") when odo delete command is run again with nothing deployed on the cluster should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:151
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34907"
<< Captured StdOut/StdErr Output
------------------------------
• [6.929 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 >>
Using Devfile Registry URL at: "http://127.0.0.1:45057"
Spawning '/go/bin/odo deploy' from /tmp/2904903040
<< Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [8.363 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38043"
<< Captured StdOut/StdErr Output
------------------------------
• [72.334 seconds]
odo dev command tests when adding local files to gitignore and running odo dev when modifying /testdir/foobar.txt file should not synchronize it
/go/odo_1/tests/integration/cmd_dev_test.go:1987
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36669"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [61.116 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43227"
<< Captured StdOut/StdErr Output
------------------------------
SS•S
------------------------------
• [6.083 seconds]
odo generic executing odo version command when executing the complete command with server info should show the version of odo major components including server login URL
/go/odo_1/tests/integration/generic_test.go:132
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46037"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [27.700 seconds]
odo delete command tests when deleting a component containing preStop event that is deployed with DEV and --files=false should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:517
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37059"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
S [4.231 seconds]
odo dev command tests when a component is bootstrapped [It] should not set securitycontext for podsecurity admission
/go/odo_1/tests/integration/cmd_dev_test.go:392
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41309"
<< Captured StdOut/StdErr Output
[SKIPPED] This is a Kubernetes specific scenario, skipping
In [It] at: /go/odo_1/tests/integration/cmd_dev_test.go:394 @ 12/01/23 09:04:51.929
------------------------------
SSSSS
------------------------------
• [80.330 seconds]
odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=true, customPortForwarding=true, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1463
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43043"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [8.585 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=false --running-in=dev should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34097"
<< Captured StdOut/StdErr Output
------------------------------
• [65.581 seconds]
odo run command tests when a component is bootstrapped when odo dev is executed with --no-commands=false and ready should execute commands
/go/odo_1/tests/integration/cmd_run_test.go:100
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45119"
<< Captured StdOut/StdErr Output
------------------------------
• [4.606 seconds]
odo create/delete/list/set namespace/project tests list project should successfully list all the projects in JSON format
/go/odo_1/tests/integration/cmd_namespace_test.go:228
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36699"
<< Captured StdOut/StdErr Output
------------------------------
• [59.373 seconds]
odo dev command tests when creating local files and dir and running odo dev - with metadata.name should correctly propagate changes to the container
/go/odo_1/tests/integration/cmd_dev_test.go:1788
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35357"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [59.385 seconds]
odo describe component command tests when creating a component when running odo dev (podman=false,debug=false) Default output when switching to another directory when describing the component from another directory should describe the named component
/go/odo_1/tests/integration/cmd_describe_component_test.go:389
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45403"
<< Captured StdOut/StdErr Output
------------------------------
SSSSSSSSS
------------------------------
• [7.970 seconds]
odo devfile deploy command tests when deploying a Devfile K8s component with multiple K8s resources defined should have created all the resources defined in the Devfile K8s component
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:372
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36073"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
S [5.136 seconds]
odo devfile deploy command tests deploying devfile with exec [It] should not set securitycontext for podsecurity admission on job's pod template
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:601
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33323"
<< Captured StdOut/StdErr Output
[SKIPPED] This is a Kubernetes specific scenario, skipping
In [It] at: /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:603 @ 12/01/23 09:05:20.506
------------------------------
• [97.957 seconds]
odo dev command tests when a component is bootstrapped when a delay is necessary for the component to start and running odo dev should first fail then succeed querying endpoint
/go/odo_1/tests/integration/cmd_dev_test.go:789
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37281"
<< Captured StdOut/StdErr Output
------------------------------
• [125.238 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=false, customPortForwarding=false, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1379
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40599"
<< Captured StdOut/StdErr Output
------------------------------
• [129.899 seconds]
odo dev command tests when java-springboot application is created and running odo dev when Update the devfile.yaml Should build the application successfully
/go/odo_1/tests/integration/cmd_dev_test.go:3269
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46317"
<< Captured StdOut/StdErr Output
------------------------------
• [6.109 seconds]
odo dev command tests when a component is bootstrapped should fail when using --random-ports and --port-forward together
/go/odo_1/tests/integration/cmd_dev_test.go:218
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41039"
<< Captured StdOut/StdErr Output
------------------------------
• [71.870 seconds]
odo dev command tests when Devfile 2.1.0 is used - with metadata.name when doing odo dev 3. should check if the env variable has a correct value
/go/odo_1/tests/integration/cmd_dev_test.go:1589
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41175"
<< Captured StdOut/StdErr Output
------------------------------
• [126.011 seconds]
odo describe component command tests checking for remote source code location when using devfile with sourceMapping and starting an odo dev session should show remote source code location in odo describe component output
/go/odo_1/tests/integration/cmd_describe_component_test.go:642
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37075"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [71.965 seconds]
odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag (custom api server port=false) should describe the API Server port
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:108
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42291"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
S [6.303 seconds]
odo preference and config command tests when DevfileRegistriesList CRD is installed on cluster [BeforeEach] when CR for devfileregistrieslists is installed in namespace should fail to delete the in-cluster registry
[BeforeEach] /go/odo_1/tests/integration/cmd_pref_config_test.go:377
[It] /go/odo_1/tests/integration/cmd_pref_config_test.go:444
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37935"
<< Captured StdOut/StdErr Output
[SKIPPED] skipped on non Kubernetes clusters
In [BeforeEach] at: /go/odo_1/tests/integration/cmd_pref_config_test.go:379 @ 12/01/23 09:05:36.93
------------------------------
S
------------------------------
• [8.022 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when an env.yaml file contains a non-current Project when running odo deploy should succeed
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:201
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38475"
<< Captured StdOut/StdErr Output
------------------------------
S [9.349 seconds]
odo dev command tests when Starting a PostgreSQL service [BeforeEach] when creating local files and dir and running odo dev - with metadata.name should correctly propagate changes to the container
[BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:1815
[It] /go/odo_1/tests/integration/cmd_dev_test.go:1865
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34379"
<< Captured StdOut/StdErr Output
[SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true
In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:1818 @ 12/01/23 09:05:38.949
------------------------------
SS
------------------------------
• [109.687 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=true, customPortForwarding=true, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1379
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34469"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [120.944 seconds]
odo dev command tests Devfile with no metadata.name when running odo dev against a component with no source code should use the directory as component name
/go/odo_1/tests/integration/cmd_dev_test.go:3873
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:32911"
<< Captured StdOut/StdErr Output
------------------------------
• [10.949 seconds]
odo describe component command tests when a non-odo application is present on the cluster should describe the component
/go/odo_1/tests/integration/cmd_describe_component_test.go:694
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37693"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [7.190 seconds]
odo run command tests when a component is bootstrapped should fail if odo dev is not running
/go/odo_1/tests/integration/cmd_run_test.go:72
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44439"
<< Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [58.976 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=false, customPortForwarding=true, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1338
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41227"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [129.584 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=true, customPortForwarding=true, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1379
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33575"
<< Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [60.297 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted using its name and namespace from another directory should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:473
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44579"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [29.207 seconds]
odo delete command tests when deleting a component containing preStop event that is deployed with DEV and --files=true should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:517
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41161"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [6.027 seconds]
odo devfile deploy command tests when recording telemetry data should record the telemetry data correctly
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:270
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44381"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [6.770 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41771"
<< Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [28.701 seconds]
odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a run command should error out on an invalid command
/go/odo_1/tests/integration/cmd_dev_test.go:3150
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46497"
<< Captured StdOut/StdErr Output
------------------------------
• [72.295 seconds]
odo describe component command tests when creating a component when running odo dev (podman=false,debug=true) Default output when describing the component in dev mode should describe the component
/go/odo_1/tests/integration/cmd_describe_component_test.go:348
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42831"
<< Captured StdOut/StdErr Output
------------------------------
• [7.345 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted using its name and namespace from another directory should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:237
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35049"
<< Captured StdOut/StdErr Output
------------------------------
• [5.741 seconds]
odo devfile build-images command tests when using a Devfile with variable image names should build images with --var (push=true)
/go/odo_1/tests/integration/cmd_devfile_build_images_test.go:437
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:32771"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [58.124 seconds]
odo dev command tests when Devfile 2.1.0 is used - without metadata.name when doing odo dev with --var-file flag should check if the env variable has a correct value
/go/odo_1/tests/integration/cmd_dev_test.go:1639
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35815"
<< Captured StdOut/StdErr Output
------------------------------
• [3.871 seconds]
odo devfile deploy command tests using a Devfile with an image component using a remote Dockerfile when remote server returns an error should not build images
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:502
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40827"
<< Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [25.315 seconds]
odo dev command tests when running odo dev with alternative commands - with metadata.name when running odo dev with a run command should error out on an invalid command
/go/odo_1/tests/integration/cmd_dev_test.go:3150
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34157"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [51.664 seconds]
odo devfile deploy command tests deploying devfile with exec when the deploy command terminates abruptly; component name of a normal character length when odo deploy command is run again should run successfully
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:595
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35125"
<< Captured StdOut/StdErr Output
------------------------------
• [81.646 seconds]
odo dev command tests when adding local files to gitignore and running odo dev when modifying /testdir/baz.txt file should synchronize it only
/go/odo_1/tests/integration/cmd_dev_test.go:1965
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36649"
<< Captured StdOut/StdErr Output
------------------------------
• [5.838 seconds]
odo dev command tests when directory is empty should error
/go/odo_1/tests/integration/cmd_dev_test.go:64
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43245"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [79.762 seconds]
odo dev command tests when creating local files and dir and running odo dev - with metadata.name when deleting local files and dir and waiting for sync should not list deleted dir and file in container
/go/odo_1/tests/integration/cmd_dev_test.go:1805
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36785"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [9.056 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 >>
Using Devfile Registry URL at: "http://127.0.0.1:39147"
Spawning '/go/bin/odo deploy' from /tmp/1586010616
<< Captured StdOut/StdErr Output
------------------------------
• [10.821 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39469"
<< Captured StdOut/StdErr Output
------------------------------
• [70.569 seconds]
odo dev command tests when a component with multiple endpoints is run should fail running a second session on the same platform
/go/odo_1/tests/integration/cmd_dev_test.go:3615
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41301"
<< Captured StdOut/StdErr Output
------------------------------
• [61.345 seconds]
odo dev command tests when a container component defines a Command or Args - without metadata.name should run odo dev successfully (#5620)
/go/odo_1/tests/integration/cmd_dev_test.go:3538
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39483"
<< Captured StdOut/StdErr Output
------------------------------
Progress Report for Ginkgo Process #14
Automatically polling progress:
odo dev command tests checking if odo dev matches local Devfile K8s resources and remote resources when odo dev is executed to run a devfile containing a k8s resource with apply command should have deleted the old resource and created the new resource (Spec Runtime: 2m3.68s)
/go/odo_1/tests/integration/cmd_dev_test.go:1077
In [BeforeEach] (Node Runtime: 2m0s)
/go/odo_1/tests/integration/cmd_dev_test.go:1050
Begin Captured GinkgoWriter Output >>
...
[odo] I1201 09:06:53.484139 28010 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops
[odo] I1201 09:06:53.487266 28010 port.go:319] port 8080 not listening in container "runtime"
[odo] I1201 09:06:55.289419 28010 exec.go:37] Executing command [/bin/sh -c cat /proc/net/tcp /proc/net/udp /proc/net/tcp6 /proc/net/udp6 || true] for pod: fefmbb-app-5d4bfd9f8d-7cw7z in container: runtime
[odo] I1201 09:06:55.486774 28010 exec.go:96] sl local_address rem_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode
[odo] I1201 09:06:55.486796 28010 exec.go:96] 0: 962B11AC:D574 22191068:01BB 06 00000000:00000000 03:00001050 00000000 0 0 0 3 0000000000000000
[odo] I1201 09:06:55.487894 28010 exec.go:96] sl local_address rem_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops
[odo] I1201 09:06:55.488026 28010 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode
[odo] I1201 09:06:55.488037 28010 exec.go:96] 0: 00000000000000000000000000000000:0BB8 00000000000000000000000000000000:0000 0A 00000000:00000000 00:00000000 00000000 1011310000 0 207702219 1 0000000000000000 100 0 0 10 0
[odo] I1201 09:06:55.490865 28010 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops
[odo] I1201 09:06:55.491815 28010 port.go:319] port 8080 not listening in container "runtime"
<< End Captured GinkgoWriter Output
Spec Goroutine
goroutine 467 [select, 2 minutes]
github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc000352310, {0x314b818?, 0xc000cbf1d0}, 0x1, {0x0, 0x0, 0x0})
/go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538
github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc000352310, {0x314b818, 0xc000cbf1d0}, {0x0, 0x0, 0x0})
/go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145
github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x2d3d3d5, 0x8}, 0xc000470de0?, 0xc000470dc0?, 0xc000cbefc0)
/go/odo_1/tests/helper/helper_run.go:54
github.com/redhat-developer/odo/tests/helper.(*DevSession).WaitSync(0xc0000b1ec0)
/go/odo_1/tests/helper/helper_dev.go:279
> github.com/redhat-developer/odo/tests/integration.glob..func7.5.1.1()
/go/odo_1/tests/integration/cmd_dev_test.go:1069
| helper.ReplaceStrings(filepath.Join(commonVar.Context, "devfile.yaml"), devfile.deploymentName, devfile.newDeploymentName)
|
> err := devSession.WaitSync()
| Expect(err).To(BeNil())
| })
github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x26c21b3, 0xc0007ca420})
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463
github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3()
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865
github.com/onsi/ginkgo/v2/internal.(*Suite).runNode
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852
------------------------------
• [68.507 seconds]
odo dev command tests when a component is bootstrapped when using a default namespace should print warning about default namespace when running odo dev
/go/odo_1/tests/integration/cmd_dev_test.go:130
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42587"
<< Captured StdOut/StdErr Output
------------------------------
• [8.772 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37787"
<< Captured StdOut/StdErr Output
------------------------------
• [60.303 seconds]
odo describe component command tests when creating a component when running odo dev (podman=false,debug=true) JSON output when switching to another directory when describing the component from another directory should describe the named component
/go/odo_1/tests/integration/cmd_describe_component_test.go:477
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45177"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [92.636 seconds]
odo dev command tests when a component is bootstrapped when odo dev is executed and Ephemeral is set to false when stopping odo dev normally should have deleted all resources before returning
/go/odo_1/tests/integration/cmd_dev_test.go:629
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41691"
<< Captured StdOut/StdErr Output
------------------------------
• [59.509 seconds]
odo describe component command tests when creating a component when running odo dev (podman=false,debug=true) Default output when switching to another directory when describing the component from another directory should describe the named component
/go/odo_1/tests/integration/cmd_describe_component_test.go:389
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42293"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [10.927 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=false --running-in=deploy should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44835"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [9.876 seconds]
odo describe component command tests should fail, with cluster
/go/odo_1/tests/integration/cmd_describe_component_test.go:89
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36363"
<< Captured StdOut/StdErr Output
------------------------------
• [118.621 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when running odo deploy with image build extra args when running and stopping odo dev should not delete the resources created with odo deploy
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:176
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38827"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [120.959 seconds]
odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy with image build extra args when running and stopping odo dev should not delete the resources created with odo deploy
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:176
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41435"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [108.847 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=false, customPortForwarding=true, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1379
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37581"
<< Captured StdOut/StdErr Output
------------------------------
• [9.166 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted using its name and namespace from another directory should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:241
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38791"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [112.571 seconds]
odo logs command tests when component is created and odo logs is executed when running in both Dev and Deploy mode should successfully show logs of the running component
/go/odo_1/tests/integration/cmd_logs_test.go:320
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42865"
<< Captured StdOut/StdErr Output
------------------------------
• [91.059 seconds]
odo dev command tests 1. devfile contains composite apply command when odo dev is running with container backend global extra args should execute the composite apply commands successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2388
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37401"
<< Captured StdOut/StdErr Output
------------------------------
• [91.457 seconds]
odo dev command tests when a component is bootstrapped when odo dev is executed and Ephemeral is set to false when killing odo dev and another process replaces it should restart a new session successfully
/go/odo_1/tests/integration/cmd_dev_test.go:609
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40523"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [85.963 seconds]
odo dev debug command tests when starting with Devfile with autoBuild or deployByDefault components when running odo dev with some components not referenced in the Devfile should create the appropriate resources
/go/odo_1/tests/integration/cmd_dev_debug_test.go:501
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45547"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [7.930 seconds]
odo devfile init command tests setting application ports when running odo init --run-port with a Devfile with no commands should ignore the run ports
/go/odo_1/tests/integration/cmd_devfile_init_test.go:628
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41133"
<< Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [79.111 seconds]
odo dev command tests when a component is bootstrapped when odo is executed with --no-watch flag and with --no-commands=false when a file in component directory is modified when p is pressed should trigger a push
/go/odo_1/tests/integration/cmd_dev_test.go:754
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34749"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [11.560 seconds]
odo list with devfile listing non-odo managed components when a non-odo managed component without the managed-by label is deployed should list the component with odo list
/go/odo_1/tests/integration/cmd_devfile_list_test.go:67
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41787"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [8.104 seconds]
odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy should succeed
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:143
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33311"
<< Captured StdOut/StdErr Output
------------------------------
• [61.178 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:3622
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36527"
PID: 32995
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [59.453 seconds]
odo dev command tests when Devfile contains metadata.language invalid as a label value when running odo dev should set the correct value in labels of resources
/go/odo_1/tests/integration/cmd_dev_test.go:4089
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46429"
<< Captured StdOut/StdErr Output
------------------------------
S [6.337 seconds]
odo preference and config command tests when DevfileRegistriesList CRD is installed on cluster [BeforeEach] when CR for devfileregistrieslists is installed in namespace registry list should return registry listed in CR
[BeforeEach] /go/odo_1/tests/integration/cmd_pref_config_test.go:377
[It] /go/odo_1/tests/integration/cmd_pref_config_test.go:414
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44841"
<< Captured StdOut/StdErr Output
[SKIPPED] skipped on non Kubernetes clusters
In [BeforeEach] at: /go/odo_1/tests/integration/cmd_pref_config_test.go:379 @ 12/01/23 09:08:17.257
------------------------------
SSSSSSSSSSSSSSSS
------------------------------
• [58.548 seconds]
odo dev command tests when devfile has sourcemappings and running odo dev - with metadata.name should sync files to the correct location
/go/odo_1/tests/integration/cmd_dev_test.go:2016
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36339"
<< Captured StdOut/StdErr Output
------------------------------
• [17.106 seconds]
odo devfile deploy command tests deploying devfile with exec when using devfile where the exec command is bound to fail should print the last 100 lines of the log to the output
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:648
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44783"
<< Captured StdOut/StdErr Output
------------------------------
•S
------------------------------
• [222.909 seconds]
odo dev command tests checking if odo dev matches local Devfile K8s resources and remote resources when odo dev is executed to run a devfile containing a k8s resource with apply command should have deleted the old resource and created the new resource
/go/odo_1/tests/integration/cmd_dev_test.go:1077
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44877"
<< Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [17.486 seconds]
odo create/delete/list/set namespace/project tests delete namespace when force-deleting a valid namespace should successfully delete the namespace asynchronously
/go/odo_1/tests/integration/cmd_namespace_test.go:107
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33163"
<< Captured StdOut/StdErr Output
------------------------------
• [28.758 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped the component is deleted while having access to the devfile.yaml when the component is deleted with --files should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:178
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41591"
<< Captured StdOut/StdErr Output
------------------------------
• [135.470 seconds]
odo dev command tests when running odo dev and composite command is used as a run command - with metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2709
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44461"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [123.318 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when running odo deploy when running and stopping odo dev should not delete the resources created with odo deploy
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:176
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41115"
<< Captured StdOut/StdErr Output
------------------------------
• [86.241 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when running odo deploy with image build extra args should run odo dev successfully
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:161
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46841"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [10.395 seconds]
odo devfile deploy command tests using a Devfile with an image component using a remote Dockerfile when remote server returns a valid file should run odo deploy
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:538
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46513"
<< Captured StdOut/StdErr Output
------------------------------
• [11.882 seconds]
odo list with devfile listing non-odo managed components when an operator managed deployment(without instance and managed-by label) is deployed should not be listed in the odo list output
/go/odo_1/tests/integration/cmd_devfile_list_test.go:88
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40071"
<< Captured StdOut/StdErr Output
------------------------------
• [8.178 seconds]
odo devfile deploy command tests Devfile with autoBuild or deployByDefault components when starting with Devfile with Deploy commands when running odo deploy with some components not referenced in the Devfile should create the appropriate resources
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:725
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34347"
<< Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [7.495 seconds]
odo dev command tests when Devfile contains metadata.language invalid as a label value when odo deploy is executed should set the correct value in labels of deployed resources
/go/odo_1/tests/integration/cmd_dev_test.go:4105
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36085"
<< Captured StdOut/StdErr Output
------------------------------
• [60.918 seconds]
odo dev debug command tests when a component without debug command is bootstrapped should log error about missing debug command when running odo dev --debug
/go/odo_1/tests/integration/cmd_dev_debug_test.go:444
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40679"
<< Captured StdOut/StdErr Output
------------------------------
• [62.258 seconds]
odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40925"
<< Captured StdOut/StdErr Output
------------------------------
• [60.758 seconds]
odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag when /instance endpoint is DELETEd should terminate the dev session
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:239
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34077"
<<< Session terminated >>>
<< Captured StdOut/StdErr Output
------------------------------
• [133.739 seconds]
odo dev command tests multiple dev sessions with different project are running on same platform (podman=false), same port when odo dev session is run for nodejs component when odo dev session is run for go project on the same port but different address when go and nodejs files are modified should be possible to access both the projects on same address and port
/go/odo_1/tests/integration/cmd_dev_test.go:1237
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41433"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [10.213 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted using its name and namespace from another directory should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:237
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46549"
<< Captured StdOut/StdErr Output
------------------------------
• [8.944 seconds]
odo dev command tests when running applications listening on the container loopback interface should error out if using --ignore-localhost on any platform other than Podman
/go/odo_1/tests/integration/cmd_dev_test.go:4211
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42687"
<< Captured StdOut/StdErr Output
------------------------------
• [7.823 seconds]
odo devfile build-images command tests when starting with Devfile with autoBuild or deployByDefault components when building and pushing images should build and push all Image components regardless of autoBuild
/go/odo_1/tests/integration/cmd_devfile_build_images_test.go:385
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:32949"
<< Captured StdOut/StdErr Output
------------------------------
• [61.551 seconds]
odo dev command tests when running odo dev and composite command are nested - with metadata.name should execute all commands in composite commmand
/go/odo_1/tests/integration/cmd_dev_test.go:2674
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34021"
<< Captured StdOut/StdErr Output
------------------------------
SSSSSS
------------------------------
• [61.790 seconds]
odo dev command tests when a component is bootstrapped when odo is executed with --no-watch flag and without --no-commands when a file in component directory is modified should not trigger a push
/go/odo_1/tests/integration/cmd_dev_test.go:736
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39989"
<< Captured StdOut/StdErr Output
------------------------------
• [26.288 seconds]
odo dev command tests when a component is bootstrapped should start on cluster even if Podman client takes long to initialize
/go/odo_1/tests/integration/cmd_dev_test.go:91
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45771"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [5.450 seconds]
odo create/delete/list/set namespace/project tests set project when running inside a component directory should set the project
/go/odo_1/tests/integration/cmd_namespace_test.go:190
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37581"
<< Captured StdOut/StdErr Output
------------------------------
• [5.963 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an Image component with no build context should build image via Docker by defaulting build context to devfile path
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:450
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37613"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [6.908 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an Image component with a build context should build image via Podman if build context references PROJECT_SOURCE env var
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:326
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45963"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [31.804 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="") when odo delete command is run again with nothing deployed on the cluster should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:151
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37843"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [26.313 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped the component is deleted while having access to the devfile.yaml when the component is deleted with --files should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:178
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38609"
<< Captured StdOut/StdErr Output
------------------------------
• [64.171 seconds]
odo dev command tests when adding local files to gitignore and running odo dev should not sync ignored files to the container
/go/odo_1/tests/integration/cmd_dev_test.go:1955
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42267"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [63.222 seconds]
odo dev command tests when running odo dev with alternative commands - without metadata.name should execute the custom non-default build and run commands successfully
/go/odo_1/tests/integration/cmd_dev_test.go:3207
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43031"
<< Captured StdOut/StdErr Output
------------------------------
• [91.127 seconds]
odo dev command tests 1. devfile contains composite apply command when odo dev is running with image build extra args should execute the composite apply commands successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2388
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42415"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [61.966 seconds]
odo dev command tests when a component is bootstrapped when odo dev is executed when odo dev is stopped should delete the component from the platform
/go/odo_1/tests/integration/cmd_dev_test.go:507
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38673"
<< Captured StdOut/StdErr Output
------------------------------
SSSSSSSSSSSS
------------------------------
• [60.383 seconds]
odo devfile deploy command tests deploying devfile with long-running exec when Automount volumes are present in the namespace should mount the volumes
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:695
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41619"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [121.364 seconds]
odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy when running and stopping odo dev should not delete the resources created with odo deploy
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:176
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35161"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
Progress Report for Ginkgo Process #12
Automatically polling progress:
odo dev command tests Devfile contains pod-overrides and container-overrides attributes should override the content in the pod it creates for the component on the cluster (Spec Runtime: 2m5.509s)
/go/odo_1/tests/integration/cmd_dev_test.go:4146
In [It] (Node Runtime: 2m0.001s)
/go/odo_1/tests/integration/cmd_dev_test.go:4146
Begin Captured GinkgoWriter Output >>
...
[odo] ✗ Finished executing the application (command: run) [1m]
[odo] I1201 09:09:40.494237 34126 execute_run.go:36] error while running background command: unable to exec command [/bin/sh -c echo $$ > /opt/odo/.odo_cmd_run.pid && cd ${PROJECT_SOURCE} && (npm start) 1>>/proc/1/fd/1 2>>/proc/1/fd/2; echo $? >> /opt/odo/.odo_cmd_run.pid]: error while streaming command: context canceled
[odo] I1201 09:09:40.499937 34126 implem.go:114] The path for preference file is /tmp/333738462/preference.yaml
[odo] I1201 09:09:40.500686 34126 segment.go:268] Checking telemetry enable status
[odo] I1201 09:09:40.500696 34126 segment.go:286] Sending telemetry disabled by env variable
[odo] Cleaning resources, please wait
[odo] I1201 09:09:40.574229 34126 all.go:46] starting to concurrently query 201 APIs
[odo] I1201 09:09:40.574687 34126 all.go:62] fired up all goroutines to query APIs
[odo] I1201 09:09:41.972530 34126 all.go:67] all goroutines have returned in 1.396835489s
[odo] I1201 09:09:41.973112 34126 all.go:76] query result: objects=632
<< End Captured GinkgoWriter Output
Spec Goroutine
goroutine 2901 [select]
github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc000550e00, {0x314b5d8?, 0xc001828198}, 0x1, {0x0, 0x0, 0x0})
/go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538
github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc000550e00, {0x314b5d8, 0xc001828198}, {0x0, 0x0, 0x0})
/go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145
github.com/onsi/gomega/gexec.(*Session).Wait(0xc000dafd50?, {0xc001723c30?, 0x2d3f1ba?, 0x9?})
/go/odo_1/vendor/github.com/onsi/gomega/gexec/session.go:144
github.com/redhat-developer/odo/tests/helper.DevSession.WaitEnd(...)
/go/odo_1/tests/helper/helper_dev.go:263
github.com/redhat-developer/odo/tests/helper.RunDevMode.func1()
/go/odo_1/tests/helper/helper_dev.go:334
github.com/redhat-developer/odo/tests/helper.RunDevMode({{0x0, 0x0, 0x0}, {0x0, 0x0, 0x0}, 0x0, 0x0, 0x0, 0x0, ...}, ...)
/go/odo_1/tests/helper/helper_dev.go:337
> github.com/redhat-developer/odo/tests/integration.glob..func7.64.2()
/go/odo_1/tests/integration/cmd_dev_test.go:4147
| })
| It("should override the content in the pod it creates for the component on the cluster", func() {
> err := helper.RunDevMode(helper.DevSessionOpts{
| RunOnPodman: ctx.podman,
| }, func(session *gexec.Session, outContents, _ string, _ map[string]string) {
github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x10a5e7e, 0xc001492900})
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463
github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3()
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865
github.com/onsi/ginkgo/v2/internal.(*Suite).runNode
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852
------------------------------
• [59.048 seconds]
odo dev command tests when a component is bootstrapped when odo is executed with --no-watch flag and with --no-commands=false when a file in component directory is modified should not trigger a push
/go/odo_1/tests/integration/cmd_dev_test.go:736
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41169"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [94.429 seconds]
odo dev command tests when a component is bootstrapped when odo dev is executed and Ephemeral is set to false when killing odo dev and running odo delete component --wait should have deleted all resources before returning
/go/odo_1/tests/integration/cmd_dev_test.go:577
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35991"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [131.284 seconds]
odo dev command tests Devfile contains pod-overrides and container-overrides attributes should override the content in the pod it creates for the component on the cluster
/go/odo_1/tests/integration/cmd_dev_test.go:4146
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33763"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [28.807 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="") should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:128
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41509"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [82.710 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 >>
Using Devfile Registry URL at: "http://127.0.0.1:37313"
Spawning '/go/bin/odo dev --random-ports' from /tmp/2828554288
<< Captured StdOut/StdErr Output
------------------------------
• [6.123 seconds]
odo dev command tests when running applications listening on the container loopback interface should error out if using --ignore-localhost on any platform other than Podman
/go/odo_1/tests/integration/cmd_dev_test.go:4211
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39023"
<< Captured StdOut/StdErr Output
------------------------------
• [59.989 seconds]
odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46353"
<< Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [85.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 >>
Using Devfile Registry URL at: "http://127.0.0.1:35099"
Spawning '/go/bin/odo dev --random-ports' from /tmp/3161570367
<< Captured StdOut/StdErr Output
------------------------------
• [58.325 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted using its name and namespace from another directory should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:473
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40623"
<< Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
S [4.104 seconds]
odo devfile deploy command tests deploying devfile with exec [It] should not set securitycontext for podsecurity admission on job's pod template
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:601
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41171"
<< Captured StdOut/StdErr Output
[SKIPPED] This is a Kubernetes specific scenario, skipping
In [It] at: /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:603 @ 12/01/23 09:10:29.904
------------------------------
SSSSS
------------------------------
• [57.004 seconds]
odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a build command should execute the default build command successfully if specified explicitly
/go/odo_1/tests/integration/cmd_dev_test.go:3126
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36417"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [11.047 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 >>
Using Devfile Registry URL at: "http://127.0.0.1:41907"
Spawning '/go/bin/odo dev --random-ports' from /tmp/1346360290
<< Captured StdOut/StdErr Output
------------------------------
• [58.617 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=false, customPortForwarding=false, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1338
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45403"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [58.946 seconds]
odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag (custom api server port=false) should start the Dev server when --api-server flag is passed
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:98
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36235"
<< Captured StdOut/StdErr Output
------------------------------
• [26.194 seconds]
odo dev command tests when running odo dev with alternative commands - with metadata.name when running odo dev with a build command should error out on an invalid command
/go/odo_1/tests/integration/cmd_dev_test.go:3080
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33271"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [5.520 seconds]
odo devfile deploy command tests when directory is empty should error
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:47
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37813"
<< Captured StdOut/StdErr Output
------------------------------
• [7.787 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33211"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [123.541 seconds]
odo dev debug command tests when creating nodejs component, doing odo dev and run command has dev.odo.push.path attribute should sync only the mentioned files at the appropriate remote destination
/go/odo_1/tests/integration/cmd_dev_debug_test.go:163
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46815"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [49.790 seconds]
odo devfile deploy command tests deploying devfile with exec when the deploy command terminates abruptly; component name of at max(63) characters length when odo deploy command is run again should run successfully
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:595
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35761"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [58.679 seconds]
odo dev command tests when odo dev is executed to run a devfile containing a k8s resource should have created the necessary k8s resources
/go/odo_1/tests/integration/cmd_dev_test.go:1127
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43747"
<< Captured StdOut/StdErr Output
------------------------------
• [57.815 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=true, customPortForwarding=false, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1338
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41121"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [69.450 seconds]
odo dev command tests when a component is bootstrapped should show validation errors if the devfile is incorrect
/go/odo_1/tests/integration/cmd_dev_test.go:156
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38367"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [88.170 seconds]
odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=false, customPortForwarding=true, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1463
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43381"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [21.825 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:211
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35705"
Spawning '/go/bin/odo dev --random-ports --no-watch' from /tmp/3273507517
<< Captured StdOut/StdErr Output
------------------------------
• [57.795 seconds]
odo describe component command tests when creating a component when running odo dev (podman=false,debug=true) JSON output when describing the component in dev mode should describe the component
/go/odo_1/tests/integration/cmd_describe_component_test.go:416
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43305"
<< Captured StdOut/StdErr Output
------------------------------
• [109.253 seconds]
odo dev command tests when a hotReload capable Run command is used with odo dev should execute the build and run commands
/go/odo_1/tests/integration/cmd_dev_test.go:3771
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41943"
<< Captured StdOut/StdErr Output
------------------------------
• [60.673 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39103"
<< Captured StdOut/StdErr Output
------------------------------
• [60.935 seconds]
odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35799"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [130.323 seconds]
odo dev command tests when running build and run commands as composite in different containers and a shared volume - without metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2772
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36115"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
S [6.619 seconds]
odo dev command tests when Starting a PostgreSQL service [BeforeEach] when creating local files and dir and running odo dev - with metadata.name when deleting local files and dir and waiting for sync should not list deleted dir and file in container
[BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:1815
[It] /go/odo_1/tests/integration/cmd_dev_test.go:1882
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34957"
<< Captured StdOut/StdErr Output
[SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true
In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:1818 @ 12/01/23 09:11:42.102
------------------------------
S
------------------------------
• [59.411 seconds]
odo dev command tests when running applications listening on the container loopback interface when running on default cluster platform should port-forward successfully
/go/odo_1/tests/integration/cmd_dev_test.go:4244
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39617"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [7.688 seconds]
odo create/delete/list/set namespace/project tests delete namespace should not succeed to delete a non-existent namespace
/go/odo_1/tests/integration/cmd_namespace_test.go:122
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40711"
<< Captured StdOut/StdErr Output
------------------------------
• [8.527 seconds]
odo list with devfile listing non-odo managed components when a non-odo managed component is deployed should list the component in JSON
/go/odo_1/tests/integration/cmd_devfile_list_test.go:47
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46447"
<< Captured StdOut/StdErr Output
------------------------------
• [80.905 seconds]
odo dev command tests when a component is bootstrapped when odo is executed with --no-watch flag and without --no-commands when a file in component directory is modified when p is pressed should trigger a push
/go/odo_1/tests/integration/cmd_dev_test.go:754
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41025"
<< Captured StdOut/StdErr Output
------------------------------
• [8.648 seconds]
odo logs command tests when odo logs is executed for a component that's not running in any modes should print that no containers are running
/go/odo_1/tests/integration/cmd_logs_test.go:99
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44523"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [120.019 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=false, customPortForwarding=false, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1379
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46747"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [3.652 seconds]
odo create/delete/list/set namespace/project tests list project should successfully list all the projects
/go/odo_1/tests/integration/cmd_namespace_test.go:221
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39009"
<< Captured StdOut/StdErr Output
------------------------------
• [63.155 seconds]
odo dev command tests when creating nodejs component, doing odo dev and run command has dev.odo.push.path attribute should sync only the mentioned files at the appropriate remote destination
/go/odo_1/tests/integration/cmd_dev_test.go:3428
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38389"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [58.194 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=true, customPortForwarding=true, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1338
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46635"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [33.263 seconds]
odo dev command tests image names as selectors when starting with a Devfile with relative and absolute image names and Kubernetes resources when adding a local registry for images when running odo dev should treat relative image names as selectors
/go/odo_1/tests/integration/cmd_dev_test.go:4756
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38577"
<< Captured StdOut/StdErr Output
------------------------------
• [86.702 seconds]
odo dev debug command tests when starting with Devfile with autoBuild or deployByDefault components when running odo dev with some components referenced in the Devfile should create the appropriate resources
/go/odo_1/tests/integration/cmd_dev_debug_test.go:631
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42007"
<< Captured StdOut/StdErr Output
------------------------------
• [60.928 seconds]
odo dev command tests when running odo dev with alternative commands - with metadata.name should execute the custom non-default build and run commands successfully
/go/odo_1/tests/integration/cmd_dev_test.go:3207
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38913"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [58.865 seconds]
odo dev command tests when setting git config and running odo dev should create vcs-uri annotation for the deployment when running odo dev
/go/odo_1/tests/integration/cmd_dev_test.go:2966
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40427"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [6.066 seconds]
odo devfile deploy command tests Devfile with autoBuild or deployByDefault components when starting with Devfile with Deploy commands when running odo deploy with some components referenced in the Devfile should create the appropriate resources
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:802
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36743"
<< Captured StdOut/StdErr Output
------------------------------
• [58.746 seconds]
odo dev command tests when a component is bootstrapped when odo dev is executed and Ephemeral is set to false should have created resources
/go/odo_1/tests/integration/cmd_dev_test.go:668
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39917"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [85.076 seconds]
odo dev command tests 1. devfile contains composite apply command when odo dev is running with both image build and container run extra args should execute the composite apply commands successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2388
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34481"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [60.167 seconds]
odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33943"
<< Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [142.822 seconds]
odo list with devfile when a component created in 'app' application when dev is running on cluster verifying the managedBy Version in the odo list output should show managedBy Version
/go/odo_1/tests/integration/cmd_devfile_list_test.go:181
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40983"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [9.765 seconds]
odo create/delete/list/set namespace/project tests create project should successfully create the project
/go/odo_1/tests/integration/cmd_namespace_test.go:54
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33107"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [7.297 seconds]
odo create/delete/list/set namespace/project tests create project should fail to create project
/go/odo_1/tests/integration/cmd_namespace_test.go:63
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41075"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [6.529 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when an env.yaml file contains a non-current Project when running odo deploy when the env.yaml file still contains a non-current Project should delete the component in the current namespace
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:226
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41845"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [120.735 seconds]
odo dev command tests when running odo dev and multiple env variables are set - with metadata.name should be able to exec command
/go/odo_1/tests/integration/cmd_dev_test.go:1717
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44191"
<< Captured StdOut/StdErr Output
------------------------------
• [69.350 seconds]
odo dev command tests when Create and dev java-springboot component should execute default build and run commands correctly
/go/odo_1/tests/integration/cmd_dev_test.go:2931
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35247"
<< Captured StdOut/StdErr Output
------------------------------
• [7.426 seconds]
odo create/delete/list/set namespace/project tests when namespace is created with -w should list the new namespace when listing namespace
/go/odo_1/tests/integration/cmd_namespace_test.go:41
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38481"
<< Captured StdOut/StdErr Output
------------------------------
• [7.717 seconds]
odo list with devfile listing non-odo managed components when a non-odo managed component without the managed-by label is deployed should list the component in JSON
/go/odo_1/tests/integration/cmd_devfile_list_test.go:71
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39679"
<< Captured StdOut/StdErr Output
------------------------------
• [10.008 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=true --running-in= should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45837"
<< Captured StdOut/StdErr Output
------------------------------
• [6.851 seconds]
odo create/delete/list/set namespace/project tests set namespace when running inside a component directory should set the namespace
/go/odo_1/tests/integration/cmd_namespace_test.go:190
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35375"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [6.597 seconds]
odo devfile build-images command tests when using a Devfile with variable image names should build images with default variable values (push=true)
/go/odo_1/tests/integration/cmd_devfile_build_images_test.go:431
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45385"
<< Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [74.022 seconds]
odo list with devfile devfile has missing metadata when projectType is missing when the component is pushed in dev mode should show the language for 'Type' in odo list
/go/odo_1/tests/integration/cmd_devfile_list_test.go:334
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36245"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [118.669 seconds]
odo dev command tests when node-js application is created and deployed with devfile schema 2.2.0 should check memory Request and Limit
/go/odo_1/tests/integration/cmd_dev_test.go:3375
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42067"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [59.803 seconds]
odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag (custom api server port=true) should start the Dev server when --api-server flag is passed
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:98
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41533"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [7.291 seconds]
odo dev command tests when a component is bootstrapped should fail when using --no-commands and --build-command and/or --run-command together
/go/odo_1/tests/integration/cmd_dev_test.go:233
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35375"
<< Captured StdOut/StdErr Output
------------------------------
• [119.102 seconds]
odo dev command tests when running odo dev and run command throws an error should error out with some log
/go/odo_1/tests/integration/cmd_dev_test.go:2858
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41649"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
S [4.730 seconds]
odo dev command tests when a component is bootstrapped when pod security is enforced as restricted [It] should set securitycontext for podsecurity admission
/go/odo_1/tests/integration/cmd_dev_test.go:414
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43271"
<< Captured StdOut/StdErr Output
[SKIPPED] This is a Kubernetes specific scenario, skipping
In [It] at: /go/odo_1/tests/integration/cmd_dev_test.go:416 @ 12/01/23 09:13:44.447
------------------------------
SSSS
------------------------------
• [72.189 seconds]
odo dev debug command tests when a composite command is used as debug command - without metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_debug_test.go:225
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41795"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [6.023 seconds]
odo dev command tests when Devfile contains metadata.projectType when odo deploy is executed should set the correct value in labels of deployed resources
/go/odo_1/tests/integration/cmd_dev_test.go:4105
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42211"
<< Captured StdOut/StdErr Output
------------------------------
• [60.680 seconds]
odo dev command tests when Devfile 2.1.0 is used - without metadata.name when doing odo dev with --var-file flag and setting value in env should check if the env variable has a correct value
/go/odo_1/tests/integration/cmd_dev_test.go:1668
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46315"
<< Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [5.916 seconds]
odo create/delete/list/set namespace/project tests list namespace should successfully list all the namespaces in JSON format
/go/odo_1/tests/integration/cmd_namespace_test.go:228
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45363"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [129.291 seconds]
odo dev command tests when running build and run commands as composite in different containers and a shared volume - with metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2772
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41935"
<< Captured StdOut/StdErr Output
------------------------------
• [84.474 seconds]
odo dev debug command tests when a composite command is used as debug command - with metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_debug_test.go:225
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37479"
<< Captured StdOut/StdErr Output
------------------------------
• [101.205 seconds]
odo dev command tests when a component is bootstrapped ensure that index information is updated
/go/odo_1/tests/integration/cmd_dev_test.go:305
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38499"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [121.508 seconds]
odo dev command tests when running odo dev and single env var is set - with metadata.name should be able to exec command
/go/odo_1/tests/integration/cmd_dev_test.go:1691
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40099"
<< Captured StdOut/StdErr Output
------------------------------
• [52.366 seconds]
odo dev command tests when a component is bootstrapped when build command takes really long to start should cancel build command and return if odo dev is stopped
/go/odo_1/tests/integration/cmd_dev_test.go:981
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40729"
<< Captured StdOut/StdErr Output
------------------------------
S [6.859 seconds]
odo devfile registry command tests when DevfileRegistriesList CRD is installed on cluster [BeforeEach] when CR for devfileregistrieslists is installed in namespace should list detailed information regarding nodejs when using an in-cluster registry
[BeforeEach] /go/odo_1/tests/integration/cmd_devfile_registry_test.go:212
[It] /go/odo_1/tests/integration/cmd_devfile_registry_test.go:240
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43153"
<< Captured StdOut/StdErr Output
[SKIPPED] skipped on non Kubernetes clusters
In [BeforeEach] at: /go/odo_1/tests/integration/cmd_devfile_registry_test.go:214 @ 12/01/23 09:14:14.656
------------------------------
• [10.445 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42209"
<< Captured StdOut/StdErr Output
------------------------------
• [92.907 seconds]
odo dev command tests 1. devfile contains composite apply command when odo dev is running should execute the composite apply commands successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2388
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46243"
<< Captured StdOut/StdErr Output
------------------------------
• [8.708 seconds]
odo dev command tests when a component is bootstrapped when a state file is not writable should fail running odo dev
/go/odo_1/tests/integration/cmd_dev_test.go:435
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35175"
<< Captured StdOut/StdErr Output
------------------------------
• [118.783 seconds]
odo dev command tests when running odo dev with devfile contain volume - without metadata.name check the volume name and mount paths for the containers
/go/odo_1/tests/integration/cmd_dev_test.go:2230
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44465"
<< Captured StdOut/StdErr Output
------------------------------
• [60.135 seconds]
odo dev command tests when running odo dev with alternative commands - with metadata.name when running odo dev with a build command should execute the default build command successfully if specified explicitly
/go/odo_1/tests/integration/cmd_dev_test.go:3126
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44835"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [6.333 seconds]
odo devfile deploy command tests Devfile with autoBuild or deployByDefault components when starting with Devfile with no Deploy command should fail to run odo deploy
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:880
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43857"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
S [9.535 seconds]
odo devfile init command tests when DevfileRegistriesList CRD is installed on cluster [BeforeEach] when CR for devfileregistrieslists is installed in namespace should be able to download devfile from the in-cluster registry
[BeforeEach] /go/odo_1/tests/integration/cmd_devfile_init_test.go:586
[It] /go/odo_1/tests/integration/cmd_devfile_init_test.go:613
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46619"
<< Captured StdOut/StdErr Output
[SKIPPED] skipped on non Kubernetes clusters
In [BeforeEach] at: /go/odo_1/tests/integration/cmd_devfile_init_test.go:588 @ 12/01/23 09:14:26.937
------------------------------
SS
------------------------------
• [64.009 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="deploy") should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:124
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34375"
<< Captured StdOut/StdErr Output
------------------------------
• [59.528 seconds]
odo dev command tests when running odo dev and composite command is marked as parallel:true - with metadata.name should execute all commands in composite command
/go/odo_1/tests/integration/cmd_dev_test.go:2642
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45443"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [73.132 seconds]
odo list with devfile devfile has missing metadata when projectType and language is missing when the component is pushed should show 'nodejs' for 'Type' in odo list
/go/odo_1/tests/integration/cmd_devfile_list_test.go:363
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38489"
<< Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [48.785 seconds]
odo dev command tests 1. devfile contains composite apply command the devfile contains an image component that uses a remote Dockerfile when [PODMAN_CMD=echo] remote server returns an error when odo dev is run should not build images when odo dev is run
/go/odo_1/tests/integration/cmd_dev_test.go:2549
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43291"
<< Captured StdOut/StdErr Output
------------------------------
• [165.241 seconds]
odo dev command tests when a component is bootstrapped when Automount volumes are present in the namespace when odo dev is executed should mount the volumes
/go/odo_1/tests/integration/cmd_dev_test.go:833
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46737"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [34.704 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33397"
<< Captured StdOut/StdErr Output
------------------------------
• [60.539 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=true, customPortForwarding=false, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1338
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34571"
<< Captured StdOut/StdErr Output
------------------------------
• [9.090 seconds]
odo describe component command tests should fail, with default cluster mode
/go/odo_1/tests/integration/cmd_describe_component_test.go:70
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33945"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [61.916 seconds]
odo dev debug command tests when a component is bootstrapped when running odo dev with debug flag should connect to relevant ports forwarded
/go/odo_1/tests/integration/cmd_dev_debug_test.go:112
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43057"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [64.933 seconds]
odo dev command tests when a component is bootstrapped should not sync .git directory
/go/odo_1/tests/integration/cmd_dev_test.go:166
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46457"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [124.977 seconds]
odo dev command tests when running odo dev with devfile contain volume - with metadata.name should create pvc and reuse if it shares the same devfile volume name
/go/odo_1/tests/integration/cmd_dev_test.go:2197
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37015"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [6.140 seconds]
odo devfile deploy command tests when a component is bootstrapped when using a default namespace should display warning when running the deploy command
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:67
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44691"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [60.215 seconds]
odo describe component command tests when creating a component when running odo dev (podman=false,debug=false) JSON output when switching to another directory when describing the component from another directory should describe the named component
/go/odo_1/tests/integration/cmd_describe_component_test.go:477
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43419"
<< Captured StdOut/StdErr Output
------------------------------
• [9.192 seconds]
odo describe component command tests when creating a component when running odo deploy to create ingress/routes should show the ingress with defaultBackend in odo describe component output
/go/odo_1/tests/integration/cmd_describe_component_test.go:552
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42799"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [62.045 seconds]
odo dev command tests when Devfile 2.1.0 is used - without metadata.name when doing odo dev 3. should check if the env variable has a correct value
/go/odo_1/tests/integration/cmd_dev_test.go:1589
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39867"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [67.397 seconds]
odo dev command tests 1. devfile contains composite apply command the devfile contains an image component that uses a remote Dockerfile when [PODMAN_CMD=a-command-not-found-for-podman-should-make-odo-fallback-to-docker DOCKER_CMD=echo] remote server returns a valid file when odo dev is run should build and push image when odo dev is run
/go/odo_1/tests/integration/cmd_dev_test.go:2526
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38271"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [64.276 seconds]
odo dev debug command tests when a component is bootstrapped when running odo dev with debug flag should not add a DEBUG_PORT variable to the container
/go/odo_1/tests/integration/cmd_dev_debug_test.go:124
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44847"
<< Captured StdOut/StdErr Output
------------------------------
SSSSSSS
------------------------------
• [61.344 seconds]
odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag (custom api server port=true) should describe the API Server port (JSON)
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:123
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40411"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [8.228 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=false --running-in= should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43383"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [59.340 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=true, customPortForwarding=true, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1338
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37337"
<< Captured StdOut/StdErr Output
------------------------------
• [59.251 seconds]
odo dev command tests when Devfile 2.1.0 is used - with metadata.name when doing odo dev with --var-file flag and setting value in env should check if the env variable has a correct value
/go/odo_1/tests/integration/cmd_dev_test.go:1668
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36297"
<< Captured StdOut/StdErr Output
------------------------------
• [80.661 seconds]
odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=false, customPortForwarding=false, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1463
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33695"
<< Captured StdOut/StdErr Output
------------------------------
• [59.114 seconds]
odo dev command tests when Devfile contains metadata.projectType invalid as a label value when running odo dev should set the correct value in labels of resources
/go/odo_1/tests/integration/cmd_dev_test.go:4089
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35771"
<< Captured StdOut/StdErr Output
------------------------------
• [86.557 seconds]
odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy should run odo dev successfully
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:161
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38589"
<< Captured StdOut/StdErr Output
------------------------------
• [27.239 seconds]
odo dev command tests when a component is bootstrapped when an env.yaml file contains a non-current Project when odo dev is executed should not have modified env.yaml, and use current namespace
/go/odo_1/tests/integration/cmd_dev_test.go:547
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43409"
<< Captured StdOut/StdErr Output
------------------------------
• [59.385 seconds]
odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a run command should execute the custom non-default run command successfully
/go/odo_1/tests/integration/cmd_dev_test.go:3181
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42905"
<< Captured StdOut/StdErr Output
------------------------------
• [61.348 seconds]
odo dev command tests port-forwarding for the component when devfile has no endpoint when running odo dev should have no endpoint forwarded (podman=false, manual=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1282
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39283"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [79.647 seconds]
odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=true, customPortForwarding=false, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1463
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35041"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [9.490 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41779"
<< Captured StdOut/StdErr Output
------------------------------
S [3.833 seconds]
odo init interactive command tests when DevfileRegistriesList CRD is installed on cluster [BeforeEach] when CR for devfileregistrieslists is installed in namespace should download correct devfile from the first in-cluster registry
[BeforeEach] /go/odo_1/tests/integration/interactive_init_test.go:708
[It] /go/odo_1/tests/integration/interactive_init_test.go:737
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38407"
<< Captured StdOut/StdErr Output
[SKIPPED] skipped on non Kubernetes clusters
In [BeforeEach] at: /go/odo_1/tests/integration/interactive_init_test.go:710 @ 12/01/23 09:16:15.524
------------------------------
SSS
------------------------------
• [50.963 seconds]
odo dev command tests 1. devfile contains composite apply command the devfile contains an image component that uses a remote Dockerfile when [PODMAN_CMD=a-command-not-found-for-podman-should-make-odo-fallback-to-docker DOCKER_CMD=echo] remote server returns an error when odo dev is run should not build images when odo dev is run
/go/odo_1/tests/integration/cmd_dev_test.go:2549
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34743"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [58.301 seconds]
odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted using its name and namespace from another directory should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:473
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45519"
<< Captured StdOut/StdErr Output
------------------------------
• [5.382 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 >>
Using Devfile Registry URL at: "http://127.0.0.1:40143"
Spawning '/go/bin/odo deploy' from /tmp/2473991242
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [8.462 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=true --running-in=deploy should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39087"
<< Captured StdOut/StdErr Output
------------------------------
• [82.759 seconds]
odo dev command tests when adding local files to gitignore and running odo dev when modifying /testdir/baz.txt file should synchronize it only
/go/odo_1/tests/integration/cmd_dev_test.go:1965
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39217"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
S [3.756 seconds]
odo dev command tests when Starting a PostgreSQL service [BeforeEach] when creating local files and dir and running odo dev - without metadata.name when deleting local files and dir and waiting for sync should not list deleted dir and file in container
[BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:1815
[It] /go/odo_1/tests/integration/cmd_dev_test.go:1882
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43021"
<< Captured StdOut/StdErr Output
[SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true
In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:1818 @ 12/01/23 09:16:37.484
------------------------------
SSS
------------------------------
• [63.010 seconds]
odo dev command tests when multiple projects are present - without metadata.name should sync to the correct dir in container
/go/odo_1/tests/integration/cmd_dev_test.go:2130
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35995"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [61.427 seconds]
odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a build command should execute the custom non-default build command successfully
/go/odo_1/tests/integration/cmd_dev_test.go:3112
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33347"
<< Captured StdOut/StdErr Output
------------------------------
• [65.073 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="deploy") should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:124
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43651"
<< Captured StdOut/StdErr Output
------------------------------
• [59.003 seconds]
odo dev command tests when Devfile 2.1.0 is used - with metadata.name when doing odo dev with --var flag should check if the env variable has a correct value
/go/odo_1/tests/integration/cmd_dev_test.go:1612
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46439"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [8.561 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when running odo deploy should succeed
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:143
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40771"
<< Captured StdOut/StdErr Output
------------------------------
• [7.090 seconds]
odo devfile build-images command tests when starting with Devfile with autoBuild or deployByDefault components when building images should build all Image components regardless of autoBuild
/go/odo_1/tests/integration/cmd_devfile_build_images_test.go:364
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44367"
<< Captured StdOut/StdErr Output
------------------------------
• [12.414 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted using its name and namespace from another directory should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:241
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36637"
<< Captured StdOut/StdErr Output
------------------------------
SSSSSSSSSSS
------------------------------
• [61.378 seconds]
odo dev command tests when running odo dev and composite command is marked as parallel:true - without metadata.name should execute all commands in composite command
/go/odo_1/tests/integration/cmd_dev_test.go:2642
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38193"
<< Captured StdOut/StdErr Output
------------------------------
• [7.459 seconds]
odo devfile deploy command tests when using a devfile.yaml containing a deploy command when an env.yaml file contains a non-current Project when running odo deploy when the env.yaml file still contains a non-current Project should delete the component in the current namespace
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:226
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35387"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [130.325 seconds]
odo logs command tests when component is created and odo logs is executed when running in both Dev and Deploy mode when --follow flag is specified should successfully follow logs of running component
/go/odo_1/tests/integration/cmd_logs_test.go:348
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39733"
<< Captured StdOut/StdErr Output
------------------------------
• [13.371 seconds]
odo generic When deleting two project one after the other should be able to delete them in any order
/go/odo_1/tests/integration/generic_test.go:107
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36999"
<< Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [61.000 seconds]
odo dev command tests when Devfile 2.1.0 is used - without metadata.name when doing odo dev with --var flag should check if the env variable has a correct value
/go/odo_1/tests/integration/cmd_dev_test.go:1612
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40753"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [131.848 seconds]
odo dev command tests when java-springboot application is created and running odo dev when Update the devfile.yaml when compare the local and remote files localFiles and remoteFiles should match
/go/odo_1/tests/integration/cmd_dev_test.go:3324
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45457"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [70.684 seconds]
odo dev command tests when running odo dev with alternative commands - with metadata.name when running odo dev with a run command should execute the custom non-default run command successfully
/go/odo_1/tests/integration/cmd_dev_test.go:3181
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37455"
<< Captured StdOut/StdErr Output
------------------------------
• [7.416 seconds]
odo dev command tests when Devfile contains metadata.projectType invalid as a label value when odo deploy is executed should set the correct value in labels of deployed resources
/go/odo_1/tests/integration/cmd_dev_test.go:4105
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45183"
<< Captured StdOut/StdErr Output
------------------------------
• [59.486 seconds]
odo dev command tests when running odo dev with alternative commands - with metadata.name when running odo dev with a run command should execute the default run command successfully if specified explicitly
/go/odo_1/tests/integration/cmd_dev_test.go:3195
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41385"
<< Captured StdOut/StdErr Output
------------------------------
• [9.415 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44883"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [7.331 seconds]
odo dev command with api server tests when the component is bootstrapped should fail if --random-ports and --api-server-port are used together
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:63
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45875"
<< Captured StdOut/StdErr Output
------------------------------
• [60.900 seconds]
odo dev command tests when Devfile 2.1.0 is used - with metadata.name when doing odo dev with --var-file flag should check if the env variable has a correct value
/go/odo_1/tests/integration/cmd_dev_test.go:1639
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39145"
<< Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [63.253 seconds]
odo describe component command tests when creating a component when running odo dev (podman=false,debug=false) JSON output when describing the component in dev mode should describe the component
/go/odo_1/tests/integration/cmd_describe_component_test.go:416
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46559"
<< Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [111.637 seconds]
odo dev command tests when hotReload capable Build and Run commands are used with odo dev when a source file is modified should not re-execute the run command
/go/odo_1/tests/integration/cmd_dev_test.go:3834
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38393"
<< Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [32.351 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40561"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [26.072 seconds]
odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a build command should error out on an invalid command
/go/odo_1/tests/integration/cmd_dev_test.go:3080
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45329"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [88.840 seconds]
odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy with image build extra args should run odo dev successfully
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:161
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36325"
<< Captured StdOut/StdErr Output
------------------------------
• [60.788 seconds]
odo dev command tests when Devfile contains metadata.language when running odo dev should set the correct value in labels of resources
/go/odo_1/tests/integration/cmd_dev_test.go:4089
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34677"
<< Captured StdOut/StdErr Output
------------------------------
• [12.701 seconds]
odo describe component command tests when creating a component when running odo deploy to create ingress/routes should show the ingress/routes in odo describe component output
/go/odo_1/tests/integration/cmd_describe_component_test.go:552
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:38509"
<< Captured StdOut/StdErr Output
------------------------------
• [60.507 seconds]
odo dev command tests when a component is bootstrapped when run command takes really long to start should cancel run command and return if odo dev is stopped
/go/odo_1/tests/integration/cmd_dev_test.go:1002
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39555"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [5.666 seconds]
odo devfile build-images command tests when using a Devfile with variable image names should build images with default variable values (push=false)
/go/odo_1/tests/integration/cmd_devfile_build_images_test.go:431
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43915"
<< Captured StdOut/StdErr Output
------------------------------
• [63.549 seconds]
odo dev command tests when devfile has sourcemappings and running odo dev - without metadata.name should sync files to the correct location
/go/odo_1/tests/integration/cmd_dev_test.go:2016
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41821"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [62.063 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=false, customPortForwarding=false, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1338
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43215"
<< Captured StdOut/StdErr Output
------------------------------
• [61.486 seconds]
odo dev command tests when a component with multiple endpoints is run when odo dev is stopped should remove forwarded ports from state file
/go/odo_1/tests/integration/cmd_dev_test.go:3583
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45229"
<< Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [27.700 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="dev") should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:128
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44653"
<< Captured StdOut/StdErr Output
------------------------------
• [61.649 seconds]
odo dev command tests when running odo dev and composite command are nested - without metadata.name should execute all commands in composite commmand
/go/odo_1/tests/integration/cmd_dev_test.go:2674
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35847"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [7.862 seconds]
odo create/delete/list/set namespace/project tests set namespace should not succeed to set the namespace
/go/odo_1/tests/integration/cmd_namespace_test.go:162
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41845"
<< Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [61.137 seconds]
odo describe component command tests when creating a component when running odo dev (podman=false,debug=false) Default output when describing the component in dev mode should describe the component
/go/odo_1/tests/integration/cmd_describe_component_test.go:348
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:40983"
<< Captured StdOut/StdErr Output
------------------------------
• [5.127 seconds]
odo devfile build-images command tests when using a Devfile with variable image names should build images with --var-file (push=false)
/go/odo_1/tests/integration/cmd_devfile_build_images_test.go:445
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36655"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [4.897 seconds]
odo devfile build-images command tests when using a Devfile with variable image names should build images with --var-file (push=true)
/go/odo_1/tests/integration/cmd_devfile_build_images_test.go:445
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34653"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [61.427 seconds]
odo dev command tests when project and clonePath is present in devfile and running odo dev - with metadata.name should sync to the correct dir in container
/go/odo_1/tests/integration/cmd_dev_test.go:2058
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45029"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [61.553 seconds]
odo dev command tests when no project is present - without metadata.name should sync to the correct dir in container
/go/odo_1/tests/integration/cmd_dev_test.go:2164
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34693"
<< Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [4.157 seconds]
odo devfile init command tests setting application ports when running odo init --run-port with a Devfile with no commands should overwrite the ports into the container component referenced by the default run command
/go/odo_1/tests/integration/cmd_devfile_init_test.go:654
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34477"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [60.938 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=false, customPortForwarding=true, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1338
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33611"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [59.899 seconds]
odo dev command tests when a component is bootstrapped should sync .git directory and subfiles with --sync-git-dir
/go/odo_1/tests/integration/cmd_dev_test.go:182
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41623"
<< Captured StdOut/StdErr Output
------------------------------
• [6.859 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=false --running-in= should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42741"
<< Captured StdOut/StdErr Output
------------------------------
• [82.601 seconds]
odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=true, customPortForwarding=false, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1463
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37383"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [71.415 seconds]
odo dev command tests when adding local files to gitignore and running odo dev when modifying /foobar.txt file should not synchronize it
/go/odo_1/tests/integration/cmd_dev_test.go:1977
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:45565"
<< Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [10.856 seconds]
odo delete command tests when running odo deploy for an exec command bound to fail should print the job in the list of resources to be deleted with named delete command
/go/odo_1/tests/integration/cmd_delete_test.go:546
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:46651"
<< Captured StdOut/StdErr Output
------------------------------
• [8.737 seconds]
odo devfile deploy command tests when deploying a Devfile OpenShift component with multiple K8s resources defined should have created all the resources defined in the Devfile OpenShift component
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:372
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:32931"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [83.388 seconds]
odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=false, customPortForwarding=true, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1463
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39203"
<< Captured StdOut/StdErr Output
------------------------------
• [30.809 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="") should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:128
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:44501"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [9.244 seconds]
odo create/delete/list/set namespace/project tests delete project should not succeed to delete a non-existent project
/go/odo_1/tests/integration/cmd_namespace_test.go:122
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39729"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [12.604 seconds]
odo generic When deleting two project one after the other should be able to delete sequentially
/go/odo_1/tests/integration/generic_test.go:100
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34031"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [12.201 seconds]
odo devfile deploy command tests when using a devfile.yaml containing a deploy command when an env.yaml file contains a non-current Project when running odo deploy should succeed
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:201
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33457"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [9.949 seconds]
odo create/delete/list/set namespace/project tests set project should not succeed to set the project
/go/odo_1/tests/integration/cmd_namespace_test.go:162
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37857"
<< Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [8.706 seconds]
odo list with devfile listing non-odo managed components when a non-odo managed component is deployed should list the component with odo list
/go/odo_1/tests/integration/cmd_devfile_list_test.go:43
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36933"
<< Captured StdOut/StdErr Output
------------------------------
• [19.042 seconds]
odo create/delete/list/set namespace/project tests delete project when force-deleting a valid project should successfully delete the project asynchronously
/go/odo_1/tests/integration/cmd_namespace_test.go:107
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34191"
<< Captured StdOut/StdErr Output
------------------------------
• [59.389 seconds]
odo dev command tests port-forwarding for the component when devfile has no endpoint when running odo dev should have no endpoint forwarded (podman=false, manual=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1282
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36733"
<< Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [5.488 seconds]
odo devfile build-images command tests when using a Devfile with variable image names should build images with --var (push=false)
/go/odo_1/tests/integration/cmd_devfile_build_images_test.go:437
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36441"
<< Captured StdOut/StdErr Output
------------------------------
• [69.063 seconds]
odo dev command tests when adding local files to gitignore and running odo dev when modifying /foobar.txt file should not synchronize it
/go/odo_1/tests/integration/cmd_dev_test.go:1977
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37101"
<< Captured StdOut/StdErr Output
------------------------------
• [83.888 seconds]
odo dev command tests when starting with Devfile with autoBuild or deployByDefault components when running odo dev with some components referenced in the Devfile should create the appropriate resources
/go/odo_1/tests/integration/cmd_dev_test.go:4579
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37299"
<< Captured StdOut/StdErr Output
------------------------------
• [76.821 seconds]
odo dev command tests cleanup of resources is not successful when using a Devfile with a Pod failing to delete before the cleanup timeout when odo dev is executed when odo dev is stopped should report that the component could not be deleted
/go/odo_1/tests/integration/cmd_dev_test.go:5007
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34877"
<< Captured StdOut/StdErr Output
------------------------------
• [61.747 seconds]
odo dev command tests when running odo dev and devfile with composite command - with metadata.name should execute all commands in composite command
/go/odo_1/tests/integration/cmd_dev_test.go:2610
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43875"
<< Captured StdOut/StdErr Output
------------------------------
• [89.962 seconds]
odo dev command tests checking if odo dev matches local Devfile K8s resources and remote resources when odo dev is executed to run a devfile containing a k8s resource without apply command should have deleted the old resource and created the new resource
/go/odo_1/tests/integration/cmd_dev_test.go:1077
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41647"
<< Captured StdOut/StdErr Output
------------------------------
• [133.819 seconds]
odo list with devfile when a component created in 'app' application when dev is running on cluster show an odo deploy or dev in the list
/go/odo_1/tests/integration/cmd_devfile_list_test.go:193
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:41247"
<< Captured StdOut/StdErr Output
------------------------------
• [86.209 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 >>
Using Devfile Registry URL at: "http://127.0.0.1:46563"
Spawning '/go/bin/odo dev --random-ports -v 4' from /tmp/1557697053
<< Captured StdOut/StdErr Output
------------------------------
• [86.687 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when running odo deploy should run odo dev successfully
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:161
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:35095"
<< Captured StdOut/StdErr Output
------------------------------
• [60.266 seconds]
odo dev command tests 1. devfile contains composite apply command the devfile contains an image component that uses a remote Dockerfile when [PODMAN_CMD=echo] remote server returns a valid file when odo dev is run should build and push image when odo dev is run
/go/odo_1/tests/integration/cmd_dev_test.go:2526
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34673"
<< Captured StdOut/StdErr Output
------------------------------
• [110.248 seconds]
odo dev command tests multiple dev sessions with different project are running on same platform (podman=false), same port when odo dev session is run for nodejs component when odo dev session is run for go project on the same port but different address should be able to run both the sessions
/go/odo_1/tests/integration/cmd_dev_test.go:1213
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36219"
<< Captured StdOut/StdErr Output
------------------------------
• [79.359 seconds]
odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=false, customPortForwarding=false, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1463
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:39191"
<< Captured StdOut/StdErr Output
------------------------------
• [244.907 seconds]
odo dev command tests when node-js application is created and deployed with devfile schema 2.2.0 when Update the devfile.yaml, and waiting synchronization should check cpuLimit, cpuRequests, memoryRequests after restart
/go/odo_1/tests/integration/cmd_dev_test.go:3391
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:34973"
<< Captured StdOut/StdErr Output
------------------------------
• [125.307 seconds]
odo list with devfile when a component created in 'app' application when dev is running on cluster should display platform
/go/odo_1/tests/integration/cmd_devfile_list_test.go:150
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:36911"
<< Captured StdOut/StdErr Output
------------------------------
• [140.292 seconds]
odo dev command tests when running odo dev with devfile containing volume-component - with metadata.name should successfully use the volume components in container components
/go/odo_1/tests/integration/cmd_dev_test.go:2278
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:43955"
<< Captured StdOut/StdErr Output
------------------------------
Ran 406 of 956 Specs in 1444.347 seconds
SUCCESS! -- 406 Passed | 0 Failed | 0 Pending | 550 Skipped
Ginkgo ran 1 suite in 25m16.33775319s
Test Suite Passed
go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo --randomize-all --poll-progress-after=120s --poll-progress-interval=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: 1701422481 - will randomize all specs
Will run 4 of 4 specs
Running in parallel across 16 processes
------------------------------
• [108.039 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:316
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42645"
Spawning '/go/bin/odo init' from /tmp/2109671348
<< Captured StdOut/StdErr Output
------------------------------
Progress Report for Ginkgo Process #9
Automatically polling progress:
E2E Test starting with empty Directory should verify developer workflow from empty Directory (Spec Runtime: 2m3.496s)
/go/odo_1/tests/e2escenarios/e2e_test.go:50
In [It] (Node Runtime: 2m0s)
/go/odo_1/tests/e2escenarios/e2e_test.go:50
Begin Captured GinkgoWriter Output >>
...
[odo] Keyboard Commands:
[odo] [Ctrl+c] - Exit and delete resources from the cluster
[odo] [p] - Manually apply local changes to the application on the cluster
[odo] I1201 09:23:40.558099 59244 watch.go:271] deployment watcher Event: Type: MODIFIED, name: wynusc-app, rv: 118983723, generation: 1, pods: 1
[odo] I1201 09:23:40.668899 59244 watch.go:348] filesystem watch event: REMOVE "/tmp/1538221776/.odo/odo-file-index.json"
[odo] I1201 09:23:40.669294 59244 watch.go:383] error removing watch for /tmp/1538221776/.odo/odo-file-index.json: can't remove non-existent watcher: /tmp/1538221776/.odo/odo-file-index.json
[odo] I1201 09:23:40.669361 59244 watch.go:348] filesystem watch event: CREATE "/tmp/1538221776/.odo/odo-file-index.json"
[odo] I1201 09:23:40.678104 59244 watch.go:348] filesystem watch event: WRITE "/tmp/1538221776/.odo/odo-file-index.json"
[odo] I1201 09:23:40.680723 59244 watch.go:348] filesystem watch event: WRITE "/tmp/1538221776/.odo/devstate.json"
[odo] I1201 09:23:40.683952 59244 watch.go:348] filesystem watch event: WRITE "/tmp/1538221776/.odo/devstate.59244.json"
<< End Captured GinkgoWriter Output
Spec Goroutine
goroutine 48 [select]
github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0001c0000, {0x2f90520?, 0xc000d16000}, 0x1, {0x0, 0x0, 0x0})
/go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538
github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0001c0000, {0x2f90520, 0xc000d16000}, {0x0, 0x0, 0x0})
/go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145
github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x2bbd9c2, 0xf}, 0x0?, 0x3?, 0xc00043d710)
/go/odo_1/tests/helper/helper_run.go:54
github.com/redhat-developer/odo/tests/helper.StartDevMode({{0x0, 0x0, 0x0}, {0x0, 0x0, 0x0}, 0x0, 0x0, 0x0, 0x0, ...})
/go/odo_1/tests/helper/helper_dev.go:192
> github.com/redhat-developer/odo/tests/e2escenarios.glob..func1.5.1()
/go/odo_1/tests/e2escenarios/e2e_test.go:142
|
| // start dev mode again
> devSession, err = helper.StartDevMode(helper.DevSessionOpts{})
| Expect(err).ToNot(HaveOccurred())
|
github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x2659bb3, 0xc0001d02a0})
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463
github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3()
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865
github.com/onsi/ginkgo/v2/internal.(*Suite).runNode
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852
------------------------------
Progress Report for Ginkgo Process #8
Automatically polling progress:
E2E Test starting with non-empty Directory should verify developer workflow from non-empty Directory (Spec Runtime: 2m3.476s)
/go/odo_1/tests/e2escenarios/e2e_test.go:186
In [It] (Node Runtime: 2m0.001s)
/go/odo_1/tests/e2escenarios/e2e_test.go:186
Begin Captured GinkgoWriter Output >>
...
[odo] stderr: []
[odo] I1201 09:23:39.534035 58812 execute_run.go:36] error while running background command: unable to exec command [/bin/sh -c echo $$ > /opt/odo/.odo_cmd_run.pid && cd ${PROJECT_SOURCE} && (mvn -Dmaven.repo.local=/home/user/.m2/repository spring-boot:run) 1>>/proc/1/fd/1 2>>/proc/1/fd/2; echo $? >> /opt/odo/.odo_cmd_run.pid]: error while streaming command: context canceled
[odo] I1201 09:23:39.539881 58812 implem.go:114] The path for preference file is /tmp/1546598755/preference.yaml
[odo] I1201 09:23:39.540704 58812 segment.go:268] Checking telemetry enable status
[odo] I1201 09:23:39.540721 58812 segment.go:286] Sending telemetry disabled by env variable
[odo] Cleaning resources, please wait
[odo] I1201 09:23:39.745969 58812 all.go:46] starting to concurrently query 201 APIs
[odo] I1201 09:23:39.747858 58812 all.go:62] fired up all goroutines to query APIs
[odo] I1201 09:23:40.480075 58812 all.go:67] all goroutines have returned in 734.112059ms
[odo] I1201 09:23:40.480140 58812 all.go:76] query result: objects=640
<< End Captured GinkgoWriter Output
Spec Goroutine
goroutine 75 [select]
github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0004da3f0, {0x2f90400?, 0xc0005e46a8}, 0x1, {0x0, 0x0, 0x0})
/go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538
github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0004da3f0, {0x2f90400, 0xc0005e46a8}, {0x0, 0x0, 0x0})
/go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145
github.com/onsi/gomega/gexec.(*Session).Wait(0xc0006fbd28?, {0xc00042a0a0?, 0xc0006fbc18?, 0x3?})
/go/odo_1/vendor/github.com/onsi/gomega/gexec/session.go:144
github.com/redhat-developer/odo/tests/helper.DevSession.WaitEnd(...)
/go/odo_1/tests/helper/helper_dev.go:263
> github.com/redhat-developer/odo/tests/e2escenarios.glob..func1.6.2()
/go/odo_1/tests/e2escenarios/e2e_test.go:245
| // "exit dev mode and run odo deploy"
| devSession.Stop()
> devSession.WaitEnd()
|
| // all resources should be deleted from the namespace
github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x2659bb3, 0xc0005ee000})
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463
github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3()
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865
github.com/onsi/ginkgo/v2/internal.(*Suite).runNode
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852
------------------------------
Progress Report for Ginkgo Process #2
Automatically polling progress:
E2E Test starting with non-empty Directory add Binding should verify developer workflow of using binding as env in innerloop (Spec Runtime: 2m10.301s)
/go/odo_1/tests/e2escenarios/e2e_test.go:448
In [It] (Node Runtime: 2m0.001s)
/go/odo_1/tests/e2escenarios/e2e_test.go:448
Begin Captured GinkgoWriter Output >>
...
[odo] I1201 09:23:43.658086 58984 exec.go:37] Executing command [/bin/sh -c cat /opt/odo/.odo_cmd_run.pid || true] for pod: btqhrr-app-59ccc4c6fb-hmqkp in container: runtime
[odo] I1201 09:23:43.818359 58984 exec.go:96] cat: /opt/odo/.odo_cmd_run.pid: No such file or directory
[odo] I1201 09:23:43.820889 58984 innerloop.go:131] running=false, execRequired=true
[odo] • Building your application in container (command: build) ...
[odo] I1201 09:23:43.821283 58984 exec.go:37] Executing command [/bin/sh -c cd ${PROJECT_SOURCE} && (export GOPATH="${PROJECT_SOURCE}/.go" GOCACHE="${PROJECT_SOURCE}/.cache" && go build main.go) 1>>/proc/1/fd/1 2>>/proc/1/fd/2] for pod: btqhrr-app-59ccc4c6fb-hmqkp in container: runtime
[odo] I1201 09:23:46.540806 58984 kubeexec.go:54] StartProcessForCommand for "run"
[odo] I1201 09:23:46.540887 58984 retry.go:48] waiting for 5 second(s) before trying task "process for command \"run\""
[odo] ↵
✓ Building your application in container (command: build) [3s]
[odo] • Executing the application (command: run) ...
[odo] I1201 09:23:46.540912 58984 exec.go:37] Executing command [/bin/sh -c echo $$ > /opt/odo/.odo_cmd_run.pid && cd ${PROJECT_SOURCE} && (./main) 1>>/proc/1/fd/1 2>>/proc/1/fd/2; echo $? >> /opt/odo/.odo_cmd_run.pid] for pod: btqhrr-app-59ccc4c6fb-hmqkp in container: runtime
<< End Captured GinkgoWriter Output
Spec Goroutine
goroutine 80 [select]
github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc00054fab0, {0x2f90520?, 0xc0005f1d70}, 0x1, {0x0, 0x0, 0x0})
/go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538
github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc00054fab0, {0x2f90520, 0xc0005f1d70}, {0x0, 0x0, 0x0})
/go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145
github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x2baf8eb, 0x8}, 0x0?, 0x48?, 0xc0003cde60)
/go/odo_1/tests/helper/helper_run.go:54
github.com/redhat-developer/odo/tests/helper.(*DevSession).WaitSync(0xc0005d5e28)
/go/odo_1/tests/helper/helper_dev.go:279
> github.com/redhat-developer/odo/tests/e2escenarios.glob..func1.8.4()
/go/odo_1/tests/e2escenarios/e2e_test.go:513
| helper.Cmd("odo", "remove", "binding", "--name", bindingName).ShouldPass()
|
> err = devSession.WaitSync()
| Expect(err).To(BeNil())
| Eventually(func() string { return helper.Cmd("odo", "describe", "binding").ShouldRun().Out() }).
github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x2659bb3, 0xc0005c4000})
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463
github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3()
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865
github.com/onsi/ginkgo/v2/internal.(*Suite).runNode
/go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852
------------------------------
• [151.733 seconds]
E2E Test starting with empty Directory should verify developer workflow from empty Directory
/go/odo_1/tests/e2escenarios/e2e_test.go:50
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:42851"
Spawning '/go/bin/odo init' from /tmp/1538221776
Spawning '/go/bin/odo delete component' from /tmp/1538221776
<< Captured StdOut/StdErr Output
------------------------------
• [172.288 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:448
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:37823"
Spawning '/go/bin/odo init' from /tmp/646246884
<< Captured StdOut/StdErr Output
------------------------------
• [240.578 seconds]
E2E Test starting with non-empty Directory should verify developer workflow from non-empty Directory
/go/odo_1/tests/e2escenarios/e2e_test.go:186
Captured StdOut/StdErr Output >>
Using Devfile Registry URL at: "http://127.0.0.1:33059"
Spawning '/go/bin/odo init' from /tmp/3814211741
Spawning '/go/bin/odo delete component' from /tmp/3814211741
<< Captured StdOut/StdErr Output
------------------------------
Ran 4 of 4 Specs in 240.636 seconds
SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped
Ginkgo ran 1 suite in 4m19.086910843s
Test Suite Passed