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

Will run 504 of 956 specs
Running in parallel across 16 processes
SSSSSSSSSSSSSSSSSS
------------------------------
• [14.214 seconds]
odo create/delete/list/set namespace/project tests list namespace should successfully list all the namespaces in JSON format
/go/odo_1/tests/integration/cmd_namespace_test.go:228

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [14.366 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an Image component with a build context should build image via Docker if build context references PROJECT_SOURCE env var
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:326

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output

  [SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:390 @ 11/11/23 14:12:28.034
------------------------------
S [15.450 seconds]
odo dev command tests when a component is bootstrapped when odo dev is executed and Ephemeral is set to false [BeforeEach] when killing odo dev and another process replaces it should restart a new session successfully
  [BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:560
  [It] /go/odo_1/tests/integration/cmd_dev_test.go:609

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output

  [SKIPPED] This is a OpenShift specific scenario, skipping
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:562 @ 11/11/23 14:12:30.85
------------------------------
• [18.867 seconds]
odo create/delete/list/set namespace/project tests set project should not succeed to set the project
/go/odo_1/tests/integration/cmd_namespace_test.go:162

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

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

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [66.409 seconds]
odo dev command tests when a component is bootstrapped should not set securitycontext for podsecurity admission
/go/odo_1/tests/integration/cmd_dev_test.go:392

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSSSSS
------------------------------
• [67.960 seconds]
odo dev command tests when a container component defines a Command or Args - with metadata.name should run odo dev successfully (#5620)
/go/odo_1/tests/integration/cmd_dev_test.go:3538

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [78.925 seconds]
odo dev command tests when Create and dev java-springboot component should execute default build and run commands correctly
/go/odo_1/tests/integration/cmd_dev_test.go:2931

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [87.463 seconds]
odo dev debug command tests when a composite command is used as debug command - without metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_debug_test.go:225

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [5.151 seconds]
odo create/delete/list/set namespace/project tests set project when running inside a component directory should set the project
/go/odo_1/tests/integration/cmd_namespace_test.go:190

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [3.511 seconds]
odo create/delete/list/set namespace/project tests delete project should not succeed to delete a non-existent project
/go/odo_1/tests/integration/cmd_namespace_test.go:122

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [45.281 seconds]
odo dev command tests when a component is bootstrapped when build command takes really long to start should cancel build command and return if odo dev is stopped
/go/odo_1/tests/integration/cmd_dev_test.go:981

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [57.789 seconds]
odo dev command tests when a component is bootstrapped should not sync .git directory
/go/odo_1/tests/integration/cmd_dev_test.go:166

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  PID: 14717
  << Captured StdOut/StdErr Output
------------------------------
• [45.815 seconds]
odo dev command tests when running odo dev --no-watch and build command throws an error should error out with some log
/go/odo_1/tests/integration/cmd_dev_test.go:2898

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [8.349 seconds]
odo preference and config command tests when DevfileRegistriesList CRD is installed on cluster when CR for devfileregistrieslists is installed in namespace registry list should return registry listed in CR
/go/odo_1/tests/integration/cmd_pref_config_test.go:414

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [128.835 seconds]
odo dev command tests when running odo dev and multiple env variables are set - with metadata.name should be able to exec command
/go/odo_1/tests/integration/cmd_dev_test.go:1717

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSSSSS
------------------------------
S [6.437 seconds]
odo dev command tests when a component is bootstrapped when odo dev is executed and Ephemeral is set to false [BeforeEach] when stopping odo dev normally should have deleted all resources before returning
  [BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:560
  [It] /go/odo_1/tests/integration/cmd_dev_test.go:629

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output

  [SKIPPED] This is a OpenShift specific scenario, skipping
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:562 @ 11/11/23 14:14:29.252
------------------------------
SSSS
------------------------------
• [11.249 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:316

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [7.425 seconds]
odo create/delete/list/set namespace/project tests list project should successfully list all the projects
/go/odo_1/tests/integration/cmd_namespace_test.go:221

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  Spawning '/go/bin/odo dev --random-ports -v 4' from /tmp/228038451
  << Captured StdOut/StdErr Output
------------------------------
• [59.150 seconds]
odo dev command tests when a component with multiple endpoints is run when odo dev is stopped should remove forwarded ports from state file
/go/odo_1/tests/integration/cmd_dev_test.go:3583

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [3.003 seconds]
odo dev command tests when directory is empty should error
/go/odo_1/tests/integration/cmd_dev_test.go:64

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [7.369 seconds]
odo devfile deploy command tests deploying devfile with exec should not set securitycontext for podsecurity admission on job's pod template
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:601

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [57.257 seconds]
odo dev command tests when a component is bootstrapped when recording telemetry data should record the telemetry data correctly
/go/odo_1/tests/integration/cmd_dev_test.go:458

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

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

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

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [6.404 seconds]
odo devfile deploy command tests Devfile with autoBuild or deployByDefault components when starting with Devfile with Deploy commands when running odo deploy with some components referenced in the Devfile should create the appropriate resources
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:802

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [86.594 seconds]
odo dev command tests when hotReload capable Build and Run commands are used with odo dev should execute the build and run commands
/go/odo_1/tests/integration/cmd_dev_test.go:3818

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [58.539 seconds]
odo dev command tests when running odo dev and composite command is marked as parallel:true - without metadata.name should execute all commands in composite command
/go/odo_1/tests/integration/cmd_dev_test.go:2642

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [27.550 seconds]
odo devfile deploy command tests deploying devfile with long-running exec when pod security is enforced as restricted should set securitycontext for podsecurity admission on job's pod template
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:676

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSSSSS
------------------------------
• [6.299 seconds]
odo describe component command tests when creating a component should not describe the component from another directory, with cluster
/go/odo_1/tests/integration/cmd_describe_component_test.go:289

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

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

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

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [4.171 seconds]
odo create/delete/list/set namespace/project tests create namespace should successfully create the namespace
/go/odo_1/tests/integration/cmd_namespace_test.go:54

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

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

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output

  [SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:1818 @ 11/11/23 14:17:40.543
------------------------------
• [26.779 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped the component is deleted while having access to the devfile.yaml when the component is deleted with --files should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:178

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [111.287 seconds]
odo logs command tests when component is created and odo logs is executed when running in both Dev and Deploy mode when --follow flag is specified should successfully follow logs of running component
/go/odo_1/tests/integration/cmd_logs_test.go:348

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [6.832 seconds]
odo deploy interactive command tests directory is not empty when there is a match from Alizer should display welcoming messages first
/go/odo_1/tests/integration/interactive_deploy_test.go:109

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  Spawning '/go/bin/odo deploy' from /tmp/4271056442
  << Captured StdOut/StdErr Output
------------------------------
• [47.547 seconds]
odo dev command tests when using a Devfile with no commands should start the Dev Session with --no-commands=false
/go/odo_1/tests/integration/cmd_dev_test.go:4921

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  Spawning '/go/bin/odo dev --random-ports' from /tmp/1609415586
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [56.571 seconds]
odo dev command tests when running odo dev with alternative commands - with metadata.name when running odo dev with a run command should execute the custom non-default run command successfully
/go/odo_1/tests/integration/cmd_dev_test.go:3181

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [3.981 seconds]
odo create/delete/list/set namespace/project tests when namespace is created with -w should list the new namespace when listing namespace
/go/odo_1/tests/integration/cmd_namespace_test.go:41

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [8.590 seconds]
odo describe component command tests should fail, with cluster
/go/odo_1/tests/integration/cmd_describe_component_test.go:89

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [7.377 seconds]
odo generic When deleting two project one after the other should be able to delete sequentially
/go/odo_1/tests/integration/generic_test.go:100

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  Spawning '/go/bin/odo deploy -v 4' from /tmp/1781587819
  << Captured StdOut/StdErr Output
------------------------------
• [14.485 seconds]
odo create/delete/list/set namespace/project tests delete project when force-deleting a valid project should successfully delete the project asynchronously
/go/odo_1/tests/integration/cmd_namespace_test.go:107

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [109.188 seconds]
odo dev command tests when a component is bootstrapped ensure that index information is updated
/go/odo_1/tests/integration/cmd_dev_test.go:305

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

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

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

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

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

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
S [5.083 seconds]
odo dev command tests when a component is bootstrapped when odo dev is executed and Ephemeral is set to false [BeforeEach] should have created resources
  [BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:649
  [It] /go/odo_1/tests/integration/cmd_dev_test.go:668

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output

  [SKIPPED] This is a OpenShift specific scenario, skipping
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:651 @ 11/11/23 14:18:50.434
------------------------------
SSSS
------------------------------
• [8.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 a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=false --running-in=dev should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:274

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [59.930 seconds]
odo dev command tests when adding local files to gitignore and running odo dev should not sync ignored files to the container
/go/odo_1/tests/integration/cmd_dev_test.go:1955

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [96.111 seconds]
odo dev command tests when a component is bootstrapped when a delay is necessary for the component to start and running odo dev should first fail then succeed querying endpoint
/go/odo_1/tests/integration/cmd_dev_test.go:789

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [3.696 seconds]
odo create/delete/list/set namespace/project tests set namespace should not succeed to set the namespace
/go/odo_1/tests/integration/cmd_namespace_test.go:162

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [3.991 seconds]
odo devfile deploy command tests when using a devfile.yaml containing two deploy commands should run odo deploy
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:244

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [116.704 seconds]
odo dev command tests when running odo dev and single env var is set - with metadata.name should be able to exec command
/go/odo_1/tests/integration/cmd_dev_test.go:1691

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [116.832 seconds]
odo dev command tests when running odo dev and single env var is set - without metadata.name should be able to exec command
/go/odo_1/tests/integration/cmd_dev_test.go:1691

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSSSSSSS
------------------------------
• [22.896 seconds]
odo dev command tests when running odo dev with alternative commands - with metadata.name when running odo dev with a run command should error out on an invalid command
/go/odo_1/tests/integration/cmd_dev_test.go:3150

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [47.283 seconds]
odo devfile deploy command tests deploying devfile with exec when the deploy command terminates abruptly; component name of at max(63) characters length when odo deploy command is run again should run successfully
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:595

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [3.658 seconds]
odo create/delete/list/set namespace/project tests create project should fail to create project
/go/odo_1/tests/integration/cmd_namespace_test.go:63

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [128.672 seconds]
odo dev command tests when running odo dev and composite command is used as a run command - without metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2709

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

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

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

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

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

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [57.917 seconds]
odo dev command tests when a component is bootstrapped should sync .git directory and subfiles with --sync-git-dir
/go/odo_1/tests/integration/cmd_dev_test.go:182

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
S [2.919 seconds]
odo dev command tests when running odo dev with devfile containing volume-component - without metadata.name [BeforeEach] should successfully use the volume components in container components
  [BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:2253
  [It] /go/odo_1/tests/integration/cmd_dev_test.go:2278

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output

  [SKIPPED] This is a OpenShift specific scenario, skipping
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:2255 @ 11/11/23 14:21:24.387
------------------------------
SSSSS
------------------------------
• [3.296 seconds]
odo devfile build-images command tests when using a Devfile with variable image names should build images with --var-file (push=false)
/go/odo_1/tests/integration/cmd_devfile_build_images_test.go:445

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [56.991 seconds]
odo dev command tests when Devfile contains metadata.projectType when running odo dev should set the correct value in labels of resources
/go/odo_1/tests/integration/cmd_dev_test.go:4089

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

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

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

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

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

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

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

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [57.622 seconds]
odo dev command tests when multiple projects are present - with metadata.name should sync to the correct dir in container
/go/odo_1/tests/integration/cmd_dev_test.go:2130

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

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

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [58.128 seconds]
odo dev command tests when a component is bootstrapped when pod security is enforced as restricted should set securitycontext for podsecurity admission
/go/odo_1/tests/integration/cmd_dev_test.go:414

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [116.045 seconds]
odo dev command tests when doing odo dev and there is a env variable with spaces - with metadata.name should be able to exec command
/go/odo_1/tests/integration/cmd_dev_test.go:1743

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [4.958 seconds]
odo create/delete/list/set namespace/project tests set namespace should successfully set the namespace
/go/odo_1/tests/integration/cmd_namespace_test.go:147

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

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

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

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

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

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

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [8.727 seconds]
odo devfile registry command tests when DevfileRegistriesList CRD is installed on cluster when CR for devfileregistrieslists is installed in namespace should list detailed information regarding nodejs when using an in-cluster registry
/go/odo_1/tests/integration/cmd_devfile_registry_test.go:244

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [5.096 seconds]
odo list with devfile listing non-odo managed components when an operator managed deployment(without instance and managed-by label) is deployed should not be listed in the odo list output
/go/odo_1/tests/integration/cmd_devfile_list_test.go:88

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [6.679 seconds]
odo describe component command tests when a non-odo application is present on the cluster should describe the component
/go/odo_1/tests/integration/cmd_describe_component_test.go:694

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [57.186 seconds]
odo dev command tests when setting git config and running odo dev should create vcs-uri annotation for the deployment when running odo dev
/go/odo_1/tests/integration/cmd_dev_test.go:2966

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [4.605 seconds]
odo dev command tests when running odo dev and prestart events are defined should not correctly execute PreStart commands
/go/odo_1/tests/integration/cmd_dev_test.go:2823

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

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

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [24.475 seconds]
odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a run command should error out on an invalid command
/go/odo_1/tests/integration/cmd_dev_test.go:3150

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [25.834 seconds]
odo delete command tests when deleting a component containing preStop event that is deployed with DEV and --files=true should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:517

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [7.106 seconds]
odo devfile init command tests when DevfileRegistriesList CRD is installed on cluster when CR for devfileregistrieslists is installed in namespace should be able to download devfile from the in-cluster registry
/go/odo_1/tests/integration/cmd_devfile_init_test.go:613

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [23.440 seconds]
odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a build command should error out on an invalid command
/go/odo_1/tests/integration/cmd_dev_test.go:3080

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
S [3.131 seconds]
odo dev command tests when a component is bootstrapped when odo dev is executed and Ephemeral is set to false [BeforeEach] when killing odo dev and running odo delete component --wait should have deleted all resources before returning
  [BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:560
  [It] /go/odo_1/tests/integration/cmd_dev_test.go:577

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output

  [SKIPPED] This is a OpenShift specific scenario, skipping
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:562 @ 11/11/23 14:24:54.943
------------------------------
• [81.789 seconds]
odo dev command tests 1. devfile contains composite apply command when odo dev is running should execute the composite apply commands successfully
/go/odo_1/tests/integration/cmd_dev_test.go:2388

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [3.925 seconds]
odo dev command with api server tests when the component is bootstrapped should fail if --random-ports and --api-server-port are used together
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:63

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  Spawning '/go/bin/odo dev --random-ports' from /tmp/2284097094
  << Captured StdOut/StdErr Output
------------------------------
• [84.433 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when running odo deploy should run odo dev successfully
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:161

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
S [3.155 seconds]
odo dev command tests when running odo dev with devfile containing volume-component - with metadata.name [BeforeEach] should successfully use the volume components in container components
  [BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:2253
  [It] /go/odo_1/tests/integration/cmd_dev_test.go:2278

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output

  [SKIPPED] This is a OpenShift specific scenario, skipping
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:2255 @ 11/11/23 14:25:35.389
------------------------------
• [3.979 seconds]
odo dev command tests when running applications listening on the container loopback interface should error out if using --ignore-localhost on any platform other than Podman
/go/odo_1/tests/integration/cmd_dev_test.go:4211

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output

  [SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:1818 @ 11/11/23 14:25:45.853
------------------------------
SSSSS
------------------------------
• [10.682 seconds]
odo create/delete/list/set namespace/project tests delete namespace when force-deleting a valid namespace should successfully delete the namespace asynchronously
/go/odo_1/tests/integration/cmd_namespace_test.go:107

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [2.868 seconds]
odo generic executing odo version command should only print client info when using --client flag
/go/odo_1/tests/integration/generic_test.go:201

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [56.700 seconds]
odo dev command tests when Devfile contains metadata.language when running odo dev should set the correct value in labels of resources
/go/odo_1/tests/integration/cmd_dev_test.go:4089

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

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

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output

  [SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:1818 @ 11/11/23 14:26:28.706
------------------------------
SS
------------------------------
• [9.363 seconds]
odo init interactive command tests when DevfileRegistriesList CRD is installed on cluster when CR for devfileregistrieslists is installed in namespace should download correct devfile from the first in-cluster registry
/go/odo_1/tests/integration/interactive_init_test.go:737

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  Spawning '/go/bin/odo init' from /tmp/1847687488
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [58.084 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [6.922 seconds]
odo describe component command tests when creating a component when running odo deploy to create ingress/routes should show the ingress with defaultBackend in odo describe component output
/go/odo_1/tests/integration/cmd_describe_component_test.go:552

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
  Progress Report for Ginkgo Process #9
  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: 2m2.11s)
      /go/odo_1/tests/integration/cmd_dev_test.go:1077
      In [BeforeEach] (Node Runtime: 2m0s)
        /go/odo_1/tests/integration/cmd_dev_test.go:1050

      Begin Captured GinkgoWriter Output >>
        ...
        [odo] I1111 14:26:39.570917    6712 exec.go:96]   sl  local_address                         remote_address                        st tx_queue rx_queue tr tm->when retrnsmt   uid  timeout inode ref pointer drops
        [odo] I1111 14:26:39.571344    6712 port.go:319] port 8080 not listening in container "runtime"
        [odo] I1111 14:26:47.373901    6712 exec.go:37] Executing command [/bin/sh -c cat /proc/net/tcp /proc/net/udp /proc/net/tcp6 /proc/net/udp6 || true] for pod: gvukvn-app-757dc787dd-hvz5s in container: runtime
        [odo] I1111 14:26:47.549795    6712 exec.go:96]   sl  local_address rem_address   st tx_queue rx_queue tr tm->when retrnsmt   uid  timeout inode                                                     
        [odo] I1111 14:26:47.549813    6712 exec.go:96]    0: FC7711AC:9E5E 23001068:01BB 06 00000000:00000000 03:00000C37 00000000     0        0 0 3 0000000000000000                                      
        [odo] I1111 14:26:47.551162    6712 exec.go:96]    sl  local_address rem_address   st tx_queue rx_queue tr tm->when retrnsmt   uid  timeout inode ref pointer drops            
        [odo] I1111 14:26:47.551272    6712 exec.go:96]   sl  local_address                         remote_address                        st tx_queue rx_queue tr tm->when retrnsmt   uid  timeout inode
        [odo] I1111 14:26:47.551280    6712 exec.go:96]    0: 00000000000000000000000000000000:0BB8 00000000000000000000000000000000:0000 0A 00000000:00000000 00:00000000 00000000  1001        0 29517534 1 0000000000000000 100 0 0 10 0
        [odo] I1111 14:26:47.551421    6712 exec.go:96]   sl  local_address                         remote_address                        st tx_queue rx_queue tr tm->when retrnsmt   uid  timeout inode ref pointer drops
        [odo] I1111 14:26:47.552402    6712 port.go:319] port 8080 not listening in container "runtime"
      << End Captured GinkgoWriter Output

      Spec Goroutine
      goroutine 865 [select]
        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc00003be30, {0x31064a8?, 0xc0010bc6f0}, 0x1, {0x0, 0x0, 0x0})
          /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538
        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc00003be30, {0x31064a8, 0xc0010bc6f0}, {0x0, 0x0, 0x0})
          /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145
        github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x2cfa0da, 0x8}, 0xc00046c360?, 0xc00046c340?, 0xc00154c630)
          /go/odo_1/tests/helper/helper_run.go:54
        github.com/redhat-developer/odo/tests/helper.(*DevSession).WaitSync(0xc000397320)
          /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({0x108af7e, 0xc000c1a8a0})
          /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
  ------------------------------
• [2.667 seconds]
odo devfile build-images command tests when using a Devfile with variable image names should build images with --var (push=false)
/go/odo_1/tests/integration/cmd_devfile_build_images_test.go:437

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [4.390 seconds]
odo devfile deploy command tests when recording telemetry data should record the telemetry data correctly
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:270

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [4.883 seconds]
odo create/delete/list/set namespace/project tests set project should successfully set the project
/go/odo_1/tests/integration/cmd_namespace_test.go:147

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
• [56.561 seconds]
odo dev command tests when Devfile contains neither metadata.language nor metadata.projectType when running odo dev should set the correct value in labels of resources
/go/odo_1/tests/integration/cmd_dev_test.go:4089

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSSSS
------------------------------
• [4.175 seconds]
odo create/delete/list/set namespace/project tests create namespace should fail to create namespace
/go/odo_1/tests/integration/cmd_namespace_test.go:63

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

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSSS
  ------------------------------
  Progress Report for Ginkgo Process #11
  Automatically polling progress:
    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 (Spec Runtime: 2m2.733s)
      /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:176
      In [BeforeEach] (Node Runtime: 2m0.001s)
        /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:169

      Begin Captured GinkgoWriter Output >>
        ...
        [odo]  ✗  Finished executing the application (command: run) [1m]
        [odo] I1111 14:27:29.408267    8597 exec.go:54] ExecuteCommand returned an an err: error while streaming command: error sending request: Post "https://c110.eu-de.containers.cloud.ibm.com:32062/api/v1/namespaces/cmd-devfile-deploy-test176khw/pods/dcoaba-app-757869575-gx56c/exec?command=%2Fbin%2Fsh&command=-c&command=cat+%2Fopt%2Fodo%2F.odo_cmd_run.pid+%7C%7C+true&container=runtime&stderr=true&stdout=true": dial tcp: lookup c110.eu-de.containers.cloud.ibm.com: operation was canceled. for command '[/bin/sh -c cat /opt/odo/.odo_cmd_run.pid || true]'
        [odo] stdout: []
        [odo] stderr: []
        [odo] I1111 14:27:29.408350    8597 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] I1111 14:27:29.549366    8597 delete.go:174] Ignoring resource: deployments/my-component; its mode(Deploy) does not match with the given mode(Dev)
        [odo] I1111 14:27:29.583482    8597 all.go:46] starting to concurrently query 98 APIs
        [odo] I1111 14:27:29.592897    8597 all.go:62] fired up all goroutines to query APIs
        [odo] I1111 14:27:29.990668    8597 all.go:67] all goroutines have returned in 407.189507ms
        [odo] I1111 14:27:29.990831    8597 all.go:76] query result: objects=382
      << End Captured GinkgoWriter Output

      Spec Goroutine
      goroutine 3317 [select]
        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc00047e850, {0x3106268?, 0xc0019420c0}, 0x1, {0x0, 0x0, 0x0})
          /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538
        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc00047e850, {0x3106268, 0xc0019420c0}, {0x0, 0x0, 0x0})
          /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145
        github.com/onsi/gomega/gexec.(*Session).Wait(0xc000e1fea8?, {0xc000146430?, 0x439d648?, 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..func9.6.2.4.1()
          /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:173
            | 	Expect(err).ShouldNot(HaveOccurred())
            | 	devSession.Stop()
            > 	devSession.WaitEnd()
            | })
            | 
        github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x108af7e, 0xc001890d20})
          /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
  ------------------------------
