[Gluster-devel] reviving spurious failures tracking

[Raghavendra Talur]

On Wed, Jul 29, 2015 at 6:57 PM, Pranith Kumar Karampuri <
pkarampu at redhat.com> wrote:

>
>
> On 07/29/2015 06:56 PM, Pranith Kumar Karampuri wrote:
>
>>
>>
>> On 07/29/2015 06:10 PM, Emmanuel Dreyfus wrote:
>>
>>> On Wed, Jul 29, 2015 at 04:06:43PM +0530, Vijay Bellur wrote:
>>>
>>>> - If there are tests that cannot be fixed easily in the near term, we
>>>> move
>>>> such tests to a different folder or drop such test units.
>>>>
>>> A tests/disabled directory seemsthe way to go. But before going there,
>>> the test maintaniner should be notified. Perhaps we should have a list
>>> of contacts ina comment on the topof each test?
>>>
>> Jeff already implemented bad-tests infra already. We can use the same?
>>
> Check is_bad_test() in run-tests.sh


tests/basic/mount-nfs-auth.t is failing very frequently on netbsd machines.
The latest failure is
https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/9296/consoleFull

The test always passes when run in bash -x mode. It seems that timeout for
test 51 and test 52 is
sometimes not enough. Can any one from NFS team verify the same and
increase the timeout if
required?

I will be moving the test to bad test list till this is fixed.



>
> Pranith
>
>
>> Pranith
>>
>>>
>>>
>> _______________________________________________
>> Gluster-devel mailing list
>> Gluster-devel at gluster.org
>> http://www.gluster.org/mailman/listinfo/gluster-devel
>>
>
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20150817/aa9a750a/attachment-0001.html>