go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=1483f4f78" ./cmd/odo/
GOFLAGS='-mod=vendor' go run -mod=vendor github.com/onsi/ginkgo/ginkgo  -randomizeAllSpecs -slowSpecThreshold=120 -timeout 14400s -nodes=32 tests/integration/
Running Suite: Integration Suite
================================
Random Seed: 1639417812 - Will randomize all specs
Will run 48 specs

Running in parallel across 32 nodes


------------------------------
• [SLOW TEST:121.351 seconds]
odo link and unlink command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:14
  when two components are deployed
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:45
    when a link is created between the two components with --bind-as-files
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:157
      should unlinking a non-pushed link successfully
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:162
------------------------------

------------------------------
• [SLOW TEST:129.852 seconds]
odo link and unlink command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:14
  when two components are deployed
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:45
    when a link is created between the two components with --bind-as-files
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:157
      when the component is pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:166
        should list the binding directory
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:174
------------------------------

------------------------------
• [SLOW TEST:138.830 seconds]
odo link and unlink command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:14
  when two components are deployed
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:45
    when a link is created between the two components with --bind-as-files
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:157
      when the component is pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:166
        should find the link in odo describe
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:171
------------------------------
• [SLOW TEST:121.132 seconds]
odo link and unlink command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:14
  when two components are deployed
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:45
    when a link is created between the two components with --bind-as-files
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:157
      when the component is pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:166
        should not allow re-linking
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:178
------------------------------
• [SLOW TEST:143.366 seconds]
odo link and unlink command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:14
  when two components are deployed
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:45
    when a link is created between the two components
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:87
      when the link is pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:101
        should ensure that the proper envFrom entry was created
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:105
------------------------------
• [SLOW TEST:134.393 seconds]
odo link and unlink command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:14
  when two components are deployed
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:45
    when a link is created between the two components
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:87
      when the link is pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:101
        should find the linked environment variable
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:113
------------------------------
• [SLOW TEST:127.609 seconds]
odo link and unlink command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:14
  when two components are deployed
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:45
    when a link is created between the two components
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:87
      when the link is pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:101
        should find the link and environment variables in odo describe
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:110
------------------------------
• [SLOW TEST:124.973 seconds]
odo link and unlink command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:14
  when two components are deployed
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:45
    when a link is created between the two components
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:87
      when the link is pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:101
        when unlinking the two components
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:128
          should not allow unlinking again
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:135
------------------------------
• [SLOW TEST:148.854 seconds]
odo link and unlink command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:14
  when two components are deployed
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:45
    when a link is created between the two components with --bind-as-files
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:157
      when the component is pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:166
        when unlinking the two components
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:183
          should find the link in odo describe
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:188
------------------------------
• [SLOW TEST:150.809 seconds]
odo link and unlink command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:14
  when two components are deployed
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:45
    when a link is created between the two components
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:87
      when the link is pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:101
        when unlinking the two components
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:128
          should find the link in odo describe
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:132
------------------------------
• [SLOW TEST:155.749 seconds]
odo link and unlink command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:14
  when two components are deployed
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:45
    when a link is created between the two components
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:87
      when the link is pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:101
        when unlinking the two components
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:128
          when odo push is executed
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:140
            should not allow unlinking again
            /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:149
------------------------------
• [SLOW TEST:162.716 seconds]
odo link and unlink command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:14
  when two components are deployed
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:45
    when a link is created between the two components
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:87
      when the link is pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:101
        when unlinking the two components
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:128
          when odo push is executed
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:140
            should no longer find the link in odo describe
            /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:144
------------------------------
• [SLOW TEST:183.268 seconds]
odo link and unlink command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:14
  when two components are deployed
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:45
    when a link is created between the two components with --bind-as-files
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:157
      when the component is pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:166
        when unlinking the two components
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:183
          when odo push is executed
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:197
            should no longer find the link in odo describe
            /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:202
------------------------------
• [SLOW TEST:191.545 seconds]
odo link and unlink command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:14
  when two components are deployed
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:45
    when a link is created between the two components with --bind-as-files
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:157
      when the component is pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:166
        when unlinking the two components
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:183
          when odo push is executed
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:197
            should not allow unlinking again
            /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/cmd_link_unlink_test.go:207
------------------------------

