On Thu, Jul 24, 2014 at 04:31:05PM +, Jeremy Stanley wrote:
> On 2014-07-18 15:09:34 +0100 (+0100), Daniel P. Berrange wrote:
> [...]
> > If there were multiple failures and only some were identified, it would
> > be reasonable to *not* automatically recheck.
> [...]
>
> Another major blocker
On 2014-07-18 15:09:34 +0100 (+0100), Daniel P. Berrange wrote:
[...]
> If there were multiple failures and only some were identified, it would
> be reasonable to *not* automatically recheck.
[...]
Another major blocker is that we often add signatures for failures
which occur 100% of the time, and
On Fri, Jul 18, 2014 at 09:06:45AM -0500, Matt Riedemann wrote:
>
>
> On 7/17/2014 9:01 AM, Matthew Booth wrote:
> >Elastic recheck is a great tool. It leaves me messages like this:
> >
> >===
> >I noticed jenkins failed, I think you hit bug(s):
> >
> >check-devstack-dsvm-cells: https://bugs.laun
On 7/17/2014 9:01 AM, Matthew Booth wrote:
Elastic recheck is a great tool. It leaves me messages like this:
===
I noticed jenkins failed, I think you hit bug(s):
check-devstack-dsvm-cells: https://bugs.launchpad.net/bugs/1334550
gate-tempest-dsvm-large-ops: https://bugs.launchpad.net/bugs/13
Elastic recheck is a great tool. It leaves me messages like this:
===
I noticed jenkins failed, I think you hit bug(s):
check-devstack-dsvm-cells: https://bugs.launchpad.net/bugs/1334550
gate-tempest-dsvm-large-ops: https://bugs.launchpad.net/bugs/1334550
We don't automatically recheck or reveri
