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=d9f25dc60" ./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: 1679400676 - will randomize all specs

Will run 435 of 777 specs
Running in parallel across 16 processes
SSSSSSSSSSSSSSSSS••••S•S•••S•SS••SS•SS•S
------------------------------
S [SKIPPED] [6.307 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:326
      when stopping odo dev normally
      /go/odo_1/tests/integration/cmd_dev_test.go:359
        should have deleted all resources before returning
        /go/odo_1/tests/integration/cmd_dev_test.go:365

  Begin Captured GinkgoWriter Output >>
    Created dir: /tmp/60183833
    Created dir: /tmp/1446678955
    Setting KUBECONFIG=/tmp/1446678955/config
    Creating a new project: cmd-dev-test365ypx
    Running kubectl with args [kubectl create namespace cmd-dev-test365ypx] and odo env: []
    [kubectl] namespace/cmd-dev-test365ypx created
    Running kubectl with args [kubectl config set-context --current --namespace cmd-dev-test365ypx] 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-test292vow             Terminating   29s
    [kubectl] cmd-delete-test299qbm                  Active        29s
    [kubectl] cmd-delete-test329ixm                  Active        8s
    [kubectl] cmd-delete-test513kwb                  Terminating   19s
    [kubectl] cmd-describe-list-binding-test742vvh   Active        11s
    [kubectl] cmd-describe-list-binding-test787bcf   Active        6s
    [kubectl] cmd-describe-list-binding-test787zjf   Active        29s
    [kubectl] cmd-dev-test109bbi                     Active        12s
    [kubectl] cmd-dev-test1393sti                    Active        29s
    [kubectl] cmd-dev-test1864gwk                    Active        30s
    [kubectl] cmd-dev-test2510nhc                    Active        6s
    [kubectl] cmd-dev-test3231gzg                    Active        30s
    [kubectl] cmd-dev-test3247vyc                    Terminating   10s
    [kubectl] cmd-dev-test3285jds                    Active        6s
    [kubectl] cmd-dev-test365ypx                     Active        2s
    [kubectl] cmd-devfile-deploy-test117hqx          Active        30s
    [kubectl] cmd-devfile-deploy-test385hfu          Terminating   13s
    [kubectl] cmd-devfile-deploy-test559aee          Active        28s
    [kubectl] cmd-logs-test140dmf                    Active        28s
    [kubectl] default                                Active        382d
    [kubectl] ibm-cert-store                         Active        382d
    [kubectl] ibm-operators                          Active        382d
    [kubectl] ibm-system                             Active        382d
    [kubectl] interactive-add-binding-test378apq     Active        5s
    [kubectl] kube-node-lease                        Active        382d
    [kubectl] kube-public                            Active        382d
    [kubectl] kube-system                            Active        382d
    [kubectl] olm                                    Active        272d
    [kubectl] operators                              Active        272d
    [kubectl] osag-namespace                         Active        132d
    Running kubectl with args [kubectl create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n cmd-dev-test365ypx] 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] I0321 12:12:48.413248   13428 implem.go:110] The path for preference file is /tmp/1446678955/preference.yaml
    [odo] Successfully removed registry
    Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: []
    [odo] I0321 12:12:48.619541   13441 implem.go:110] The path for preference file is /tmp/1446678955/preference.yaml
    [odo] New registry successfully added
    Setting current dir to: /tmp/60183833
    Running odo with args [odo init --name stejad --devfile-path /go/odo_1/tests/examples/source/devfiles/nodejs/devfile.yaml] and odo env: []
    [odo] I0321 12:12:49.307662   13467 implem.go:110] The path for preference file is /tmp/1446678955/preference.yaml
    [odo] I0321 12:12:49.309664   13467 util.go:198] path /tmp/60183833/devfile.yaml doesn't exist, skipping it
    [odo] I0321 12:12:49.309776   13467 util.go:198] path /tmp/60183833/.devfile.yaml doesn't exist, skipping it
    [odo] I0321 12:12:49.309829   13467 util.go:198] path /tmp/60183833/devfile.yaml doesn't exist, skipping it
    [odo]   __
    [odo]  /  \__     Initializing a new component
    [odo]  \__/  \    
    [odo]  /  \__/    odo version: v3.8.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" [1ms]
    [odo] I0321 12:12:49.313033   13467 context.go:159] absolute devfile path: '/tmp/60183833/devfile.yaml'
    [odo] I0321 12:12:49.313169   13467 context.go:110] absolute devfile path: '/tmp/60183833/devfile.yaml'
    [odo] I0321 12:12:49.314890   13467 content.go:48] converted devfile YAML to JSON
    [odo] I0321 12:12:49.314959   13467 apiVersion.go:60] devfile schemaVersion: '2.0.0'
    [odo] I0321 12:12:49.315386   13467 helper.go:56] devfile apiVersion '2.0.0' is supported
    [odo] I0321 12:12:49.322244   13467 schema.go:61] validated devfile schema
    [odo] I0321 12:12:49.336561   13467 writer.go:55] devfile yaml created at: 'devfile.yaml'
    [odo] 
    [odo] Your new component 'stejad' 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.
    Deleting project: cmd-dev-test365ypx
    Running kubectl with args [kubectl delete namespaces cmd-dev-test365ypx --wait=false] and odo env: []
    [kubectl] namespace "cmd-dev-test365ypx" deleted
    Setting current dir to: /go/odo_1/tests/integration
    Deleting dir: /tmp/60183833
    Deleting dir: /tmp/1446678955
  << End Captured GinkgoWriter Output

  This is a OpenShift specific scenario, skipping
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:328
------------------------------
• [16.596 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/2982005705
  << End Captured StdOut/StdErr Output
------------------------------
SSS••SSS•SSSS••S•SSS••••SSSSSSSS••S•••••SS•S••SSSSSS
------------------------------
• [13.751 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/679143437
  << End Captured StdOut/StdErr Output
------------------------------
S•••S•S•••
------------------------------
• [18.761 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/464029776
  << End Captured StdOut/StdErr Output
------------------------------
SS•SS•SS•SSSS•••••SSS•
------------------------------
• [10.546 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/2016564329
  << End Captured StdOut/StdErr Output
------------------------------
• [SLOW TEST] [130.189 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:2510
------------------------------
S•••
------------------------------
• [8.723 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/915091164
  << End Captured StdOut/StdErr Output
------------------------------
•••S•SS•S•••SSSS
------------------------------
• [SLOW TEST] [141.390 seconds]
odo dev command tests when Starting a PostgreSQL service 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:1229
------------------------------
•••••S•
------------------------------
• [4.456 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/3047867638
  << End Captured StdOut/StdErr Output
------------------------------
SS••••••••SSS•••SS•S•S••S••SS•SSSSSS•SSSSS••
------------------------------
S [SKIPPED] [2.872 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:385
      should have created resources
      /go/odo_1/tests/integration/cmd_dev_test.go:404

  Begin Captured GinkgoWriter Output >>
    Created dir: /tmp/4294279796
    Created dir: /tmp/4167532042
    Setting KUBECONFIG=/tmp/4167532042/config
    Creating a new project: cmd-dev-test404axp
    Running kubectl with args [kubectl create namespace cmd-dev-test404axp] and odo env: []
    [kubectl] namespace/cmd-dev-test404axp created
    Running kubectl with args [kubectl config set-context --current --namespace cmd-dev-test404axp] 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-test278qyd             Active        27s
    [kubectl] cmd-add-binding-test278vdf             Active        17s
    [kubectl] cmd-delete-test299czs                  Active        13s
    [kubectl] cmd-delete-test513ixw                  Terminating   8s
    [kubectl] cmd-delete-test670yhu                  Active        17s
    [kubectl] cmd-delete-test670zxf                  Terminating   40s
    [kubectl] cmd-describe-component-test294lts      Active        47s
    [kubectl] cmd-describe-component-test294uoi      Active        50s
    [kubectl] cmd-describe-list-binding-test742jyg   Active        8s
    [kubectl] cmd-describe-list-binding-test742tnk   Terminating   91s
    [kubectl] cmd-describe-list-binding-test742yjw   Active        31s
    [kubectl] cmd-describe-list-binding-test787rky   Terminating   103s
    [kubectl] cmd-dev-test1532wbo                    Active        56s
    [kubectl] cmd-dev-test2305nxl                    Active        29s
    [kubectl] cmd-dev-test2319trk                    Active        22s
    [kubectl] cmd-dev-test2366bgc                    Active        27s
    [kubectl] cmd-dev-test3231sqn                    Active        18s
    [kubectl] cmd-dev-test404axp                     Active        1s
    [kubectl] cmd-dev-test90wfx                      Active        32s
    [kubectl] cmd-devfile-deploy-test184sdb          Active        1s
    [kubectl] cmd-logs-test275diw                    Terminating   85s
    [kubectl] cmd-namespace-test196mhn               Terminating   5s
    [kubectl] default                                Active        382d
    [kubectl] ibm-cert-store                         Active        382d
    [kubectl] ibm-operators                          Active        382d
    [kubectl] ibm-system                             Active        382d
    [kubectl] interactive-dev-test40mdx              Active        18s
    [kubectl] kube-node-lease                        Active        382d
    [kubectl] kube-public                            Active        382d
    [kubectl] kube-system                            Active        382d
    [kubectl] olm                                    Active        272d
    [kubectl] operators                              Active        272d
    [kubectl] osag-namespace                         Active        132d
    Running kubectl with args [kubectl create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n cmd-dev-test404axp] 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] I0321 12:16:31.845006   21466 implem.go:110] The path for preference file is /tmp/4167532042/preference.yaml
    [odo] Successfully removed registry
    Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: []
    [odo] I0321 12:16:32.158347   21481 implem.go:110] The path for preference file is /tmp/4167532042/preference.yaml
    [odo] New registry successfully added
    Setting current dir to: /tmp/4294279796
    Running odo with args [odo init --name bqdihv --devfile-path /go/odo_1/tests/examples/source/devfiles/nodejs/devfile.yaml] and odo env: []
    [odo] I0321 12:16:32.386083   21512 implem.go:110] The path for preference file is /tmp/4167532042/preference.yaml
    [odo] I0321 12:16:32.387145   21512 util.go:198] path /tmp/4294279796/devfile.yaml doesn't exist, skipping it
    [odo] I0321 12:16:32.387211   21512 util.go:198] path /tmp/4294279796/.devfile.yaml doesn't exist, skipping it
    [odo] I0321 12:16:32.387265   21512 util.go:198] path /tmp/4294279796/devfile.yaml doesn't exist, skipping it
    [odo]   __
    [odo]  /  \__     Initializing a new component
    [odo]  \__/  \    
    [odo]  /  \__/    odo version: v3.8.0
    [odo]  \__/
    [odo] 
    [odo]  •  Copying devfile from "/go/odo_1/tests/examples/source/devfiles/nodejs/devfile.yaml"  ...
    [odo] I0321 12:16:32.388879   21512 context.go:159] absolute devfile path: '/tmp/4294279796/devfile.yaml'
    [odo] I0321 12:16:32.388888   21512 context.go:110] absolute devfile path: '/tmp/4294279796/devfile.yaml'
    [odo] ↵
 ✓  Copying devfile from "/go/odo_1/tests/examples/source/devfiles/nodejs/devfile.yaml" 
    [odo] I0321 12:16:32.389415   21512 content.go:48] converted devfile YAML to JSON
    [odo] I0321 12:16:32.389462   21512 apiVersion.go:60] devfile schemaVersion: '2.0.0'
    [odo] I0321 12:16:32.389468   21512 helper.go:56] devfile apiVersion '2.0.0' is supported
    [odo] I0321 12:16:32.400924   21512 schema.go:61] validated devfile schema
    [odo] I0321 12:16:32.405441   21512 writer.go:55] devfile yaml created at: 'devfile.yaml'
    [odo] 
    [odo] Your new component 'bqdihv' 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.
    Deleting project: cmd-dev-test404axp
    Running kubectl with args [kubectl delete namespaces cmd-dev-test404axp --wait=false] and odo env: []
    [kubectl] namespace "cmd-dev-test404axp" deleted
    Setting current dir to: /go/odo_1/tests/integration
    Deleting dir: /tmp/4294279796
    Deleting dir: /tmp/4167532042
  << End Captured GinkgoWriter Output

  This is a OpenShift specific scenario, skipping
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:387
------------------------------
SS•
------------------------------
• [21.552 seconds]
odo dev interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile successfully even with -v flag
/go/odo_1/tests/integration/interactive_dev_test.go:40

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo dev --random-ports -v 4' from /tmp/1406651806
  << End Captured StdOut/StdErr Output
