| Re: [mdt-papyrus.dev] Tests refactoring & Tycho build |
|
Dear all, Most Tycho jobs are now properly configured and running. They also give the same results as Buckminster, which is good! So, we now have: -
Full build for Main, Extra, Main-Tests and Extra-Tests. The update sites produced by Main and Extra are available as artifacts of the build; they are not published to Eclipse Downloads (The builds from
Eclipse Downloads still come from Buckminster) -
Gerrit now builds both the Main and Extra components. This is the reason why builds now take 15 minutes instead of ~8
o
The tests are not built/executed on Gerrit
o
Multiple Gerrit jobs are now allowed to run in parallel, which reduces the waiting time for parallel reviews -
Analysis: Findbugs runs on Papyrus-Master daily The builds still need to be tuned a little bit, to be more stable and accept more parameters (Especially custom branches), but they are mostly complete now. Regarding the Tycho-based tests, the main difference with Buckminster is that the plug-ins are built and deployed, whereas Buckminster was relying on a nested Eclipse instance (Launch config). This means that
you need to properly fill the “build.properties” when the test plug-ins provides some resources (Models...).
I’ve also included some launch configs to run the Tycho builds locally. They are located in the releng/ project at the root of the repository. To use them, you simply need to install m2e (Maven), from the Release
Train update site. The source plug-ins don’t need to be imported in the Eclipse workspace. Tycho-based builds (On HIPP):
https://hudson.eclipse.org/papyrus/ Buckminster-based builds (Shared instance):
https://hudson.eclipse.org/hudson/user/vlorenzo/my-views/view/Papyrus/ Regards, De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de LETAVERNIER Camille Hi all, Here are the post-refactoring test results: Buckminster: 20 failures, 9191 total Tycho: 44 failures (+8), 9202 total Pre-refactoring resuls: 0 failure, 9069 total For buckminster, failures only appear in test plug-ins which were previously not executed by Hudson, so there doesn’t seem to be any regression: -
Infra.core.sasheditor.tests: Related to the de-fragmentation of the test bundle. I will fix that -
Editor.integration.tests.EditorReloadTest: Platform-specific issues? -
Sysml.modelexplorer.tests: To be verified (Seems to be an actual failure) Tycho fails on the resourceloading tests (model2), which are all green on Buckminster (And all green locally for me too). It also seems to be executing these tests twice (24 failures for 12 tests). Here’s the new test job (On Papyrus’ HIPP): https://hudson.eclipse.org/papyrus/job/Papyrus-Master-Tests/ (Note: The 8 additional failures on Tycho are actual failures, because for this comparison, Tycho and Buckminster didn’t build exactly the same commit) Regards, De :
mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de LETAVERNIER Camille Hi all, In the context of moving all our builds to Tycho, I’ve refactored some of the tests plug-ins. Changes include: -
Test plugins and packages have been renamed/moved, to match the Papyrus naming policy (And for consistency with the Papyrus plugins) -
Test plugins metadata have been fixed (Especially, since build.properties was not used by the current Buckminster builds, these files were missing a lot of entries) -
Test fragments are now package-imported by AllTests, to ensure they are properly resolved
o
If you include new test fragments, don’t forget to import the package of the fragment’s main test class in oep.tests The builds are currently running to ensure that this didn’t introduce any regression. Note that some of the tests fragments were previously not executed at all, and now are, so the builds will probably become unstable. Only the main tests have been migrated to Tycho (yet). Once this is stable enough (and properly integrated on Hudson), the extra-tests will be integrated as well Regards, |