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

Fix timeouts of waiting on extensions complete installation in 'Java 11 with Quarkus' RecommendedExtensions test #22502

Closed
dmytro-ndp opened this issue Sep 11, 2023 · 3 comments · Fixed by #22514
Assignees
Labels
area/qe kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.

Comments

@dmytro-ndp
Copy link
Contributor

dmytro-ndp commented Sep 11, 2023

Is your task related to a problem? Please describe

'Java 11 with Quarkus' RecommendedExtensions test is waiting on extensions complete installation 20 minutes which is too long
https://main-jenkins-csb-crwqe.apps.ocp-c1.prod.psi.redhat.com/job/Testing/job/e2e/job/basic/job/typescript-tests/11671/console

20:00:16        • Check if {"publisher":"redhat","name":"java"} are installed.
20:00:16            ▼ extensionSection.findItem(java).
20:20:26            ▼ ActivityBar().getViewControl("Extensions"))?.openView(): open Extensions view.
20:20:26            ▼ extensionsView?.getContent().getSections(): get current section.
20:20:26              ‣ DriverHelper.waitAllPresence - By(css selector, .name)
20:20:26        • Check if {"publisher":"redhat","name":"java"} are installed.
20:20:26            ▼ extensionSection.findItem(java).
20:40:20            ▼ ActivityBar().getViewControl("Extensions"))?.openView(): open Extensions view.
20:40:20            ▼ extensionsView?.getContent().getSections(): get current section.
20:40:20              ‣ DriverHelper.waitAllPresence - By(css selector, .name)
20:40:20        • Check if {"publisher":"redhat","name":"java"} are installed.
20:40:20            ▼ extensionSection.findItem(java).
20:57:37  Cancelling nested steps due to timeout

Command to run the test:

docker run --shm-size=4096m -p 5920:5920 -e TS_SELENIUM_LOAD_PAGE_TIMEOUT=420000 -e TS_SELENIUM_BASE_URL=https://devspaces.apps.ocp413.crw-qe.com/ -e DELETE_WORKSPACE_ON_FAILED_TEST=true -e TS_SELENIUM_START_WORKSPACE_TIMEOUT=120000 -e NODE_TLS_REJECT_UNAUTHORIZED=0 -e VIDEO_RECORDING=true -e E2E_OCP_CLUSTER_API_URL=https://api.ocp413.crw-qe.com:6443/ -e TS_SELENIUM_LOG_LEVEL=TRACE -e TS_WAIT_LOADER_PRESENCE_TIMEOUT=120000 -e TS_COMMON_DASHBOARD_WAIT_TIMEOUT=30000 -e OCP_INFRA=PSI -v /tmp:/usr/local/bin:Z -v /home/hudson/.kube:/home/seluser/.kube:Z -v /mnt/hudson_workspace/workspace/Testing/e2e/basic/typescript-tests/test-repo/tests/e2e:/tmp/e2e:Z -v /mnt/hudson_workspace/workspace/Testing/e2e/basic/typescript-tests/test-repo/tests/e2e/video:/tmp/ffmpeg_report:Z -e USERSTORY=RecommendedExtensions -e TS_SELENIUM_VALUE_OPENSHIFT_OAUTH=true -e TS_OCP_LOGIN_PAGE_PROVIDER_TITLE=htpasswd -e TS_SELENIUM_OCP_USERNAME=admin -e 'TS_SAMPLE_LIST=Java 11 with Quarkus' -e TS_COMMON_DASHBOARD_WAIT_TIMEOUT=120_000 quay.io/eclipse/che-e2e:next

Describe the solution you'd like

Fix timeouts of waiting on extensions complete installation in 'Java 11 with Quarkus' RecommendedExtensions test.

Describe alternatives you've considered

No response

Additional context

The is the same problem with 'Java 11 with Lombok' RecommendedExtensions test: https://main-jenkins-csb-crwqe.apps.ocp-c1.prod.psi.redhat.com/job/Testing/job/e2e/job/complex/job/latest/job/functional-tests/893/

@dmytro-ndp dmytro-ndp added kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. area/qe labels Sep 11, 2023
@nallikaea
Copy link
Contributor

After investigation I found that installation of "java" extension not finished if the page was not reloaded. Even after 40min it has "installing" webelement and don`t become "reload required".
image

It become, installed only if reload page in even in 30sec. Looks like an issue but is it on our side, extensions or Code? WDYT? @dmytro-ndp

@dmytro-ndp
Copy link
Contributor Author

@nallikaea : thank you for investigation

It is known product issue https://issues.redhat.com/browse/CRW-4790

The point is that the test should fail quickly in this case, with respect to pre-defined timeouts.

@nallikaea
Copy link
Contributor

@nallikaea : thank you for investigation

It is known product issue https://issues.redhat.com/browse/CRW-4790

The point is that the test should fail quickly in this case, with respect to pre-defined timeouts.

I see
Thank you 👍
Will fix it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/qe kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
2 participants