Ran 48 of 48 Specs in 193.683 seconds
SUCCESS! -- 48 Passed | 0 Failed | 0 Pending | 0 Skipped


Ginkgo ran 1 suite in 3m57.670382978s
Test Suite Passed
GOFLAGS='-mod=vendor' go run -mod=vendor github.com/onsi/ginkgo/ginkgo  -randomizeAllSpecs -slowSpecThreshold=120 -timeout 14400s -nodes=32 tests/integration/devfile/
Running Suite: Devfile Suite
============================
Random Seed: 1639418055 - Will randomize all specs
Will run 248 specs

Running in parallel across 32 nodes

S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
odo devfile describe command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:15
  when devfile has missing metadata [BeforeEach]
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:103
    when projectType and language is missing
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:140
      when the component is pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:148
        should show 'Not available' for 'Type' in odo describe
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:152

        Plain Kubernetes scenario only, skipping

        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:21
------------------------------
S [SKIPPING] in Spec Setup (BeforeEach) [0.000 seconds]
odo devfile describe command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:15
  when devfile has missing metadata [BeforeEach]
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:103
    when projectType and language is missing
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:140
      should show 'Not available' for 'Type' in odo describe
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:145

      Plain Kubernetes scenario only, skipping

      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:21
------------------------------

------------------------------
S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
odo devfile describe command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:15
  when a component is created with storage and url [BeforeEach]
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:31
    should describe the component correctly from a disconnected cluster
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:80

    Plain Kubernetes scenario only, skipping

    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:21
------------------------------

------------------------------
P [PENDING]
odo devfile delete command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_delete_test.go:17
  when a component is created
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_delete_test.go:41
    when the component is pushed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_delete_test.go:50
      deleting a component from other component directory
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_delete_test.go:62
        when the second component is created
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_delete_test.go:76
          when the second component is pushed
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_delete_test.go:81
            should delete with the component name
            /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_delete_test.go:105
------------------------------

------------------------------
• [SLOW TEST:155.688 seconds]
odo devfile push command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:18
  devfile is modified
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:835
    odo push -f is executed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:922
      when java-springboot application is created and pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:839
        when Update the devfile.yaml, do odo push
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:852
          when compare the local and remote files
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:868
            localFiles and remoteFiles should match
            /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:912
------------------------------

------------------------------
• [SLOW TEST:136.157 seconds]
odo devfile watch command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_watch_test.go:18
  when a component is created and pushed in debug mode
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_watch_test.go:228
    should be able to start a debug session after push with debug flag using odo watch and revert back after normal push
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_watch_test.go:237
------------------------------

------------------------------
S [SKIPPING] in Spec Setup (BeforeEach) [0.000 seconds]
odo devfile describe command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:15
  when a component is created with storage and url [BeforeEach]
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:31
    should describe the component correctly
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:76

    Plain Kubernetes scenario only, skipping

    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:21
------------------------------

------------------------------
• [SLOW TEST:160.804 seconds]
odo list with devfile
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_list_test.go:16
  devfile has missing metadata
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_list_test.go:115
    when projectType and language is missing
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_list_test.go:152
      when the component is pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_list_test.go:160
        should show 'Not available' for 'Type' in odo list
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_list_test.go:164
------------------------------
S [SKIPPING] in Spec Setup (BeforeEach) [10.994 seconds]
odo devfile push command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:18
  using Kubernetes cluster
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:1029
    when project with with 'default' name is used [BeforeEach]
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:1035
      should push successfully
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:1037

      This is a Kubernetes specific scenario, skipping

      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:1032
------------------------------

------------------------------
• [SLOW TEST:156.016 seconds]
odo devfile push command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:18
  devfile is modified
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:835
    odo push (without -f) is executed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:925
      when java-springboot application is created and pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:839
        when Update the devfile.yaml, do odo push
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:852
          when compare the local and remote files
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:868
            localFiles and remoteFiles should match
            /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:912
------------------------------

------------------------------
S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
odo devfile describe command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:15
  when devfile has missing metadata [BeforeEach]
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:103
    when projectType is missing
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:121
      when the component is pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:130
        should show the language for 'Type' in odo describe
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:134

        Plain Kubernetes scenario only, skipping

        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:21
------------------------------

