Hi Christian,
We’re getting a little bit better with the tests (Jobs are back to “Unstable” rather than crashed, time outs are solved, and using Tycho 0.21 instead of 0.22
fixes the tests-failure job). So we can now rely on Hudson a little bit more, which is a good news. We’ll be able to focus on fixing tests/regressions now, and since Test-failures is back online, we can start annotating some tests again.
CDO Integration is an extra-plugin, so it can wait a little bit (It is not included into the release train so the M6/M7 constraints don’t apply ; it should
still however follow the release calendar so we need to include it sometime during the Release Candidates)
Diagram Synchronization should definitely be merged today, but I won’t be able to review the branch for another hour or two (Meaning that M7 will be another
late build :( ). If anyone in the committers team wants to review
https://git.eclipse.org/r/#/c/47188/ (And is not already busy with last minute regressions), that would help!
Sorry for the delays and trouble... We didn’t really expect the 40 test failures which happened 3 days after any new commit or build change, and all the issues
that stacked on top of that
Camille
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Christian W. Damus
Envoyé : mercredi 6 mai 2015 14:54
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] Building M7 & Gerrit failures
Today is M7. I have a diagram synchronization feature pending in Gerrit [1] and also a contribution to process that migrates the CDO integration to the new checkouts UI [2]. What shall I do about those?
On Wed, May 6, 2015 at 4:17 AM, LETAVERNIER Camille <Camille.LETAVERNIER@xxxxxx> wrote:
Hi all,
While the job compilation is back to normal, we now have issues with the tests (And especially, a corrupt Junit XML file is produced for some reason,
which means that all tests are properly executed but the results cannot be published and the test build fails). I’ve no idea what causes this, I’m investigating (We’ve had the same issue on the tests-failure job for several months but could not solve it so
far)
Given the time it takes to run the tests, and that the failure occurs at the very end of the build, it may take quite some time to identify and fix the
issue. Please avoid committing anything that it not a test fix today, to avoid overloading the build server
Thanks,
Camille
Hi all,
The builds are back to normal. You may need to rebase your change to force a rebuild for the failed Gerrit builds
Regards,
Camille
Hi all,
Lots of builds are currently failing (including Gerrit builds), due to the M7 builds in progress. Especially, one of our dependencies’ update site has been removed but the new one
is not yet available. I expect the issue to be fixed quickly since this breaks the Simultaneous Release builds, but until this is fixed all Papyrus builds will be failing (Except maybe for Gerrit builds based on an older version of Papyrus Master, which didn’t
rely on M7 dependencies)
Regards,
Camille