Hi Marc,
You've raised a very valid concern. When we've known list of smoketest failures, it's understandable that most people may not understand how to interpret them and ignore them. Access to the Trillian environment is another issue. I don't have all the answers and a solution ot these problems at the moment but let me discuss that internally and get back to you. Can you and others help review PR 2211 where I've tried to address that? I ask this because this PR not only tries to migrate us to a newer Debian systemvmtemplate but focuses on stabilizing master by getting almost 100% smoketest pass rate on VMware/KVM/XenServer, to get there I had to fix some tests as well. Once we can have such a pass rate on master, it will be easier to verify test results on other PRs against the baseline. I'll see if we can improvement Trillian test runs to include management server (and agent) logs in the marvin log zip that is put as part of the result on the github pr. - Rohit ________________________________ From: Marc-Aur?le Brothier <ma...@exoscale.ch> Sent: Wednesday, December 20, 2017 6:26:05 PM To: dev@cloudstack.apache.org Subject: Known trillian test failures @rhtyd 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 available. Cheers rohit.ya...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue
