-
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
Unexpected hanging of the Loader after actions #8300
Comments
Similar behavior with RenameParametersTest, TestAnnotationsTest: Log:
|
I've add some messages to the loader it will help identify problems more accurate. Not close issue yet will wait on detail information |
Attachment for PreviewUrlIntoCommandsEditorTest Log:
|
…migration to master * commit '47fe46a34fa1df988ed61d46e5a478e0f67675b7': (156 commits) Fixed build errors eclipse-che#6331 disable key binding handle when any 'Window' opened (eclipse-che#8473) changed info about known issue (eclipse-che#8483) Avoid removal of non-test workspaces at the cleanup environment stage of selenium testing (eclipse-che#8481) Add changes in the methods of checking git-marker in the page object 'CodenvyEditor' updated the command Use nightly stack by default and -Pdev for development Changes pvc name to a prefix + 8 random characters init and cli images should not use tag from CHE (eclipse-che#8474) CHE-7581 Improved keycloak initialization (eclipse-che#8425) CHE-8240: Switch to project explorer tab for reavel resources action. (eclipse-che#8460) Selenium: Create selenium tests to cover the authorization on GitHub (eclipse-che#8395) apply formating for 'CreateNewPackagesWithHelpCreationJavaClassTest' selenium test (eclipse-che#8464) remove read 'preferences' in try/catch block (eclipse-che#8463) add project build to CheckAutocompleteFeaturesInTheTestFolderTest (eclipse-che#8457) Selenium: Add try/catch block for displaying "Known issue" with eclipse-che#8300 bug (eclipse-che#8454) add info about known issue to FileStructureNodesTest selenium test (eclipse-che#8452) Remove "source" field from stack object (eclipse-che#8407) Selenium: Fix unexpected fail of MacrosCommandsEditorTest selenium test (eclipse-che#8441) Fix formatting (eclipse-che#8447) ...
It is reliably reproduced when CPU is overloaded, for example, when the number of test threads >= number of CPU cores. Report from here:
According to the logs there was a problem with processing request:
|
The try/catch blocks for FileStructureNodesTest, at least are too broad:
I have at least one case where the problem is not a hung loader, but the expected text is wrong (looking at the screenshot). If we need to preserve context, we should pass it into the FileStructure.wait...() methods. |
Investigation has shown that the issue can't be reproduced neither on jenkins nor local machine. |
Description
We have unexpected fail of FileStructureNodesTest selenium test. The test sometimes fails while is waiting for the File Structure form.
Reproduction Steps:
Expected behavior:
The File Structure form is opened.
Observed behavior:
The File Structure form is not appeared and the test fails because the Loader is still visible(after waiting for 180 second that it is closed).
Failed selenium test: FileStructureNodesTest, PreviewUrlIntoCommandsEditorTest
Log:
Screenshot:
Report with reproduced problem:
https://ci.codenvycorp.com/view/qa/job/che-integration-tests-master-docker/148/Selenium_tests_report/
The text was updated successfully, but these errors were encountered: