Re: [che-dev] Status of Happy path PR check of Eclipse Che repos

[Dmytro Nochevnov <dnochevn@xxxxxxxxxx>]

Hello everyone,

Recent Happy path test issues have been fixed:

- Happy path e2e test failed on Java LS validation step 

- E2E Happy path tests fails on autocomplete validation step

If your PR is for Eclipse Che repo - please, make sure you have a fixup commit "Add 'java.server.launchMode: Standard' preference to E2E Happy path test devfile" in your PR.

On Mon, Oct 26, 2020 at 1:49 PM Dmytro Nochevnov <dnochevn@xxxxxxxxxx> wrote:

FYI: E2E Happy path test PR check of Eclipse Che / Che-Theia repos is failing on two different steps from time to time:

(1) on autocomplete validation step https://github.com/eclipse/che/issues/18196:
   * Problem recognized by the following error messages in Jenkins job console log:

-----------------------------------------------

          ▼ Editor.pressControlSpaceCombination "PetClinicApplication.java"
          ▼ Editor.performKeyCombination title: "PetClinicApplication.java" text: ""
    1) Autocomplete


  4 passing (3m)
  1 failing

  1) Language server validation
       Autocomplete:
     TimeoutError: Wait timed out after 34471ms

===========================

(2) on Java LS initialization step https://github.com/eclipse/che/issues/18193:

   * Problem recognized by the following error messages in Jenkins job console log:

-----------------------------------------------

          ▼ Editor.waitTabFocused "PetClinicApplication.java"
          ▼ Ide.checkLsInitializationStart
          ▼ Ide.waitStatusBarContains "Activating Language Support for Java"
Known flakiness has occurred https://github.com/eclipse/che/issues/17864
          ▼ Ide.waitStatusBarContains "Activating Java Test Runner"
    1) Java LS initialization


  2 passing (5m)
  1 failing

  1) Language server validation
       Java LS initialization:
     TimeoutError: Wait timed out after 181107ms

===========================

Che QE team is investigating the problems described above.

Also, please, make sure you have updated your PR with the latest changes in the "master" branch.

-- 

With best regards,

Dmytro Nochevnov

Senior Software Quality Engineer

CodeReady Workspaces QE team

--

With best regards,

Dmytro Nochevnov

Senior Software Quality Engineer

CodeReady Workspaces QE team