cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Angus <>
Subject RE: Known trillian test failures
Date Wed, 20 Dec 2017 18:21:48 GMT
Hi Marc-Aurèle, (and everyone else)

The title probably is slightly incorrect.  It should really say known Marvin test failures.
 Trillian is the automation that creates the environments to run the tests in, the tests are
purely those that are in Marvin codebase so anyone can repeat them.  In fact we would like
to see other people running the tests in their environments and comparing the results.

With regard to the failing tests, I agree, that it would be dangerous to hide failures.
I would like to see however, a matrix of known good and known bad tests, and any PR that then
fails known good tests has a problem.
With a visible list of known bad tests we can 'not fail' a PR due to failing a bad test, and
also there would be a list of bad tests which the community can attack and whittle down the
list until all tests *should* pass.

That way we can make clear (automated) decisions on pass/fail.  Rather than get a list of
pass/fails that we then have to interpret.

Kind regards,

Paul Angus
53 Chandos Place, Covent Garden, London  WC2N 4HSUK

-----Original Message-----
From: Marc-Aurèle Brothier [] 
Sent: 20 December 2017 12:56
Subject: Known trillian test failures


Could something be done to avoid confusing people pushing PR to have trillian test failures,
which apparently are know to fail all the time or often? I know it's hard to keep the tests
in good shape and make them run smoothly but I find it very disturbing and therefore I have
to admit I'm not paying attention to those outputs, sadly.

Skipping them adds the high risk of never getting fixed... I would hope that someone having
full access the the management & agent's logs could fix them, since AFAIK they aren't

View raw message