cp ododevapispec.yaml pkg/apiserver-impl/swagger-ui/swagger.yaml go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=0daac77fc" ./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: 1698219271 - will randomize all specs Will run 504 of 956 specs Running in parallel across 16 processes SSSSSSSSSSSSSSSSSSSSSSS ------------------------------ • [16.803 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [18.461 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [20.519 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [20.695 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [21.588 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [22.287 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [6.642 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [5.581 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [8.376 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [7.633 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [37.732 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [65.611 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [66.154 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [67.978 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [75.399 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [59.686 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [78.941 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ S [3.774 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: "https://registry.stage.devfile.io" << 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 @ 10/25/23 07:36:55.029 ------------------------------ • [60.120 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [6.782 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ • [59.634 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [15.346 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: "https://registry.stage.devfile.io" Spawning '/go/bin/odo dev --random-ports' from /tmp/2674343802 << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [6.952 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [68.381 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [11.750 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [107.893 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [107.878 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [8.349 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [58.626 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [27.692 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [57.413 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [59.782 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [129.939 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [129.863 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ S [3.398 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: "https://registry.stage.devfile.io" << 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 @ 10/25/23 07:37:48.862 ------------------------------ Progress Report for Ginkgo Process #14 Automatically polling progress: 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 (Spec Runtime: 2m13.653s) /go/odo_1/tests/integration/cmd_dev_test.go:2230 In [BeforeEach] (Node Runtime: 2m0s) /go/odo_1/tests/integration/cmd_dev_test.go:2178 Begin Captured GinkgoWriter Output >> ... [odo] I1025 07:37:38.987316 13193 exec.go:96] sl local_address rem_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops [odo] I1025 07:37:38.987321 13193 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode [odo] I1025 07:37:38.987326 13193 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops [odo] I1025 07:37:38.990438 13193 port.go:319] port 3000 not listening in container "runtime" [odo] I1025 07:37:48.757294 13193 exec.go:37] Executing command [/bin/sh -c cat /proc/net/tcp /proc/net/udp /proc/net/tcp6 /proc/net/udp6 || true] for pod: vusepr-app-6b9fcdf9bc-r4j4d in container: runtime [odo] I1025 07:37:48.988198 13193 exec.go:96] sl local_address rem_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode [odo] I1025 07:37:48.988657 13193 exec.go:96] sl local_address rem_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops [odo] I1025 07:37:48.989338 13193 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode [odo] I1025 07:37:48.991924 13193 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops [odo] I1025 07:37:48.992960 13193 port.go:319] port 3000 not listening in container "runtime" << End Captured GinkgoWriter Output Spec Goroutine goroutine 69 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc000401030, {0x30fed88?, 0xc000e229c0}, 0x1, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc000401030, {0x30fed88, 0xc000e229c0}, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x2d02089, 0xf}, 0x0?, 0x3?, 0xc000e22960) /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/integration.glob..func7.22.1() /go/odo_1/tests/integration/cmd_dev_test.go:2189 | } | var err error > devSession, err = helper.StartDevMode(helper.DevSessionOpts{}) | Expect(err).ToNot(HaveOccurred()) | }) github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x269b4f3, 0xc00051cea0}) /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 ------------------------------ • [64.983 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [30.361 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [30.133 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [61.117 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [8.603 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ S [4.659 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: "https://registry.stage.devfile.io" << 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 @ 10/25/23 07:38:00.681 ------------------------------ SS ------------------------------ • [8.483 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [54.073 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ S [4.558 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] skipped on non Kubernetes clusters In [BeforeEach] at: /go/odo_1/tests/integration/interactive_init_test.go:710 @ 10/25/23 07:38:05.198 ------------------------------ SS ------------------------------ • [6.456 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [121.466 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [9.523 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [5.407 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [78.603 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [7.207 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [29.206 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [51.791 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [5.504 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [3.487 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [5.435 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [56.173 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [60.123 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [59.879 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [4.284 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [120.091 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [59.125 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSS ------------------------------ • [58.390 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [208.808 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [6.077 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [58.878 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [56.497 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [64.192 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [4.053 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [120.796 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [4.365 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [59.599 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [5.962 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [123.185 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [70.955 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSS ------------------------------ • [5.403 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: "https://registry.stage.devfile.io" Spawning '/go/bin/odo deploy' from /tmp/1334577536 << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [58.065 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ S [3.766 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: "https://registry.stage.devfile.io" << 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 @ 10/25/23 07:39:50.877 ------------------------------ SSS ------------------------------ • [60.259 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ • [58.691 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: "https://registry.stage.devfile.io" <<< Session terminated >>> << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [4.514 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [121.002 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [108.530 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [57.408 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [118.805 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [69.359 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [59.735 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [28.660 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [15.580 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [113.478 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [9.283 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [46.897 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [59.323 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [74.500 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [58.743 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [58.948 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [5.424 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: "https://registry.stage.devfile.io" Spawning '/go/bin/odo deploy -v 4' from /tmp/1362862326 << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [58.608 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [28.438 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [59.665 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [4.572 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [7.637 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [8.332 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [6.840 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [5.532 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [59.403 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [108.502 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [4.544 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [57.257 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [81.455 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [5.036 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [58.433 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [29.692 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [58.802 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: "https://registry.stage.devfile.io" PID: 22724 << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [9.703 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [110.833 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [59.563 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSS ------------------------------ • [85.281 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [47.124 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [56.751 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [27.175 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [120.077 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [6.839 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [16.004 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [60.104 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [121.404 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [24.381 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [7.901 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [128.179 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [59.941 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [27.424 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [58.772 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [5.421 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [4.463 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [27.838 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [79.497 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [15.474 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [10.595 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ S [4.575 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] skipped on non Kubernetes clusters In [BeforeEach] at: /go/odo_1/tests/integration/cmd_pref_config_test.go:379 @ 10/25/23 07:43:11.329 ------------------------------ • [117.150 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [85.119 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [3.998 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [77.199 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [57.956 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [5.935 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [79.047 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [59.338 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [3.964 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [57.030 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [130.304 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [59.645 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [11.682 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [150.194 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [5.653 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [89.489 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [96.616 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [6.195 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [58.047 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSS ------------------------------ • [8.948 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [48.311 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ Progress Report for Ginkgo Process #4 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.751s) /go/odo_1/tests/integration/cmd_dev_test.go:1077 In [BeforeEach] (Node Runtime: 2m0.001s) /go/odo_1/tests/integration/cmd_dev_test.go:1050 Begin Captured GinkgoWriter Output >> ... [odo] I1025 07:44:07.092666 25603 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops [odo] I1025 07:44:07.093535 25603 port.go:319] port 8080 not listening in container "runtime" [odo] I1025 07:44:14.907778 25603 exec.go:37] Executing command [/bin/sh -c cat /proc/net/tcp /proc/net/udp /proc/net/tcp6 /proc/net/udp6 || true] for pod: nninrj-app-b757d67b-89prv in container: runtime [odo] I1025 07:44:15.447693 25603 exec.go:96] sl local_address rem_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode [odo] I1025 07:44:15.447714 25603 exec.go:96] 0: 662E11AC:E8C0 221F1068:01BB 06 00000000:00000000 03:00000BCE 00000000 0 0 0 3 0000000000000000 [odo] I1025 07:44:15.447719 25603 exec.go:96] sl local_address rem_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops [odo] I1025 07:44:15.447723 25603 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode [odo] I1025 07:44:15.447727 25603 exec.go:96] 0: 00000000000000000000000000000000:0BB8 00000000000000000000000000000000:0000 0A 00000000:00000000 00:00000000 00000000 1002690000 0 1513290464 1 0000000000000000 100 0 0 10 0 [odo] I1025 07:44:15.447733 25603 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops [odo] I1025 07:44:15.484098 25603 port.go:319] port 8080 not listening in container "runtime" << End Captured GinkgoWriter Output Spec Goroutine goroutine 393 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc000470000, {0x30fed88?, 0xc0012c0000}, 0x1, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc000470000, {0x30fed88, 0xc0012c0000}, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x2cf3414, 0x8}, 0xc000601cc0?, 0xc000601ca0?, 0xc0014a0930) /go/odo_1/tests/helper/helper_run.go:54 github.com/redhat-developer/odo/tests/helper.(*DevSession).WaitSync(0xc00010f440) /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({0x1088f3e, 0xc00073c660}) /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 ------------------------------ • [129.268 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [59.761 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [8.157 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [8.396 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ S [6.436 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: "https://registry.stage.devfile.io" << 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 @ 10/25/23 07:44:25.358 ------------------------------ • [58.792 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [8.558 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [8.595 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [229.033 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [8.100 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ S [5.509 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: "https://registry.stage.devfile.io" << 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 @ 10/25/23 07:44:40.774 ------------------------------ • [88.991 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [96.132 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [62.363 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [62.864 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ • [61.125 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [6.639 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [61.336 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [60.504 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [62.438 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [208.665 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [60.103 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [79.979 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [5.239 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [76.176 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [129.007 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [59.200 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [58.793 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [112.220 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [60.012 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [9.554 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [31.659 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [61.590 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [15.574 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [120.151 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [90.905 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [85.080 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [4.885 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [8.446 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [121.713 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [27.945 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [59.917 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [135.406 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [50.040 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ S [5.141 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: "https://registry.stage.devfile.io" << 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 @ 10/25/23 07:46:58.555 ------------------------------ S ------------------------------ • [24.941 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [7.917 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [5.263 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ S [3.524 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:216 [It] /go/odo_1/tests/integration/cmd_devfile_registry_test.go:244 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] skipped on non Kubernetes clusters In [BeforeEach] at: /go/odo_1/tests/integration/cmd_devfile_registry_test.go:218 @ 10/25/23 07:47:08.539 ------------------------------ • [5.087 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [53.476 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [62.382 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [6.015 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [62.488 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [31.329 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [163.032 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [69.480 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [83.858 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: "https://registry.stage.devfile.io" Spawning '/go/bin/odo dev --random-ports -v 4' from /tmp/1514623156 << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [62.036 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [4.259 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [79.298 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [68.209 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [118.276 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ S [4.902 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] skipped on non Kubernetes clusters In [BeforeEach] at: /go/odo_1/tests/integration/cmd_pref_config_test.go:379 @ 10/25/23 07:47:43.422 ------------------------------ S ------------------------------ S [3.452 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: "https://registry.stage.devfile.io" << 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 @ 10/25/23 07:47:46.775 ------------------------------ • [5.677 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [26.036 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSS ------------------------------ • [6.200 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [60.081 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSS ------------------------------ • [51.429 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSS ------------------------------ • [58.900 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [59.248 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [38.488 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [32.652 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [61.120 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [11.068 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [19.706 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [11.111 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [12.902 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [8.778 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [80.084 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [6.173 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [6.890 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [118.538 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [88.336 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [4.638 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [60.793 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [112.416 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSS ------------------------------ • [12.949 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [5.865 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [131.613 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [7.778 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [60.803 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [119.332 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [4.418 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [49.813 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [60.366 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [4.525 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [4.389 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ • [8.217 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: "https://registry.stage.devfile.io" Spawning '/go/bin/odo deploy' from /tmp/3431677750 << Captured StdOut/StdErr Output ------------------------------ • [7.585 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [87.093 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: "https://registry.stage.devfile.io" Spawning '/go/bin/odo dev --random-ports' from /tmp/76456674 << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [8.710 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [6.331 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [81.560 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [91.903 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [91.465 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [59.919 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [7.314 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [6.010 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [9.241 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [80.801 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [80.607 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [119.843 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [107.939 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [57.703 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [5.848 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [60.420 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [59.520 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [64.965 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [127.533 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [130.495 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [48.439 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [80.385 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ Progress Report for Ginkgo Process #3 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: 3m32.222s) /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: 27.008s) /go/odo_1/tests/integration/cmd_dev_debug_test.go:326 Begin Captured GinkgoWriter Output >> ... [odo] ✗ Finished executing the application (command: start-debug) [1m] [odo] I1025 07:50:38.090596 2876 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] I1025 07:50:38.093231 2876 implem.go:114] The path for preference file is /tmp/1479199589/preference.yaml [odo] Cleaning resources, please wait [odo] I1025 07:50:38.094464 2876 segment.go:268] Checking telemetry enable status [odo] I1025 07:50:38.094477 2876 segment.go:286] Sending telemetry disabled by env variable [odo] I1025 07:50:38.156510 2876 all.go:46] starting to concurrently query 200 APIs [odo] I1025 07:50:38.158243 2876 all.go:62] fired up all goroutines to query APIs [odo] I1025 07:50:38.982522 2876 all.go:67] all goroutines have returned in 825.98899ms [odo] I1025 07:50:38.982622 2876 all.go:76] query result: objects=652 << End Captured GinkgoWriter Output Spec Goroutine goroutine 533 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0004ccaf0, {0x30feb48?, 0xc000d9ac00}, 0x1, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0004ccaf0, {0x30feb48, 0xc000d9ac00}, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/onsi/gomega/gexec.(*Session).Wait(0xc000458720?, {0xc00032ef80?, 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(0xc0001b0000, {0x2d5356e, 0x2f}, {0xc00014fe70, 0x1, 0x0?}) /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:309 github.com/onsi/ginkgo/v2.By({0x2d5356e?, 0xf7289d?}, {0xc00014fe70?, 0x1279ea0?, 0x0?}) /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({0x1088f3e, 0xc0014e8300}) /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 ------------------------------ • [24.079 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [57.397 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [94.733 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [224.939 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [100.003 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [13.599 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [69.044 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [64.078 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [58.907 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [6.766 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [10.880 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [9.470 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [37.436 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [58.779 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [69.005 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [58.849 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [29.074 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [8.605 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [74.278 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [5.724 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [59.628 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [26.336 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [62.496 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S•S ------------------------------ • [27.339 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [84.892 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [79.029 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [60.613 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [3.845 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ Progress Report for Ginkgo Process #5 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: 2m2.344s) /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] I1025 07:52:24.934861 8705 segment.go:286] Sending telemetry disabled by env variable [odo] I1025 07:52:24.934711 8705 exec.go:54] ExecuteCommand returned an an err: error while streaming command: error sending request: Post "https://c100-e.eu-de.containers.cloud.ibm.com:31952/api/v1/namespaces/cmd-dev-test4146bkf/pods/riphhb-app-56f6d46784-lrg8g/exec?command=%2Fbin%2Fsh&command=-c&command=cat+%2Fopt%2Fodo%2F.odo_cmd_run.pid+%7C%7C+true&container=runtime&stderr=true&stdout=true": dial tcp: lookup c100-e.eu-de.containers.cloud.ibm.com: operation was canceled. for command '[/bin/sh -c cat /opt/odo/.odo_cmd_run.pid || true]' [odo] stdout: [] [odo] stderr: [] [odo] ✗ Finished executing the application (command: run) [1m] [odo] I1025 07:52:24.935728 8705 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] I1025 07:52:25.018501 8705 all.go:46] starting to concurrently query 200 APIs [odo] I1025 07:52:25.024713 8705 all.go:62] fired up all goroutines to query APIs [odo] I1025 07:52:26.678532 8705 all.go:67] all goroutines have returned in 1.660191946s [odo] I1025 07:52:26.678629 8705 all.go:76] query result: objects=615 << End Captured GinkgoWriter Output Spec Goroutine goroutine 848 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0006f8230, {0x30feb48?, 0xc0017c6ac8}, 0x1, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0006f8230, {0x30feb48, 0xc0017c6ac8}, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/onsi/gomega/gexec.(*Session).Wait(0xc000addd50?, {0xc0007906f0?, 0x2cf51f1?, 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({0x1088f3e, 0xc00006d560}) /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 ------------------------------ • [118.430 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [86.645 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [128.298 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [61.748 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [73.416 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [61.383 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [88.510 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSS ------------------------------ • [80.916 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [27.577 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [14.046 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [119.189 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [15.208 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [60.812 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ • [6.425 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ • [7.408 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [30.449 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ Progress Report for Ginkgo Process #16 Automatically polling progress: odo dev command tests when running odo dev and single env var is set - with metadata.name should be able to exec command (Spec Runtime: 2m5.641s) /go/odo_1/tests/integration/cmd_dev_test.go:1691 In [It] (Node Runtime: 2m0.001s) /go/odo_1/tests/integration/cmd_dev_test.go:1691 Begin Captured GinkgoWriter Output >> ... [odo] read: read /dev/stdin: input/output error [odo] I1025 07:53:20.585641 10088 watch.go:333] Dev mode interrupted by user [odo] I1025 07:53:20.592848 10088 implem.go:114] The path for preference file is /tmp/2167100078/preference.yaml [odo] Cleaning resources, please wait [odo] I1025 07:53:20.593706 10088 segment.go:268] Checking telemetry enable status [odo] I1025 07:53:20.593717 10088 segment.go:286] Sending telemetry disabled by env variable [odo] I1025 07:53:20.727428 10088 all.go:46] starting to concurrently query 200 APIs [odo] I1025 07:53:20.728830 10088 all.go:62] fired up all goroutines to query APIs [odo] I1025 07:53:21.617359 10088 all.go:67] all goroutines have returned in 889.9095ms [odo] I1025 07:53:21.617497 10088 all.go:76] query result: objects=618 << End Captured GinkgoWriter Output Spec Goroutine goroutine 967 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0004a0af0, {0x30feb48?, 0xc00151e048}, 0x1, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0004a0af0, {0x30feb48, 0xc00151e048}, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/onsi/gomega/gexec.(*Session).Wait(0xc000bb3d70?, {0xc0007b8290?, 0xc000bb3c38?, 0x2?}) /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.11.2() /go/odo_1/tests/integration/cmd_dev_test.go:1692 | | 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({0x1088f3e, 0xc00158cea0}) /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 ------------------------------ • [5.810 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [8.125 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [60.788 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [59.084 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ • [4.955 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [137.626 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [55.957 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [141.777 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [60.516 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [5.804 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [97.954 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [64.329 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [72.693 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [5.508 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [8.576 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [74.993 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [5.348 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [91.347 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S [3.170 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: "https://registry.stage.devfile.io" << 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 @ 10/25/23 07:54:37.302 ------------------------------ • [86.067 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ • [59.384 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [5.277 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [67.398 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [91.789 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [59.089 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [4.954 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [58.219 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [68.519 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [26.035 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [85.265 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S [5.380 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: "https://registry.stage.devfile.io" << 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 @ 10/25/23 07:55:17.233 ------------------------------ SS ------------------------------ • [55.617 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [4.126 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [62.043 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [123.144 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [6.052 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [5.668 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [107.017 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [57.786 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [58.765 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [58.006 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [58.430 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [109.589 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [9.256 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [49.041 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [5.525 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [117.312 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [61.791 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [4.853 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSS ------------------------------ • [6.887 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [9.523 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [107.689 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [58.539 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [79.509 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [6.019 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [62.026 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [57.955 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [79.715 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [4.619 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [8.479 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: "https://registry.stage.devfile.io" Spawning '/go/bin/odo deploy' from /tmp/1543494281 << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [60.113 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [6.537 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [57.602 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [19.972 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: "https://registry.stage.devfile.io" Spawning '/go/bin/odo dev --random-ports --no-watch' from /tmp/462175690 << Captured StdOut/StdErr Output ------------------------------ • [5.697 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [61.567 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [59.576 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [5.076 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [63.578 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [84.379 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [60.835 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [62.032 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [5.028 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [57.207 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [31.097 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [7.217 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [4.315 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ •SS ------------------------------ S [3.772 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] skipped on non Kubernetes clusters In [BeforeEach] at: /go/odo_1/tests/integration/cmd_devfile_init_test.go:588 @ 10/25/23 07:57:16.972 ------------------------------ • [49.761 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [8.322 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [58.428 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [118.430 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [67.964 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [84.560 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [58.766 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [83.474 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [81.136 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: "https://registry.stage.devfile.io" Spawning '/go/bin/odo dev --random-ports' from /tmp/143537434 << Captured StdOut/StdErr Output ------------------------------ • [126.897 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [97.247 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [107.713 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [149.641 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ • [107.929 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: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ Ran 406 of 956 Specs in 1398.929 seconds SUCCESS! -- 406 Passed | 0 Failed | 0 Pending | 550 Skipped Ginkgo ran 1 suite in 24m27.419727327s 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: 1698220746 - will randomize all specs Will run 4 of 4 specs Running in parallel across 16 processes ------------------------------ • [110.394 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: "https://registry.stage.devfile.io" Spawning '/go/bin/odo init' from /tmp/1734595684 << Captured StdOut/StdErr Output ------------------------------ Progress Report for Ginkgo Process #4 Automatically polling progress: E2E Test starting with empty Directory should verify developer workflow from empty Directory (Spec Runtime: 2m4.903s) /go/odo_1/tests/e2escenarios/e2e_test.go:50 In [It] (Node Runtime: 2m0.001s) /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] I1025 08:01:28.112312 21643 watch.go:271] deployment watcher Event: Type: MODIFIED, name: wljlaq-app, rv: 95781042, generation: 1, pods: 1 [odo] I1025 08:01:28.219216 21643 watch.go:348] filesystem watch event: REMOVE "/tmp/3633024612/.odo/odo-file-index.json" [odo] I1025 08:01:28.219621 21643 watch.go:383] error removing watch for /tmp/3633024612/.odo/odo-file-index.json: can't remove non-existent watcher: /tmp/3633024612/.odo/odo-file-index.json [odo] I1025 08:01:28.219698 21643 watch.go:348] filesystem watch event: CREATE "/tmp/3633024612/.odo/odo-file-index.json" [odo] I1025 08:01:28.225353 21643 watch.go:348] filesystem watch event: WRITE "/tmp/3633024612/.odo/odo-file-index.json" [odo] I1025 08:01:28.228669 21643 watch.go:348] filesystem watch event: WRITE "/tmp/3633024612/.odo/devstate.json" [odo] I1025 08:01:28.232636 21643 watch.go:348] filesystem watch event: WRITE "/tmp/3633024612/.odo/devstate.21643.json" << End Captured GinkgoWriter Output Spec Goroutine goroutine 74 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0000f8700, {0x2f3fb30?, 0xc000efcdb0}, 0x1, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0000f8700, {0x2f3fb30, 0xc000efcdb0}, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x2b6fc95, 0xf}, 0x0?, 0x3?, 0xc000efcd50) /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({0x103b705, 0xc0001007e0}) /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 #1 Automatically polling progress: E2E Test starting with non-empty Directory should verify developer workflow from non-empty Directory (Spec Runtime: 2m4.961s) /go/odo_1/tests/e2escenarios/e2e_test.go:186 In [It] (Node Runtime: 2m0.003s) /go/odo_1/tests/e2escenarios/e2e_test.go:186 Begin Captured GinkgoWriter Output >> ... [odo] ✗ Finished executing the application (command: run) [27s] [odo] I1025 08:01:26.703686 21333 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] I1025 08:01:26.716917 21333 implem.go:114] The path for preference file is /tmp/709416063/preference.yaml [odo] I1025 08:01:26.717987 21333 segment.go:268] Checking telemetry enable status [odo] I1025 08:01:26.718015 21333 segment.go:286] Sending telemetry disabled by env variable [odo] Cleaning resources, please wait [odo] I1025 08:01:26.793956 21333 all.go:46] starting to concurrently query 200 APIs [odo] I1025 08:01:26.794110 21333 all.go:62] fired up all goroutines to query APIs [odo] I1025 08:01:27.465739 21333 all.go:67] all goroutines have returned in 671.814689ms [odo] I1025 08:01:27.465801 21333 all.go:76] query result: objects=623 << End Captured GinkgoWriter Output Spec Goroutine goroutine 70 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0006ba0e0, {0x2f3fa10?, 0xc0008180d8}, 0x1, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0006ba0e0, {0x2f3fa10, 0xc0008180d8}, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/onsi/gomega/gexec.(*Session).Wait(0xc00067bd28?, {0xc0005cc270?, 0xc00067bc18?, 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({0x2630113, 0xc00006cde0}) /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 #7 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: 2m9.781s) /go/odo_1/tests/e2escenarios/e2e_test.go:448 In [It] (Node Runtime: 2m0s) /go/odo_1/tests/e2escenarios/e2e_test.go:448 Begin Captured GinkgoWriter Output >> ... [odo] I1025 08:01:33.513538 21421 exec.go:37] Executing command [/bin/sh -c cat /opt/odo/.odo_cmd_run.pid || true] for pod: ckglzb-app-5fcd7bb77b-cb6mg in container: runtime [odo] I1025 08:01:33.711173 21421 exec.go:96] 162 [odo] I1025 08:01:33.715849 21421 exec.go:37] Executing command [/bin/sh -c kill -0 162; echo $?] for pod: ckglzb-app-5fcd7bb77b-cb6mg in container: runtime [odo] I1025 08:01:33.890536 21421 exec.go:96] 0 [odo] I1025 08:01:33.892944 21421 kubeexec.go:40] GetProcessInfoForCommand for "run" [odo] I1025 08:01:33.892989 21421 exec.go:37] Executing command [/bin/sh -c cat /opt/odo/.odo_cmd_run.pid || true] for pod: ckglzb-app-5fcd7bb77b-cb6mg in container: runtime [odo] I1025 08:01:34.070361 21421 exec.go:96] 162 [odo] I1025 08:01:34.073425 21421 exec.go:37] Executing command [/bin/sh -c kill -0 162; echo $?] for pod: ckglzb-app-5fcd7bb77b-cb6mg in container: runtime [odo] I1025 08:01:34.254384 21421 exec.go:96] 0 [odo] • Waiting for the application to be ready ... << End Captured GinkgoWriter Output Spec Goroutine goroutine 88 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc00073aaf0, {0x2f3fb30?, 0xc0003c2c30}, 0x1, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc00073aaf0, {0x2f3fb30, 0xc0003c2c30}, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x2b61c23, 0x8}, 0x0?, 0x48?, 0xc0003c2030) /go/odo_1/tests/helper/helper_run.go:54 github.com/redhat-developer/odo/tests/helper.(*DevSession).WaitSync(0xc000991e28) /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({0x103b71e, 0xc00006c960}) /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 ------------------------------ • [153.982 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: "https://registry.stage.devfile.io" Spawning '/go/bin/odo init' from /tmp/3633024612 Spawning '/go/bin/odo delete component' from /tmp/3633024612 << Captured StdOut/StdErr Output ------------------------------ • [171.362 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: "https://registry.stage.devfile.io" Spawning '/go/bin/odo init' from /tmp/981539845 << Captured StdOut/StdErr Output ------------------------------ Progress Report for Ginkgo Process #1 Automatically polling progress: E2E Test starting with non-empty Directory should verify developer workflow from non-empty Directory (Spec Runtime: 4m4.966s) /go/odo_1/tests/e2escenarios/e2e_test.go:186 In [It] (Node Runtime: 4m0.008s) /go/odo_1/tests/e2escenarios/e2e_test.go:186 Begin Captured GinkgoWriter Output >> ... [odo] ↪ Dev mode [odo] Status: [odo] Watching for changes in the current directory /tmp/3979178119 [odo] [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] I1025 08:03:22.693589 21841 watch.go:271] deployment watcher Event: Type: MODIFIED, name: yduajd-app, rv: 95782268, generation: 1, pods: 1 [odo] I1025 08:03:22.810747 21841 watch.go:348] filesystem watch event: WRITE "/tmp/3979178119/.odo/odo-file-index.json" [odo] I1025 08:03:22.813007 21841 watch.go:348] filesystem watch event: WRITE "/tmp/3979178119/.odo/odo-file-index.json" << End Captured GinkgoWriter Output Spec Goroutine goroutine 70 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0004e0af0, {0x2f3fb30?, 0xc0000ea3c0}, 0x1, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0004e0af0, {0x2f3fb30, 0xc0000ea3c0}, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x2b61c23, 0x8}, 0xc000b34000?, 0xc0000b0600?, 0xc0008f1890) /go/odo_1/tests/helper/helper_run.go:54 github.com/redhat-developer/odo/tests/helper.(*DevSession).WaitSync(0xc000a9fd28) /go/odo_1/tests/helper/helper_dev.go:279 > github.com/redhat-developer/odo/tests/e2escenarios.glob..func1.6.2() /go/odo_1/tests/e2escenarios/e2e_test.go:274 | // making changes to the project again | helper.ReplaceString(filepath.Join(commonVar.Context, "src", "main", "java", "com", "example", "demo", "DemoApplication.java"), "Hello from an updated World!", "Hello from an updated v2 World!") > err = devSession.WaitSync() | Expect(err).ToNot(HaveOccurred()) | github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x2630113, 0xc00006cde0}) /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 ------------------------------ • [252.306 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: "https://registry.stage.devfile.io" Spawning '/go/bin/odo init' from /tmp/3979178119 Spawning '/go/bin/odo delete component' from /tmp/3979178119 << Captured StdOut/StdErr Output ------------------------------ Ran 4 of 4 Specs in 252.412 seconds SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped Ginkgo ran 1 suite in 4m30.644290494s Test Suite Passed