On Tue, Sep 27, 2016 at 01:13:15PM +0530, Nigel Babu wrote:
> On Tue, Sep 27, 2016 at 12:52:45PM +0530, Pranith Kumar Karampuri wrote:
> > On Tue, Sep 27, 2016 at 12:39 PM, Nigel Babu wrote:
> >
> > > On Tue, Sep 27, 2016 at 12:00:40PM +0530, Pranith Kumar Karampuri wrote:
> >
On Fri, Sep 30, 2016 at 4:00 PM, Nigel Babu wrote:
> On Tue, Sep 27, 2016 at 01:13:15PM +0530, Nigel Babu wrote:
> > On Tue, Sep 27, 2016 at 12:52:45PM +0530, Pranith Kumar Karampuri wrote:
> > > On Tue, Sep 27, 2016 at 12:39 PM, Nigel Babu
> wrote:
> > >
>
On Tue, Sep 27, 2016 at 12:52:45PM +0530, Pranith Kumar Karampuri wrote:
> On Tue, Sep 27, 2016 at 12:39 PM, Nigel Babu wrote:
>
> > On Tue, Sep 27, 2016 at 12:00:40PM +0530, Pranith Kumar Karampuri wrote:
> > > On Tue, Sep 27, 2016 at 11:20 AM, Nigel Babu
On Tue, Sep 27, 2016 at 12:39 PM, Nigel Babu wrote:
> On Tue, Sep 27, 2016 at 12:00:40PM +0530, Pranith Kumar Karampuri wrote:
> > On Tue, Sep 27, 2016 at 11:20 AM, Nigel Babu wrote:
> >
> > > These are gbench failures rather than smoke failures. If you
On Tue, Sep 27, 2016 at 12:00:40PM +0530, Pranith Kumar Karampuri wrote:
> On Tue, Sep 27, 2016 at 11:20 AM, Nigel Babu wrote:
>
> > These are gbench failures rather than smoke failures. If you know how to
> > debug dbench failures, please add comments on the bug and I'll get
On Tue, Sep 27, 2016 at 11:20 AM, Nigel Babu wrote:
> These are gbench failures rather than smoke failures. If you know how to
> debug dbench failures, please add comments on the bug and I'll get you the
> logs you need.
>
Oh, we can't archive the logs like we do for
These are gbench failures rather than smoke failures. If you know how to
debug dbench failures, please add comments on the bug and I'll get you the
logs you need.
On Tue, Sep 27, 2016 at 9:40 AM, Ravishankar N
wrote:
> On 09/27/2016 09:36 AM, Pranith Kumar Karampuri
On 09/27/2016 09:36 AM, Pranith Kumar Karampuri wrote:
hi Nigel,
Is there already a bug to capture these in the runs when
failures happen? I am not able to understand why this failure
happened: https://build.gluster.org/job/smoke/30843/console,
logs/cores would have helped. Let me know
hi Nigel,
Is there already a bug to capture these in the runs when failures
happen? I am not able to understand why this failure happened:
https://build.gluster.org/job/smoke/30843/console, logs/cores would have
helped. Let me know if I should raise a bug for this.
--
Pranith