------------------------------
• [SLOW TEST:152.213 seconds]
odo devfile push command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:18
  devfile is modified
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:835
    odo push (without -f) is executed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:925
      when java-springboot application is created and pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:839
        when Update the devfile.yaml, do odo push
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:852
          Ensure the build passes
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:864
------------------------------

------------------------------
S [SKIPPING] in Spec Setup (BeforeEach) [11.375 seconds]
odo devfile url command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_url_test.go:16
  Testing URLs for Kubernetes specific scenarios
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_url_test.go:467
    when creating a nodejs component [BeforeEach]
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_url_test.go:475
      when creating url
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_url_test.go:481
        should verify
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_url_test.go:502

        This is a Kubernetes specific scenario, skipping

        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_url_test.go:471
------------------------------

------------------------------
S [SKIPPING] in Spec Setup (BeforeEach) [10.098 seconds]
odo devfile url command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_url_test.go:16
  Testing URLs for Kubernetes specific scenarios
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_url_test.go:467
    when creating a nodejs component [BeforeEach]
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_url_test.go:475
      when creating url
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_url_test.go:481
        when creating a second url
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_url_test.go:488
          should use an existing URL when there are URLs with no host defined in the env file with same port
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_url_test.go:494

          This is a Kubernetes specific scenario, skipping

          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_url_test.go:471
------------------------------
S [SKIPPING] in Spec Setup (BeforeEach) [0.000 seconds]
odo devfile describe command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:15
  when devfile has missing metadata [BeforeEach]
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:103
    when projectType is missing
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:121
      should show the language for 'Type' in odo describe
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:127

      Plain Kubernetes scenario only, skipping

      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:21
------------------------------
• [SLOW TEST:156.477 seconds]
odo devfile push command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:18
  devfile is modified
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:835
    odo push -f is executed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:922
      when java-springboot application is created and pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:839
        when Update the devfile.yaml, do odo push
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:852
          Ensure the build passes
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:864
------------------------------

------------------------------
S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds]
odo devfile describe command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:15
  when a component is created with storage and url [BeforeEach]
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:31
    when the component is pushed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:93
      should describe the component correctly
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:97

      Plain Kubernetes scenario only, skipping

      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_describe_test.go:21
------------------------------

------------------------------
• [SLOW TEST:245.236 seconds]
odo devfile storage command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_storage_test.go:14
  When devfile storage list command is executed
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_storage_test.go:178
    should list the storage with the proper states and container names
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_storage_test.go:226
------------------------------

------------------------------
• [SLOW TEST:128.221 seconds]
odo devfile log command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_log_test.go:12
  Verify odo log for devfile works
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_log_test.go:27
    should log run command output and fail for debug command
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_log_test.go:29
------------------------------

------------------------------
• [SLOW TEST:328.656 seconds]
odo devfile storage command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_storage_test.go:14
  When devfile storage create command is executed
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_storage_test.go:29
    should create storage and attach to specified container successfully and list it correctly
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_storage_test.go:71
------------------------------

------------------------------
• [SLOW TEST:120.461 seconds]
odo list with devfile
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_list_test.go:16
  devfile has missing metadata
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_list_test.go:115
    when projectType is missing
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_list_test.go:133
      when the component is pushed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_list_test.go:142
        should show the language for 'Type' in odo list
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_list_test.go:146
------------------------------

------------------------------
• [SLOW TEST:247.757 seconds]
odo devfile push command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:18
  when creating a nodejs component
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:35
    when events are defined
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:588
      should correctly execute PostStart commands
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/devfile/cmd_devfile_push_test.go:651
------------------------------

Ran 237 of 248 Specs in 382.667 seconds
SUCCESS! -- 237 Passed | 0 Failed | 1 Pending | 10 Skipped


Ginkgo ran 1 suite in 7m0.529452008s
Test Suite Passed
GOFLAGS='-mod=vendor' go run -mod=vendor github.com/onsi/ginkgo/ginkgo  -randomizeAllSpecs -slowSpecThreshold=120 -timeout 14400s -nodes=1 tests/integration/devfile/debug/
Running Suite: Devfile Debug Suite
==================================
Random Seed: 1639418476 - Will randomize all specs
Will run 1 of 1 specs


Ran 1 of 1 Specs in 16.040 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS

