+1 it doesn’t help like this.
I look at actual test result people post combined with code reviews. Plus an OK from Jenkins should be more than enough to judge a PR. Let’s make Jenkins more reliable, that would help as well. Regards, Remi On 29/10/15 10:33, "Daan Hoogland" <daan.hoogl...@gmail.com> wrote: >Guys and dolls, > >We have been having travis builds for a while now and they seem to generate >more work then help. There are a lot of time-outs, (false positive) and >when a suite passes it is often because all tests where skipped (false >negative). In addition, and this may be just me, I've never been able to >pinpoint a problem based on travis output. > >therefore: > >I move that we completely disable travis runs on PRs to the cloudstack >project. This will reduce confusion about whether a PR is good and will >reduce the need for willing contributers to force push their branch over >and over. > >-- >Daan
