On 04/14/2016 04:38 PM, Jeff Darcy wrote:
>> On Thu, Apr 14, 2016 at 10:13 AM, Atin Mukherjee < amukh...@redhat.com >
>> wrote:
>
>>> I am pretty sure that earlier we used to log the culprit test generating
>>
>>> the core. But now I don't see that same behavior in these runs [1] [2]
>>
>
>>> [
> On Thu, Apr 14, 2016 at 10:13 AM, Atin Mukherjee < amukh...@redhat.com >
> wrote:
> > I am pretty sure that earlier we used to log the culprit test generating
>
> > the core. But now I don't see that same behavior in these runs [1] [2]
>
> > [1]
>
> > https://build.gluster.org/job/rackspace-
On Thu, Apr 14, 2016 at 10:13 AM, Atin Mukherjee
wrote:
> I am pretty sure that earlier we used to log the culprit test generating
> the core. But now I don't see that same behavior in these runs [1] [2]
>
> [1]
>
> https://build.gluster.org/job/rackspace-regression-2GB-triggered/19709/consoleFul
I am pretty sure that earlier we used to log the culprit test generating
the core. But now I don't see that same behavior in these runs [1] [2]
[1]
https://build.gluster.org/job/rackspace-regression-2GB-triggered/19709/consoleFull
[2]
https://build.gluster.org/job/rackspace-regression-2GB-triggere