Fix Happy path tests on minikube on CRW CCI instances due to "plugin runtime crashed unexpectedly" error

Describe the bug

There was an error “Plugin runtime crashed unexpectedly” in time of running Happy path tests on minikube within CRW CCI instances with 16Gb RAM / 8 CPUs:

• https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/Che-Theia-master-check-E2E-Happy-path-tests-against-K8S/155
• https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/che-regular-tests/view/K8S/job/Single-Che-master-check-E2E-Happy-path-tests-against-k8s/2066/

  Validation of workspace build and run
    ✓ Build application (37424ms)
After clicking to the "Terminal" -> "Run Task ..." the "Quick Open Container" has not been displayed, one more try
    1) Run application


  9 passing (15m)
  1 pending
  1 failing

  1) Validation of workspace build and run
       Run application:
     TimeoutError: Waiting until element is visible
Wait timed out after 300173ms
      at /tmp/e2e/node_modules/selenium-webdriver/lib/promise.js:2201:17
      at ManagedPromise.invokeCallback_ (/tmp/e2e/node_modules/selenium-webdriver/lib/promise.js:1376:14)
      at TaskQueue.execute_ (/tmp/e2e/node_modules/selenium-webdriver/lib/promise.js:3084:14)
      at TaskQueue.executeNext_ (/tmp/e2e/node_modules/selenium-webdriver/lib/promise.js:3067:27)
      at asyncRun (/tmp/e2e/node_modules/selenium-webdriver/lib/promise.js:2927:27)
      at /tmp/e2e/node_modules/selenium-webdriver/lib/promise.js:668:7
      at <anonymous>
      at process._tickCallback (internal/process/next_tick.js:188:7)
  From: Task: Waiting until element is visible
      at scheduleWait (/tmp/e2e/node_modules/selenium-webdriver/lib/promise.js:2188:20)
      at ControlFlow.wait (/tmp/e2e/node_modules/selenium-webdriver/lib/promise.js:2517:12)
      at thenableWebDriverProxy.wait (/tmp/e2e/node_modules/selenium-webdriver/lib/webdriver.js:934:29)
      at DriverHelper.<anonymous> (/tmp/e2e/utils/DriverHelper.ts:100:61)
      at Generator.next (<anonymous>)
      at fulfilled (/tmp/e2e/dist/utils/DriverHelper.js:17:58)
      at <anonymous>
      at process._tickCallback (internal/process/next_tick.js:188:7)

The issue is related to https://github.com/eclipse/che/issues/14551

The problem was not reproduced on instance 32 GB RAM / 16 CPUs.

Workspace devfile

https://github.com/eclipse/che/blob/78e35343504ee33e6aa5ed0c3a35d07b601db62e/e2e/files/happy-path/happy-path-workspace.yaml#L30

Server logs

https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/Che-Theia-master-check-E2E-Happy-path-tests-against-K8S/155/artifact/logs-and-configs/

Che version

• latest
• nightly
• other: please specify

Steps to reproduce

Happy path E2E tests scenario.

Runtime

• minikube 1.1.1:

/usr/local/bin/minikube start \
      --vm-driver=none \
      --cpus 4 \
      --memory 12288 \
      --logtostderr

Installation method

• chectl
• che-operator
• minishift-addon
• I don’t know

Environment

• my computer
  • Windows
  • Linux
  • macOS
• Cloud
  • Amazon
  • Azure
  • GCE
  • other: CRW CCI
• other: please specify

Additional context

[tolusha]

I mean

  - id: eclipse/che-theia/latest
    type: cheEditor
    memoryLimit: 768Mi

[mmorhun]

@dmytro-ndp sorry I wasn’t clear enough… I meant the one with increased memory limits…