Happy path E2E tests failed on 'Run debug and check application stop in the breakpoint' step

[dmytro-ndp]

Describe the bug

Happy path E2E tests failed on 'Run debug and check application stop in the breakpoint' step on minikube and minishift from time to time:
https://ci.centos.org/view/Devtools/job/devtools-che-nightly-happy-path-test/237/console
https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/basic-MultiUser-Che-check-e2e-tests-against-k8s/2318/consoleFull

          ▼ Editor.selectTab "WelcomeController.java"
          ▼ Editor.waitTab "WelcomeController.java"
          ▼ Editor.clickOnTab "WelcomeController.java"
          ▼ Editor.waitTabFocused "WelcomeController.java"
          ▼ TopMenu.selectOption "View"
          ▼ TopMenu.clickOnTopMenuButton "View"
          ▼ Ide.closeAllNotifications
          ▼ NotificationCenter.open
          ▼ NotificationCenter.clickIconOnStatusBar
          ▼ NotificationCenter.waitOpening
          ▼ NotificationCenter.closeAll
          ▼ NotificationCenter.clickCloseAllNotificationsButton
          ▼ NotificationCenter.waitClearNotificationsList
          ▼ TopMenu.clickOnSubmenuItem "Debug"
          ▼ Ide.waitLeftToolbarButton
          ▼ DebugView.clickOnDebugConfigurationDropDown
          ▼ DebugView.clickOnDebugConfigurationItem "Debug (Attach) - Remote"
          ▼ Ide.performKeyCombination ""
          ▼ DebugView.clickOnRunDebugButton
          ▼ Waiting for debugger to connect (threads to appear in "Threads" view)
...
          ▼ Waiting for debugger to connect (threads to appear in "Threads" view)
    1) Run debug and check application stop in the breakpoint


  21 passing (11m)
  1 pending
  1 failing

  1) Validation of debug functionality
       Run debug and check application stop in the breakpoint:
     TimeoutError: Wait timed out after 30001ms
      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: <anonymous wait>
      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 DebugView.waitForDebuggerToConnect (/tmp/e2e/pageobjects/ide/DebugView.ts:53:45)
      at Context.test (/tmp/e2e/tests/e2e_happy_path/HappyPath.spec.ts:259:25)
      at <anonymous>
      at process._tickCallback (internal/process/next_tick.js:188:7)

Che version

• latest
• nightly
• other: please specify

Steps to reproduce

Happy path tests script

Expected behavior

Runtime

• kubernetes (include output of kubectl version)
• Openshift (include output of oc version)
• minikube 1.1.1 (include output of minikube version and kubectl version)
• minishift 3.11 (include output of minishift version and oc version)
• docker-desktop + K8S (include output of docker version and kubectl version)
• other: (please specify)

Screenshots

Screencast

https://youtu.be/jqfECJXL5EQ

Installation method

• chectl
  • provide a full command that was used to deploy Eclipse Che (including the output)
  • provide an output of chectl version command
• OperatorHub
• I don't know

Environment

• my computer
  • Windows
  • Linux
  • macOS
• Cloud
  • Amazon
  • Azure
  • GCE
  • other (please specify)
• other: CRW CCI, Centos CI

Eclipse Che Logs

Additional context

[sleshchenko]

Assigning severity/blocker since AFAIU it prevents new PRs from being merged.

[tsmaeder]

@dmytro-ndp youtube says "this video is private".

[dmytro-ndp]

@tsmaeder: sorry for that.
Screencast should be public now https://youtu.be/jqfECJXL5EQ

[tsmaeder]

@dmytro-ndp the sequence of events in the video seems to be:

1. Set a break point
2. Start the application
3. Open the preview
4. Connect the debugger
5. Nothing

I don't see a refresh in the browser: why would you expect the breakpoint to be hit if the code is not executed again?

[dmytro-ndp]

@tsmaeder: thank you for investigation!
If you look at normal debug flow https://www.youtube.com/watch?v=dN1oprNuyyg&feature=youtu.be&t=600, you might notice that there should threads in THREADS list be appeared after connection to debugger:

Expected THREADS list

Actual THREADS list