• [56.352 seconds]
odo dev command tests when running odo dev and composite command are nested - without metadata.name should execute all commands in composite commmand
/go/odo_1/tests/integration/cmd_dev_test.go:2674

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

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [4.495 seconds]
odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when an env.yaml file contains a non-current Project when running odo deploy when the env.yaml file still contains a non-current Project should delete the component in the current namespace
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:226

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
  Progress Report for Ginkgo Process #13
  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: 3m22.349s)
      /go/odo_1/tests/integration/cmd_dev_debug_test.go:288
      In [It] (Node Runtime: 2m0s)
        /go/odo_1/tests/integration/cmd_dev_debug_test.go:288
        At [By Step] cleaning up the resources on ending the session (Step Runtime: 27.084s)
          /go/odo_1/tests/integration/cmd_dev_debug_test.go:326

        Begin Captured GinkgoWriter Output >>
          ...
          [odo]  ✗  Finished executing the application (command: start-debug) [1m]
          [odo] I1111 14:27:51.805362    6991 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] I1111 14:27:51.806876    6991 implem.go:114] The path for preference file is /tmp/2441471630/preference.yaml
          [odo] I1111 14:27:51.807684    6991 segment.go:268] Checking telemetry enable status
          [odo] Cleaning resources, please wait
          [odo] I1111 14:27:51.807747    6991 segment.go:286] Sending telemetry disabled by env variable
          [odo] I1111 14:27:51.928024    6991 all.go:46] starting to concurrently query 98 APIs
          [odo] I1111 14:27:51.928145    6991 all.go:62] fired up all goroutines to query APIs
          [odo] I1111 14:27:52.818760    6991 all.go:67] all goroutines have returned in 890.915282ms
          [odo] I1111 14:27:52.818844    6991 all.go:76] query result: objects=397
        << End Captured GinkgoWriter Output

        Spec Goroutine
        goroutine 651 [select]
          github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0002d6000, {0x3106268?, 0xc000948510}, 0x1, {0x0, 0x0, 0x0})
            /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538
          github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0002d6000, {0x3106268, 0xc000948510}, {0x0, 0x0, 0x0})
            /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145
          github.com/onsi/gomega/gexec.(*Session).Wait(0xc00053d500?, {0xc001546070?, 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(0xc0000ce000, {0x2d5a346, 0x2f}, {0xc000fb9e70, 0x1, 0x0?})
            /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:309
          github.com/onsi/ginkgo/v2.By({0x2d5a346?, 0x0?}, {0xc000fb9e70?, 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
  ------------------------------
• [25.108 seconds]
odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="") should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:128

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [212.862 seconds]
odo dev debug command tests when a composite apply command is used as debug command should execute the composite apply commands successfully
/go/odo_1/tests/integration/cmd_dev_debug_test.go:288

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  Spawning '/go/bin/odo deploy' from /tmp/2438022591
  << Captured StdOut/StdErr Output
------------------------------
• [5.658 seconds]
odo describe component command tests when creating a component when running odo deploy to create ingress/routes should show the ingress/routes in odo describe component output
/go/odo_1/tests/integration/cmd_describe_component_test.go:552

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

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

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

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [57.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 while having access to the devfile.yaml should delete the appropriate resources
/go/odo_1/tests/integration/cmd_delete_test.go:428

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [4.595 seconds]
odo create/delete/list/set namespace/project tests create project should successfully create the project
/go/odo_1/tests/integration/cmd_namespace_test.go:54

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [8.164 seconds]
odo devfile deploy command tests deploying devfile with exec should not set securitycontext for podsecurity admission on job's pod template
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:601

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [46.800 seconds]
odo dev command tests when using a Devfile with no commands should start the Dev Session with --no-commands=true
/go/odo_1/tests/integration/cmd_dev_test.go:4921

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [5.272 seconds]
odo create/delete/list/set namespace/project tests list namespace should successfully list all the namespaces
/go/odo_1/tests/integration/cmd_namespace_test.go:221

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [5.702 seconds]
odo describe component command tests should fail, with default cluster mode
/go/odo_1/tests/integration/cmd_describe_component_test.go:70

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  Spawning '/go/bin/odo dev --random-ports' from /tmp/3595171173
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [117.477 seconds]
odo list with devfile when a component created in 'app' application when dev is running on cluster verifying the managedBy Version in the odo list output should show managedBy Version
/go/odo_1/tests/integration/cmd_devfile_list_test.go:181

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [5.578 seconds]
odo preference and config command tests when DevfileRegistriesList CRD is installed on cluster when CR for devfileregistrieslists is installed in namespace should fail to delete the in-cluster registry
/go/odo_1/tests/integration/cmd_pref_config_test.go:444

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [5.757 seconds]
odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy should succeed
/go/odo_1/tests/integration/cmd_devfile_deploy_test.go:143

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [5.693 seconds]
odo create/delete/list/set namespace/project tests list project should successfully list all the projects in JSON format
/go/odo_1/tests/integration/cmd_namespace_test.go:228

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [59.012 seconds]
odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a build command should execute the custom non-default build command successfully
/go/odo_1/tests/integration/cmd_dev_test.go:3112

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [2.985 seconds]
odo logs command tests when directory is empty should error
/go/odo_1/tests/integration/cmd_logs_test.go:86

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [48.833 seconds]
odo dev command tests when a component is bootstrapped when running with --no-commands (debug=false) should start the dev session
/go/odo_1/tests/integration/cmd_dev_test.go:268

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SSSS
------------------------------
• [26.705 seconds]
odo delete command tests when deleting a component containing preStop event that is deployed with DEV and --files=false should delete the component
/go/odo_1/tests/integration/cmd_delete_test.go:517

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

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  Spawning '/go/bin/odo deploy' from /tmp/152565167
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [24.401 seconds]
odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="dev") should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:128

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [58.230 seconds]
odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag should serve endpoints
/go/odo_1/tests/integration/cmd_dev_api_server_test.go:171

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [3.718 seconds]
odo dev command tests when a component is bootstrapped when a state file is not writable should fail running odo dev
/go/odo_1/tests/integration/cmd_dev_test.go:435

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output

  [SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:1818 @ 11/11/23 14:32:08.4
------------------------------
• [46.999 seconds]
odo dev command tests when a component is bootstrapped when running with --no-commands (debug=true) should start the dev session
/go/odo_1/tests/integration/cmd_dev_test.go:268

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
S•
------------------------------
• [69.382 seconds]
odo dev debug command tests when a composite command is used as debug command - with metadata.name should run successfully
/go/odo_1/tests/integration/cmd_dev_debug_test.go:225

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [21.435 seconds]
odo dev interactive command tests when a component is bootstrapped should sync files when p is pressed
/go/odo_1/tests/integration/interactive_dev_test.go:211

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  Spawning '/go/bin/odo dev --random-ports --no-watch' from /tmp/2304929032
  << Captured StdOut/StdErr Output
------------------------------
  Progress Report for Ginkgo Process #11
  Automatically polling progress:
    odo dev command tests Devfile contains pod-overrides and container-overrides attributes should override the content in the pod it creates for the component on the cluster (Spec Runtime: 2m2.864s)
      /go/odo_1/tests/integration/cmd_dev_test.go:4146
      In [It] (Node Runtime: 2m0s)
        /go/odo_1/tests/integration/cmd_dev_test.go:4146

      Begin Captured GinkgoWriter Output >>
        ...
        [odo] Cleaning resources, please wait
        [odo] I1111 14:32:10.164116   18482 exec.go:54] ExecuteCommand returned an an err: error while streaming command: error sending request: Post "https://c110.eu-de.containers.cloud.ibm.com:32062/api/v1/namespaces/cmd-dev-test4146xmm/pods/esrfwy-app-5456f88b6-t4nsr/exec?command=%2Fbin%2Fsh&command=-c&command=cat+%2Fopt%2Fodo%2F.odo_cmd_run.pid+%7C%7C+true&container=runtime&stderr=true&stdout=true": dial tcp: lookup c110.eu-de.containers.cloud.ibm.com: operation was canceled. for command '[/bin/sh -c cat /opt/odo/.odo_cmd_run.pid || true]'
        [odo] stdout: []
        [odo] stderr: []
        [odo]  ✗  Finished executing the application (command: run) [1m]
        [odo] I1111 14:32:10.164188   18482 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] I1111 14:32:10.242089   18482 all.go:46] starting to concurrently query 98 APIs
        [odo] I1111 14:32:10.242213   18482 all.go:62] fired up all goroutines to query APIs
        [odo] I1111 14:32:11.285413   18482 all.go:67] all goroutines have returned in 1.043334016s
        [odo] I1111 14:32:11.285979   18482 all.go:76] query result: objects=362
      << End Captured GinkgoWriter Output

      Spec Goroutine
      goroutine 31623 [select]
        github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc00047ed90, {0x3106268?, 0xc0019a1638}, 0x1, {0x0, 0x0, 0x0})
          /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538
        github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc00047ed90, {0x3106268, 0xc0019a1638}, {0x0, 0x0, 0x0})
          /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145
        github.com/onsi/gomega/gexec.(*Session).Wait(0xc001f25d50?, {0xc001f09e00?, 0x2cfbeb7?, 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({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
  ------------------------------
• [83.073 seconds]
odo dev command tests when starting with Devfile with autoBuild or deployByDefault components when running odo dev with some components referenced in the Devfile should create the appropriate resources
/go/odo_1/tests/integration/cmd_dev_test.go:4579

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

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

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------
• [57.956 seconds]
odo dev command tests when a component is bootstrapped when odo dev is executed when odo dev is stopped should delete the component from the platform
/go/odo_1/tests/integration/cmd_dev_test.go:507

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

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

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

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

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

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

  Captured StdOut/StdErr Output >>
  Using Devfile Registry URL at: "https://registry.stage.devfile.io"
  << Captured StdOut/StdErr Output
------------------------------

Ran 410 of 956 Specs in 1289.138 seconds
SUCCESS! -- 410 Passed | 0 Failed | 0 Pending | 546 Skipped


Ginkgo ran 1 suite in 22m39.132504332s
Test Suite Passed