Ginkgo ran 1 suite in 23.128470979s
Test Suite Passed
GOFLAGS='-mod=vendor' go run -mod=vendor github.com/onsi/ginkgo/ginkgo  -randomizeAllSpecs -slowSpecThreshold=120 -timeout 14400s -nodes=32 tests/integration/operatorhub/
Running Suite: Operatorhub Suite
================================
Random Seed: 1639418505 - Will randomize all specs
Will run 83 specs

Running in parallel across 32 nodes

P [PENDING]
odo link command tests for OperatorHub
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:16
  Operators are installed in the cluster
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:29
    when getting sources, a devfile defining a component, a service and a link, and executing odo push
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:309
      should find owner references on link and service
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:331
------------------------------

------------------------------
• [SLOW TEST:122.517 seconds]
odo service command tests for OperatorHub
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:18
  Operators are installed in the cluster
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:32
    a specific operator is installed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:50
      when a nodejs component is created
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:115
        when a Redis instance is created with a specific name
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:394
          when odo push is executed
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:422
            when the redisCluster instance is deleted
            /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:442
              when odo push is executed
              /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:452
                should not be listed anymore
                /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:457
------------------------------

------------------------------
• [SLOW TEST:139.773 seconds]
odo service command tests for OperatorHub
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:18
  Operators are installed in the cluster
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:32
    a specific operator is installed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:50
      when a nodejs component is created
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:115
        when a Redis instance definition copied from example file
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:209
          when a service is created from the output of the dryRun command with a specific name and odo push is executed
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:239
            should create pods in running state
            /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:260
------------------------------

------------------------------
• [SLOW TEST:145.714 seconds]
odo link command tests for OperatorHub
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:16
  Operators are installed in the cluster
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:29
    when a component and a service are deployed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:50
      when a link between the component and the service is created inline
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:187
        when odo push is executed
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:206
          should find the link in odo describe
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:213
------------------------------
• [SLOW TEST:144.815 seconds]
odo link command tests for OperatorHub
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:16
  Operators are installed in the cluster
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:29
    when a component and a service are deployed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:50
      when a link with between the component and the service is created with --bind-as-files
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:142
        when odo push is executed
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:163
          should find files in component container
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:170
------------------------------
P [PENDING]
odo link command tests for OperatorHub
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:16
  when one component is deployed
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:348
    when another component is deployed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:379
      should link the two components successfully with service binding operator
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:400
------------------------------

------------------------------
• [SLOW TEST:149.443 seconds]
odo link command tests for OperatorHub
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:16
  Operators are installed in the cluster
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:29
    when a component and a service are deployed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:50
      when a link between the component and the service is created
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:93
        when odo push is executed
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:112
          should find files in component container
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:119
------------------------------

------------------------------
• [SLOW TEST:158.437 seconds]
odo link command tests for OperatorHub
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:16
  Operators are installed in the cluster
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:29
    when a component and a service are deployed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:50
      when a link with between the component and the service is created with --bind-as-files
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:142
        when odo push is executed
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:163
          should find bindings for service
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:174
------------------------------

------------------------------
• [SLOW TEST:184.957 seconds]
odo service command tests for OperatorHub
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:18
  Operators are installed in the cluster
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:32
    a specific operator is installed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:50
      when a nodejs component is created
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:115
        when a Redis instance is created with a specific name
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:394
          when odo push is executed
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:422
            when a link is created with a specific name and bind-as-files flag
            /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:492
              should create a link with bindAsFiles set to true
              /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:508
------------------------------

------------------------------
S [SKIPPING] [74.665 seconds]
odo link command tests for OperatorHub
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:16
  when one component is deployed
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:348
    when another component is deployed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:379
      should link the two components successfully without service binding operator [It]
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:422

      This is a Kubernetes specific scenario, skipping

      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:426
------------------------------

------------------------------
• [SLOW TEST:148.173 seconds]
odo link command tests for OperatorHub
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:16
  Operators are installed in the cluster
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:29
    when a component and a service are deployed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:50
      when a storage is added and deployed
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:75
        when a link between the component and the service is created
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:81
          should run odo push successfully
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:87
------------------------------

