Thanks, I didn't realize that the problem was failure to complete the build, but of course, that makes sense now that you explain it.
Please let me know if I can help in some way. Perhaps there are some specific bugzillae tracking the leaks that may be in areas of the code with which I am familiar?
cW
Sent from my iPhone
To complete the email of Camille, of course, we are working on this memory leaks. We did already a lot of progress, but we still need to fix some others. It
is definitively in the plan for Luna to fix them.
------------------------------------------------------------------------------------------------------------------------------------------------
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
<image003.png>www.eclipse.org/papyrus
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?
|