------------------------------
S•••••S•S•••S•S••S••S••S•••S
------------------------------
• [11.488 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/558413303
  << End Captured StdOut/StdErr Output
------------------------------
•••S•S•S•S•SSS••••S•SSSSS•SS•S
------------------------------
• [13.098 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/2123196928
  << End Captured StdOut/StdErr Output
------------------------------
•S••S•S•••
------------------------------
• [29.138 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/640385954
  << End Captured StdOut/StdErr Output
------------------------------
SS•
------------------------------
• [15.152 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/1049238079
  << End Captured StdOut/StdErr Output
------------------------------
S••S
------------------------------
• [12.444 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

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo dev --random-ports' from /tmp/1607535803
  << End Captured StdOut/StdErr Output
------------------------------
SS•S••••••S•S•••S•••S••S•
------------------------------
• [11.181 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/3522412626
  << End Captured StdOut/StdErr Output
------------------------------
•••••S•S•S••SS••S•••SS•SS•S•••
------------------------------
• [12.696 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/816211163
  << End Captured StdOut/StdErr Output
------------------------------
SS•••SS••SS••S•S
------------------------------
• [5.105 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/3625792213
  << End Captured StdOut/StdErr Output
------------------------------
S••S•S
------------------------------
S [SKIPPED] [3.009 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:326
      when killing odo dev and running odo delete component --wait
      /go/odo_1/tests/integration/cmd_dev_test.go:336
        should have deleted all resources before returning
        /go/odo_1/tests/integration/cmd_dev_test.go:343

  Begin Captured GinkgoWriter Output >>
    Created dir: /tmp/83779081
    Created dir: /tmp/2161540161
    Setting KUBECONFIG=/tmp/2161540161/config
    Creating a new project: cmd-dev-test343orc
    Running kubectl with args [kubectl create namespace cmd-dev-test343orc] and odo env: []
    [kubectl] namespace/cmd-dev-test343orc created
    Running kubectl with args [kubectl config set-context --current --namespace cmd-dev-test343orc] 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-delete-test177sxs                  Active        1s
    [kubectl] cmd-delete-test299hca                  Terminating   63s
    [kubectl] cmd-delete-test358jbn                  Terminating   32s
    [kubectl] cmd-delete-test358lke                  Active        53s
    [kubectl] cmd-delete-test513wob                  Terminating   10s
    [kubectl] cmd-delete-test625hgo                  Active        14s
    [kubectl] cmd-delete-test625lgp                  Active        55s
    [kubectl] cmd-delete-test625wvu                  Terminating   89s
    [kubectl] cmd-describe-component-test217xwe      Terminating   5s
    [kubectl] cmd-describe-component-test423xrt      Active        26s
    [kubectl] cmd-describe-list-binding-test787xhk   Active        56s
    [kubectl] cmd-dev-test1043gjj                    Active        38s
    [kubectl] cmd-dev-test1212ege                    Active        52s
    [kubectl] cmd-dev-test1750idf                    Active        0s
    [kubectl] cmd-dev-test1995jjf                    Active        14s
    [kubectl] cmd-dev-test2109xjq                    Active        38s
    [kubectl] cmd-dev-test2575jfq                    Active        79s
    [kubectl] cmd-dev-test3231boo                    Active        45s
    [kubectl] cmd-dev-test343orc                     Active        1s
    [kubectl] cmd-dev-test71yfl                      Terminating   62s
    [kubectl] cmd-dev-test826zft                     Active        49s
    [kubectl] cmd-dev-test991fpi                     Active        4s
    [kubectl] cmd-logs-test194dxb                    Terminating   25s
    [kubectl] default                                Active        382d
    [kubectl] ibm-cert-store                         Active        382d
    [kubectl] ibm-operators                          Active        382d
    [kubectl] ibm-system                             Active        382d
    [kubectl] interactive-add-binding-test463emt     Terminating   67s
    [kubectl] interactive-deploy-test40eae           Terminating   6s
    [kubectl] kube-node-lease                        Active        382d
    [kubectl] kube-public                            Active        382d
    [kubectl] kube-system                            Active        382d
    [kubectl] olm                                    Active        272d
    [kubectl] operators                              Active        272d
    [kubectl] osag-namespace                         Active        132d
    Running kubectl with args [kubectl create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n cmd-dev-test343orc] 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] I0321 12:20:18.507269   31632 implem.go:110] The path for preference file is /tmp/2161540161/preference.yaml
    [odo] Successfully removed registry
    Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: []
    [odo] I0321 12:20:18.772437   31656 implem.go:110] The path for preference file is /tmp/2161540161/preference.yaml
    [odo] New registry successfully added
    Setting current dir to: /tmp/83779081
    Running odo with args [odo init --name moktjc --devfile-path /go/odo_1/tests/examples/source/devfiles/nodejs/devfile.yaml] and odo env: []
    [odo] I0321 12:20:19.019548   31681 implem.go:110] The path for preference file is /tmp/2161540161/preference.yaml
    [odo] I0321 12:20:19.020533   31681 util.go:198] path /tmp/83779081/devfile.yaml doesn't exist, skipping it
    [odo] I0321 12:20:19.020627   31681 util.go:198] path /tmp/83779081/.devfile.yaml doesn't exist, skipping it
    [odo] I0321 12:20:19.020694   31681 util.go:198] path /tmp/83779081/devfile.yaml doesn't exist, skipping it
    [odo]   __
    [odo]  /  \__     Initializing a new component
    [odo]  \__/  \    
    [odo]  /  \__/    odo version: v3.8.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" 
    [odo] I0321 12:20:19.023156   31681 context.go:159] absolute devfile path: '/tmp/83779081/devfile.yaml'
    [odo] I0321 12:20:19.023177   31681 context.go:110] absolute devfile path: '/tmp/83779081/devfile.yaml'
    [odo] I0321 12:20:19.023791   31681 content.go:48] converted devfile YAML to JSON
    [odo] I0321 12:20:19.023884   31681 apiVersion.go:60] devfile schemaVersion: '2.0.0'
    [odo] I0321 12:20:19.023911   31681 helper.go:56] devfile apiVersion '2.0.0' is supported
    [odo] I0321 12:20:19.054470   31681 schema.go:61] validated devfile schema
    [odo] I0321 12:20:19.067307   31681 writer.go:55] devfile yaml created at: 'devfile.yaml'
    [odo] 
    [odo] Your new component 'moktjc' 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.
    Deleting project: cmd-dev-test343orc
    Running kubectl with args [kubectl delete namespaces cmd-dev-test343orc --wait=false] and odo env: []
    [kubectl] namespace "cmd-dev-test343orc" deleted
    Setting current dir to: /go/odo_1/tests/integration
    Deleting dir: /tmp/83779081
    Deleting dir: /tmp/2161540161
  << End Captured GinkgoWriter Output

  This is a OpenShift specific scenario, skipping
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:328
------------------------------
••S•••S••S•SSSS••SSSSS•SSSS•••SS••S•••S•••SSS••••SS•SSS•S•SSSS•S••••S••S•S••SS•S••••SSS••••S
------------------------------
• [18.088 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:206

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo dev --random-ports --no-watch' from /tmp/2210816416
  << End Captured StdOut/StdErr Output
------------------------------
S•••S•SS••SSSS•••S•S•S•SS•S•S•S••••••••S
------------------------------
• [23.398 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/679344210
  << End Captured StdOut/StdErr Output
------------------------------
S••••
------------------------------
• [13.115 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/1835585875
  << End Captured StdOut/StdErr Output
------------------------------
SSSS••••S••
------------------------------
• [11.179 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/1302121795
  << End Captured StdOut/StdErr Output
------------------------------
••••S•S•S
------------------------------
• [20.241 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

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo dev --random-ports' from /tmp/1070969698
  << End Captured StdOut/StdErr Output
------------------------------
S••SS•S•S
------------------------------
• [11.610 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/2090034836
  << End Captured StdOut/StdErr Output
------------------------------
SS•SS•••••••
------------------------------
• [11.100 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/3899275875
  << End Captured StdOut/StdErr Output
------------------------------
SS
------------------------------
• [9.077 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:600

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo init' from /tmp/4053543654
  << End Captured StdOut/StdErr Output
------------------------------
••••
------------------------------
• [21.572 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

  Begin Captured StdOut/StdErr Output >>
    Spawning '/go/bin/odo dev --random-ports' from /tmp/1973596117
  << End Captured StdOut/StdErr Output
------------------------------
•SS•••SS••SSSS•S•SSS•SSSS••••SS••••S•S•S•
------------------------------
• [10.586 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/3892003374
  << End Captured StdOut/StdErr Output
------------------------------
••SSSS•
------------------------------
• [17.745 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/3504438488
  << End Captured StdOut/StdErr Output
------------------------------
•••S••••••SSSSS••••SS•S•SS••SSS••S•
------------------------------
• [SLOW TEST] [126.607 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:2455
------------------------------
•S•S••SS••••S••••SSSSS••S•••SSS•S••
------------------------------
• [15.113 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/2677962164
  << End Captured StdOut/StdErr Output
------------------------------
SSS
------------------------------
S [SKIPPED] [4.194 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:1588
    should successfully use the volume components in container components
    /go/odo_1/tests/integration/cmd_dev_test.go:1613

  Begin Captured GinkgoWriter Output >>
    Created dir: /tmp/346195959
    Created dir: /tmp/1344430531
    Setting KUBECONFIG=/tmp/1344430531/config
    Creating a new project: cmd-dev-test1613lit
    Running kubectl with args [kubectl create namespace cmd-dev-test1613lit] and odo env: []
    [kubectl] namespace/cmd-dev-test1613lit created
    Running kubectl with args [kubectl config set-context --current --namespace cmd-dev-test1613lit] 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-delete-test276ubb                  Terminating   28s
    [kubectl] cmd-delete-test358lev                  Active        58s
    [kubectl] cmd-describe-list-binding-test701fze   Active        15s
    [kubectl] cmd-describe-list-binding-test701wcq   Terminating   83s
    [kubectl] cmd-describe-list-binding-test701wsh   Terminating   102s
    [kubectl] cmd-describe-list-binding-test742hcu   Active        49s
    [kubectl] cmd-describe-list-binding-test787cmh   Terminating   72s
    [kubectl] cmd-describe-list-binding-test787elo   Terminating   65s
    [kubectl] cmd-describe-list-binding-test787fox   Active        64s
    [kubectl] cmd-describe-list-binding-test787kot   Terminating   66s
    [kubectl] cmd-describe-list-binding-test787ncr   Terminating   74s
    [kubectl] cmd-describe-list-binding-test787zie   Terminating   74s
    [kubectl] cmd-dev-debug-test179uxw               Active        38s
    [kubectl] cmd-dev-test1140toq                    Active        41s
    [kubectl] cmd-dev-test1157zqe                    Active        74s
    [kubectl] cmd-dev-test1613lit                    Active        1s
    [kubectl] cmd-dev-test2392vew                    Active        49s
    [kubectl] cmd-dev-test2561ysr                    Active        1s
    [kubectl] cmd-dev-test2842ofe                    Active        43s
    [kubectl] cmd-dev-test509tfa                     Terminating   59s
    [kubectl] cmd-dev-test590pzw                     Active        0s
    [kubectl] cmd-dev-test641tzp                     Active        8s
    [kubectl] cmd-devfile-deploy-test571lnn          Active        19s
    [kubectl] cmd-devfile-list-test181mly            Active        29s
    [kubectl] cmd-namespace-test165dvl               Active        2s
    [kubectl] default                                Active        382d
    [kubectl] ibm-cert-store                         Active        382d
    [kubectl] ibm-operators                          Active        382d
    [kubectl] ibm-system                             Active        382d
    [kubectl] interactive-add-binding-test463chf     Terminating   16s
    [kubectl] kube-node-lease                        Active        382d
    [kubectl] kube-public                            Active        382d
    [kubectl] kube-system                            Active        382d
    [kubectl] olm                                    Active        272d
    [kubectl] operators                              Active        272d
    [kubectl] osag-namespace                         Active        132d
    Running kubectl with args [kubectl create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n cmd-dev-test1613lit] 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] I0321 12:27:31.914614   17094 implem.go:110] The path for preference file is /tmp/1344430531/preference.yaml
    [odo] Successfully removed registry
    Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: []
    [odo] I0321 12:27:32.219864   17123 implem.go:110] The path for preference file is /tmp/1344430531/preference.yaml
    [odo] New registry successfully added
    Setting current dir to: /tmp/346195959
    Deleting project: cmd-dev-test1613lit
    Running kubectl with args [kubectl delete namespaces cmd-dev-test1613lit --wait=false] and odo env: []
    [kubectl] namespace "cmd-dev-test1613lit" deleted
    Setting current dir to: /go/odo_1/tests/integration
    Deleting dir: /tmp/346195959
    Deleting dir: /tmp/1344430531
  << End Captured GinkgoWriter Output

  This is a OpenShift specific scenario, skipping
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:1590
------------------------------
••SS•SS••S••S•••••••S••S•SS••••S••SSS••S•
------------------------------
• [11.928 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/2370471344
  << End Captured StdOut/StdErr Output
------------------------------
••SSS•••SSS••SSS•SS•••S•SSS
------------------------------
S [SKIPPED] [2.013 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:1588
    should successfully use the volume components in container components
    /go/odo_1/tests/integration/cmd_dev_test.go:1613

  Begin Captured GinkgoWriter Output >>
    Created dir: /tmp/3031491005
    Created dir: /tmp/1101735661
    Setting KUBECONFIG=/tmp/1101735661/config
    Creating a new project: cmd-dev-test1613bky
    Running kubectl with args [kubectl create namespace cmd-dev-test1613bky] and odo env: []
    [kubectl] namespace/cmd-dev-test1613bky created
    Running kubectl with args [kubectl config set-context --current --namespace cmd-dev-test1613bky] 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-describe-component-test362dyi      Active        25s
    [kubectl] cmd-describe-list-binding-test701rfn   Active        23s
    [kubectl] cmd-describe-list-binding-test742bwe   Active        55s
    [kubectl] cmd-describe-list-binding-test742cpa   Terminating   85s
    [kubectl] cmd-describe-list-binding-test742kgy   Active        49s
    [kubectl] cmd-dev-debug-test243bxi               Active        69s
    [kubectl] cmd-dev-test1300gaq                    Active        2s
    [kubectl] cmd-dev-test1300ook                    Active        74s
    [kubectl] cmd-dev-test1312pgo                    Active        36s
    [kubectl] cmd-dev-test1613bky                    Active        0s
    [kubectl] cmd-dev-test1773gml                    Active        42s
    [kubectl] cmd-dev-test1832isd                    Active        50s
    [kubectl] cmd-dev-test1832pyw                    Active        28s
    [kubectl] cmd-dev-test2082dkc                    Active        26s
    [kubectl] cmd-dev-test2319vvr                    Active        37s
    [kubectl] cmd-dev-test2970nmj                    Active        60s
    [kubectl] cmd-dev-test3382ozd                    Active        22s
    [kubectl] cmd-dev-test964xqr                     Active        35s
    [kubectl] cmd-devfile-deploy-test312qob          Terminating   13s
    [kubectl] cmd-devfile-deploy-test347lnm          Terminating   46s
    [kubectl] cmd-devfile-deploy-test530ric          Terminating   20s
    [kubectl] cmd-namespace-test82yrc                Terminating   10s
    [kubectl] default                                Active        382d
    [kubectl] ibm-cert-store                         Active        382d
    [kubectl] ibm-operators                          Active        382d
    [kubectl] ibm-system                             Active        382d
    [kubectl] kube-node-lease                        Active        382d
    [kubectl] kube-public                            Active        382d
    [kubectl] kube-system                            Active        382d
    [kubectl] olm                                    Active        272d
    [kubectl] operators                              Active        272d
    [kubectl] osag-namespace                         Active        132d
    Running kubectl with args [kubectl create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n cmd-dev-test1613bky] 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] I0321 12:29:02.471104   20770 implem.go:110] The path for preference file is /tmp/1101735661/preference.yaml
    [odo] Successfully removed registry
    Running odo with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: []
    [odo] I0321 12:29:02.631797   20777 implem.go:110] The path for preference file is /tmp/1101735661/preference.yaml
    [odo] New registry successfully added
    Setting current dir to: /tmp/3031491005
    Deleting project: cmd-dev-test1613bky
    Running kubectl with args [kubectl delete namespaces cmd-dev-test1613bky --wait=false] and odo env: []
    [kubectl] namespace "cmd-dev-test1613bky" deleted
    Setting current dir to: /go/odo_1/tests/integration
    Deleting dir: /tmp/3031491005
    Deleting dir: /tmp/1101735661
  << End Captured GinkgoWriter Output

  This is a OpenShift specific scenario, skipping
  In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:1590
------------------------------
••S•
------------------------------
• [4.088 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/72608551
  << End Captured StdOut/StdErr Output
------------------------------
•••••••••••••

Ran 430 of 777 Specs in 1080.594 seconds
SUCCESS! -- 430 Passed | 0 Failed | 0 Pending | 347 Skipped


Ginkgo ran 1 suite in 19m2.461966541s
Test Suite Passed