[Gluster-devel] NetBSD tests not running to completion.

Pranith Kumar Karampuri pkarampu at redhat.com
Sun Jan 10 08:34:05 UTC 2016



On 01/10/2016 11:08 AM, Emmanuel Dreyfus wrote:
> Pranith Kumar Karampuri <pkarampu at redhat.com> wrote:
>
>> tests/basic/afr/arbiter-statfs.t
> I posted patches to fix this one (but it seems Jenkins is down? No
> regression is running)
>
>> tests/basic/afr/self-heal.t
It seems like in this run, self-heal.t and quota.t are running at the 
same time. Not sure why that can happen. So for now not going to 
investigate more.
[2016-01-08 07:58:55.6N]:++++++++++ G_LOG:./tests/basic/afr/self-heal.t: 
TEST: 88 88 test -d /d/backends/brick0/file ++++++++++
[2016-01-08 07:58:55.6N]:++++++++++ G_LOG:./tests/basic/afr/self-heal.t: 
TEST: 89 89 diff /dev/fd/63 /dev/fd/62 ++++++++++
[2016-01-08 07:58:55.6N]:++++++++++ G_LOG:./tests/basic/quota.t: TEST: 
124 124 gluster --mode=script --wignore volume quota patchy limit-usage 
/addbricktest/dir8 100MB ++++++++++
[2016-01-08 07:58:55.6N]:++++++++++ G_LOG:./tests/basic/afr/self-heal.t: 
TEST: 92 92 rm -rf /mnt/glusterfs/0/addbricktest ++++++++++
[2016-01-08 07:58:55.6N]:++++++++++ G_LOG:./tests/basic/quota.t: TEST: 
124 124 gluster --mode=script --wignore volume quota patchy limit-usage 
/addbricktest/dir9 100MB ++++++++++

>> tests/basic/afr/entry-self-heal.t
This seem to have a bit of history. We have more data points that keeps 
failing once in a while considering that michael posted a patch: 
http://review.gluster.org/12938

Will be looking into this more now.
> That two ones are still to be investigated, and it seems
> tests/basic/afr/split-brain-resolution.t is now reliabily broken as
> well.
Will take a look at this today after entry-self-heal.t

Pranith
>
>> tests/basic/quota-nfs.t
> That one is marked as bad test and should not cause harm on spurious
> failure as its result is ignored.
>
> I am trying to reproduce a spurious VM reboot during tests by looping on
> the whole test suite on nbslave70, with reboot on panic disabled (it
> will drop into kernel debugger instead). No result so far.
>



More information about the Gluster-devel mailing list