-
Notifications
You must be signed in to change notification settings - Fork 67
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
Build o.e.equinox.compendium.tests and o.e.equinox.region.tests #29
base: master
Are you sure you want to change the base?
Conversation
3982fae
to
fe7599b
Compare
Do you plan to finish this one? |
Yes I do. But at the moment I'm stuck, because when I build equinox locally on my windows computer the build/tests pass (I have commented out the launcher fragments/features and the other tests to speed up the build). If you use Linux, can you try if the the build succeeds on your computer? |
I have RHEL and can take a look this week. |
If this helps, and we think its good to test on different OS because equinox contains OS specific behaviour, we can setup a matrix build for equinox with windows/linux/mac(?) like I recently did for SWT. |
For this case it would at least help to check if the failure is OS specific or if some magic is happening at my computer that the tests pass. |
Looks like the tests are not executed now and therefore don't fail. Furthermore there are many errors during compilation like the following in multiple modules. I wonder why the build doesn't fail because of them:
|
Because they only printed out, see eclipse-jdt/eclipse.jdt.core#239 To fail the build, you could try to set |
Thank you for the hint! |
Do you plan to rebase and finish this one? |
Thanks for the heads up. I still think this would be good to have (the more tests the better). |
Test Results 726 files + 63 726 suites +63 1h 17m 16s ⏱️ + 3m 42s For more details on these errors, see this check. Results for commit cf9b4b5. ± Comparison against base commit 5810f68. ♻️ This comment has been updated with latest results. |
e706213
to
bcfaf7a
Compare
The tests are now running again (I configured to skip their execution when replacing pom.xml files with pom-less, just like it was before). |
5e0c10a
to
dd83565
Compare
This seems to require manual rebase now. |
@HannesWell is this still of interest? |
Done.
Since more tests are usually always better I think it still would be good to have this. |
112b319
to
e14312b
Compare
- Disable currently failing RegionTests. - Remove unnecessary test-suites that included all tests and just execute all tests in the project. - Move required Java version to 17.
e14312b
to
cf9b4b5
Compare
This PR was originally created as eclipse-equinox/equinox.bundles#22 and is now moved to this repository due to the merge of the equinox.framework and equinox.bundles repository.
The tests in o.e.equinox.compendium.tests and o.e.equinox.region.tests are not obsolete and therefore should be build.
The tests in o.e.equinox.region.tests were disabled as part of Bug 470000 that had the goal to reduce/remove the dependencies to aspectj.
@tjwatson explained in eclipse-equinox/equinox.bundles#19 (comment) that the tests could function even without aspectj in the platform by using corresponding mocks.
For now I suggest to simply disable failing tests and to fix them later.
The reason is I would like the build to function with all projects in the repository. This way we can later fully leverage Tycho-pomless and don't have to list each module to build.