This repository has been archived by the owner on May 3, 2022. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Do not merge
The previously suggested changes are not needed, increasing shm size should do the trick.:
ezsystems/ezplatform#214
This is something similar to the problem that occured in #895:When elements overlap Chrome driver reacts differently than Firefox. It tries to click the spinner and fails with UnknownError exception:This time the issue occurs in various places and is involved with the spinner visible when application is reloading.Screen of example failure:
The selector to detect the spinner is still correct, I suspect Chrome driver is more prone to the spinner "blinking" (disappearing and appearing again in very short time) - it can be seen in the Studio part.I've considered various solutions:- Overriding the click method to catch the Exception, wait some time and then try again feels like an overkill.- Different selectors for the spinner also did not help, as the selector is correct (and it really disappears for a moment).My approach requires multiple checks in a row to pass in order to decide, that the spinner is indeed gone. It's a simple solution, but has some drawbacks:- there's still a chance that a test will fail (hopefully it's low - I've chosen the $consecutiveTimesRequired by hand and it looks stable)- every waitWhileLoading execution will execute at least 3 sleeps instead of 1 (one sleep is 250 ms).Execution times before and after, based on StudioUI common suite:Before; 42 min 23 secAfter: 45 min 52 secI think it's acceptable, at least for now.