Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
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

__________________________

Camille Letavernier

+33 (0)1 69 08 00 59 - camille.letavernier@xxxxxx

CEA LIST - Laboratoire d'Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE)

Papyrus : http://www.eclipse.org/papyrus

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Christian W. Damus
Envoyé : mardi 17 septembre 2013 05:04
À : Papyrus Project list
Objet : [mdt-papyrus.dev] Nightly test execution results

 


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?

 

Thanks,

 

Christian

 

 

 


Back to the top