-
Notifications
You must be signed in to change notification settings - Fork 121
Use own Parser in UpdateUnitVersions #2133
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
Conversation
|
Lets see if this is enough. See my comment here: #666 (comment) With the UI event processing and editor closing, the test doesn't fail after so many repetitions and it doesn't get slower. I don't know if the fails are a byproduct of repeating the test though... Since repeating it results in tons of editors getting opened (and maybe some code in Eclipse starts closing them when there are too many, maybe also saving them). Maybe the problem is elsewhere. I wasn't able to run into a race condition though, while debugging. |
|
This pull request changes some projects for the first time in this development cycle. An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the git patch. Git patchFurther information are available in Common Build Issues - Missing version increments. |
|
No, it still fails: The other build failed with: #1903 |
Test Results 771 files ±0 771 suites ±0 54m 42s ⏱️ - 3m 18s For more details on these failures, see this check. Results for commit 8f5b93f. ± Comparison against base commit 85b502b. ♻️ This comment has been updated with latest results. |
|
@laeubi sorry to take more of your time, but how can I run tests in a specific test plug-in, while using changes in a production plug-in? E.g. I want to add some extra If I I've tried bumping the bundle version of So when I run Are there maybe some arguments I can pass to |
you can go to the git root then run
see https://books.sonatype.com/mvnref-book/reference/_using_advanced_reactor_options.html |
a6cf13f to
5b4c5fb
Compare
70d5f01 to
4f29253
Compare
|
Following this comment from @jukzi : #666 (comment) Running the test with this change: Results in a dialog shown during the test:
Clicking OK on the dialog results in a test fail: Due to the dialog I'm not sure the fail is the same as what we observe in #666... But this is another thing to try to fix. Other code (not the tested command) calling If the problem is caused by one of those, I'm not sure how to wait on them. They are not jobs. No dialog/fail if I remove Maybe the test can disable code minings and re-enable it after its done?... In particular the command exits early due to this code: The code minings task seems to somehow work on the same node, which I don't understand: |
|
Looks like calling Different callers can start working on the structure created by some other thread... |
4f29253 to
f743a7a
Compare
|
Fail on Linux is: |
|
@iloveeclipse please review. I'm not sure this fixes all fails I've seen for the test, but it fixes some. |
5ae7b60 to
939721d
Compare
d136942 to
8c704fe
Compare
|
Two questions:
|
Yes, we can wait for a general solution, if we decide on one.
Might be fixed by: #2129 Might not be. If so, #2128 stays open. |
|
Lets see if #2139 gets accepted. |
|
Closing in favor of #2139. |

Fixes: #666