-
Notifications
You must be signed in to change notification settings - Fork 192
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
Refresh option not available for some resources that are not closed p… #2601
base: master
Are you sure you want to change the base?
Conversation
Test Results 1 214 files 1 214 suites 1h 36m 59s ⏱️ For more details on these failures, see this check. Results for commit 39da4c6. ♻️ This comment has been updated with latest results. |
…rojects eclipse-platform#2538 Change made since the fix to eclipse-platform#1438 unintentionally removed the "refresh" contextual menu for resources that are not projects. With this change the "refresh" contextual menu is shown if ANY navigator selection is either (A) an open project, or (B) a non-project resource. Put another way: the 'refresh' item is NOT shown if ALL selections are closed projects. Fixes eclipse-platform#2538
@mickaelistria can you review this? #2003 (comment) |
The failing ProgressContantsTest.testKeepOneProperty is unrelated see #370 |
Code looks good and safe enough. However we didn't get any build completing from https://ci.eclipse.org/platform/job/eclipse.platform.ui/job/PR-2601/ , and I wouldn't feel comfortable merging until we have 1 build running entirely. |
For the record: Build failed with OutOfMemoryError, i have not seen that elsewhere. @DaveCarpeneto can you help investigate the reason for OOME? May be its even related to this PR?
|
The OutOfMemory seems to be already discussed in #2432 |
The CI logfile contains messages like
does it relate to this PR? |
i don't get if the added tests are useful: Only one of them fails when the PR is reverted and has an error message that is not understandable to me:
|
The one test that fails relates directly to the code change. The other 4 handle other situations where eclipse behaves as expected today. I added those 4 tests in the hope that future changes do not introduce a regression bug, like was done in the code added for #1438 .
My hope was that the error message was enough that if this test failed that people investigating would have enough information to see what went wrong. In this case RefreshAction was not included, where the test was expecting to be included. If you feel that further elaboration is needed for a unit test failure message please let me know & I will submit another change to cover this. |
No. I see this in the stdout when I grab pretty much any recent build & run these tests (which succeed). The NotHandledException is in fact what was expected by the test. These lines come from things like the following in org.eclipse.ui.tests.commands.CommandExecutionTest :
... which were added as part of the tests in 2012. These lines have been reported in builds for quite some time :-) |
…rojects #2538
Change made since the fix to #1438 unintentionally removed the "refresh" contextual menu for resources that are not projects.
With this change the "refresh" contextual menu is shown if ANY navigator selection is either (A) an open project, or (B) a non-project resource. Put another way: the 'refresh' item is NOT shown if ALL selections are closed projects.
Fixes #2538