Hi All, For anybody interested I setup my own mirror of cloudstack: https://github.com/cs-travis-runs/cs-travis-run It will check for updates every 5 minutes.
As this isn't owned by the apache travis account we get all 5 concurrent jobs to ourselves. Along with this we can assign user roles so people can abort or re-trigger jobs. https://travis-ci.org/cs-travis-runs/cs-travis-run/builds If anybody wants access let me know your github username and I can add it. Thanks, Ian On 17 September 2014 23:21, Edison Su <edison...@citrix.com> wrote: > I only checked into my personal branch: pytest, which is converting nose > to pytest, so if you run nose against pytest test cases, definitely, it > will fail. > I think it's ok to fail for travis on my pytest branch at this time, as I > haven't start the discussion in the community about how to improve marvin > yet. > > > -----Original Message----- > > From: sebgoa [mailto:run...@gmail.com] > > Sent: Wednesday, September 17, 2014 4:34 AM > > To: dev@cloudstack.apache.org; Edison Su; Min Chen > > Subject: Travis failures > > > > Hi folks, > > > > With Travis tests now passing, it's a good time for everyone to get > familiar > > with it and understanding the tests that are being run (advanced zone, > > simulator, smoke tests). > > > > While most builds have been green since yesterday there was two commits > > (from Edison and Min) that turned out red. > > > > https://travis-ci.org/apache/cloudstack/builds > > > > Ideally we should all get in the habit of committing on a separate > branch, let > > the tests run and when they pass we can commit to master or the main > > develop branch. > > > > my 2cts > > > > -Sebastien >
