Hi Raja, Let’s think of a way to get the BVT score on any PR that is opened. Then we know if there’s a problem introduced in a PR before merge, instead of after. We need to automate this, or else we keep having the same issues.
We can meet online somewhere next week to discuss our approach? I like setting a date, but it needs to be realistic. We’re not going to solve all blockers by just saying it should be resolved next week. Many people need to step in and each fix one blocker or else it will take much longer. And it’s not only fixing blockers, but also testing them once a PR is there. Testing means building a CloudStack setup, verifying the problem is gone, etc. Regards, Remi On 18/09/15 13:55, "Raja Pullela" <raja.pull...@citrix.com> wrote: >Hi, > >We have been having steady rate of blocker issues/breakages. I am proposing >to see if we can get to a 100% passrate on BVTs by next Friday, Sep 25th or >sooner. > >Once we reach 100% passrate, we should closely monitor BVTs and back out >commits that we think have broken BVTs. >I will report the BVTs passrate on a daily basis. Also, working with Kishan >to see a way to make the data available online? > >Here is the latest status on the BVTs - >XS Basic - 93% / >CLOUDSTACK-8843<https://issues.apache.org/jira/browse/CLOUDSTACK-8843> (in the >process of testing Jayapal's fix), >XS Adv - 81.8% / >CLOUDSTACK-8881<https://issues.apache.org/jira/browse/CLOUDSTACK-8881>, >CLOUDSTACK-8697<https://issues.apache.org/jira/browse/CLOUDSTACK-8697> > >KVM Basic - Deployment failure / >CLOUDSTACK-8883<https://issues.apache.org/jira/browse/CLOUDSTACK-8883> > >KVM Adv - Deployment failure / >CLOUDSTACK-8883<https://issues.apache.org/jira/browse/CLOUDSTACK-8883>, >CLOUDSTACK-8881<https://issues.apache.org/jira/browse/CLOUDSTACK-8881>, >CLOUDSTACK-8697 > >BTW - currently, no one has picked up >CLOUDSTACK-8883<https://issues.apache.org/jira/browse/CLOUDSTACK-8883> yet, > >best, >Raja >
