Error from server (NotFound): namespaces "devfile-proxy" not found
Using Devfile proxy:
go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=e11c63fb6" ./cmd/odo/
go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo  --randomize-all --slow-spec-threshold=120s -timeout 14400s --no-color -nodes=16 --junit-report="test-integration.xml" --label-filter="!unauth && !nocluster && !podman" tests/integration
Running Suite: Integration Suite - /go/odo_1/tests/integration
==============================================================
Random Seed: 1674839148 - will randomize all specs

Will run 411 of 742 specs
Running in parallel across 16 processes
SSSSSSS•••SS•SSSSS•SS
------------------------------
• [26.799 seconds]
odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile (custom naming strategy: "any string")
/go/odo_1/tests/integration/interactive_add_binding_test.go:180

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo add binding' from /tmp/730882129
  << End Captured StdOut/StdErr Output
------------------------------
• [39.834 seconds]
odo add binding interactive command tests when the component is bootstrapped when binding to a service in a different namespace should error out if service is not found in the namespace selected
/go/odo_1/tests/integration/interactive_add_binding_test.go:242

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo add binding' from /tmp/982378098
  << End Captured StdOut/StdErr Output
------------------------------
••••••S•S
------------------------------
• [6.448 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

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo deploy' from /tmp/3030569017
  << End Captured StdOut/StdErr Output
------------------------------
S••••S•••SSSSS•SSS•S•••SSSS•••S••••
------------------------------
• [15.483 seconds]
odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile (custom naming strategy: "{ .name | upper }")
/go/odo_1/tests/integration/interactive_add_binding_test.go:180

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo add binding' from /tmp/1017021137
  << End Captured StdOut/StdErr Output
------------------------------
S•••SS••••••SSSS•••S•••S•S••S•S••••••SS••••S••••SSSSS•SS•S••S•S••SSS••SSSS••SS••SS•S•SS••SS•SS••S
------------------------------
• [14.489 seconds]
odo add binding interactive command tests when running a deployment should successfully add binding without devfile (custom naming strategy: "{ .name | upper }")
/go/odo_1/tests/integration/interactive_add_binding_test.go:463

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo add binding' from /tmp/20638509
  << End Captured StdOut/StdErr Output
------------------------------
••SS••
------------------------------
• [4.966 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

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo deploy -v 4' from /tmp/2269224995
  << End Captured StdOut/StdErr Output
------------------------------
••SS•SSSS•••••••••S•SS
------------------------------
• [12.280 seconds]
odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile ("uppercase" as naming strategy)
/go/odo_1/tests/integration/interactive_add_binding_test.go:131

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo add binding' from /tmp/791049519
  << End Captured StdOut/StdErr Output
------------------------------
•••SS••S•S•
------------------------------
• [13.125 seconds]
odo add binding interactive command tests when running a deployment should successfully add binding without devfile (naming strategy: "uppercase")
/go/odo_1/tests/integration/interactive_add_binding_test.go:378

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo add binding' from /tmp/356005081
  << End Captured StdOut/StdErr Output
------------------------------
••S•S•••S
------------------------------
• [12.935 seconds]
odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile (custom naming strategy: "")
/go/odo_1/tests/integration/interactive_add_binding_test.go:180

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo add binding' from /tmp/219040486
  << End Captured StdOut/StdErr Output
------------------------------
••••••S
------------------------------
S [SKIPPED] [8.994 seconds]
odo dev command tests
/go/odo_1/tests/integration/cmd_dev_test.go:34
  when a component is bootstrapped and pushed
  /go/odo_1/tests/integration/cmd_dev_test.go:64
    when odo dev is executed and Ephemeral is set to false [BeforeEach]
    /go/odo_1/tests/integration/cmd_dev_test.go:372
      should have created resources
      /go/odo_1/tests/integration/cmd_dev_test.go:391

  Begin Captured GinkgoWriter Output >>
    Created dir: /tmp/977358324
    Created dir: /tmp/3088811828
    Setting KUBECONFIG=/tmp/3088811828/config
    Creating a new project: cmd-dev-test391xlh
    Running kubectl with args [kubectl create namespace cmd-dev-test391xlh] and odo env: []
    [kubectl] namespace/cmd-dev-test391xlh created
    Running kubectl with args [kubectl config set-context --current --namespace cmd-dev-test391xlh] and odo env: []
    [kubectl] Context "odo-test-kubernetes-cluster/c8giauof0f337j4pe5u0/admin" modified.
    Running kubectl with args [kubectl get namespaces] and odo env: []
    [kubectl] NAME                                   STATUS        AGE
    [kubectl] cmd-add-binding-test151lyn             Terminating   29s
    [kubectl] cmd-add-binding-test151mmb             Terminating   19s
    [kubectl] cmd-delete-test357zec                  Terminating   66s
    [kubectl] cmd-delete-test624mef                  Active        29s
    [kubectl] cmd-delete-test624qtr                  Active        11s
    [kubectl] cmd-delete-test669duc                  Active        36s
    [kubectl] cmd-describe-list-binding-test548cks   Terminating   109s
    [kubectl] cmd-describe-list-binding-test548irb   Active        9s
    [kubectl] cmd-describe-list-binding-test581cly   Active        11s
    [kubectl] cmd-describe-list-binding-test581srr   Terminating   98s
    [kubectl] cmd-describe-list-binding-test626cwv   Terminating   86s
    [kubectl] cmd-describe-list-binding-test626ezu   Active        66s
    [kubectl] cmd-describe-list-binding-test95nnm    Active        6s
    [kubectl] cmd-describe-list-binding-test95yoh    Terminating   8s
    [kubectl] cmd-dev-test1474ppw                    Active        22s
    [kubectl] cmd-dev-test1507bhp                    Active        39s
    [kubectl] cmd-dev-test1721jef                    Active        54s
    [kubectl] cmd-dev-test2086kuq                    Active        38s
    [kubectl] cmd-dev-test2302ikk                    Active        23s
    [kubectl] cmd-dev-test2444stp                    Active        70s
    [kubectl] cmd-dev-test391xlh                     Active        2s
    [kubectl] cmd-devfile-deploy-test318wct          Terminating   24s
    [kubectl] cmd-devfile-deploy-test444zix          Active        4s
    [kubectl] default                                Active        329d
    [kubectl] ibm-cert-store                         Active        329d
    [kubectl] ibm-operators                          Active        329d
    [kubectl] ibm-system                             Active        329d
    [kubectl] interactive-add-binding-test180qdv     Terminating   18s
    [kubectl] interactive-add-binding-test463nzp     Terminating   101s
    [kubectl] kube-node-lease                        Active        329d
    [kubectl] kube-public                            Active        329d
    [kubectl] kube-system                            Active        329d
    [kubectl] olm                                    Active        219d
    [kubectl] operators                              Active        219d
    [kubectl] osag-namespace                         Active        79d
    Running kubectl with args [kubectl create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n cmd-dev-test391xlh] and odo env: []
    [kubectl] configmap/config-map-for-cleanup created
    Current working dir: /go/odo_1/tests/integration
    Running odo with args [odo preference remove registry DefaultDevfileRegistry -f] and odo env: []
    [odo] I0127 17:12:31.101537   24541 implem.go:109] The path for preference file is /tmp/3088811828/preference.yaml
    [odo] Successfully removed registry
    [odo] I0127 17:12:31.110876   24541 util.go:810] Cached response used.
    [odo] I0127 17:12:31.113612   24541 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :)
    Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: []
    [odo] I0127 17:12:31.874393   24579 implem.go:109] The path for preference file is /tmp/3088811828/preference.yaml
    [odo] New registry successfully added
    [odo] I0127 17:12:31.876182   24579 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :)
    Setting current dir to: /tmp/977358324
    Running odo with args [odo init --name plhtkk --devfile-path /go/odo_1/tests/examples/source/devfiles/nodejs/devfile.yaml] and odo env: []
    [odo] I0127 17:12:32.697259   24591 util.go:810] Cached response used.
    [odo] I0127 17:12:32.696725   24591 implem.go:109] The path for preference file is /tmp/3088811828/preference.yaml
    [odo] I0127 17:12:32.698033   24591 util.go:201] path /tmp/977358324/devfile.yaml doesn't exist, skipping it
    [odo] I0127 17:12:32.698106   24591 util.go:201] path /tmp/977358324/.devfile.yaml doesn't exist, skipping it
    [odo] I0127 17:12:32.698170   24591 util.go:201] path /tmp/977358324/devfile.yaml doesn't exist, skipping it
    [odo]   __
    [odo]  /  \__     Initializing a new component
    [odo]  \__/  \    
    [odo]  /  \__/    odo version: v3.6.0
    [odo]  \__/
    [odo] 
    [odo]  •  Copying devfile from "/go/odo_1/tests/examples/source/devfiles/nodejs/devfile.yaml"  ...
    [odo] I0127 17:12:32.700798   24591 context.go:159] absolute devfile path: '/tmp/977358324/devfile.yaml'
    [odo] I0127 17:12:32.700807   24591 context.go:110] absolute devfile path: '/tmp/977358324/devfile.yaml'
    [odo] ↵
 ✓  Copying devfile from "/go/odo_1/tests/examples/source/devfiles/nodejs/devfile.yaml" [1ms]
    [odo] I0127 17:12:32.701548   24591 content.go:48] converted devfile YAML to JSON
    [odo] I0127 17:12:32.701605   24591 apiVersion.go:60] devfile schemaVersion: '2.0.0'
    [odo] I0127 17:12:32.701616   24591 helper.go:56] devfile apiVersion '2.0.0' is supported
    [odo] I0127 17:12:32.751512   24591 schema.go:61] validated devfile schema
    [odo] I0127 17:12:32.770837   24591 writer.go:55] devfile yaml created at: 'devfile.yaml'
    [odo] 
    [odo] Your new component 'plhtkk' is ready in the current directory.
    [odo] To start editing your component, use 'odo dev' and open this folder in your favorite IDE.
    [odo] Changes will be directly reflected on the cluster.
    [odo] I0127 17:12:32.773934   24591 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :)
    Deleting project: cmd-dev-test391xlh
    Running kubectl with args [kubectl delete namespaces cmd-dev-test391xlh --wait=false] and odo env: []
    [kubectl] namespace "cmd-dev-test391xlh" deleted
    Setting current dir to: /go/odo_1/tests/integration
    Deleting dir: /tmp/977358324
    Deleting dir: /tmp/3088811828
  << End Captured GinkgoWriter Output

  This is a OpenShift specific scenario, skipping
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:374
------------------------------
S•S•
------------------------------
• [8.820 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

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo deploy' from /tmp/242398605
  << End Captured StdOut/StdErr Output
------------------------------
•••SSS•SSSS•S•S•S•S•SSS•••SSS••
------------------------------
• [SLOW TEST] [128.337 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:2444
------------------------------
S••S•SSS••SSSS•SS••SSS•S•S•
------------------------------
• [12.197 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:155

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo dev --random-ports' from /tmp/600695183
  << End Captured StdOut/StdErr Output
------------------------------
••S•••••S••S•SS••••SSSS•S••
------------------------------
• [18.068 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:194

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo dev --random-ports --no-watch' from /tmp/3318315843
  << End Captured StdOut/StdErr Output
------------------------------
•S
------------------------------
S [SKIPPED] [4.288 seconds]
odo dev command tests
/go/odo_1/tests/integration/cmd_dev_test.go:34
  when running odo dev with devfile containing volume-component - with metadata.name [BeforeEach]
  /go/odo_1/tests/integration/cmd_dev_test.go:1563
    should successfully use the volume components in container components
    /go/odo_1/tests/integration/cmd_dev_test.go:1588

  Begin Captured GinkgoWriter Output >>
    Created dir: /tmp/495368211
    Created dir: /tmp/2559039181
    Setting KUBECONFIG=/tmp/2559039181/config
    Creating a new project: cmd-dev-test1588rtp
    Running kubectl with args [kubectl create namespace cmd-dev-test1588rtp] and odo env: []
    [kubectl] namespace/cmd-dev-test1588rtp created
    Running kubectl with args [kubectl config set-context --current --namespace cmd-dev-test1588rtp] and odo env: []
    [kubectl] Context "odo-test-kubernetes-cluster/c8giauof0f337j4pe5u0/admin" modified.
    Running kubectl with args [kubectl get namespaces] and odo env: []
    [kubectl] NAME                                   STATUS        AGE
    [kubectl] cmd-add-binding-test164hsu             Terminating   17s
    [kubectl] cmd-add-binding-test260awd             Active        3s
    [kubectl] cmd-add-binding-test260guu             Active        14s
    [kubectl] cmd-delete-test271fvn                  Terminating   64s
    [kubectl] cmd-delete-test357qci                  Active        4s
    [kubectl] cmd-delete-test624tqr                  Active        36s
    [kubectl] cmd-delete-test713ifn                  Terminating   26s
    [kubectl] cmd-describe-list-binding-test581lau   Active        46s
    [kubectl] cmd-describe-list-binding-test626efl   Terminating   101s
    [kubectl] cmd-describe-list-binding-test626fup   Terminating   72s
    [kubectl] cmd-describe-list-binding-test626hbk   Terminating   91s
    [kubectl] cmd-describe-list-binding-test626pda   Terminating   85s
    [kubectl] cmd-describe-list-binding-test626xdr   Active        49s
    [kubectl] cmd-dev-debug-test128igy               Active        65s
    [kubectl] cmd-dev-test1018cwh                    Active        37s
    [kubectl] cmd-dev-test1287nen                    Active        41s
    [kubectl] cmd-dev-test1368vjt                    Active        25s
    [kubectl] cmd-dev-test1407fjw                    Active        5s
    [kubectl] cmd-dev-test1588rtp                    Active        1s
    [kubectl] cmd-dev-test2758vuc                    Active        53s
    [kubectl] cmd-dev-test2956sol                    Active        67s
    [kubectl] cmd-logs-test115mup                    Active        8s
    [kubectl] cmd-logs-test217fsl                    Active        35s
    [kubectl] default                                Active        329d
    [kubectl] ibm-cert-store                         Active        329d
    [kubectl] ibm-operators                          Active        329d
    [kubectl] ibm-system                             Active        329d
    [kubectl] interactive-dev-test194xcj             Terminating   20s
    [kubectl] kube-node-lease                        Active        329d
    [kubectl] kube-public                            Active        329d
    [kubectl] kube-system                            Active        329d
    [kubectl] olm                                    Active        219d
    [kubectl] operators                              Active        219d
    [kubectl] osag-namespace                         Active        79d
    Running kubectl with args [kubectl create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n cmd-dev-test1588rtp] and odo env: []
    [kubectl] configmap/config-map-for-cleanup created
    Current working dir: /go/odo_1/tests/integration
    Running odo with args [odo preference remove registry DefaultDevfileRegistry -f] and odo env: []
    [odo] I0127 17:15:00.991351   29587 implem.go:109] The path for preference file is /tmp/2559039181/preference.yaml
    [odo] I0127 17:15:00.991608   29587 util.go:776] HTTPGetRequest: https://raw.githubusercontent.com/redhat-developer/odo/main/build/VERSION
    [odo] Successfully removed registry
    [odo] I0127 17:15:00.993451   29587 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :)
    Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: []
    [odo] I0127 17:15:01.295280   29605 implem.go:109] The path for preference file is /tmp/2559039181/preference.yaml
    [odo] I0127 17:15:01.295545   29605 util.go:797] Response will be cached in /tmp/odohttpcache for 1h0m0s
    [odo] I0127 17:15:01.296360   29605 util.go:810] Cached response used.
    [odo] New registry successfully added
    [odo] I0127 17:15:01.297139   29605 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :)
    Setting current dir to: /tmp/495368211
    Deleting project: cmd-dev-test1588rtp
    Running kubectl with args [kubectl delete namespaces cmd-dev-test1588rtp --wait=false] and odo env: []
    [kubectl] namespace "cmd-dev-test1588rtp" deleted
    Setting current dir to: /go/odo_1/tests/integration
    Deleting dir: /tmp/495368211
    Deleting dir: /tmp/2559039181
  << End Captured GinkgoWriter Output

  This is a OpenShift specific scenario, skipping
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:1565
------------------------------
S•SS•••••••SS•
------------------------------
• [13.562 seconds]
odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile ("lowercase" as naming strategy)
/go/odo_1/tests/integration/interactive_add_binding_test.go:131

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo add binding' from /tmp/1876892478
  << End Captured StdOut/StdErr Output
