Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[happy-path] Somethimes "Happy Path" test fails on validation of autocomplete #14018

Closed
3 of 23 tasks
Ohrimenko1988 opened this issue Jul 25, 2019 · 4 comments · Fixed by #14046
Closed
3 of 23 tasks

[happy-path] Somethimes "Happy Path" test fails on validation of autocomplete #14018

Ohrimenko1988 opened this issue Jul 25, 2019 · 4 comments · Fixed by #14046
Assignees
Labels
e2e-test/failure Issues that is related to a test failures reported by our CI platform and our QE. severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@Ohrimenko1988
Copy link
Contributor

Describe the bug

Somethimes "Happy Path" test fails on validation of autocomplete

Che version

Che 7.0.0-rc-4.0-SNAPSHOT

  • latest
  • nightly
  • other: please specify

Steps to reproduce

Expected behavior

After invoking, autocomplete container displays with java suggestions

Runtime

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

Screenshots

screenshot-Autocomplete

HTML dump

pagesource-Autocomplete.zip

Browser logs

browserlogs-Autocomplete.txt

Installation method

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

Environment

  • my computer
    • Windows
    • Linux
    • macOS
  • Cloud
    • Amazon
    • Azure
    • GCE
    • other (please specify)
  • other: please specify

Additional context

@Ohrimenko1988 Ohrimenko1988 added kind/bug Outline of a bug - must adhere to the bug report template. e2e-test/failure Issues that is related to a test failures reported by our CI platform and our QE. team/che-qe labels Jul 25, 2019
@Ohrimenko1988 Ohrimenko1988 self-assigned this Jul 25, 2019
@tsmaeder tsmaeder added status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. labels Jul 25, 2019
@tsmaeder
Copy link
Contributor

Not quite sure about this one: does this fail when you do it by hand or does it fail when you run it in the test? If by hand, does it succeed first and then fail some time afterwards? Any exceptions in any of the outputs?

@rhopp
Copy link
Contributor

rhopp commented Jul 26, 2019

We weren't able to reproduce this by hand. This failure is happening only when running automated test. It's happening few times a day (we are running the test every hour on different infras (minishift,minikube)).
This issue is about investigation of this test failure. If we find out it's possible LS bug, or any other bug, we'll open another issue. (It still can be some timing issue in test - that would need to be resolved on the test side)
Triaging this for 7.0, as this is prerequisite of having stable Happy Path test.

@rhopp rhopp added severity/P1 Has a major impact to usage or development of the system. and removed kind/bug Outline of a bug - must adhere to the bug report template. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jul 26, 2019
@rhopp rhopp added this to the 7.0.0 milestone Jul 26, 2019
Ohrimenko1988 added a commit that referenced this issue Jul 26, 2019
…validation of autocomplete) (#14046)


Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
@dmytro-ndp dmytro-ndp reopened this Jul 30, 2019
@dmytro-ndp
Copy link
Contributor

dmytro-ndp commented Jul 30, 2019

There was wrong branch investigate-13973 used in the job where issue happened.
It didn't reproduce on master branch https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/che7-e2e-tests/job/CHE-7-Happy-Path-Tests/643/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
e2e-test/failure Issues that is related to a test failures reported by our CI platform and our QE. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
4 participants