cp ododevapispec.yaml pkg/apiserver-impl/swagger-ui/swagger.yaml
go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=8252c1fed" ./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: 1701428129 - will randomize all specs

Will run 504 of 956 specs
Running in parallel across 16 processes
SSSSSSSSSSSSSSSSSSSSSS
------------------------------
S [18.037 seconds]
odo devfile deploy command tests deploying devfile with exec [It] should not set securitycontext for podsecurity admission on job's pod template
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:601

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43147"
  << Captured StdOut/StdErr Output

  [SKIPPED] This is a Kubernetes specific scenario, skipping
  In [It] at: /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:603 @ 12/01/23 10:56:52.306
------------------------------
S [18.326 seconds]
odo dev command tests when Starting a PostgreSQL service [BeforeEach] when creating local files and dir and running odo dev - with metadata.name should correctly propagate changes to the container
  [BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:1815
  [It] /go/odo_1/tests/integration/cmd_dev_test.go:1865

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33937"
  << Captured StdOut/StdErr Output

  [SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:1818 @ 12/01/23 10:56:51.77
------------------------------
• [18.777 seconds]
odo deploy interactive command tests directory is not empty when there is a match from Alizer should display welcoming messages first
/go/odo_1/tests/integration/interactive_deploy_test.go:109

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:32835"
  Spawning '/go/bin/odo deploy' from /tmp/2135093525
  << Captured StdOut/StdErr Output
------------------------------
• [20.849 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an Image component with a build context should build image via Docker if build context references PROJECT_SOURCE env var
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:326

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40453"
  << Captured StdOut/StdErr Output
------------------------------
• [20.283 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when an env.yaml file contains a non-current Project when running odo deploy should succeed
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:201

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38747"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [23.089 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=true --running-in=deploy should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34997"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [7.798 seconds]
odo devfile build-images command tests when using a Devfile with variable image names should build images with --var (push=true)
/go/odo_1/tests/integration/cmd_devfile_build_images_test.go:437

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36133"
  << Captured StdOut/StdErr Output
------------------------------
• [5.825 seconds]
odo dev command tests when a component is bootstrapped should fail when using --no-commands and --build-command and/or --run-command together
/go/odo_1/tests/integration/cmd_dev_test.go:233

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37945"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [7.016 seconds]
odo create/delete/list/set namespace/project tests create project should fail to create project
/go/odo_1/tests/integration/cmd_namespace_test.go:63

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41651"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [33.541 seconds]
odo create/delete/list/set namespace/project tests delete project when force-deleting a valid project should successfully delete the project synchronously with --wait
/go/odo_1/tests/integration/cmd_namespace_test.go:115

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44079"
  << Captured StdOut/StdErr Output
------------------------------
• [9.234 seconds]
odo create/delete/list/set namespace/project tests set project should not succeed to set the project
/go/odo_1/tests/integration/cmd_namespace_test.go:162

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45663"
  << Captured StdOut/StdErr Output
------------------------------
• [39.769 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="dev") when odo delete command is run again with nothing deployed on the cluster should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:151

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40759"
  << Captured StdOut/StdErr Output
------------------------------
• [6.005 seconds]
odo dev command with api server tests when the component is bootstrapped should fail if --api-server is false but --api-server-port is true
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:46

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43005"
  << Captured StdOut/StdErr Output
------------------------------
S [4.862 seconds]
odo init interactive command tests when DevfileRegistriesList CRD is installed on cluster [BeforeEach] when CR for devfileregistrieslists is installed in namespace should download correct devfile from the first in-cluster registry
  [BeforeEach] /go/odo_1/tests/integration/interactive_init_test.go:708
  [It] /go/odo_1/tests/integration/interactive_init_test.go:737

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44595"
  << Captured StdOut/StdErr Output

  [SKIPPED] skipped on non Kubernetes clusters
  In [BeforeEach] at: /go/odo_1/tests/integration/interactive_init_test.go:710 @ 12/01/23 10:57:25.342
------------------------------
SSSS
------------------------------
• [48.970 seconds]
odo delete command tests when deleting a component containing preStop event that is deployed with DEV and --files=true should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:517

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35759"
  << Captured StdOut/StdErr Output
------------------------------
•S
------------------------------
• [49.511 seconds]
odo dev command tests when running odo dev --no-watch and build command throws an error should error out with some log
/go/odo_1/tests/integration/cmd_dev_test.go:2898

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40091"
  << Captured StdOut/StdErr Output
------------------------------
• [52.852 seconds]
odo devfile deploy command tests deploying devfile with exec when the deploy command terminates abruptly; component name of a normal character length when odo deploy command is run again should run successfully
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:595

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42587"
  << Captured StdOut/StdErr Output
------------------------------
• [71.672 seconds]
odo dev command tests when odo dev is executed to run a devfile containing a k8s resource should have created the necessary k8s resources
/go/odo_1/tests/integration/cmd_dev_test.go:1127

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36145"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [72.131 seconds]
odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted using its name and namespace from another directory should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:473

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35525"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [77.301 seconds]
odo dev command tests 1. devfile contains composite apply command the devfile contains an image component that uses a remote Dockerfile when [PODMAN_CMD=echo] remote server returns a valid file when odo dev is run should build and push image when odo dev is run
/go/odo_1/tests/integration/cmd_dev_test.go:2526

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42007"
  << Captured StdOut/StdErr Output
------------------------------
• [62.126 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted using its name and namespace from another directory should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:473

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42133"
  << Captured StdOut/StdErr Output
------------------------------
• [81.614 seconds]
odo dev command tests when creating local files and dir and running odo dev - without metadata.name should correctly propagate changes to the container
/go/odo_1/tests/integration/cmd_dev_test.go:1788

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40983"
  << Captured StdOut/StdErr Output
------------------------------
• [87.913 seconds]
odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=false, customPortForwarding=false, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1463

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36731"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [48.606 seconds]
odo dev command tests 1. devfile contains composite apply command the devfile contains an image component that uses a remote Dockerfile when [PODMAN_CMD=a-command-not-found-for-podman-should-make-odo-fallback-to-docker DOCKER_CMD=echo] remote server returns an error when odo dev is run should not build images when odo dev is run
/go/odo_1/tests/integration/cmd_dev_test.go:2549

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46849"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [89.025 seconds]
odo dev command tests when a component is bootstrapped when odo is executed with --no-watch flag and with --no-commands=false when a file in component directory is modified when p is pressed should trigger a push
/go/odo_1/tests/integration/cmd_dev_test.go:754

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44737"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [59.890 seconds]
odo describe component command tests when creating a component when running odo dev (podman=false,debug=false) JSON output when switching to another directory when describing the component from another directory should describe the named component
/go/odo_1/tests/integration/cmd_describe_component_test.go:477

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46143"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [5.469 seconds]
odo create/delete/list/set namespace/project tests set project when running inside a component directory should set the project
/go/odo_1/tests/integration/cmd_namespace_test.go:190

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34039"
  << Captured StdOut/StdErr Output
------------------------------
• [99.293 seconds]
odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=true, customPortForwarding=true, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1463

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42123"
  << Captured StdOut/StdErr Output
------------------------------
• [72.924 seconds]
odo dev debug command tests when running build and debug commands as composite in different containers and a shared volume - with metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_debug_test.go:388

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40977"
  << Captured StdOut/StdErr Output
------------------------------
• [15.578 seconds]
odo create/delete/list/set namespace/project tests delete namespace when force-deleting a valid namespace should successfully delete the namespace synchronously with --wait
/go/odo_1/tests/integration/cmd_namespace_test.go:115

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40799"
  << Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [40.313 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="") should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:128

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36753"
  << Captured StdOut/StdErr Output
------------------------------
• [64.088 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="deploy") when odo delete command is run again with nothing deployed on the cluster should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:151

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33727"
  << Captured StdOut/StdErr Output
------------------------------
• [6.541 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted using its name and namespace from another directory should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:237

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35159"
  << Captured StdOut/StdErr Output
------------------------------
• [8.723 seconds]
odo create/delete/list/set namespace/project tests create namespace should successfully create the namespace
/go/odo_1/tests/integration/cmd_namespace_test.go:54

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37527"
  << Captured StdOut/StdErr Output
------------------------------
• [28.814 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped the component is deleted while having access to the devfile.yaml when the component is deleted with --files should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:178

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35845"
  << Captured StdOut/StdErr Output
------------------------------
• [15.431 seconds]
odo devfile deploy command tests deploying devfile with exec when using devfile where the exec command is bound to fail should print the last 100 lines of the log to the output
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:648

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39991"
  << Captured StdOut/StdErr Output
------------------------------
• [58.792 seconds]
odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag (custom api server port=false) should start the Dev server when --api-server flag is passed
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:98

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34521"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [110.779 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=true, customPortForwarding=true, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1379

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42209"
  << Captured StdOut/StdErr Output
------------------------------
• [58.191 seconds]
odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag (custom api server port=true) should describe the API Server port (JSON)
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:123

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42963"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [56.973 seconds]
odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag (custom api server port=true) should describe the API Server port
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:108

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46173"
  << Captured StdOut/StdErr Output
------------------------------
• [71.867 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=false, customPortForwarding=true, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1338

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35987"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [57.716 seconds]
odo dev command tests when running odo dev with alternative commands - with metadata.name when running odo dev with a build command should execute the default build command successfully if specified explicitly
/go/odo_1/tests/integration/cmd_dev_test.go:3126

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45735"
  << Captured StdOut/StdErr Output
------------------------------
• [27.979 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="") when odo delete command is run again with nothing deployed on the cluster should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:151

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39227"
  << Captured StdOut/StdErr Output
------------------------------
• [5.870 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=false --running-in=dev should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46813"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [119.094 seconds]
odo describe component command tests checking for remote source code location when using devfile with sourceMapping and starting an odo dev session should show remote source code location in odo describe component output
/go/odo_1/tests/integration/cmd_describe_component_test.go:642

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42051"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [5.410 seconds]
odo create/delete/list/set namespace/project tests set namespace when running inside a component directory should set the namespace
/go/odo_1/tests/integration/cmd_namespace_test.go:190

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43013"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [4.229 seconds]
odo logs command tests when directory is empty should error
/go/odo_1/tests/integration/cmd_logs_test.go:86

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44313"
  << Captured StdOut/StdErr Output
------------------------------
• [86.159 seconds]
odo dev command tests 1. devfile contains composite apply command when odo dev is running with both image build and container run extra args should execute the composite apply commands successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2388

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38007"
  << Captured StdOut/StdErr Output
------------------------------
S [4.517 seconds]
odo devfile registry command tests when DevfileRegistriesList CRD is installed on cluster [BeforeEach] when CR for devfileregistrieslists is installed in namespace should list detailed information regarding nodejs when using an in-cluster registry
  [BeforeEach] /go/odo_1/tests/integration/cmd_devfile_registry_test.go:212
  [It] /go/odo_1/tests/integration/cmd_devfile_registry_test.go:240

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45553"
  << Captured StdOut/StdErr Output

  [SKIPPED] skipped on non Kubernetes clusters
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_devfile_registry_test.go:214 @ 12/01/23 10:59:31.314
------------------------------
• [58.326 seconds]
odo describe component command tests when creating a component when running odo dev (podman=false,debug=false) JSON output when describing the component in dev mode should describe the component
/go/odo_1/tests/integration/cmd_describe_component_test.go:416

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40811"
  << Captured StdOut/StdErr Output
------------------------------
• [58.901 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=true, customPortForwarding=true, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1338

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34663"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [25.859 seconds]
odo dev command tests when running odo dev with alternative commands - with metadata.name when running odo dev with a run command should error out on an invalid command
/go/odo_1/tests/integration/cmd_dev_test.go:3150

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34869"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [57.148 seconds]
odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag (custom api server port=true) should start the Dev server when --api-server flag is passed
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:98

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42861"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [107.840 seconds]
odo dev command tests when hotReload capable Build and Run commands are used with odo dev when a source file is modified should not re-execute the run command
/go/odo_1/tests/integration/cmd_dev_test.go:3834

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33153"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [120.396 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=false, customPortForwarding=false, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1379

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39723"
  << Captured StdOut/StdErr Output
------------------------------
• [7.121 seconds]
odo devfile deploy command tests when using a devfile.yaml containing a deploy command when an env.yaml file contains a non-current Project when running odo deploy when the env.yaml file still contains a non-current Project should delete the component in the current namespace
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:226

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36339"
  << Captured StdOut/StdErr Output
------------------------------
• [91.023 seconds]
odo list with devfile devfile has missing metadata when projectType and language is missing when the component is pushed should show 'nodejs' for 'Type' in odo list
/go/odo_1/tests/integration/cmd_devfile_list_test.go:363

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41179"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [15.542 seconds]
odo create/delete/list/set namespace/project tests delete namespace when force-deleting a valid namespace should successfully delete the namespace asynchronously
/go/odo_1/tests/integration/cmd_namespace_test.go:107

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:32779"
  << Captured StdOut/StdErr Output
------------------------------
• [10.715 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted using its name and namespace from another directory should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:241

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36055"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [5.887 seconds]
odo run command tests when a component is bootstrapped should fail if odo dev is not running
/go/odo_1/tests/integration/cmd_run_test.go:72

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33863"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [5.272 seconds]
odo dev command tests when running applications listening on the container loopback interface should error out if using --ignore-localhost on any platform other than Podman
/go/odo_1/tests/integration/cmd_dev_test.go:4211

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41597"
  << Captured StdOut/StdErr Output
------------------------------
• [119.991 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when running odo deploy when running and stopping odo dev should not delete the resources created with odo deploy
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:176

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44547"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [88.300 seconds]
odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=true, customPortForwarding=false, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1463

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40539"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [85.593 seconds]
odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy with image build extra args should run odo dev successfully
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:161

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43505"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [57.616 seconds]
odo dev command tests when running odo dev with alternative commands - with metadata.name when running odo dev with a run command should execute the default run command successfully if specified explicitly
/go/odo_1/tests/integration/cmd_dev_test.go:3195

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33659"
  << Captured StdOut/StdErr Output
------------------------------
• [62.168 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38949"
  << Captured StdOut/StdErr Output
------------------------------
SSSSSSSSS
------------------------------
• [58.359 seconds]
odo dev command tests when Devfile 2.1.0 is used - with metadata.name when doing odo dev with --var-file flag should check if the env variable has a correct value
/go/odo_1/tests/integration/cmd_dev_test.go:1639

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36637"
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [60.354 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped the component is deleted while having access to the devfile.yaml when the component is deleted with --files should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:178

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36053"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [7.370 seconds]
odo devfile deploy command tests when deploying a Devfile OpenShift component with multiple K8s resources defined should have created all the resources defined in the Devfile OpenShift component
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:372

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41693"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [132.160 seconds]
odo dev command tests when running odo dev and composite command is used as a run command - without metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2709

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34221"
  << Captured StdOut/StdErr Output
------------------------------
• [7.947 seconds]
odo list with devfile listing non-odo managed components when a non-odo managed component is deployed should list the component with odo list
/go/odo_1/tests/integration/cmd_devfile_list_test.go:43

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37673"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [117.842 seconds]
odo dev command tests when running odo dev and run command throws an error should error out with some log
/go/odo_1/tests/integration/cmd_dev_test.go:2858

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40599"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [59.882 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=false, customPortForwarding=false, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1338

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38633"
  << Captured StdOut/StdErr Output
------------------------------
• [4.733 seconds]
odo create/delete/list/set namespace/project tests list namespace should successfully list all the namespaces
/go/odo_1/tests/integration/cmd_namespace_test.go:221

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40301"
  << Captured StdOut/StdErr Output
------------------------------
S [3.802 seconds]
odo dev command tests when Starting a PostgreSQL service [BeforeEach] when creating local files and dir and running odo dev - with metadata.name when deleting local files and dir and waiting for sync should not list deleted dir and file in container
  [BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:1815
  [It] /go/odo_1/tests/integration/cmd_dev_test.go:1882

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36343"
  << Captured StdOut/StdErr Output

  [SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:1818 @ 12/01/23 11:00:59.657
------------------------------
• [119.988 seconds]
odo dev command tests when running odo dev and multiple env variables are set - with metadata.name should be able to exec command
/go/odo_1/tests/integration/cmd_dev_test.go:1717

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43513"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [63.802 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="deploy") when odo delete command is run again with nothing deployed on the cluster should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:151

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45651"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [10.141 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted using its name and namespace from another directory should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:241

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44829"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [7.814 seconds]
odo dev command tests when Devfile contains metadata.language invalid as a label value when odo deploy is executed should set the correct value in labels of deployed resources
/go/odo_1/tests/integration/cmd_dev_test.go:4105

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35027"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [48.929 seconds]
odo dev command tests when a component is bootstrapped when odo is executed with --no-watch flag and with --no-commands when a file in component directory is modified should not trigger a push
/go/odo_1/tests/integration/cmd_dev_test.go:736

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39101"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [87.877 seconds]
odo dev command tests 1. devfile contains composite apply command when odo dev is running should execute the composite apply commands successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2388

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43605"
  << Captured StdOut/StdErr Output
------------------------------
• [78.746 seconds]
odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=false, customPortForwarding=false, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1463

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45933"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [4.107 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an Image component with no build context should build image via Docker by defaulting build context to devfile path
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:450

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43223"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [118.783 seconds]
odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy with image build extra args when running and stopping odo dev should not delete the resources created with odo deploy
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:176

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40035"
  << Captured StdOut/StdErr Output
------------------------------
• [8.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 the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41725"
  << Captured StdOut/StdErr Output
------------------------------
• [5.888 seconds]
odo devfile build-images command tests when using a Devfile with variable image names should build images with --var-file (push=false)
/go/odo_1/tests/integration/cmd_devfile_build_images_test.go:445

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44259"
  << Captured StdOut/StdErr Output
------------------------------
• [93.315 seconds]
odo logs command tests when component is created and odo logs is executed when running in Dev mode should successfully show logs of the running component
/go/odo_1/tests/integration/cmd_logs_test.go:140

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34393"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [28.949 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="") should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:128

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43321"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [121.206 seconds]
odo dev command tests when running odo dev and single env var is set - with metadata.name should be able to exec command
/go/odo_1/tests/integration/cmd_dev_test.go:1691

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45141"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [62.287 seconds]
odo dev debug command tests when a component is bootstrapped when running odo dev with debug flag should not add a DEBUG_PORT variable to the container
/go/odo_1/tests/integration/cmd_dev_debug_test.go:124

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41599"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [59.933 seconds]
odo dev command tests when devfile project field is present and running odo dev - without metadata.name should sync to the correct dir in container
/go/odo_1/tests/integration/cmd_dev_test.go:2097

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34111"
  << Captured StdOut/StdErr Output
------------------------------
• [8.558 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39665"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [24.877 seconds]
odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a build command should error out on an invalid command
/go/odo_1/tests/integration/cmd_dev_test.go:3080

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45031"
  << Captured StdOut/StdErr Output
------------------------------
• [4.947 seconds]
odo devfile init command tests setting application ports when running odo init --run-port with a Devfile with no commands should ignore the run ports
/go/odo_1/tests/integration/cmd_devfile_init_test.go:628

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39919"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [93.321 seconds]
odo dev command tests when a component is bootstrapped when odo dev is executed and Ephemeral is set to false when killing odo dev and running odo delete component --wait should have deleted all resources before returning
/go/odo_1/tests/integration/cmd_dev_test.go:577

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45055"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [59.723 seconds]
odo dev command tests when a container component defines a Command or Args - with metadata.name should run odo dev successfully (#5620)
/go/odo_1/tests/integration/cmd_dev_test.go:3538

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44667"
  << Captured StdOut/StdErr Output
------------------------------
SSSSSSS
------------------------------
S [7.701 seconds]
odo preference and config command tests when DevfileRegistriesList CRD is installed on cluster [BeforeEach] when CR for devfileregistrieslists is installed in namespace should fail to delete the in-cluster registry
  [BeforeEach] /go/odo_1/tests/integration/cmd_pref_config_test.go:377
  [It] /go/odo_1/tests/integration/cmd_pref_config_test.go:444

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40639"
  << Captured StdOut/StdErr Output

  [SKIPPED] skipped on non Kubernetes clusters
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_pref_config_test.go:379 @ 12/01/23 11:01:53.697
------------------------------
S
------------------------------
• [10.512 seconds]
odo generic When deleting two project one after the other should be able to delete sequentially
/go/odo_1/tests/integration/generic_test.go:100

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43545"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [58.199 seconds]
odo dev command tests when odo dev is executed to run a devfile containing multiple k8s resource defined under a single Devfile component should have created the necessary k8s resources
/go/odo_1/tests/integration/cmd_dev_test.go:1127

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33291"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [117.345 seconds]
odo logs command tests when component is created and odo logs is executed when running in both Dev and Deploy mode when --follow flag is specified should successfully follow logs of running component
/go/odo_1/tests/integration/cmd_logs_test.go:348

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43887"
  << Captured StdOut/StdErr Output
------------------------------
• [28.994 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="dev") should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:128

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45651"
  << Captured StdOut/StdErr Output
------------------------------
• [86.049 seconds]
odo dev debug command tests when starting with Devfile with autoBuild or deployByDefault components when running odo dev with some components not referenced in the Devfile should create the appropriate resources
/go/odo_1/tests/integration/cmd_dev_debug_test.go:501

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33531"
  << Captured StdOut/StdErr Output
------------------------------
• [6.487 seconds]
odo deploy interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile successfully even with -v flag
/go/odo_1/tests/integration/interactive_deploy_test.go:40

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40001"
  Spawning '/go/bin/odo deploy -v 4' from /tmp/2786355331
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [52.857 seconds]
odo devfile deploy command tests deploying devfile with exec when the deploy command terminates abruptly; component name of at max(63) characters length when odo deploy command is run again should run successfully
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:595

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36461"
  << Captured StdOut/StdErr Output
------------------------------
• [65.161 seconds]
odo dev command tests when running odo dev with alternative commands - without metadata.name should execute the custom non-default build and run commands successfully
/go/odo_1/tests/integration/cmd_dev_test.go:3207

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41709"
  << Captured StdOut/StdErr Output
------------------------------
SSSSSS
------------------------------
• [41.289 seconds]
odo delete command tests when deleting a component containing preStop event that is deployed with DEV and --files=false should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:517

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39829"
  << Captured StdOut/StdErr Output
------------------------------
• [58.376 seconds]
odo dev command tests when a component is bootstrapped when run command takes really long to start should cancel run command and return if odo dev is stopped
/go/odo_1/tests/integration/cmd_dev_test.go:1002

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38921"
  << Captured StdOut/StdErr Output
------------------------------
• [58.522 seconds]
odo dev command tests when Devfile 2.1.0 is used - without metadata.name when doing odo dev 3. should check if the env variable has a correct value
/go/odo_1/tests/integration/cmd_dev_test.go:1589

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37989"
  << Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [129.383 seconds]
odo dev command tests when java-springboot application is created and running odo dev when Update the devfile.yaml when compare the local and remote files localFiles and remoteFiles should match
/go/odo_1/tests/integration/cmd_dev_test.go:3324

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38083"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [10.060 seconds]
odo list with devfile listing non-odo managed components when a non-odo managed component without the managed-by label is deployed should list the component in JSON
/go/odo_1/tests/integration/cmd_devfile_list_test.go:71

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38221"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [4.723 seconds]
odo devfile deploy command tests when using a devfile.yaml containing a deploy command when an env.yaml file contains a non-current Project when running odo deploy should succeed
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:201

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34803"
  << Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [59.872 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=true, customPortForwarding=true, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1338

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37193"
  << Captured StdOut/StdErr Output
------------------------------
• [6.513 seconds]
odo dev command tests when Devfile contains metadata.projectType invalid as a label value when odo deploy is executed should set the correct value in labels of deployed resources
/go/odo_1/tests/integration/cmd_dev_test.go:4105

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36943"
  << Captured StdOut/StdErr Output
------------------------------
• [4.256 seconds]
odo dev command tests when running odo dev and prestart events are defined should not correctly execute PreStart commands
/go/odo_1/tests/integration/cmd_dev_test.go:2823

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45645"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [58.486 seconds]
odo dev command tests when a component with multiple endpoints is run when odo dev is stopped should remove forwarded ports from state file
/go/odo_1/tests/integration/cmd_dev_test.go:3583

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42927"
  << Captured StdOut/StdErr Output
------------------------------
• [8.482 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37803"
  << Captured StdOut/StdErr Output
------------------------------
• [91.205 seconds]
odo dev command tests when adding local files to gitignore and running odo dev when modifying /testdir/baz.txt file should synchronize it only
/go/odo_1/tests/integration/cmd_dev_test.go:1965

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46327"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [11.513 seconds]
odo devfile deploy command tests deploying devfile with exec when using devfile that works; with component name of at max(63) characters length should complete the command execution successfully
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:576

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42993"
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [60.836 seconds]
odo dev command tests when Devfile contains neither metadata.language nor metadata.projectType when running odo dev should set the correct value in labels of resources
/go/odo_1/tests/integration/cmd_dev_test.go:4089

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33449"
  << Captured StdOut/StdErr Output
------------------------------
• [124.241 seconds]
odo dev command tests Devfile with no metadata.name when running odo dev against a component with no source code should use the directory as component name
/go/odo_1/tests/integration/cmd_dev_test.go:3873

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39165"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [49.665 seconds]
odo dev command tests when running odo dev and build command throws an error should error out with some log
/go/odo_1/tests/integration/cmd_dev_test.go:2898

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36255"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [60.531 seconds]
odo dev command tests when Devfile contains metadata.language when running odo dev should set the correct value in labels of resources
/go/odo_1/tests/integration/cmd_dev_test.go:4089

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37011"
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [9.735 seconds]
odo describe component command tests should fail, with cluster
/go/odo_1/tests/integration/cmd_describe_component_test.go:89

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40019"
  << Captured StdOut/StdErr Output
------------------------------
• [8.161 seconds]
odo dev command tests when directory is empty should error
/go/odo_1/tests/integration/cmd_dev_test.go:64

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41287"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [40.467 seconds]
odo dev command tests image names as selectors when starting with a Devfile with relative and absolute image names and Kubernetes resources when adding a local registry for images when running odo dev should treat relative image names as selectors
/go/odo_1/tests/integration/cmd_dev_test.go:4756

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42311"
  << Captured StdOut/StdErr Output
------------------------------
• [7.294 seconds]
odo dev command tests when Devfile contains neither metadata.language nor metadata.projectType when odo deploy is executed should set the correct value in labels of deployed resources
/go/odo_1/tests/integration/cmd_dev_test.go:4105

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41029"
  << Captured StdOut/StdErr Output
------------------------------
SSSSSS
------------------------------
• [7.218 seconds]
odo create/delete/list/set namespace/project tests delete namespace should not succeed to delete a non-existent namespace
/go/odo_1/tests/integration/cmd_namespace_test.go:122

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44219"
  << Captured StdOut/StdErr Output
------------------------------
• [62.013 seconds]
odo dev command tests when project and clonePath is present in devfile and running odo dev - without metadata.name should sync to the correct dir in container
/go/odo_1/tests/integration/cmd_dev_test.go:2058

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36531"
  << Captured StdOut/StdErr Output
------------------------------
S [5.902 seconds]
odo devfile deploy command tests deploying devfile with exec [It] should not set securitycontext for podsecurity admission on job's pod template
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:601

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43225"
  << Captured StdOut/StdErr Output

  [SKIPPED] This is a Kubernetes specific scenario, skipping
  In [It] at: /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:603 @ 12/01/23 11:03:23.484
------------------------------
• [58.818 seconds]
odo describe component command tests when creating a component when running odo dev (podman=false,debug=false) Default output when switching to another directory when describing the component from another directory should describe the named component
/go/odo_1/tests/integration/cmd_describe_component_test.go:389

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40547"
  << Captured StdOut/StdErr Output
------------------------------
• [3.921 seconds]
odo dev command tests when running applications listening on the container loopback interface should error out if using --ignore-localhost on any platform other than Podman
/go/odo_1/tests/integration/cmd_dev_test.go:4211

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40347"
  << Captured StdOut/StdErr Output
------------------------------
• [61.919 seconds]
odo dev command tests when creating local files and dir and running odo dev - with metadata.name should correctly propagate changes to the container
/go/odo_1/tests/integration/cmd_dev_test.go:1788

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35951"
  << Captured StdOut/StdErr Output
------------------------------
• [5.422 seconds]
odo create/delete/list/set namespace/project tests list project should successfully list all the projects in JSON format
/go/odo_1/tests/integration/cmd_namespace_test.go:228

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40287"
  << Captured StdOut/StdErr Output
------------------------------
• [27.439 seconds]
odo dev command tests when a component is bootstrapped should start on cluster even if Podman client takes long to initialize
/go/odo_1/tests/integration/cmd_dev_test.go:91

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41483"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [81.230 seconds]
odo dev interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile
/go/odo_1/tests/integration/interactive_dev_test.go:76

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43261"
  Spawning '/go/bin/odo dev --random-ports' from /tmp/3019699522
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [5.830 seconds]
odo list with devfile listing non-odo managed components when an operator managed deployment(without instance and managed-by label) is deployed should not be listed in the odo list output
/go/odo_1/tests/integration/cmd_devfile_list_test.go:88

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38755"
  << Captured StdOut/StdErr Output
------------------------------
• [124.825 seconds]
odo dev command tests when doing odo dev and there is a env variable with spaces - without metadata.name should be able to exec command
/go/odo_1/tests/integration/cmd_dev_test.go:1743

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43725"
  << Captured StdOut/StdErr Output
------------------------------
• [60.838 seconds]
odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41355"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [79.500 seconds]
odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=false, customPortForwarding=true, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1463

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41959"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [8.152 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted using its name and namespace from another directory should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:237

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36557"
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [55.851 seconds]
odo dev command tests when a component is bootstrapped when running with --no-commands (debug=false) should start the dev session
/go/odo_1/tests/integration/cmd_dev_test.go:268

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41811"
  << Captured StdOut/StdErr Output
------------------------------
• [6.503 seconds]
odo devfile deploy command tests using a Devfile with an image component using a remote Dockerfile when remote server returns an error should not build images
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:502

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45455"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [10.539 seconds]
odo describe component command tests when creating a component when running odo deploy to create ingress/routes should show the ingress with defaultBackend in odo describe component output
/go/odo_1/tests/integration/cmd_describe_component_test.go:552

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35891"
  << Captured StdOut/StdErr Output
------------------------------
• [20.255 seconds]
odo create/delete/list/set namespace/project tests delete project when force-deleting a valid project should successfully delete the project asynchronously
/go/odo_1/tests/integration/cmd_namespace_test.go:107

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40177"
  << Captured StdOut/StdErr Output
------------------------------
• [69.380 seconds]
odo dev command tests when adding local files to gitignore and running odo dev when modifying /testdir/foobar.txt file should not synchronize it
/go/odo_1/tests/integration/cmd_dev_test.go:1987

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43823"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [50.385 seconds]
odo dev command tests when using a Devfile with no commands should start the Dev Session with --no-commands=true
/go/odo_1/tests/integration/cmd_dev_test.go:4921

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39773"
  << Captured StdOut/StdErr Output
------------------------------
• [122.925 seconds]
odo dev debug command tests when creating nodejs component, doing odo dev and run command has dev.odo.push.path attribute should sync only the mentioned files at the appropriate remote destination
/go/odo_1/tests/integration/cmd_dev_debug_test.go:163

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40165"
  << Captured StdOut/StdErr Output
------------------------------
• [13.433 seconds]
odo dev interactive command tests directory is not empty when Alizer cannot determine a Devfile based on the current source code should not fail but fallback to the interactive mode
/go/odo_1/tests/integration/interactive_dev_test.go:164

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33715"
  Spawning '/go/bin/odo dev --random-ports' from /tmp/1508527031
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [79.226 seconds]
odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=true, customPortForwarding=false, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1463

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37837"
  << Captured StdOut/StdErr Output
------------------------------
• [28.858 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="dev") should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:128

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35051"
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [7.102 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=false --running-in=deploy should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38685"
  << Captured StdOut/StdErr Output
------------------------------
S [4.191 seconds]
odo preference and config command tests when DevfileRegistriesList CRD is installed on cluster [BeforeEach] when CR for devfileregistrieslists is installed in namespace registry list should return registry listed in CR
  [BeforeEach] /go/odo_1/tests/integration/cmd_pref_config_test.go:377
  [It] /go/odo_1/tests/integration/cmd_pref_config_test.go:414

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38585"
  << Captured StdOut/StdErr Output

  [SKIPPED] skipped on non Kubernetes clusters
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_pref_config_test.go:379 @ 12/01/23 11:04:33.58
------------------------------
SS
------------------------------
• [7.158 seconds]
odo devfile deploy command tests using a Devfile with an image component using a remote Dockerfile when remote server returns a valid file should run odo deploy
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:538

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40421"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [4.701 seconds]
odo devfile deploy command tests deploying devfile with exec when using a devfile name with length more than 63 should fail with invalid component name error
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:622

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42131"
  << Captured StdOut/StdErr Output
------------------------------
• [61.198 seconds]
odo dev command tests when no project is present - with metadata.name should sync to the correct dir in container
/go/odo_1/tests/integration/cmd_dev_test.go:2164

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41629"
  << Captured StdOut/StdErr Output
------------------------------
• [100.153 seconds]
odo dev command tests when a component is bootstrapped ensure that index information is updated
/go/odo_1/tests/integration/cmd_dev_test.go:305

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:32997"
  << Captured StdOut/StdErr Output
------------------------------
• [60.273 seconds]
odo dev command tests when Devfile contains metadata.projectType invalid as a label value when running odo dev should set the correct value in labels of resources
/go/odo_1/tests/integration/cmd_dev_test.go:4089

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45055"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [112.377 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=true, customPortForwarding=false, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1379

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37861"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [6.319 seconds]
odo create/delete/list/set namespace/project tests set namespace should successfully set the namespace
/go/odo_1/tests/integration/cmd_namespace_test.go:147

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38435"
  << Captured StdOut/StdErr Output
------------------------------
• [26.175 seconds]
odo dev command tests when running odo dev with alternative commands - with metadata.name when running odo dev with a build command should error out on an invalid command
/go/odo_1/tests/integration/cmd_dev_test.go:3080

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43749"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [6.101 seconds]
odo create/delete/list/set namespace/project tests list project should successfully list all the projects
/go/odo_1/tests/integration/cmd_namespace_test.go:221

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41571"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [6.787 seconds]
odo deploy interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile
/go/odo_1/tests/integration/interactive_deploy_test.go:75

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40171"
  Spawning '/go/bin/odo deploy' from /tmp/1130463407
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [4.276 seconds]
odo dev command with api server tests when the component is bootstrapped should fail if --random-ports and --api-server-port are used together
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:63

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45679"
  << Captured StdOut/StdErr Output
------------------------------
• [3.709 seconds]
odo devfile build-images command tests when starting with Devfile with autoBuild or deployByDefault components when building images should build all Image components regardless of autoBuild
/go/odo_1/tests/integration/cmd_devfile_build_images_test.go:364

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41121"
  << Captured StdOut/StdErr Output
------------------------------
• [57.757 seconds]
odo dev command tests when a component with multiple endpoints is run should create state files containing information, including forwarded ports
/go/odo_1/tests/integration/cmd_dev_test.go:3622

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44199"
  PID: 28660
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [60.920 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39919"
  << Captured StdOut/StdErr Output
------------------------------
• [121.182 seconds]
odo dev command tests when running odo dev with devfile contain volume - without metadata.name check the volume name and mount paths for the containers
/go/odo_1/tests/integration/cmd_dev_test.go:2230

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41411"
  << Captured StdOut/StdErr Output
------------------------------
• [120.294 seconds]
odo list with devfile when a component created in 'app' application when dev is running on cluster verifying the managedBy Version in the odo list output should show managedBy Version
/go/odo_1/tests/integration/cmd_devfile_list_test.go:181

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43411"
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [29.315 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="") when odo delete command is run again with nothing deployed on the cluster should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:151

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33759"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [59.522 seconds]
odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a build command should execute the default build command successfully if specified explicitly
/go/odo_1/tests/integration/cmd_dev_test.go:3126

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34825"
  << Captured StdOut/StdErr Output
------------------------------
• [60.833 seconds]
odo dev command tests when a component is bootstrapped when odo is executed with --no-watch flag and with --no-commands when a file in component directory is modified when p is pressed should trigger a push
/go/odo_1/tests/integration/cmd_dev_test.go:754

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33129"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [59.875 seconds]
odo dev command tests when a component is bootstrapped when odo dev is executed when odo dev is stopped should delete the component from the platform
/go/odo_1/tests/integration/cmd_dev_test.go:507

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36643"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [98.849 seconds]
odo dev command tests when a component is bootstrapped when odo dev is executed and Ephemeral is set to false when killing odo dev and another process replaces it should restart a new session successfully
/go/odo_1/tests/integration/cmd_dev_test.go:609

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42399"
  << Captured StdOut/StdErr Output
------------------------------
• [110.896 seconds]
odo logs command tests when component is created and odo logs is executed when running in Dev mode when --follow flag is specified should successfully follow logs of running component
/go/odo_1/tests/integration/cmd_logs_test.go:172

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43831"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [29.067 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped the component is deleted while having access to the devfile.yaml when the component is deleted with --files should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:178

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46211"
  << Captured StdOut/StdErr Output
------------------------------
• [28.018 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped the component is deleted while having access to the devfile.yaml when the component is deleted with --files should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:178

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43787"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [8.428 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted using its name and namespace from another directory should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:241

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40763"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [130.250 seconds]
odo dev command tests when running build and run commands as composite in different containers and a shared volume - with metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2772

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43389"
  << Captured StdOut/StdErr Output
------------------------------
• [57.405 seconds]
odo dev command tests when Devfile 2.1.0 is used - without metadata.name when doing odo dev with --var flag should check if the env variable has a correct value
/go/odo_1/tests/integration/cmd_dev_test.go:1612

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38679"
  << Captured StdOut/StdErr Output
------------------------------
• [7.311 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46413"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [57.613 seconds]
odo describe component command tests when creating a component when running odo dev (podman=false,debug=false) Default output when describing the component in dev mode should describe the component
/go/odo_1/tests/integration/cmd_describe_component_test.go:348

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35313"
  << Captured StdOut/StdErr Output
------------------------------
• [81.635 seconds]
odo dev command tests when adding local files to gitignore and running odo dev when modifying /testdir/baz.txt file should synchronize it only
/go/odo_1/tests/integration/cmd_dev_test.go:1965

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44485"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [5.600 seconds]
odo devfile deploy command tests when deploying a Devfile K8s component with multiple K8s resources defined should have created all the resources defined in the Devfile K8s component
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:372

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37819"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [68.924 seconds]
odo dev command tests when running odo dev and composite command are nested - without metadata.name should execute all commands in composite commmand
/go/odo_1/tests/integration/cmd_dev_test.go:2674

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44347"
  << Captured StdOut/StdErr Output
------------------------------
• [59.042 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted using its name and namespace from another directory should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:473

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42515"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [32.337 seconds]
odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38423"
  << Captured StdOut/StdErr Output
------------------------------
• [12.444 seconds]
odo generic When deleting two project one after the other should be able to delete them in any order
/go/odo_1/tests/integration/generic_test.go:107

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39097"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [53.706 seconds]
odo dev command tests when a component is bootstrapped when running with --no-commands (debug=true) should start the dev session
/go/odo_1/tests/integration/cmd_dev_test.go:268

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43271"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [26.860 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped the component is deleted while having access to the devfile.yaml when the component is deleted with --files should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:178

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42995"
  << Captured StdOut/StdErr Output
------------------------------
• [59.179 seconds]
odo dev command tests port-forwarding for the component when devfile has no endpoint when running odo dev should have no endpoint forwarded (podman=false, manual=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1282

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43387"
  << Captured StdOut/StdErr Output
------------------------------
• [84.679 seconds]
odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy should run odo dev successfully
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:161

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34929"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [59.248 seconds]
odo dev command tests when Devfile contains metadata.projectType when running odo dev should set the correct value in labels of resources
/go/odo_1/tests/integration/cmd_dev_test.go:4089

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42607"
  << Captured StdOut/StdErr Output
------------------------------
• [4.702 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when running odo deploy should succeed
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:143

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37301"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [122.699 seconds]
odo list with devfile when a component created in 'app' application when dev is running on cluster should display platform
/go/odo_1/tests/integration/cmd_devfile_list_test.go:150

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40953"
  << Captured StdOut/StdErr Output
------------------------------
• [140.947 seconds]
odo dev command tests when java-springboot application is created and running odo dev when Update the devfile.yaml Should build the application successfully
/go/odo_1/tests/integration/cmd_dev_test.go:3269

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35795"
  << Captured StdOut/StdErr Output
------------------------------
• [59.408 seconds]
odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag (custom api server port=false) should describe the API Server port
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:108

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41901"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [81.406 seconds]
odo list with devfile devfile has missing metadata when projectType is missing when the component is pushed in dev mode should show the language for 'Type' in odo list
/go/odo_1/tests/integration/cmd_devfile_list_test.go:334

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39337"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [8.064 seconds]
odo generic executing odo version command when executing the complete command with server info should show the version of odo major components including server login URL
/go/odo_1/tests/integration/generic_test.go:132

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46833"
  << Captured StdOut/StdErr Output
------------------------------
• [61.423 seconds]
odo dev command tests when a container component defines a Command or Args - without metadata.name should run odo dev successfully (#5620)
/go/odo_1/tests/integration/cmd_dev_test.go:3538

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46645"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [71.975 seconds]
odo devfile deploy command tests deploying devfile with exec when using devfile with a long running command in exec should print the tip to run odo logs after 1 minute of execution
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:636

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45821"
  << Captured StdOut/StdErr Output
------------------------------
• [58.063 seconds]
odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a run command should execute the default run command successfully if specified explicitly
/go/odo_1/tests/integration/cmd_dev_test.go:3195

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35827"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [63.899 seconds]
odo run command tests when a component is bootstrapped when odo dev is executed with --no-commands=false and ready should execute commands
/go/odo_1/tests/integration/cmd_run_test.go:100

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34573"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [57.845 seconds]
odo dev command tests port-forwarding for the component when devfile has no endpoint when running odo dev should have no endpoint forwarded (podman=false, manual=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1282

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33915"
  << Captured StdOut/StdErr Output
------------------------------
S [4.558 seconds]
odo dev command tests when a component is bootstrapped when pod security is enforced as restricted [It] should set securitycontext for podsecurity admission
/go/odo_1/tests/integration/cmd_dev_test.go:414

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33617"
  << Captured StdOut/StdErr Output

  [SKIPPED] This is a Kubernetes specific scenario, skipping
  In [It] at: /go/odo_1/tests/integration/cmd_dev_test.go:416 @ 12/01/23 11:07:27.743
------------------------------
SSS
------------------------------
• [10.544 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43951"
  << Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [26.658 seconds]
odo dev command tests when a component is bootstrapped when an env.yaml file contains a non-current Project when odo dev is executed should not have modified env.yaml, and use current namespace
/go/odo_1/tests/integration/cmd_dev_test.go:547

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40781"
  << Captured StdOut/StdErr Output
------------------------------
• [57.876 seconds]
odo dev command tests when a component is bootstrapped when odo dev is executed and Ephemeral is set to false should have created resources
/go/odo_1/tests/integration/cmd_dev_test.go:668

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42455"
  << Captured StdOut/StdErr Output
------------------------------
• [7.542 seconds]
odo create/delete/list/set namespace/project tests list namespace should successfully list all the namespaces in JSON format
/go/odo_1/tests/integration/cmd_namespace_test.go:228

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45605"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [8.883 seconds]
odo create/delete/list/set namespace/project tests delete project should not succeed to delete a non-existent project
/go/odo_1/tests/integration/cmd_namespace_test.go:122

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43799"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [246.776 seconds]
odo dev command tests when node-js application is created and deployed with devfile schema 2.2.0 when Update the devfile.yaml, and waiting synchronization should check cpuLimit, cpuRequests, memoryRequests after restart
/go/odo_1/tests/integration/cmd_dev_test.go:3391

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35427"
  << Captured StdOut/StdErr Output
------------------------------
• [32.958 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45319"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [7.476 seconds]
odo devfile build-images command tests when using a Devfile with variable image names should build images with --var (push=false)
/go/odo_1/tests/integration/cmd_devfile_build_images_test.go:437

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42533"
  << Captured StdOut/StdErr Output
------------------------------
• [89.859 seconds]
odo dev command tests 1. devfile contains composite apply command when odo dev is running with container backend global extra args should execute the composite apply commands successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2388

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43597"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [32.335 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted using its name and namespace from another directory should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:473

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37169"
  << Captured StdOut/StdErr Output
------------------------------
• [92.852 seconds]
odo logs command tests when component is created and odo logs is executed when logs --follow is started when running in Dev mode should successfully follow logs of running component
/go/odo_1/tests/integration/cmd_logs_test.go:219

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42861"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [5.678 seconds]
odo create/delete/list/set namespace/project tests set project should successfully set the project
/go/odo_1/tests/integration/cmd_namespace_test.go:147

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36009"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [5.450 seconds]
odo dev command tests when running applications listening on the container loopback interface should error out if using --forward-localhost on any platform other than Podman
/go/odo_1/tests/integration/cmd_dev_test.go:4220

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44211"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [62.893 seconds]
odo dev command tests when devfile has sourcemappings and running odo dev - with metadata.name should sync files to the correct location
/go/odo_1/tests/integration/cmd_dev_test.go:2016

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37717"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [111.515 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=false, customPortForwarding=false, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1379

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38141"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [91.305 seconds]
odo dev command tests 1. devfile contains composite apply command when odo dev is running with image build extra args should execute the composite apply commands successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2388

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42331"
  << Captured StdOut/StdErr Output
------------------------------
SSSSSS
------------------------------
• [61.400 seconds]
odo dev command tests when a component is bootstrapped when odo is executed with --no-watch flag and with --no-commands=false when a file in component directory is modified should not trigger a push
/go/odo_1/tests/integration/cmd_dev_test.go:736

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39551"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [88.095 seconds]
odo dev command tests 1. devfile contains composite apply command when odo dev is running with container run extra args should execute the composite apply commands successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2388

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35297"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [3.783 seconds]
odo devfile deploy command tests Devfile with autoBuild or deployByDefault components when starting with Devfile with no Deploy command should fail to run odo deploy
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:880

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44569"
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [7.439 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34855"
  << Captured StdOut/StdErr Output
------------------------------
• [79.470 seconds]
odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=false, customPortForwarding=true, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1463

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36149"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [73.446 seconds]
odo dev command tests when running odo dev with alternative commands - with metadata.name should execute the custom non-default build and run commands successfully
/go/odo_1/tests/integration/cmd_dev_test.go:3207

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40903"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [108.308 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=false, customPortForwarding=true, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1379

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35977"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [127.270 seconds]
odo dev command tests when running build and run commands as composite in different containers and a shared volume - without metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2772

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44323"
  << Captured StdOut/StdErr Output
------------------------------
• [86.006 seconds]
odo dev command tests when starting with Devfile with autoBuild or deployByDefault components when running odo dev with some components not referenced in the Devfile should create the appropriate resources
/go/odo_1/tests/integration/cmd_dev_test.go:4466

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45561"
  << Captured StdOut/StdErr Output
------------------------------
• [119.542 seconds]
odo dev command tests when node-js application is created and deployed with devfile schema 2.2.0 should check memory Request and Limit
/go/odo_1/tests/integration/cmd_dev_test.go:3375

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46483"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [69.033 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=true, customPortForwarding=false, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1338

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45629"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [117.711 seconds]
odo dev command tests when a hotReload capable Run command is used with odo dev when a source file is modified should not re-execute the run command
/go/odo_1/tests/integration/cmd_dev_test.go:3787

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37847"
  << Captured StdOut/StdErr Output
------------------------------
SSSSSS
------------------------------
• [7.770 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=true --running-in=deploy should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33487"
  << Captured StdOut/StdErr Output
------------------------------
• [110.795 seconds]
odo dev command tests when a hotReload capable Run command is used with odo dev should execute the build and run commands
/go/odo_1/tests/integration/cmd_dev_test.go:3771

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42413"
  << Captured StdOut/StdErr Output
------------------------------
• [8.070 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=true --running-in=dev should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34057"
  << Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [78.711 seconds]
odo dev command tests when adding local files to gitignore and running odo dev when modifying /foobar.txt file should not synchronize it
/go/odo_1/tests/integration/cmd_dev_test.go:1977

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42169"
  << Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [28.931 seconds]
odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36051"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [7.554 seconds]
odo create/delete/list/set namespace/project tests when namespace is created with -w should list the new namespace when listing namespace
/go/odo_1/tests/integration/cmd_namespace_test.go:41

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44979"
  << Captured StdOut/StdErr Output
------------------------------
• [4.908 seconds]
odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy with image build extra args should succeed
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:143

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41543"
  << Captured StdOut/StdErr Output
------------------------------
• [58.976 seconds]
odo dev command tests when running odo dev and devfile with composite command - with metadata.name should execute all commands in composite command
/go/odo_1/tests/integration/cmd_dev_test.go:2610

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36413"
  << Captured StdOut/StdErr Output
------------------------------
• [60.477 seconds]
odo dev command tests when a component is bootstrapped should not sync .git directory
/go/odo_1/tests/integration/cmd_dev_test.go:166

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39767"
  << Captured StdOut/StdErr Output
------------------------------
• [48.706 seconds]
odo dev command tests 1. devfile contains composite apply command the devfile contains an image component that uses a remote Dockerfile when [PODMAN_CMD=echo] remote server returns an error when odo dev is run should not build images when odo dev is run
/go/odo_1/tests/integration/cmd_dev_test.go:2549

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36979"
  << Captured StdOut/StdErr Output
------------------------------
• [119.169 seconds]
odo describe component command tests checking for remote source code location when using devfile with no sourceMapping, defaults to /projects and starting an odo dev session should show remote source code location in odo describe component output
/go/odo_1/tests/integration/cmd_describe_component_test.go:642

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42985"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [25.362 seconds]
odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a run command should error out on an invalid command
/go/odo_1/tests/integration/cmd_dev_test.go:3150

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38233"
  << Captured StdOut/StdErr Output
------------------------------
• [6.975 seconds]
odo deploy interactive command tests directory is not empty when Alizer cannot determine a Devfile based on the current source code should not fail but fallback to the interactive mode
/go/odo_1/tests/integration/interactive_deploy_test.go:159

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43423"
  Spawning '/go/bin/odo deploy' from /tmp/746003141
  << Captured StdOut/StdErr Output
------------------------------
• [108.443 seconds]
odo dev command tests when a component is bootstrapped when a delay is necessary for the component to start and running odo dev should first fail then succeed querying endpoint
/go/odo_1/tests/integration/cmd_dev_test.go:789

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35427"
  << Captured StdOut/StdErr Output
------------------------------
SSSSSS
------------------------------
• [80.075 seconds]
odo dev command tests when a component is bootstrapped when odo is executed with --no-watch flag and without --no-commands when a file in component directory is modified when p is pressed should trigger a push
/go/odo_1/tests/integration/cmd_dev_test.go:754

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40909"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [6.328 seconds]
odo devfile deploy command tests using a Devfile with an image component using a remote Dockerfile when remote server returns a valid file should run odo deploy
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:538

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39733"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [118.818 seconds]
odo dev command tests when doing odo dev and there is a env variable with spaces - with metadata.name should be able to exec command
/go/odo_1/tests/integration/cmd_dev_test.go:1743

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37801"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [4.989 seconds]
odo describe component command tests when creating a component should not describe the component from another directory, with cluster
/go/odo_1/tests/integration/cmd_describe_component_test.go:289

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41867"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [119.520 seconds]
odo dev command tests when running odo dev with devfile contain volume - with metadata.name check the volume name and mount paths for the containers
/go/odo_1/tests/integration/cmd_dev_test.go:2230

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35351"
  << Captured StdOut/StdErr Output
------------------------------
• [76.897 seconds]
odo dev command tests cleanup of resources is not successful when using a Devfile with a Pod failing to delete before the cleanup timeout when odo dev is executed when odo dev is stopped should report that the component could not be deleted
/go/odo_1/tests/integration/cmd_dev_test.go:5007

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41405"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [63.836 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="deploy") should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:124

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41085"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [6.433 seconds]
odo devfile deploy command tests when using a devfile.yaml containing two deploy commands should run odo deploy
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:244

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33327"
  << Captured StdOut/StdErr Output
------------------------------
• [7.478 seconds]
odo describe component command tests should fail, with default cluster mode
/go/odo_1/tests/integration/cmd_describe_component_test.go:70

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35997"
  << Captured StdOut/StdErr Output
------------------------------
• [8.235 seconds]
odo logs command tests when odo logs is executed for a component that's not running in any modes should print that no containers are running
/go/odo_1/tests/integration/cmd_logs_test.go:99

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43273"
  << Captured StdOut/StdErr Output
------------------------------
• [11.768 seconds]
odo describe component command tests when creating a component when running odo deploy to create ingress/routes should show the ingress/routes in odo describe component output
/go/odo_1/tests/integration/cmd_describe_component_test.go:552

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34241"
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [6.370 seconds]
odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy should succeed
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:143

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46769"
  << Captured StdOut/StdErr Output
------------------------------
• [62.014 seconds]
odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37597"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [6.600 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39063"
  << Captured StdOut/StdErr Output
------------------------------
• [60.657 seconds]
odo describe component command tests when creating a component when running odo dev (podman=false,debug=true) Default output when switching to another directory when describing the component from another directory should describe the named component
/go/odo_1/tests/integration/cmd_describe_component_test.go:389

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40281"
  << Captured StdOut/StdErr Output
------------------------------
• [61.606 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44073"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [60.715 seconds]
odo dev command tests when running applications listening on the container loopback interface when running on default cluster platform should port-forward successfully
/go/odo_1/tests/integration/cmd_dev_test.go:4244

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46121"
  << Captured StdOut/StdErr Output
------------------------------
• [5.390 seconds]
odo devfile build-images command tests when using a Devfile with variable image names should build images with default variable values (push=true)
/go/odo_1/tests/integration/cmd_devfile_build_images_test.go:431

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42263"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [9.002 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34793"
  << Captured StdOut/StdErr Output
------------------------------
• [82.244 seconds]
odo dev interactive command tests directory is not empty when there is a match from Alizer should display welcoming messages first
/go/odo_1/tests/integration/interactive_dev_test.go:112

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34981"
  Spawning '/go/bin/odo dev --random-ports' from /tmp/3920793045
  << Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [58.786 seconds]
odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag (custom api server port=false) should describe the API Server port (JSON)
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:123

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39255"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [6.829 seconds]
odo devfile build-images command tests when using a Devfile with variable image names should build images with default variable values (push=false)
/go/odo_1/tests/integration/cmd_devfile_build_images_test.go:431

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44863"
  << Captured StdOut/StdErr Output
------------------------------
• [12.569 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45049"
  << Captured StdOut/StdErr Output
------------------------------
• [5.325 seconds]
odo devfile build-images command tests when starting with Devfile with autoBuild or deployByDefault components when building and pushing images should build and push all Image components regardless of autoBuild
/go/odo_1/tests/integration/cmd_devfile_build_images_test.go:385

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43219"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [6.483 seconds]
odo devfile deploy command tests Devfile with autoBuild or deployByDefault components when starting with Devfile with Deploy commands when running odo deploy with some components not referenced in the Devfile should create the appropriate resources
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:725

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39739"
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [7.072 seconds]
odo describe component command tests when a non-odo application is present on the cluster should describe the component
/go/odo_1/tests/integration/cmd_describe_component_test.go:694

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33423"
  << Captured StdOut/StdErr Output
------------------------------
S [3.776 seconds]
odo dev command tests when Starting a PostgreSQL service [BeforeEach] when creating local files and dir and running odo dev - without metadata.name should correctly propagate changes to the container
  [BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:1815
  [It] /go/odo_1/tests/integration/cmd_dev_test.go:1865

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33239"
  << Captured StdOut/StdErr Output

  [SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:1818 @ 12/01/23 11:11:14.931
------------------------------
• [58.895 seconds]
odo describe component command tests when creating a component when running odo dev (podman=false,debug=true) Default output when describing the component in dev mode should describe the component
/go/odo_1/tests/integration/cmd_describe_component_test.go:348

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33191"
  << Captured StdOut/StdErr Output
------------------------------
• [5.481 seconds]
odo dev command tests when running applications listening on the container loopback interface should error out if using --forward-localhost on any platform other than Podman
/go/odo_1/tests/integration/cmd_dev_test.go:4220

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35853"
  << Captured StdOut/StdErr Output
------------------------------
• [120.349 seconds]
odo dev command tests when running odo dev with devfile contain volume - without metadata.name should create pvc and reuse if it shares the same devfile volume name
/go/odo_1/tests/integration/cmd_dev_test.go:2197

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46577"
  << Captured StdOut/StdErr Output
------------------------------
• [9.394 seconds]
odo delete command tests when running odo deploy for an exec command bound to fail should print the job in the list of resources to be deleted with named delete command
/go/odo_1/tests/integration/cmd_delete_test.go:546

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45403"
  << Captured StdOut/StdErr Output
------------------------------
• [5.715 seconds]
odo devfile deploy command tests when a component is bootstrapped when using a default namespace should display warning when running the deploy command
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:67

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40195"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [58.648 seconds]
odo dev command tests when a component is bootstrapped when recording telemetry data should record the telemetry data correctly
/go/odo_1/tests/integration/cmd_dev_test.go:458

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35889"
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [5.186 seconds]
odo dev command tests when a component is bootstrapped should fail when using --no-commands and --build-command and/or --run-command together
/go/odo_1/tests/integration/cmd_dev_test.go:233

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46459"
  << Captured StdOut/StdErr Output
------------------------------
• [121.809 seconds]
odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy when running and stopping odo dev should not delete the resources created with odo deploy
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:176

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38133"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [87.176 seconds]
odo dev command tests when a component with endpoints is bootstrapped and pushed should not create Ingress or Route resources in the cluster
/go/odo_1/tests/integration/cmd_dev_test.go:3463

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36259"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
S [4.700 seconds]
odo devfile init command tests when DevfileRegistriesList CRD is installed on cluster [BeforeEach] when CR for devfileregistrieslists is installed in namespace should be able to download devfile from the in-cluster registry
  [BeforeEach] /go/odo_1/tests/integration/cmd_devfile_init_test.go:586
  [It] /go/odo_1/tests/integration/cmd_devfile_init_test.go:613

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33583"
  << Captured StdOut/StdErr Output

  [SKIPPED] skipped on non Kubernetes clusters
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_devfile_init_test.go:588 @ 12/01/23 11:11:39.751
------------------------------
SSSSSSS
------------------------------
• [111.358 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=false, customPortForwarding=true, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1379

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39431"
  << Captured StdOut/StdErr Output
------------------------------
• [6.667 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=false --running-in=deploy should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37491"
  << Captured StdOut/StdErr Output
------------------------------
• [27.475 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="dev") when odo delete command is run again with nothing deployed on the cluster should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:151

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43085"
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [9.266 seconds]
odo devfile deploy command tests deploying devfile with exec when using devfile that works; with component name of a normal character length should complete the command execution successfully
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:576

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34557"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [59.550 seconds]
odo dev command tests when Devfile 2.1.0 is used - with metadata.name when doing odo dev with --var-file flag and setting value in env should check if the env variable has a correct value
/go/odo_1/tests/integration/cmd_dev_test.go:1668

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40731"
  << Captured StdOut/StdErr Output
------------------------------
• [61.410 seconds]
odo dev command tests when a component is bootstrapped should use the index information from previous push operation
/go/odo_1/tests/integration/cmd_dev_test.go:200

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43255"
  << Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [59.447 seconds]
odo dev command tests when Devfile 2.1.0 is used - without metadata.name when doing odo dev with --var-file flag should check if the env variable has a correct value
/go/odo_1/tests/integration/cmd_dev_test.go:1639

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35865"
  << Captured StdOut/StdErr Output
------------------------------
• [85.005 seconds]
odo dev debug command tests when starting with Devfile with autoBuild or deployByDefault components when running odo dev with some components referenced in the Devfile should create the appropriate resources
/go/odo_1/tests/integration/cmd_dev_debug_test.go:631

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36975"
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [21.397 seconds]
odo dev interactive command tests when a component is bootstrapped should sync files when p is pressed
/go/odo_1/tests/integration/interactive_dev_test.go:211

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37793"
  Spawning '/go/bin/odo dev --random-ports --no-watch' from /tmp/4067617543
  << Captured StdOut/StdErr Output
------------------------------
SSSSSS
------------------------------
• [8.109 seconds]
odo devfile deploy command tests Devfile with autoBuild or deployByDefault components when starting with Devfile with Deploy commands when running odo deploy with some components referenced in the Devfile should create the appropriate resources
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:802

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36795"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [110.581 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=true, customPortForwarding=false, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1379

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45735"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [85.527 seconds]
odo dev command tests when starting with Devfile with autoBuild or deployByDefault components when running odo dev with some components referenced in the Devfile should create the appropriate resources
/go/odo_1/tests/integration/cmd_dev_test.go:4579

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41849"
  << Captured StdOut/StdErr Output
------------------------------
  Progress Report for Ginkgo Process #8
  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: 3m34.217s)
      /go/odo_1/tests/integration/cmd_dev_debug_test.go:288
      In [It] (Node Runtime: 2m0s)
        /go/odo_1/tests/integration/cmd_dev_debug_test.go:288
        At [By Step] cleaning up the resources on ending the session (Step Runtime: 26.186s)
          /go/odo_1/tests/integration/cmd_dev_debug_test.go:326

        Begin Captured GinkgoWriter Output >>
          ...
          [odo] stderr: []
          [odo] I1201 11:12:01.325725   38169 execute_run.go:36] error while running background command: unable to exec command [/bin/sh -c echo $$ > /opt/odo/.odo_cmd_start-debug.pid && cd /projects &&  (npm run debug) 1>>/proc/1/fd/1 2>>/proc/1/fd/2; echo $? >> /opt/odo/.odo_cmd_start-debug.pid]: error while streaming command: context canceled
          [odo] I1201 11:12:01.340006   38169 implem.go:114] The path for preference file is /tmp/1502856323/preference.yaml
          [odo] Cleaning resources, please wait
          [odo] I1201 11:12:01.340983   38169 segment.go:268] Checking telemetry enable status
          [odo] I1201 11:12:01.341015   38169 segment.go:286] Sending telemetry disabled by env variable
          [odo] I1201 11:12:01.427060   38169 all.go:46] starting to concurrently query 201 APIs
          [odo] I1201 11:12:01.431235   38169 all.go:62] fired up all goroutines to query APIs
          [odo] I1201 11:12:02.542839   38169 all.go:67] all goroutines have returned in 1.11577955s
          [odo] I1201 11:12:02.542906   38169 all.go:76] query result: objects=669
        << End Captured GinkgoWriter Output

        Spec Goroutine
        goroutine 723 [select]
          github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0000e8000, {0x31589b8?, 0xc000ceeab0}, 0x1, {0x0, 0x0, 0x0})
            /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538
          github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0000e8000, {0x31589b8, 0xc000ceeab0}, {0x0, 0x0, 0x0})
            /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145
          github.com/onsi/gomega/gexec.(*Session).Wait(0xc000375080?, {0xc0007985c0?, 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(0xc00019c000, {0x2da9fb5, 0x2f}, {0xc000ddfe70, 0x1, 0x0?})
            /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:309
          github.com/onsi/ginkgo/v2.By({0x2da9fb5?, 0x0?}, {0xc000ddfe70?, 0x0?, 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({0x0, 0x0})
            /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463
          github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3()
            /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865
          github.com/onsi/ginkgo/v2/internal.(*Suite).runNode
            /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852
  ------------------------------
• [50.618 seconds]
odo dev command tests when using a Devfile with no commands should start the Dev Session with --no-commands=false
/go/odo_1/tests/integration/cmd_dev_test.go:4921

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44909"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [4.573 seconds]
odo devfile deploy command tests when directory is empty should error
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:47

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46703"
  << Captured StdOut/StdErr Output
------------------------------
• [59.867 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46307"
  << Captured StdOut/StdErr Output
------------------------------
• [58.494 seconds]
odo dev command tests when a component is bootstrapped should add annotation to use ImageStreams
/go/odo_1/tests/integration/cmd_dev_test.go:147

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40619"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [119.185 seconds]
odo dev command tests when running odo dev and multiple env variables are set - without metadata.name should be able to exec command
/go/odo_1/tests/integration/cmd_dev_test.go:1717

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46537"
  << Captured StdOut/StdErr Output
------------------------------
• [9.394 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41303"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
S [6.784 seconds]
odo devfile deploy command tests deploying devfile with long-running exec when pod security is enforced as restricted [It] should set securitycontext for podsecurity admission on job's pod template
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:676

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36967"
  << Captured StdOut/StdErr Output

  [SKIPPED] This is a Kubernetes specific scenario, skipping
  In [It] at: /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:678 @ 12/01/23 11:12:40.88
------------------------------
• [230.159 seconds]
odo dev debug command tests when a composite apply command is used as debug command should execute the composite apply commands successfully
/go/odo_1/tests/integration/cmd_dev_debug_test.go:288

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42417"
  << Captured StdOut/StdErr Output
------------------------------
• [59.084 seconds]
odo dev debug command tests when a component without debug command is bootstrapped should log error about missing debug command when running odo dev --debug
/go/odo_1/tests/integration/cmd_dev_debug_test.go:444

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38439"
  << Captured StdOut/StdErr Output
------------------------------
• [7.531 seconds]
odo generic executing odo version command should only print client info when using --client flag
/go/odo_1/tests/integration/generic_test.go:201

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41879"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [60.272 seconds]
odo dev command tests when adding local files to gitignore and running odo dev should not sync ignored files to the container
/go/odo_1/tests/integration/cmd_dev_test.go:1955

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35709"
  << Captured StdOut/StdErr Output
------------------------------
• [92.541 seconds]
odo dev command tests when a component is bootstrapped when odo dev is executed and Ephemeral is set to false when stopping odo dev normally should have deleted all resources before returning
/go/odo_1/tests/integration/cmd_dev_test.go:629

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36907"
  << Captured StdOut/StdErr Output
------------------------------
• [59.983 seconds]
odo dev command tests when running odo dev and composite command are nested - with metadata.name should execute all commands in composite commmand
/go/odo_1/tests/integration/cmd_dev_test.go:2674

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41565"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [5.585 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an Image component with a build context should build image via Podman if build context references PROJECT_SOURCE env var
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:326

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36705"
  << Captured StdOut/StdErr Output
------------------------------
• [6.786 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=true --running-in=dev should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40785"
  << Captured StdOut/StdErr Output
------------------------------
• [6.855 seconds]
odo dev command tests when a component is bootstrapped should fail when using --random-ports and --port-forward together
/go/odo_1/tests/integration/cmd_dev_test.go:218

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42207"
  << Captured StdOut/StdErr Output
------------------------------
• [61.594 seconds]
odo dev command tests when Devfile 2.1.0 is used - without metadata.name when doing odo dev with --var-file flag and setting value in env should check if the env variable has a correct value
/go/odo_1/tests/integration/cmd_dev_test.go:1668

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35359"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [6.294 seconds]
odo dev command tests when Devfile contains metadata.language when odo deploy is executed should set the correct value in labels of deployed resources
/go/odo_1/tests/integration/cmd_dev_test.go:4105

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40201"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [5.884 seconds]
odo list with devfile listing non-odo managed components when a non-odo managed component without the managed-by label is deployed should list the component with odo list
/go/odo_1/tests/integration/cmd_devfile_list_test.go:67

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45199"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [61.716 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped the component is deleted while having access to the devfile.yaml when the component is deleted with --files should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:178

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34969"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [6.048 seconds]
odo devfile build-images command tests when using a Devfile with variable image names should build images with --var-file (push=true)
/go/odo_1/tests/integration/cmd_devfile_build_images_test.go:445

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37423"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [152.095 seconds]
odo dev command tests when running odo dev with devfile containing volume-component - without metadata.name should successfully use the volume components in container components
/go/odo_1/tests/integration/cmd_dev_test.go:2278

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38537"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [65.846 seconds]
odo dev command tests 1. devfile contains composite apply command the devfile contains an image component that uses a remote Dockerfile when [PODMAN_CMD=a-command-not-found-for-podman-should-make-odo-fallback-to-docker DOCKER_CMD=echo] remote server returns a valid file when odo dev is run should build and push image when odo dev is run
/go/odo_1/tests/integration/cmd_dev_test.go:2526

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36243"
  << Captured StdOut/StdErr Output
------------------------------
• [58.283 seconds]
odo dev command tests when setting git config and running odo dev should create vcs-uri annotation for the deployment when running odo dev
/go/odo_1/tests/integration/cmd_dev_test.go:2966

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45833"
  << Captured StdOut/StdErr Output
------------------------------
SS•S
------------------------------
• [86.009 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when running odo deploy should run odo dev successfully
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:161

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46027"
  << Captured StdOut/StdErr Output
------------------------------
• [5.072 seconds]
odo dev command tests when a component is bootstrapped should fail when using --no-commands and --build-command and/or --run-command together
/go/odo_1/tests/integration/cmd_dev_test.go:233

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33285"
  << Captured StdOut/StdErr Output
------------------------------
• [50.611 seconds]
odo dev command tests when a component is bootstrapped when using a default namespace should print warning about default namespace when running odo dev
/go/odo_1/tests/integration/cmd_dev_test.go:130

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41369"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
S [6.671 seconds]
odo dev command tests when a component is bootstrapped [It] should not set securitycontext for podsecurity admission
/go/odo_1/tests/integration/cmd_dev_test.go:392

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37867"
  << Captured StdOut/StdErr Output

  [SKIPPED] This is a Kubernetes specific scenario, skipping
  In [It] at: /go/odo_1/tests/integration/cmd_dev_test.go:394 @ 12/01/23 11:13:32.633
------------------------------
SSSS
------------------------------
• [7.303 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when an env.yaml file contains a non-current Project when running odo deploy when the env.yaml file still contains a non-current Project should delete the component in the current namespace
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:226

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35657"
  << Captured StdOut/StdErr Output
------------------------------
• [7.601 seconds]
odo create/delete/list/set namespace/project tests create namespace should fail to create namespace
/go/odo_1/tests/integration/cmd_namespace_test.go:63

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40967"
  << Captured StdOut/StdErr Output
------------------------------
• [8.028 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted using its name and namespace from another directory should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:241

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41745"
  << Captured StdOut/StdErr Output
------------------------------
SSSSSS
------------------------------
• [61.516 seconds]
odo dev debug command tests when a component is bootstrapped when running odo dev with debug flag and custom port mapping for port forwarding should connect to relevant custom ports forwarded
/go/odo_1/tests/integration/cmd_dev_debug_test.go:76

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40313"
  << Captured StdOut/StdErr Output
------------------------------
• [61.628 seconds]
odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted using its name and namespace from another directory should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:473

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33877"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [59.228 seconds]
odo dev debug command tests when a component is bootstrapped when running odo dev with debug flag should connect to relevant ports forwarded
/go/odo_1/tests/integration/cmd_dev_debug_test.go:112

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43611"
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [59.197 seconds]
odo dev command tests when running odo dev with alternative commands - with metadata.name when running odo dev with a run command should execute the custom non-default run command successfully
/go/odo_1/tests/integration/cmd_dev_test.go:3181

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44173"
  << Captured StdOut/StdErr Output
------------------------------
• [7.438 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=false --running-in= should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40191"
  << Captured StdOut/StdErr Output
------------------------------
• [110.860 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=true, customPortForwarding=true, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1379

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40625"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [60.747 seconds]
odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a run command should execute the custom non-default run command successfully
/go/odo_1/tests/integration/cmd_dev_test.go:3181

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44837"
  << Captured StdOut/StdErr Output
------------------------------
• [91.181 seconds]
odo dev command with api server tests when the component is bootstrapped when odo is executed with --no-watch and --api-server flags when a file in component directory is modified when /component/command endpoint is POSTed should trigger a push
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:282

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36149"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [100.772 seconds]
odo dev command tests when hotReload capable Build and Run commands are used with odo dev should execute the build and run commands
/go/odo_1/tests/integration/cmd_dev_test.go:3818

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45391"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [60.003 seconds]
odo dev command tests when running odo dev and composite command is marked as parallel:true - with metadata.name should execute all commands in composite command
/go/odo_1/tests/integration/cmd_dev_test.go:2642

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44927"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [61.166 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=false, customPortForwarding=false, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1338

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35983"
  << Captured StdOut/StdErr Output
------------------------------
• [10.596 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=true --running-in= should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46791"
  << Captured StdOut/StdErr Output
------------------------------
• [7.531 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=false --running-in=dev should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44323"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [70.465 seconds]
odo dev command tests when Devfile 2.1.0 is used - with metadata.name when doing odo dev with --var flag should check if the env variable has a correct value
/go/odo_1/tests/integration/cmd_dev_test.go:1612

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45033"
  << Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [70.670 seconds]
odo dev command tests when Devfile 2.1.0 is used - with metadata.name when doing odo dev 3. should check if the env variable has a correct value
/go/odo_1/tests/integration/cmd_dev_test.go:1589

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41565"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [4.879 seconds]
odo dev command tests when Devfile contains metadata.projectType when odo deploy is executed should set the correct value in labels of deployed resources
/go/odo_1/tests/integration/cmd_dev_test.go:4105

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40065"
  << 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: 2m3.662s)
      /go/odo_1/tests/integration/cmd_dev_test.go:4146
      In [It] (Node Runtime: 2m0.001s)
        /go/odo_1/tests/integration/cmd_dev_test.go:4146

      Begin Captured GinkgoWriter Output >>
        ...
        [odo]  ✗  Finished executing the application (command: run) [1m]
        [odo] I1201 11:14:17.651014   46059 execute_run.go:36] error while running background command: unable to exec command [/bin/sh -c echo $$ > /opt/odo/.odo_cmd_run.pid && cd ${PROJECT_SOURCE} &&  (npm start) 1>>/proc/1/fd/1 2>>/proc/1/fd/2; echo $? >> /opt/odo/.odo_cmd_run.pid]: error while streaming command: context canceled
        [odo] I1201 11:14:17.655956   46059 implem.go:114] The path for preference file is /tmp/2773848181/preference.yaml
        [odo] Cleaning resources, please wait
        [odo] I1201 11:14:17.656705   46059 segment.go:268] Checking telemetry enable status
        [odo] I1201 11:14:17.656715   46059 segment.go:286] Sending telemetry disabled by env variable
        [odo] I1201 11:14:17.723612   46059 all.go:46] starting to concurrently query 201 APIs
        [odo] I1201 11:14:17.724089   46059 all.go:62] fired up all goroutines to query APIs
        [odo] I1201 11:14:18.950735   46059 all.go:67] all goroutines have returned in 1.22715237s
        [odo] I1201 11:14:18.950793   46059 all.go:76] query result: objects=632
      << End Captured GinkgoWriter Output

      Spec Goroutine
      goroutine 897 [select]
        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0004cd6c0, {0x31589b8?, 0xc0008c5338}, 0x1, {0x0, 0x0, 0x0})
          /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538
        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0004cd6c0, {0x31589b8, 0xc0008c5338}, {0x0, 0x0, 0x0})
          /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145
        github.com/onsi/gomega/gexec.(*Session).Wait(0xc00178fd50?, {0xc0007c5600?, 0x2d4b5e9?, 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({0x10a8ebe, 0xc001631c20})
          /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
  ------------------------------
• [58.915 seconds]
odo dev command tests when running odo dev and composite command is marked as parallel:true - without metadata.name should execute all commands in composite command
/go/odo_1/tests/integration/cmd_dev_test.go:2642

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34579"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [129.188 seconds]
odo dev command tests Devfile contains pod-overrides and container-overrides attributes should override the content in the pod it creates for the component on the cluster
/go/odo_1/tests/integration/cmd_dev_test.go:4146

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34985"
  << Captured StdOut/StdErr Output
------------------------------
SSSSSS
------------------------------
• [6.268 seconds]
odo dev command tests when a component is bootstrapped when a state file is not writable should fail running odo dev
/go/odo_1/tests/integration/cmd_dev_test.go:435

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37937"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [150.882 seconds]
odo dev command tests when running odo dev with devfile containing volume-component - with metadata.name should successfully use the volume components in container components
/go/odo_1/tests/integration/cmd_dev_test.go:2278

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33333"
  << Captured StdOut/StdErr Output
------------------------------
• [67.909 seconds]
odo dev command tests when adding local files to gitignore and running odo dev when modifying /testdir/foobar.txt file should not synchronize it
/go/odo_1/tests/integration/cmd_dev_test.go:1987

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43301"
  << Captured StdOut/StdErr Output
------------------------------
S [4.524 seconds]
odo devfile deploy command tests when deploying a ServiceBinding k8s resource [BeforeEach] when odo deploy is run should successfully deploy the ServiceBinding resource
  [BeforeEach] /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:387
  [It] /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:412

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34867"
  << Captured StdOut/StdErr Output

  [SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:390 @ 12/01/23 11:15:01.26
------------------------------
• [9.031 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43385"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [59.398 seconds]
odo dev command tests when project and clonePath is present in devfile and running odo dev - with metadata.name should sync to the correct dir in container
/go/odo_1/tests/integration/cmd_dev_test.go:2058

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41203"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [8.529 seconds]
odo devfile deploy command tests when recording telemetry data should record the telemetry data correctly
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:270

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46307"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [79.782 seconds]
odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag when /component/command endpoint is POSTed should trigger a push
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:221

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43679"
  << Captured StdOut/StdErr Output
------------------------------
• [60.327 seconds]
odo describe component command tests when creating a component when running odo dev (podman=false,debug=true) JSON output when switching to another directory when describing the component from another directory should describe the named component
/go/odo_1/tests/integration/cmd_describe_component_test.go:477

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45247"
  << Captured StdOut/StdErr Output
------------------------------
• [61.870 seconds]
odo dev command tests when a component is bootstrapped should sync .git directory and subfiles with --sync-git-dir
/go/odo_1/tests/integration/cmd_dev_test.go:182

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42247"
  << Captured StdOut/StdErr Output
------------------------------
• [16.820 seconds]
odo logs command tests when component is created and odo logs is executed when running in Deploy mode should successfully show logs of the running component
/go/odo_1/tests/integration/cmd_logs_test.go:267

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39219"
  << Captured StdOut/StdErr Output
------------------------------
S [4.986 seconds]
odo dev command tests when Starting a PostgreSQL service [BeforeEach] when creating local files and dir and running odo dev - without metadata.name when deleting local files and dir and waiting for sync should not list deleted dir and file in container
  [BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:1815
  [It] /go/odo_1/tests/integration/cmd_dev_test.go:1882

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37937"
  << Captured StdOut/StdErr Output

  [SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:1818 @ 12/01/23 11:15:26.125
------------------------------
SSSSS
------------------------------
• [81.097 seconds]
odo dev debug command tests when a composite command is used as debug command - without metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_debug_test.go:225

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40475"
  << Captured StdOut/StdErr Output
------------------------------
• [6.886 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when running odo deploy with image build extra args should succeed
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:143

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42721"
  << Captured StdOut/StdErr Output
------------------------------
• [61.277 seconds]
odo dev command tests when no project is present - without metadata.name should sync to the correct dir in container
/go/odo_1/tests/integration/cmd_dev_test.go:2164

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37009"
  << Captured StdOut/StdErr Output
------------------------------
• [31.033 seconds]
odo logs command tests when component is created and odo logs is executed when running in Deploy mode when --follow flag is specified should successfully follow logs of running component
/go/odo_1/tests/integration/cmd_logs_test.go:291

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46849"
  << Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [120.951 seconds]
odo dev command tests when running odo dev and single env var is set - without metadata.name should be able to exec command
/go/odo_1/tests/integration/cmd_dev_test.go:1691

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44785"
  << Captured StdOut/StdErr Output
------------------------------
• [60.343 seconds]
odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33787"
  << Captured StdOut/StdErr Output
------------------------------
• [89.588 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when running odo deploy with image build extra args should run odo dev successfully
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:161

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44521"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [11.309 seconds]
odo list with devfile listing non-odo managed components when a non-odo managed component is deployed should list the component in JSON
/go/odo_1/tests/integration/cmd_devfile_list_test.go:47

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33463"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [10.619 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=true --running-in= should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40479"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [63.513 seconds]
odo dev command tests when running odo dev and devfile with composite command - without metadata.name should execute all commands in composite command
/go/odo_1/tests/integration/cmd_dev_test.go:2610

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45165"
  << Captured StdOut/StdErr Output
------------------------------
• [58.103 seconds]
odo devfile deploy command tests deploying devfile with long-running exec when Automount volumes are present in the namespace should mount the volumes
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:695

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37525"
  << Captured StdOut/StdErr Output
------------------------------
• [114.414 seconds]
odo dev debug command tests when running build and debug commands as composite in different containers and a shared volume - without metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_debug_test.go:388

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42441"
  << Captured StdOut/StdErr Output
------------------------------
SSS
  ------------------------------
  Progress Report for Ginkgo Process #11
  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: 2m5.004s)
      /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] I1201 11:16:04.181718   49103 exec.go:96]   sl  local_address                         remote_address                        st tx_queue rx_queue tr tm->when retrnsmt   uid  timeout inode ref pointer drops
        [odo] I1201 11:16:04.186881   49103 port.go:319] port 8080 not listening in container "runtime"
        [odo] I1201 11:16:07.992228   49103 exec.go:37] Executing command [/bin/sh -c cat /proc/net/tcp /proc/net/udp /proc/net/tcp6 /proc/net/udp6 || true] for pod: brzzrw-app-765f6c4c89-5jp7q in container: runtime
        [odo] I1201 11:16:08.458334   49103 exec.go:96]   sl  local_address rem_address   st tx_queue rx_queue tr tm->when retrnsmt   uid  timeout inode                                                     
        [odo] I1201 11:16:08.458367   49103 exec.go:96]    0: 502E11AC:D87E 221D1068:01BB 06 00000000:00000000 03:00000EE5 00000000     0        0 0 3 0000000000000000                                      
        [odo] I1201 11:16:08.458407   49103 exec.go:96]   sl  local_address rem_address   st tx_queue rx_queue tr tm->when retrnsmt   uid  timeout inode ref pointer drops             
        [odo] I1201 11:16:08.458861   49103 exec.go:96]   sl  local_address                         remote_address                        st tx_queue rx_queue tr tm->when retrnsmt   uid  timeout inode
        [odo] I1201 11:16:08.458881   49103 exec.go:96]    0: 00000000000000000000000000000000:0BB8 00000000000000000000000000000000:0000 0A 00000000:00000000 00:00000000 00000000 1038440000        0 290241485 1 0000000000000000 100 0 0 10 0
        [odo] I1201 11:16:08.459594   49103 exec.go:96]   sl  local_address                         remote_address                        st tx_queue rx_queue tr tm->when retrnsmt   uid  timeout inode ref pointer drops
        [odo] I1201 11:16:08.462576   49103 port.go:319] port 8080 not listening in container "runtime"
      << End Captured GinkgoWriter Output

      Spec Goroutine
      goroutine 1146 [select, 2 minutes]
        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc00025cd20, {0x3158bf8?, 0xc000ea9b30}, 0x1, {0x0, 0x0, 0x0})
          /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538
        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc00025cd20, {0x3158bf8, 0xc000ea9b30}, {0x0, 0x0, 0x0})
          /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145
        github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x2d497fc, 0x8}, 0xc0005bbf60?, 0xc0005bbf20?, 0xc000ea9680)
          /go/odo_1/tests/helper/helper_run.go:54
        github.com/redhat-developer/odo/tests/helper.(*DevSession).WaitSync(0xc00045f560)
          /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({0x10a8ebe, 0xc0016a2540})
          /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
  ------------------------------
• [92.565 seconds]
odo dev command tests checking if odo dev matches local Devfile K8s resources and remote resources when odo dev is executed to run a devfile containing a k8s resource without apply command should have deleted the old resource and created the new resource
/go/odo_1/tests/integration/cmd_dev_test.go:1077

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33573"
  << Captured StdOut/StdErr Output
------------------------------
• [66.207 seconds]
odo dev command tests when adding local files to gitignore and running odo dev should not sync ignored files to the container
/go/odo_1/tests/integration/cmd_dev_test.go:1955

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39273"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [61.957 seconds]
odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a build command should execute the custom non-default build command successfully
/go/odo_1/tests/integration/cmd_dev_test.go:3112

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38465"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [4.560 seconds]
odo create/delete/list/set namespace/project tests set namespace should not succeed to set the namespace
/go/odo_1/tests/integration/cmd_namespace_test.go:162

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33919"
  << Captured StdOut/StdErr Output
------------------------------
• [58.959 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=false, customPortForwarding=true, customAddress=true)
/go/odo_1/tests/integration/cmd_dev_test.go:1338

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36367"
  << Captured StdOut/StdErr Output
------------------------------
• [80.267 seconds]
odo dev command tests when creating local files and dir and running odo dev - without metadata.name when deleting local files and dir and waiting for sync should not list deleted dir and file in container
/go/odo_1/tests/integration/cmd_dev_test.go:1805

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38427"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [60.665 seconds]
odo dev command tests when multiple projects are present - without metadata.name should sync to the correct dir in container
/go/odo_1/tests/integration/cmd_dev_test.go:2130

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44971"
  << Captured StdOut/StdErr Output
------------------------------
• [59.667 seconds]
odo dev command tests when devfile has sourcemappings and running odo dev - without metadata.name should sync files to the correct location
/go/odo_1/tests/integration/cmd_dev_test.go:2016

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43391"
  << Captured StdOut/StdErr Output
------------------------------
• [79.423 seconds]
odo dev command tests when creating local files and dir and running odo dev - with metadata.name when deleting local files and dir and waiting for sync should not list deleted dir and file in container
/go/odo_1/tests/integration/cmd_dev_test.go:1805

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44383"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [63.647 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="deploy") should output that there are no resources to be deleted
/go/odo_1/tests/integration/cmd_delete_test.go:124

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36015"
  << Captured StdOut/StdErr Output
------------------------------
• [5.254 seconds]
odo devfile init command tests setting application ports when running odo init --run-port with a Devfile with no commands should overwrite the ports into the container component referenced by the default run command
/go/odo_1/tests/integration/cmd_devfile_init_test.go:654

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40801"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [91.785 seconds]
odo logs command tests when component is created and odo logs is executed when running in Dev mode with --logs 1. should successfully show logs of the running component
/go/odo_1/tests/integration/cmd_logs_test.go:249

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46179"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [71.508 seconds]
odo dev command tests when adding local files to gitignore and running odo dev when modifying /foobar.txt file should not synchronize it
/go/odo_1/tests/integration/cmd_dev_test.go:1977

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39361"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [7.636 seconds]
odo describe component command tests when creating a component should not describe the component from another directory, with default cluster mode
/go/odo_1/tests/integration/cmd_describe_component_test.go:264

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:32811"
  << Captured StdOut/StdErr Output
------------------------------
• [67.309 seconds]
odo dev command tests when a component with multiple endpoints is run should fail running a second session on the same platform
/go/odo_1/tests/integration/cmd_dev_test.go:3615

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34247"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [6.362 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=false --running-in= should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45751"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [59.515 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=true, customPortForwarding=false, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1338

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:41591"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [47.905 seconds]
odo dev command tests when a component is bootstrapped when build command takes really long to start should cancel build command and return if odo dev is stopped
/go/odo_1/tests/integration/cmd_dev_test.go:981

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:34421"
  << Captured StdOut/StdErr Output
------------------------------
• [7.540 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an Image component with no build context should build image via Podman by defaulting build context to devfile path
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:450

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39331"
  << Captured StdOut/StdErr Output
------------------------------
SSSSSSSSSSSS
------------------------------
• [71.662 seconds]
odo dev command tests when Create and dev java-springboot component should execute default build and run commands correctly
/go/odo_1/tests/integration/cmd_dev_test.go:2931

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33763"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [71.724 seconds]
odo dev debug command tests when a composite command is used as debug command - with metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_debug_test.go:225

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46543"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [35.840 seconds]
odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted using its name and namespace from another directory should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:473

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40767"
  << Captured StdOut/StdErr Output
------------------------------
• [7.691 seconds]
odo devfile deploy command tests using a Devfile with an image component using a remote Dockerfile when remote server returns an error should not build images
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:502

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39859"
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [61.154 seconds]
odo dev command tests when devfile project field is present and running odo dev - with metadata.name should sync to the correct dir in container
/go/odo_1/tests/integration/cmd_dev_test.go:2097

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44553"
  << Captured StdOut/StdErr Output
------------------------------
• [121.561 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when running odo deploy with image build extra args when running and stopping odo dev should not delete the resources created with odo deploy
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:176

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36513"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [14.000 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46369"
  << Captured StdOut/StdErr Output
------------------------------
• [213.012 seconds]
odo dev command tests checking if odo dev matches local Devfile K8s resources and remote resources when odo dev is executed to run a devfile containing a k8s resource with apply command should have deleted the old resource and created the new resource
/go/odo_1/tests/integration/cmd_dev_test.go:1077

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40611"
  << Captured StdOut/StdErr Output
------------------------------
• [116.302 seconds]
odo dev command tests multiple dev sessions with different project are running on same platform (podman=false), same port when odo dev session is run for nodejs component when odo dev session is run for go project on the same port but different address should be able to run both the sessions
/go/odo_1/tests/integration/cmd_dev_test.go:1213

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46113"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [58.803 seconds]
odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag should serve endpoints
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:171

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42793"
  << Captured StdOut/StdErr Output
------------------------------
• [61.405 seconds]
odo describe component command tests when creating a component when running odo dev (podman=false,debug=true) JSON output when describing the component in dev mode should describe the component
/go/odo_1/tests/integration/cmd_describe_component_test.go:416

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35777"
  << Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [62.934 seconds]
odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46541"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [33.817 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44139"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [79.637 seconds]
odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=true, customPortForwarding=true, customAddress=false)
/go/odo_1/tests/integration/cmd_dev_test.go:1463

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:33093"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [57.912 seconds]
odo run command tests when a component is bootstrapped when odo dev is executed with --no-commands=true and ready should execute commands
/go/odo_1/tests/integration/cmd_run_test.go:100

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:32785"
  << Captured StdOut/StdErr Output
------------------------------
• [59.455 seconds]
odo dev command tests when running odo dev with alternative commands - with metadata.name when running odo dev with a build command should execute the custom non-default build command successfully
/go/odo_1/tests/integration/cmd_dev_test.go:3112

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38429"
  << Captured StdOut/StdErr Output
------------------------------
• [60.136 seconds]
odo dev command tests when Devfile contains metadata.language invalid as a label value when running odo dev should set the correct value in labels of resources
/go/odo_1/tests/integration/cmd_dev_test.go:4089

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35719"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [7.641 seconds]
odo create/delete/list/set namespace/project tests create project should successfully create the project
/go/odo_1/tests/integration/cmd_namespace_test.go:54

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45885"
  << Captured StdOut/StdErr Output
------------------------------
• [117.565 seconds]
odo logs command tests when component is created and odo logs is executed when running in both Dev and Deploy mode should successfully show logs of the running component
/go/odo_1/tests/integration/cmd_logs_test.go:320

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36145"
  << Captured StdOut/StdErr Output
------------------------------
• [82.552 seconds]
odo dev interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile successfully even with -v flag
/go/odo_1/tests/integration/interactive_dev_test.go:40

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:42837"
  Spawning '/go/bin/odo dev --random-ports -v 4' from /tmp/960795253
  << Captured StdOut/StdErr Output
------------------------------
• [62.331 seconds]
odo dev command tests when multiple projects are present - with metadata.name should sync to the correct dir in container
/go/odo_1/tests/integration/cmd_dev_test.go:2130

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45833"
  << Captured StdOut/StdErr Output
------------------------------
• [127.023 seconds]
odo list with devfile when a component created in 'app' application when dev is running on cluster show an odo deploy or dev in the list
/go/odo_1/tests/integration/cmd_devfile_list_test.go:193

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44587"
  << Captured StdOut/StdErr Output
------------------------------
• [67.462 seconds]
odo dev command tests when a component is bootstrapped should show validation errors if the devfile is incorrect
/go/odo_1/tests/integration/cmd_dev_test.go:156

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38991"
  << Captured StdOut/StdErr Output
------------------------------
• [61.918 seconds]
odo dev command tests when a component is bootstrapped when odo is executed with --no-watch flag and without --no-commands when a file in component directory is modified should not trigger a push
/go/odo_1/tests/integration/cmd_dev_test.go:736

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:37715"
  << Captured StdOut/StdErr Output
------------------------------
• [63.717 seconds]
odo dev command tests when creating nodejs component, doing odo dev and run command has dev.odo.push.path attribute should sync only the mentioned files at the appropriate remote destination
/go/odo_1/tests/integration/cmd_dev_test.go:3428

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36411"
  << Captured StdOut/StdErr Output
------------------------------
• [168.651 seconds]
odo dev command tests when a component is bootstrapped when Automount volumes are present in the namespace when odo dev is executed should mount the volumes
/go/odo_1/tests/integration/cmd_dev_test.go:833

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:40277"
  << Captured StdOut/StdErr Output
------------------------------
• [121.160 seconds]
odo dev command tests when running odo dev with devfile contain volume - with metadata.name should create pvc and reuse if it shares the same devfile volume name
/go/odo_1/tests/integration/cmd_dev_test.go:2197

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:32813"
  << Captured StdOut/StdErr Output
------------------------------
• [58.545 seconds]
odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag when /instance endpoint is DELETEd should terminate the dev session
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:239

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46259"
  <<< Session terminated >>>
  << Captured StdOut/StdErr Output
------------------------------
• [132.183 seconds]
odo describe component command tests checking for remote source code location when using devfile with containers that has mountSource set to false and starting an odo dev session should show remote source code location in odo describe component output
/go/odo_1/tests/integration/cmd_describe_component_test.go:642

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:44945"
  << Captured StdOut/StdErr Output
------------------------------
• [132.730 seconds]
odo dev command tests multiple dev sessions with different project are running on same platform (podman=false), same port when odo dev session is run for nodejs component when odo dev session is run for go project on the same port but different address when go and nodejs files are modified should be possible to access both the projects on same address and port
/go/odo_1/tests/integration/cmd_dev_test.go:1237

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:46547"
  << Captured StdOut/StdErr Output
------------------------------
• [129.468 seconds]
odo dev command tests when running odo dev and composite command is used as a run command - with metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2709

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:43261"
  << Captured StdOut/StdErr Output
------------------------------
• [118.154 seconds]
odo dev command tests when a devfile with a local parent is used for odo dev and the parent is not synced when updating the parent should update the component
/go/odo_1/tests/integration/cmd_dev_test.go:3697

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:35661"
  << Captured StdOut/StdErr Output
------------------------------

Ran 406 of 956 Specs in 1416.418 seconds
SUCCESS! -- 406 Passed | 0 Failed | 0 Pending | 550 Skipped


Ginkgo ran 1 suite in 24m48.585742815s
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: 1701429628 - will randomize all specs

Will run 4 of 4 specs
Running in parallel across 16 processes
------------------------------
• [109.516 seconds]
E2E Test starting with non-empty Directory test debugging should verify developer workflow from non-empty Directory
/go/odo_1/tests/e2escenarios/e2e_test.go:316

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:45827"
  Spawning '/go/bin/odo init' from /tmp/1779303725
  << Captured StdOut/StdErr Output
------------------------------
• [120.691 seconds]
E2E Test starting with non-empty Directory add Binding should verify developer workflow of using binding as env in innerloop
/go/odo_1/tests/e2escenarios/e2e_test.go:448

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:39179"
  Spawning '/go/bin/odo init' from /tmp/1607015118
  << 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: 2m5.295s)
      /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] I1201 11:22:49.762917   58952 watch.go:271] deployment watcher Event: Type: MODIFIED, name: zkopit-app, rv: 119222830, generation: 1, pods: 1
        [odo] I1201 11:22:49.910588   58952 watch.go:348] filesystem watch event: REMOVE        "/tmp/3292150460/.odo/odo-file-index.json"
        [odo] I1201 11:22:49.910912   58952 watch.go:383] error removing watch for /tmp/3292150460/.odo/odo-file-index.json: can't remove non-existent watcher: /tmp/3292150460/.odo/odo-file-index.json
        [odo] I1201 11:22:49.910983   58952 watch.go:348] filesystem watch event: CREATE        "/tmp/3292150460/.odo/odo-file-index.json"
        [odo] I1201 11:22:49.916271   58952 watch.go:348] filesystem watch event: WRITE         "/tmp/3292150460/.odo/odo-file-index.json"
        [odo] I1201 11:22:49.920196   58952 watch.go:348] filesystem watch event: WRITE         "/tmp/3292150460/.odo/devstate.json"
        [odo] I1201 11:22:49.923908   58952 watch.go:348] filesystem watch event: WRITE         "/tmp/3292150460/.odo/devstate.58952.json"
      << End Captured GinkgoWriter Output

      Spec Goroutine
      goroutine 69 [select]
        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0003b44d0, {0x2f9c860?, 0xc0009fa000}, 0x1, {0x0, 0x0, 0x0})
          /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538
        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0003b44d0, {0x2f9c860, 0xc0009fa000}, {0x0, 0x0, 0x0})
          /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145
        github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x2bc8ddd, 0xf}, 0x0?, 0x3?, 0xc000903f80)
          /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({0x105b59e, 0xc000368700})
          /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: 2m5.38s)
      /go/odo_1/tests/e2escenarios/e2e_test.go:186
      In [It] (Node Runtime: 2m0s)
        /go/odo_1/tests/e2escenarios/e2e_test.go:186

      Begin Captured GinkgoWriter Output >>
        ...
        [odo]  Watching for changes in the current directory /tmp/3861787096
        [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] I1201 11:22:47.849499   58539 libdevfile.go:326] not running in Debug mode, so ignored Debug port for container tools:debug:5858
        [odo] I1201 11:22:47.849535   58539 status.go:34] setting inner loop State "Ready"
        [odo] I1201 11:22:47.849583   58539 watch.go:271] deployment watcher Event: Type: MODIFIED, name: vwokgv-app, rv: 119222665, generation: 1, pods: 1
        [odo] I1201 11:22:47.950883   58539 watch.go:348] filesystem watch event: WRITE         "/tmp/3861787096/.odo/odo-file-index.json"
        [odo] I1201 11:22:47.951885   58539 watch.go:348] filesystem watch event: WRITE         "/tmp/3861787096/.odo/odo-file-index.json"
      << End Captured GinkgoWriter Output

      Spec Goroutine
      goroutine 60 [select]
        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0004c83f0, {0x2f9c860?, 0xc0002b43f0}, 0x1, {0x0, 0x0, 0x0})
          /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538
        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0004c83f0, {0x2f9c860, 0xc0002b43f0}, {0x0, 0x0, 0x0})
          /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145
        github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x2bbacd2, 0x8}, 0xc00029ad80?, 0xc0000b05a0?, 0xc0000e4b70)
          /go/odo_1/tests/helper/helper_run.go:54
        github.com/redhat-developer/odo/tests/helper.(*DevSession).WaitSync(0xc0007e5d28)
          /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:233
            | // "changes are made to the applications"
            | helper.ReplaceString(filepath.Join(commonVar.Context, "src", "main", "java", "com", "example", "demo", "DemoApplication.java"), "Hello updated World!", "Hello from an updated World!")
            > err = devSession.WaitSync()
            | Expect(err).ToNot(HaveOccurred())
            | // "should deploy new changes"
        github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x105b585, 0x13ecf2a})
          /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.766 seconds]
E2E Test starting with empty Directory should verify developer workflow from empty Directory
/go/odo_1/tests/e2escenarios/e2e_test.go:50

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:36399"
  Spawning '/go/bin/odo init' from /tmp/3292150460
  Spawning '/go/bin/odo delete component' from /tmp/3292150460
  << 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: 4m5.387s)
      /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/3861787096
        [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] I1201 11:24:46.970731   59200 watch.go:271] deployment watcher Event: Type: MODIFIED, name: vwokgv-app, rv: 119223999, generation: 1, pods: 1
        [odo] I1201 11:24:47.071811   59200 watch.go:348] filesystem watch event: WRITE         "/tmp/3861787096/.odo/odo-file-index.json"
        [odo] I1201 11:24:47.073532   59200 watch.go:348] filesystem watch event: WRITE         "/tmp/3861787096/.odo/odo-file-index.json"
      << End Captured GinkgoWriter Output

      Spec Goroutine
      goroutine 60 [select, 1 minutes]
        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc00046c540, {0x2f9c860?, 0xc000671440}, 0x1, {0x0, 0x0, 0x0})
          /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538
        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc00046c540, {0x2f9c860, 0xc000671440}, {0x0, 0x0, 0x0})
          /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145
        github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x2bbacd2, 0x8}, 0xc00060cb40?, 0xc0000b05a0?, 0xc0006713b0)
          /go/odo_1/tests/helper/helper_run.go:54
        github.com/redhat-developer/odo/tests/helper.(*DevSession).WaitSync(0xc0009f1d28)
          /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({0x105b585, 0x13ecf2a})
          /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.914 seconds]
E2E Test starting with non-empty Directory should verify developer workflow from non-empty Directory
/go/odo_1/tests/e2escenarios/e2e_test.go:186

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "http://127.0.0.1:38977"
  Spawning '/go/bin/odo init' from /tmp/3861787096
  Spawning '/go/bin/odo delete component' from /tmp/3861787096
  << Captured StdOut/StdErr Output
------------------------------

Ran 4 of 4 Specs in 252.971 seconds
SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped


Ginkgo ran 1 suite in 4m32.562107506s
Test Suite Passed