------------------------------
S••••SS•SS•••
------------------------------
• [20.535 seconds]
odo add binding interactive command tests when running a deployment should successfully add binding without devfile (naming strategy: "lowercase")
/go/odo_1/tests/integration/interactive_add_binding_test.go:378

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo add binding' from /tmp/3319021671
  << End Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [34.501 seconds]
odo add binding interactive command tests when running a deployment when binding to a service in a different namespace should successfully add binding without devfile
/go/odo_1/tests/integration/interactive_add_binding_test.go:591

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo add binding' from /tmp/2896853088
  << End Captured StdOut/StdErr Output
------------------------------
S
------------------------------
• [20.798 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

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo dev --random-ports -v 4' from /tmp/2093550953
  << End Captured StdOut/StdErr Output
------------------------------
•S•S•SSSSSS••S••S•••S•S
------------------------------
• [14.672 seconds]
odo add binding interactive command tests when running a deployment should successfully add binding without devfile (custom naming strategy: "any string")
/go/odo_1/tests/integration/interactive_add_binding_test.go:463

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo add binding' from /tmp/1717557457
  << End Captured StdOut/StdErr Output
------------------------------
SS•S••••S••SSSSS•
------------------------------
• [13.060 seconds]
odo add binding interactive command tests when running a deployment should successfully add binding without devfile (naming strategy: "none")
/go/odo_1/tests/integration/interactive_add_binding_test.go:378

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo add binding' from /tmp/3240764941
  << End Captured StdOut/StdErr Output
------------------------------
•SS•S••S••S
------------------------------
• [25.679 seconds]
odo add binding interactive command tests when running a deployment when binding to a service in a different namespace should error out if service is not found in the namespace selected
/go/odo_1/tests/integration/interactive_add_binding_test.go:577

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo add binding' from /tmp/693530764
  << End Captured StdOut/StdErr Output
------------------------------
S••SS••SS•SS•••SSS••SS••••S••SSS••SS•S•S•••••SSS•S•SS••SSS••••S•••••SS•••S•••••SS•S•••S•••SS•S•••SS
------------------------------
• [12.383 seconds]
odo add binding interactive command tests when running a deployment should successfully add binding without devfile (default naming strategy)
/go/odo_1/tests/integration/interactive_add_binding_test.go:311

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo add binding' from /tmp/2921117022
  << End Captured StdOut/StdErr Output
------------------------------
••SS••SS••••SS••••
------------------------------
• [18.089 seconds]
odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile ("none" as naming strategy)
/go/odo_1/tests/integration/interactive_add_binding_test.go:131

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo add binding' from /tmp/1528180108
  << End Captured StdOut/StdErr Output
------------------------------
• [7.837 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

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo deploy' from /tmp/1889399870
  << End Captured StdOut/StdErr Output
------------------------------
SSSS••
------------------------------
• [18.124 seconds]
odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile (Bind as Environment Variables)
/go/odo_1/tests/integration/interactive_add_binding_test.go:73

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo add binding' from /tmp/3313101243
  << End Captured StdOut/StdErr Output
------------------------------
•••S•SS•S•S•••S•S•
------------------------------
• [28.407 seconds]
odo add binding interactive command tests when the component is bootstrapped when binding to a service in a different namespace should successfully add binding to the devfile
/go/odo_1/tests/integration/interactive_add_binding_test.go:257

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo add binding' from /tmp/1374526421
  << End Captured StdOut/StdErr Output
------------------------------
•••S•SSS•S••••
------------------------------
• [19.930 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:73

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo dev --random-ports' from /tmp/2629427232
  << End Captured StdOut/StdErr Output
------------------------------
SSS••••S
------------------------------
• [14.424 seconds]
odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile (Bind as Files)
/go/odo_1/tests/integration/interactive_add_binding_test.go:101

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo add binding' from /tmp/1183280220
  << End Captured StdOut/StdErr Output
------------------------------
•S•S•SS•S•••••SSSS••SSS•SS•SSS
------------------------------
• [23.664 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:106

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo dev --random-ports' from /tmp/219937072
  << End Captured StdOut/StdErr Output
------------------------------
SS•S••S
------------------------------
• [SLOW TEST] [129.939 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:2499
------------------------------
SS
------------------------------
• [22.432 seconds]
odo add binding interactive command tests when running a deployment should successfully add binding without devfile (custom naming strategy: "")
/go/odo_1/tests/integration/interactive_add_binding_test.go:463

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo add binding' from /tmp/1989651072
  << End Captured StdOut/StdErr Output
------------------------------
•S•SS•••••S•SS••SSSS•SS••S
------------------------------
S [SKIPPED] [3.920 seconds]
odo dev command tests
/go/odo_1/tests/integration/cmd_dev_test.go:34
  when a component is bootstrapped and pushed
  /go/odo_1/tests/integration/cmd_dev_test.go:64
    when odo dev is executed and Ephemeral is set to false [BeforeEach]
    /go/odo_1/tests/integration/cmd_dev_test.go:313
      when killing odo dev and running odo delete component --wait
      /go/odo_1/tests/integration/cmd_dev_test.go:323
        should have deleted all resources before returning
        /go/odo_1/tests/integration/cmd_dev_test.go:330

  Begin Captured GinkgoWriter Output >>
    Created dir: /tmp/1568493891
    Created dir: /tmp/326958299
    Setting KUBECONFIG=/tmp/326958299/config
    Creating a new project: cmd-dev-test330pdd
    Running kubectl with args [kubectl create namespace cmd-dev-test330pdd] and odo env: []
    [kubectl] namespace/cmd-dev-test330pdd created
    Running kubectl with args [kubectl config set-context --current --namespace cmd-dev-test330pdd] and odo env: []
    [kubectl] Context "odo-test-kubernetes-cluster/c8giauof0f337j4pe5u0/admin" modified.
    Running kubectl with args [kubectl get namespaces] and odo env: []
    [kubectl] NAME                                   STATUS        AGE
    [kubectl] cmd-add-binding-test278qpm             Active        49s
    [kubectl] cmd-add-binding-test278sgi             Active        67s
    [kubectl] cmd-delete-test298bnw                  Active        12s
    [kubectl] cmd-delete-test357fvg                  Active        54s
    [kubectl] cmd-delete-test374pju                  Active        2s
    [kubectl] cmd-delete-test624aey                  Terminating   66s
    [kubectl] cmd-delete-test669esw                  Terminating   40s
    [kubectl] cmd-describe-component-test504qxt      Active        4s
    [kubectl] cmd-describe-component-test665wgr      Terminating   64s
    [kubectl] cmd-describe-list-binding-test548kje   Terminating   76s
    [kubectl] cmd-describe-list-binding-test548mkc   Active        50s
    [kubectl] cmd-describe-list-binding-test548sqj   Active        44s
    [kubectl] cmd-describe-list-binding-test581yrv   Terminating   106s
    [kubectl] cmd-describe-list-binding-test626wdx   Active        21s
    [kubectl] cmd-describe-list-binding-test626xra   Active        4s
    [kubectl] cmd-dev-debug-test290nrg               Active        37s
    [kubectl] cmd-dev-test1187qls                    Terminating   75s
    [kubectl] cmd-dev-test1275wnb                    Active        19s
    [kubectl] cmd-dev-test1326bbf                    Active        26s
    [kubectl] cmd-dev-test2381zmr                    Active        41s
    [kubectl] cmd-dev-test330pdd                     Active        1s
    [kubectl] cmd-dev-test801osw                     Active        53s
    [kubectl] cmd-dev-test80dpv                      Active        70s
    [kubectl] cmd-dev-test966gjf                     Active        29s
    [kubectl] default                                Active        329d
    [kubectl] ibm-cert-store                         Active        329d
    [kubectl] ibm-operators                          Active        329d
    [kubectl] ibm-system                             Active        329d
    [kubectl] kube-node-lease                        Active        329d
    [kubectl] kube-public                            Active        329d
    [kubectl] kube-system                            Active        329d
    [kubectl] olm                                    Active        219d
    [kubectl] operators                              Active        219d
    [kubectl] osag-namespace                         Active        79d
    Running kubectl with args [kubectl create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n cmd-dev-test330pdd] and odo env: []
    [kubectl] configmap/config-map-for-cleanup created
    Current working dir: /go/odo_1/tests/integration
    Running odo with args [odo preference remove registry DefaultDevfileRegistry -f] and odo env: []
    [odo] I0127 17:22:12.095541   14851 util.go:797] Response will be cached in /tmp/odohttpcache for 1h0m0s
    [odo] I0127 17:22:12.096512   14851 util.go:810] Cached response used.
    [odo] I0127 17:22:12.098995   14851 implem.go:109] The path for preference file is /tmp/326958299/preference.yaml
    [odo] Successfully removed registry
    [odo] I0127 17:22:12.100706   14851 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :)
    Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: []
    [odo] I0127 17:22:12.387878   14864 implem.go:109] The path for preference file is /tmp/326958299/preference.yaml
    [odo] I0127 17:22:12.388050   14864 util.go:797] Response will be cached in /tmp/odohttpcache for 1h0m0s
    [odo] I0127 17:22:12.389091   14864 util.go:810] Cached response used.
    [odo] New registry successfully added
    [odo] I0127 17:22:12.389767   14864 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :)
    Setting current dir to: /tmp/1568493891
    Running odo with args [odo init --name hnzhep --devfile-path /go/odo_1/tests/examples/source/devfiles/nodejs/devfile.yaml] and odo env: []
    [odo] I0127 17:22:12.641445   14881 util.go:810] Cached response used.
    [odo] I0127 17:22:12.641169   14881 implem.go:109] The path for preference file is /tmp/326958299/preference.yaml
    [odo] I0127 17:22:12.642403   14881 util.go:201] path /tmp/1568493891/devfile.yaml doesn't exist, skipping it
    [odo] I0127 17:22:12.642474   14881 util.go:201] path /tmp/1568493891/.devfile.yaml doesn't exist, skipping it
    [odo] I0127 17:22:12.642570   14881 util.go:201] path /tmp/1568493891/devfile.yaml doesn't exist, skipping it
    [odo]   __
    [odo]  /  \__     Initializing a new component
    [odo]  \__/  \    
    [odo]  /  \__/    odo version: v3.6.0
    [odo]  \__/
    [odo] 
    [odo]  •  Copying devfile from "/go/odo_1/tests/examples/source/devfiles/nodejs/devfile.yaml"  ...
    [odo] ↵
 ✓  Copying devfile from "/go/odo_1/tests/examples/source/devfiles/nodejs/devfile.yaml" [3ms]
    [odo] I0127 17:22:12.647779   14881 context.go:159] absolute devfile path: '/tmp/1568493891/devfile.yaml'
    [odo] I0127 17:22:12.647792   14881 context.go:110] absolute devfile path: '/tmp/1568493891/devfile.yaml'
    [odo] I0127 17:22:12.648646   14881 content.go:48] converted devfile YAML to JSON
    [odo] I0127 17:22:12.648739   14881 apiVersion.go:60] devfile schemaVersion: '2.0.0'
    [odo] I0127 17:22:12.648757   14881 helper.go:56] devfile apiVersion '2.0.0' is supported
    [odo] I0127 17:22:12.668216   14881 schema.go:61] validated devfile schema
    [odo] I0127 17:22:12.674067   14881 writer.go:55] devfile yaml created at: 'devfile.yaml'
    [odo] 
    [odo] Your new component 'hnzhep' is ready in the current directory.
    [odo] To start editing your component, use 'odo dev' and open this folder in your favorite IDE.
    [odo] Changes will be directly reflected on the cluster.
    [odo] I0127 17:22:12.674989   14881 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :)
    Deleting project: cmd-dev-test330pdd
    Running kubectl with args [kubectl delete namespaces cmd-dev-test330pdd --wait=false] and odo env: []
    [kubectl] namespace "cmd-dev-test330pdd" deleted
    Setting current dir to: /go/odo_1/tests/integration
    Deleting dir: /tmp/1568493891
    Deleting dir: /tmp/326958299
  << End Captured GinkgoWriter Output

  This is a OpenShift specific scenario, skipping
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:315
------------------------------
•SS•••SSS••SS•SS•S•S•••••••
------------------------------
S [SKIPPED] [3.365 seconds]
odo dev command tests
/go/odo_1/tests/integration/cmd_dev_test.go:34
  when running odo dev with devfile containing volume-component - without metadata.name [BeforeEach]
  /go/odo_1/tests/integration/cmd_dev_test.go:1563
    should successfully use the volume components in container components
    /go/odo_1/tests/integration/cmd_dev_test.go:1588

  Begin Captured GinkgoWriter Output >>
    Created dir: /tmp/2419744415
    Created dir: /tmp/2793238079
    Setting KUBECONFIG=/tmp/2793238079/config
    Creating a new project: cmd-dev-test1588sjc
    Running kubectl with args [kubectl create namespace cmd-dev-test1588sjc] and odo env: []
    [kubectl] namespace/cmd-dev-test1588sjc created
    Running kubectl with args [kubectl config set-context --current --namespace cmd-dev-test1588sjc] and odo env: []
    [kubectl] Context "odo-test-kubernetes-cluster/c8giauof0f337j4pe5u0/admin" modified.
    Running kubectl with args [kubectl get namespaces] and odo env: []
    [kubectl] NAME                                   STATUS        AGE
    [kubectl] cmd-add-binding-test278qpm             Terminating   98s
    [kubectl] cmd-add-binding-test278sgi             Terminating   116s
    [kubectl] cmd-add-binding-test42xya              Terminating   22s
    [kubectl] cmd-delete-test298bnw                  Terminating   61s
    [kubectl] cmd-delete-test357fvg                  Active        103s
    [kubectl] cmd-delete-test374pju                  Active        51s
    [kubectl] cmd-delete-test512fqz                  Active        8s
    [kubectl] cmd-describe-component-test504qxt      Active        53s
    [kubectl] cmd-describe-list-binding-test548mkc   Terminating   99s
    [kubectl] cmd-describe-list-binding-test581glg   Active        12s
    [kubectl] cmd-describe-list-binding-test581rmh   Active        41s
    [kubectl] cmd-describe-list-binding-test581yxk   Active        48s
    [kubectl] cmd-describe-list-binding-test626qwq   Active        46s
    [kubectl] cmd-describe-list-binding-test626wdx   Terminating   70s
    [kubectl] cmd-describe-list-binding-test626xra   Active        53s
    [kubectl] cmd-dev-debug-test290nrg               Terminating   86s
    [kubectl] cmd-dev-test1204cbu                    Active        7s
    [kubectl] cmd-dev-test1275wnb                    Active        68s
    [kubectl] cmd-dev-test1297twb                    Active        5s
    [kubectl] cmd-dev-test1588sjc                    Active        1s
    [kubectl] cmd-dev-test1626saq                    Active        22s
    [kubectl] cmd-dev-test2288hdt                    Active        34s
    [kubectl] cmd-dev-test2605qut                    Active        7s
    [kubectl] cmd-devfile-deploy-test256pfy          Terminating   36s
    [kubectl] cmd-devfile-list-test393vjh            Active        31s
    [kubectl] cmd-logs-test91wvk                     Active        32s
    [kubectl] cmd-namespace-test82lxq                Terminating   19s
    [kubectl] default                                Active        329d
    [kubectl] ibm-cert-store                         Active        329d
    [kubectl] ibm-operators                          Active        329d
    [kubectl] ibm-system                             Active        329d
    [kubectl] kube-node-lease                        Active        329d
    [kubectl] kube-public                            Active        329d
    [kubectl] kube-system                            Active        329d
    [kubectl] olm                                    Active        219d
    [kubectl] operators                              Active        219d
    [kubectl] osag-namespace                         Active        79d
    Running kubectl with args [kubectl create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n cmd-dev-test1588sjc] and odo env: []
    [kubectl] configmap/config-map-for-cleanup created
    Current working dir: /go/odo_1/tests/integration
    Running odo with args [odo preference remove registry DefaultDevfileRegistry -f] and odo env: []
    [odo] I0127 17:23:01.467932   16699 implem.go:109] The path for preference file is /tmp/2793238079/preference.yaml
    [odo] Successfully removed registry
    [odo] I0127 17:23:01.469754   16699 util.go:810] Cached response used.
    [odo] I0127 17:23:01.474797   16699 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :)
    Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: []
    [odo] I0127 17:23:01.917995   16721 implem.go:109] The path for preference file is /tmp/2793238079/preference.yaml
    [odo] I0127 17:23:01.921655   16721 util.go:776] HTTPGetRequest: https://raw.githubusercontent.com/redhat-developer/odo/main/build/VERSION
    [odo] I0127 17:23:01.931836   16721 util.go:797] Response will be cached in /tmp/odohttpcache for 1h0m0s
    [odo] I0127 17:23:01.932450   16721 util.go:810] Cached response used.
    [odo] New registry successfully added
    [odo] I0127 17:23:01.932549   16721 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :)
    Setting current dir to: /tmp/2419744415
    Deleting project: cmd-dev-test1588sjc
    Running kubectl with args [kubectl delete namespaces cmd-dev-test1588sjc --wait=false] and odo env: []
    [kubectl] namespace "cmd-dev-test1588sjc" deleted
    Setting current dir to: /go/odo_1/tests/integration
    Deleting dir: /tmp/2419744415
    Deleting dir: /tmp/2793238079
  << End Captured GinkgoWriter Output

  This is a OpenShift specific scenario, skipping
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:1565
------------------------------
••SSSS••SSS•SSS•SS
------------------------------
• [SLOW TEST] [121.150 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 without --files 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:357
------------------------------
S•S•SS•SSSSS••SSSSSS
------------------------------
S [SKIPPED] [3.139 seconds]
odo dev command tests
/go/odo_1/tests/integration/cmd_dev_test.go:34
  when a component is bootstrapped and pushed
  /go/odo_1/tests/integration/cmd_dev_test.go:64
    when odo dev is executed and Ephemeral is set to false [BeforeEach]
    /go/odo_1/tests/integration/cmd_dev_test.go:313
      when stopping odo dev normally
      /go/odo_1/tests/integration/cmd_dev_test.go:346
        should have deleted all resources before returning
        /go/odo_1/tests/integration/cmd_dev_test.go:352

  Begin Captured GinkgoWriter Output >>
    Created dir: /tmp/1481602290
    Created dir: /tmp/2377857652
    Setting KUBECONFIG=/tmp/2377857652/config
    Creating a new project: cmd-dev-test352hlv
    Running kubectl with args [kubectl create namespace cmd-dev-test352hlv] and odo env: []
    [kubectl] namespace/cmd-dev-test352hlv created
    Running kubectl with args [kubectl config set-context --current --namespace cmd-dev-test352hlv] and odo env: []
    [kubectl] Context "odo-test-kubernetes-cluster/c8giauof0f337j4pe5u0/admin" modified.
    Running kubectl with args [kubectl get namespaces] and odo env: []
    [kubectl] NAME                                   STATUS        AGE
    [kubectl] cmd-add-binding-test42xya              Terminating   53s
    [kubectl] cmd-delete-test298mnn                  Active        2s
    [kubectl] cmd-delete-test624gsa                  Active        9s
    [kubectl] cmd-describe-component-test343lty      Active        29s
    [kubectl] cmd-describe-list-binding-test581glg   Active        43s
    [kubectl] cmd-describe-list-binding-test581rmh   Terminating   72s
    [kubectl] cmd-describe-list-binding-test581yxk   Terminating   79s
    [kubectl] cmd-describe-list-binding-test626wdx   Terminating   101s
    [kubectl] cmd-describe-list-binding-test626xra   Terminating   84s
    [kubectl] cmd-describe-list-binding-test626yrd   Active        28s
    [kubectl] cmd-dev-test1132wwu                    Active        12s
    [kubectl] cmd-dev-test1204cbu                    Active        38s
    [kubectl] cmd-dev-test1297twb                    Active        36s
    [kubectl] cmd-dev-test1440zmv                    Active        19s
    [kubectl] cmd-dev-test1507sol                    Active        16s
    [kubectl] cmd-dev-test1626saq                    Active        53s
    [kubectl] cmd-dev-test2288hdt                    Terminating   65s
    [kubectl] cmd-dev-test2605qut                    Active        38s
    [kubectl] cmd-dev-test352hlv                     Active        1s
    [kubectl] cmd-dev-test698nlv                     Active        21s
    [kubectl] cmd-dev-test698ywh                     Active        20s
    [kubectl] cmd-devfile-deploy-test211wkb          Terminating   7s
    [kubectl] cmd-devfile-list-test393vjh            Active        62s
    [kubectl] cmd-logs-test91wvk                     Terminating   63s
    [kubectl] default                                Active        329d
    [kubectl] ibm-cert-store                         Active        329d
    [kubectl] ibm-operators                          Active        329d
    [kubectl] ibm-system                             Active        329d
    [kubectl] kube-node-lease                        Active        329d
    [kubectl] kube-public                            Active        329d
    [kubectl] kube-system                            Active        329d
    [kubectl] olm                                    Active        219d
    [kubectl] operators                              Active        219d
    [kubectl] osag-namespace                         Active        79d
    Running kubectl with args [kubectl create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n cmd-dev-test352hlv] and odo env: []
    [kubectl] configmap/config-map-for-cleanup created
    Current working dir: /go/odo_1/tests/integration
    Running odo with args [odo preference remove registry DefaultDevfileRegistry -f] and odo env: []
    [odo] I0127 17:23:31.963382   17910 implem.go:109] The path for preference file is /tmp/2377857652/preference.yaml
    [odo] I0127 17:23:31.964413   17910 util.go:797] Response will be cached in /tmp/odohttpcache for 1h0m0s
    [odo] Successfully removed registry
    [odo] I0127 17:23:31.965101   17910 util.go:810] Cached response used.
    [odo] I0127 17:23:31.965267   17910 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :)
    Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: []
    [odo] I0127 17:23:32.169011   17919 implem.go:109] The path for preference file is /tmp/2377857652/preference.yaml
    [odo] I0127 17:23:32.170671   17919 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :)
    [odo] New registry successfully added
    Setting current dir to: /tmp/1481602290
    Running odo with args [odo init --name buoimt --devfile-path /go/odo_1/tests/examples/source/devfiles/nodejs/devfile.yaml] and odo env: []
    [odo] I0127 17:23:32.370899   17925 util.go:776] HTTPGetRequest: https://raw.githubusercontent.com/redhat-developer/odo/main/build/VERSION
    [odo] I0127 17:23:32.370944   17925 implem.go:109] The path for preference file is /tmp/2377857652/preference.yaml
    [odo] I0127 17:23:32.373271   17925 util.go:797] Response will be cached in /tmp/odohttpcache for 1h0m0s
    [odo] I0127 17:23:32.373517   17925 util.go:201] path /tmp/1481602290/devfile.yaml doesn't exist, skipping it
    [odo] I0127 17:23:32.373711   17925 util.go:201] path /tmp/1481602290/.devfile.yaml doesn't exist, skipping it
    [odo] I0127 17:23:32.374175   17925 util.go:201] path /tmp/1481602290/devfile.yaml doesn't exist, skipping it
    [odo] I0127 17:23:32.374445   17925 util.go:810] Cached response used.
    [odo]   __
    [odo]  /  \__     Initializing a new component
    [odo]  \__/  \    
    [odo]  /  \__/    odo version: v3.6.0
    [odo]  \__/
    [odo] 
    [odo]  •  Copying devfile from "/go/odo_1/tests/examples/source/devfiles/nodejs/devfile.yaml"  ...
    [odo] ↵
 ✓  Copying devfile from "/go/odo_1/tests/examples/source/devfiles/nodejs/devfile.yaml" [2ms]
    [odo] I0127 17:23:32.380032   17925 context.go:159] absolute devfile path: '/tmp/1481602290/devfile.yaml'
    [odo] I0127 17:23:32.380291   17925 context.go:110] absolute devfile path: '/tmp/1481602290/devfile.yaml'
    [odo] I0127 17:23:32.382021   17925 content.go:48] converted devfile YAML to JSON
    [odo] I0127 17:23:32.382574   17925 apiVersion.go:60] devfile schemaVersion: '2.0.0'
    [odo] I0127 17:23:32.382797   17925 helper.go:56] devfile apiVersion '2.0.0' is supported
    [odo] I0127 17:23:32.388926   17925 schema.go:61] validated devfile schema
    [odo] I0127 17:23:32.392375   17925 writer.go:55] devfile yaml created at: 'devfile.yaml'
    [odo] 
    [odo] Your new component 'buoimt' is ready in the current directory.
    [odo] To start editing your component, use 'odo dev' and open this folder in your favorite IDE.
    [odo] Changes will be directly reflected on the cluster.
    [odo] I0127 17:23:32.401791   17925 odo.go:88] Could not get the latest release information in time. Never mind, exiting gracefully :)
    Deleting project: cmd-dev-test352hlv
    Running kubectl with args [kubectl delete namespaces cmd-dev-test352hlv --wait=false] and odo env: []
    [kubectl] namespace "cmd-dev-test352hlv" deleted
    Setting current dir to: /go/odo_1/tests/integration
    Deleting dir: /tmp/1481602290
    Deleting dir: /tmp/2377857652
  << End Captured GinkgoWriter Output

  This is a OpenShift specific scenario, skipping
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:315
------------------------------
SSS•SSSSS••••••••••••••••

Ran 406 of 742 Specs in 1069.645 seconds
SUCCESS! -- 406 Passed | 0 Failed | 0 Pending | 336 Skipped


Ginkgo ran 1 suite in 18m51.839112262s
Test Suite Passed