-
Notifications
You must be signed in to change notification settings - Fork 107
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
Update tycho to 4.0.7 #1733
base: master
Are you sure you want to change the base?
Update tycho to 4.0.7 #1733
Conversation
Test Results 107 files ± 0 107 suites ±0 1m 51s ⏱️ - 7m 25s For more details on these errors, see this check. Results for commit b784e23. ± Comparison against base commit e76a84d. ♻️ This comment has been updated with latest results. |
c971827
to
e8049f4
Compare
6fca821
to
3d61610
Compare
18ffb1d
to
8fda5f6
Compare
From the buildfailure it is a problem due to classfile changes (ECJ update?) |
The update to Tycho 4.0.6 already failed in #1688 and IIRC the comparator errors were not the problem and the fixed ECJ version was removed in an attempt to resolve that failure, but it seems like it didn't fix it. |
e150616
to
8074444
Compare
The comparator errors are resolved and now we (again) have the 500 test-failures. |
As they all fail the same way maybe some change in P2 causing this, I would try to add a direct dependency in the test plugin to make sure its not caused by some indirect dependency missing now. |
The plugin |
The error says that the bundle |
Right (I just read the first line and checked the test class). But even |
31186b1
to
86d7ee3
Compare
7bac292
to
08020fa
Compare
Interestingly I get these errors locally as well with Tycho 4.0.4 |
As I can "reproduce" it here with Tycho 4.0.4 I suspect it must be some kind of classpath ordering problem, e.g that for consistency we order the dependencies differently (either Tycho or P2)... |
No description provided.