------------------------------
• [SLOW TEST:129.535 seconds]
odo link command tests for OperatorHub
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:16
  Operators are installed in the cluster
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:29
    when a component and a service are deployed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:50
      when a link is created and custom binding data is being injected with --map
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:259
        when --bind-as-files flag is used along with --map
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:291
          should have created the mappings correctly
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:299
------------------------------

------------------------------
• [SLOW TEST:123.933 seconds]
odo link command tests for OperatorHub
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:16
  Operators are installed in the cluster
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:29
    when a component and a service are deployed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:50
      when a link is created and custom binding data is being injected with --map
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:259
        when no additional flag other than --map is passed to odo link
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:267
          should have created the mappings correctly
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:273
------------------------------

------------------------------
• [SLOW TEST:128.293 seconds]
odo link command tests for OperatorHub
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:16
  Operators are installed in the cluster
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:29
    when a component and a service are deployed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:50
      when a link with between the component and the service is created with --bind-as-files and --inlined
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:222
        when odo push is executed
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:243
          should display the link in odo describe
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:250
------------------------------
• [SLOW TEST:128.483 seconds]
odo link command tests for OperatorHub
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:16
  Operators are installed in the cluster
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:29
    when a component and a service are deployed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:50
      when a link between the component and the service is created
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:93
        when odo push is executed
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:112
          should find the link in odo describe
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_link_test.go:128
------------------------------

------------------------------
• [SLOW TEST:136.551 seconds]
odo service command tests for OperatorHub
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:18
  Operators are installed in the cluster
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:32
    a specific operator is installed
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:50
      when a nodejs component is created
      /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:115
        when a Redis instance is created with a specific name
        /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:394
          when odo push is executed
          /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:422
            when a link is created with a specific name
            /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:464
              should create the link with the specified name
              /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/operatorhub/cmd_service_test.go:480
------------------------------

Ran 80 of 83 Specs in 270.308 seconds
SUCCESS! -- 80 Passed | 0 Failed | 2 Pending | 1 Skipped


Ginkgo ran 1 suite in 4m36.4102354s
Test Suite Passed
GOFLAGS='-mod=vendor' go run -mod=vendor github.com/onsi/ginkgo/ginkgo  -randomizeAllSpecs -slowSpecThreshold=120 -timeout 14400s -nodes=1 -focus="odo login and logout command tests" tests/integration/loginlogout/
Running Suite: Login Logout Suite
=================================
Random Seed: 1639418786 - Will randomize all specs
Will run 3 of 3 specs


------------------------------
S [SKIPPING] [0.001 seconds]
odo login and logout command tests
/workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/loginlogout/cmd_login_logout_test.go:12
  when running login tests
  /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/loginlogout/cmd_login_logout_test.go:41
    should successful with correct credentials and fails with incorrect token [It]
    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/loginlogout/cmd_login_logout_test.go:42

    Skipping login command tests as SKIP_USER_LOGIN_TESTS is true

    /workspace/42df4393-bff1-43ec-948d-b3316698a80c/tests/integration/loginlogout/cmd_login_logout_test.go:46
------------------------------

Ran 2 of 3 Specs in 0.369 seconds
SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 1 Skipped
PASS

Ginkgo ran 1 suite in 6.162212288s
Test Suite Passed
GOFLAGS='-mod=vendor' go run -mod=vendor github.com/onsi/ginkgo/ginkgo  -randomizeAllSpecs -slowSpecThreshold=120 -timeout 14400s -nodes=32 -focus="odo project command tests" tests/integration/project/
Running Suite: Project Suite
============================
Random Seed: 1639418798 - Will randomize all specs
Will run 11 specs

Running in parallel across 32 nodes


Ran 11 of 11 Specs in 20.964 seconds
SUCCESS! -- 11 Passed | 0 Failed | 0 Pending | 0 Skipped


Ginkgo ran 1 suite in 26.696665453s
Test Suite Passed
GOFLAGS='-mod=vendor' go run -mod=vendor github.com/onsi/ginkgo/ginkgo  -randomizeAllSpecs -slowSpecThreshold=120 -timeout 14400s -nodes=32 -focus="odo devfile supported tests" tests/e2escenarios/
Running Suite: odo e2e scenarios
================================
Random Seed: 1639418830 - Will randomize all specs
Will run 4 specs

Running in parallel across 32 nodes


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


Ginkgo ran 1 suite in 1m48.047876694s
Test Suite Passed