------------------------------------------------------------------------------------------------------------------------------------------------
Sébastien Gérard
+33 (0)1 69 08 58 24 / +33(0)6 88 20 00 47
CEA Saclay Nano-INNOV
Institut CARNOT CEA LIST
DILS/Laboratoire
d’Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE),
Point Courrier n°174
91 191 Gif sur Yvette CEDEX
www.eclipse.org/papyrus
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de LETAVERNIER Camille
Envoyé : mardi 17 septembre 2013 09:53
À : Papyrus Project list
Objet : [PROVENANCE INTERNET] Re: [mdt-papyrus.dev] Nightly test execution results
Hi Christian,
The Trunk nightly tests have not completed properly for a few months (Because of Timeouts, related to Papyrus memory leaks). When the job completes, I think
the test results are properly displayed.
Regards,
Camille
Hi,
The Papyrus nightly build of the master branch test execution [1] differs from the similar build for the "extra" plug-ins tests [2]. Unlike the latter, it doesn't show a link to the JUnit test report. Compare
which has a handy link to the test report, with this:
which provides only an inconvenient archive download. Moreover, the "extra" test builds show yellow balls (unstable builds) which is correct, but the main test builds show grey balls, not yellow, despite having test failures.
All in all, it is hard to judge the health of the tests. Is there an intentional reason for this difference? Is it easy to make the main test build behave more like the "extra" test build? Is this already on somebody's
plan?