-
Notifications
You must be signed in to change notification settings - Fork 49
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
OpenFromClipboardTests still randomly fail #28
Comments
I assume something like running other jobs (charset delta, autobuild) etc might confuse Java search. Let disable autobuild, wait for charset delta job that might be running & see if that helps. May be fixes issue eclipse-jdt#28
I assume something like running other jobs (charset delta, autobuild) etc might confuse Java search. Let disable autobuild, wait for charset delta job that might be running & see if that helps. May be fixes issue eclipse-jdt#28
I assume something like running other jobs (charset delta, autobuild) etc might confuse Java search. Let disable autobuild, wait for charset delta job that might be running & see if that helps. May be fixes issue #28
https://download.eclipse.org/eclipse/downloads/drops4/I20220420-1800/testResults.php is OK, few builds before we had fails in every build. But we also had one build with no fails, so let keep it open for a while and monitor. |
|
|
I created a PR to help identify the underlying cause of the failures --> #279 . I do have a question though, perhaps someone has a hint. Does anyone know why the call to
... when I can simply call:
? Is it just to make sure that all other UI-blocking tasks like indexing and encoding are done before calling the |
Makes TestAgainException protected, let OpenFromClipboardTests extend AbstractDebugTest to actually use the retry logic eclipse-jdt#28
Makes TestAgainException protected, let OpenFromClipboardTests extend AbstractDebugTest to actually use the retry logic eclipse-jdt#28
OpenFromClipboardTests can not use TestAgainException because it does not extend AbstractDebugTest to actually use the retry logic. Use a junit4 RetryRule instead. eclipse-jdt#28
OpenFromClipboardTests can not use TestAgainException because it does not extend AbstractDebugTest to actually use the retry logic also a retry does not in this test. wait for ResourcesPlugin.FAMILY_AUTO_REFRESH eclipse-jdt#28
OpenFromClipboardTests can not use TestAgainException because it does not extend AbstractDebugTest to actually use the retry logic also a retry does not in this test. wait for ResourcesPlugin.FAMILY_AUTO_REFRESH eclipse-jdt#28
…dt#28 OpenFromClipboardTests can not use TestAgainException because it does not extend AbstractDebugTest to actually use the retry logic also a retry does not in this test. eclipse-jdt#28
OpenFromClipboardTests can not use TestAgainException because it does not extend AbstractDebugTest to actually use the retry logic also a retry does not in this test. #28
should be fixed with #358 |
I assume something like running other jobs (charset delta, autobuild) etc might confuse Java search.
Let disable autobuild, wait for charset delta job that might be running & see if that helps.
https://download.eclipse.org/eclipse/downloads/drops4/I20220419-1800/testresults/html/org.eclipse.jdt.debug.tests_ep424I-unit-cen64-gtk3-java18_linux.gtk.x86_64_18.html
https://download.eclipse.org/eclipse/downloads/drops4/I20220419-1800/testresults/html/org.eclipse.jdt.debug.tests_ep424I-unit-win32-java11_win32.win32.x86_64_11.html
The text was updated successfully, but these errors were encountered: