-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 E2E tests failed on 'Run debug and check application stop in the breakpoint' step #18034
Comments
Assigning severity/blocker since AFAIU it prevents new PRs from being merged. |
@dmytro-ndp youtube says "this video is private". |
@tsmaeder: sorry for that. |
@dmytro-ndp the sequence of events in the video seems to be:
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? |
@tsmaeder: thank you for investigation! Expected THREADS listActual THREADS list |
Changed priority, because the issue hasn't been reproduced during the last few days. |
@dmytro-ndp The crucial difference between "normal" flow and this bug is that in the "normal" flow, the preview widget gets reloaded (which triggers the breakpoint). That's what's missing in the screencast of this bug, as Thomas was saying. |
@rhopp: that is not true. If you look at normal flow screen cast, you will see that threads had appeared in the THREADS list BEFORE the test was refreshed preview tabs. |
TBH... I blame that on slow UI. |
Ok. Dmytro proved me wrong... I was thinking (the same way as Thomas), that the test failed on waiting for the breakpoint to be hit, but that's not the case. |
@tsmaeder, @l0rd: the issue has being reproduced quite often in 7.21.0-SNAPSHOT, 7.22.0-SNAPHSOT last days: PR check:
Nightly tests:
Could you, please, take a close look at it? |
@dmytro-ndp, Vanilla Theia has the same behavior: #18564 (comment), so, what can I propose is to not stick to the specific items in a list, but check, for example whether the view is collapsed or not. If collapsed, then expand. Or choose another DOM elements that can be an anchor for testing scenario. If you switch to the debugger panel and refresh the page, the application state will be restored in the same way as it was before reloading. cc @azatsarynnyy |
Thanks @vzhukovs for checking it. |
Still reproducing on https://github.com/eclipse/che-theia/runs/1890254370?check_suite_focus=true |
@benoitf: thank you update!
Please, review corresponding PR to Happy path tests che-incubator/happy-path-tests-action#1 |
As this has now had 3 milestone designations (7.26, 7.27, 7.28) I've moved it to 7.x as it's either not getting done, or needs an owner to set a valid fixversion. |
Closing the issue because the problem hasn't been reproduced for a long time. |
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
Che version
Steps to reproduce
Happy path tests script
Expected behavior
Runtime
kubectl version
)oc version
)minikube version
andkubectl version
)minishift version
andoc version
)docker version
andkubectl version
)Screenshots
Screencast
https://youtu.be/jqfECJXL5EQ
Installation method
chectl version
commandEnvironment
Eclipse Che Logs
Additional context
The text was updated successfully, but these errors were encountered: