[Gluster-devel] [FAILED] NetBSD-regression for ./tests/basic/afr/self-heald.t

Ravishankar N ravishankar at redhat.com
Mon Feb 8 10:14:43 UTC 2016


On 02/08/2016 03:37 PM, Emmanuel Dreyfus wrote:
> On Mon, Feb 08, 2016 at 03:26:54PM +0530, Milind Changire wrote:
>> https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/14089/consoleFull
>>
>>
>> [08:44:20] ./tests/basic/afr/self-heald.t ..
>> not ok 37 Got "0" instead of "1"
>> not ok 52 Got "0" instead of "1"
>> not ok 67
>> Failed 4/83 subtests
> There is a core but it is from NetBSD FUSE subsystem. The trace is
> not helpful but suggests an abort() call because of unexpected
> situation:
>
> Core was generated by `perfused'.
> Program terminated with signal SIGABRT, Aborted.
> #0  0xbb7574b7 in _lwp_kill () from /usr/lib/libc.so.12
> (gdb) bt
> #0  0xbb7574b7 in _lwp_kill () from /usr/lib/libc.so.12
>
> /var/log/messages has a hint:
> Feb  8 08:43:15 nbslave7c perfused: file write grow without resize
>
> Indeed I have this assertion in NetBSD FUSE to catch a race condition.
> I think it is the first time I see hit raised, but I am unable to
> conclude on the cause. Let us retrigger (I did it) and see if someone
> else ever hit that again. The bug is more likely in NetBSD FUSE than
> in glusterfs.
>
The .t has been added to bad tests for now @ 
http://review.gluster.org/#/c/13344/, so you can probably rebase your patch.
I'm not sure this is a problem with the case, the same issue was 
reported by Manikandan last week : 
https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/13895/consoleFull 

Is it one of those vndconfig errors? The .t seems to have skipped a few 
tests:

-------------------
./tests/basic/afr/self-heald.t (Wstat: 0 Tests: 82 Failed: 3)
   Failed tests:  37, 52, 67
   Parse errors: Tests out of sequence.  Found (31) but expected (30)
                 Tests out of sequence.  Found (32) but expected (31)
                 Tests out of sequence.  Found (33) but expected (32)
                 Tests out of sequence.  Found (34) but expected (33)
                 Tests out of sequence.  Found (35) but expected (34)
Displayed the first 5 of 54 TAP syntax errors.
Re-run prove with the -p option to see them all.





More information about the Gluster-devel mailing list