[Gluster-devel] CentOS 7: Gluster Test Framework testcases failure

[Kiran Patil]

Now on XFS, the Test Summary Report is same as running on ZFS except test
case bug-953887.t failure.

Test case tests/bugs/bug-953887.t expects force at end of line, TEST
gluster volume add-brick $V0 $H0:$B0/${V0}{2,3} and it passed once force is
substituted at the end of the line.

Test case tests/bugs/bug-767095.t failed due to path issue and now it no
more fails.

So the failures are no more specific to on disk filesystems such as ZFS and
XFS but glusterfs.

Thanks,
Kiran.

On Sat, Sep 27, 2014 at 1:30 PM, Kiran Patil <kirantpatil at gmail.com> wrote:

> I ran each testcases with DEBUG=1 and pasted at http://ur1.ca/i8xay (
> http://fpaste.org/136940/)
>
> This time I ran the testcases by keeping default paths and now
> tests/bugs/bug-861542.t passes
>
> Need to create /var/run/gluster directory on reboot
>
> Test Setup:
> ---------------------
> CentOS 7 : 3.10.0-123.8.1.el7.x86_64
>
> gluster --version : glusterfs 3.4.5 built on Jul 24 2014 19:14:13
>
> Zfs : zfs-0.6.3
>
> glusterfs testcases version :
> git branch : * (detached from v3.4.5)
>
>
> Test Summary Report
> -------------------
> ./tests/bugs/bug-802417.t                       (Wstat: 0 Tests: 39
> Failed: 2)
>   Failed tests:  28, 31
> ./tests/bugs/bug-821056.t                       (Wstat: 0 Tests: 21
> Failed: 1)
>   Failed test:  15
> ./tests/bugs/bug-908146.t                       (Wstat: 0 Tests: 10
> Failed: 2)
>   Failed tests:  8-9
> ./tests/bugs/bug-913555.t                       (Wstat: 0 Tests: 11
> Failed: 4)
>   Failed tests:  4-6, 9
> ./tests/bugs/bug-948686.t                       (Wstat: 0 Tests: 19
> Failed: 8)
>   Failed tests:  5-7, 9, 11, 13-15
> ./tests/bugs/bug-948729/bug-948729-force.t      (Wstat: 0 Tests: 35
> Failed: 6)
>   Failed tests:  29-31, 33-35
> ./tests/bugs/bug-948729/bug-948729-mode-script.t (Wstat: 0 Tests: 35
> Failed: 6)
>   Failed tests:  29-31, 33-35
> ./tests/bugs/bug-948729/bug-948729.t            (Wstat: 0 Tests: 23
> Failed: 2)
>   Failed tests:  19, 23
> Files=123, Tests=2019, 4834 wallclock secs ( 1.62 usr  0.25 sys + 258.83
> cusr 201.05 csys = 461.75 CPU)
> Result: FAIL
>
> Thanks,
> Kiran.
>
> On Fri, Sep 26, 2014 at 9:32 PM, Lalatendu Mohanty <lmohanty at redhat.com>
> wrote:
>
>> On 09/26/2014 02:59 AM, Justin Clift wrote:
>>
>>> On 25/09/2014, at 9:28 PM, Lalatendu Mohanty wrote:
>>> <snip>
>>>
>>>> Have we published somewhere which distributions or OS versions we are
>>>> running regression tests ? if not lets compile it and publish as this will
>>>> help community to understand which os distributions are part of the
>>>> regression testing.
>>>>
>>> The best we have so far is probably this:
>>>
>>>    http://www.gluster.org/community/documentation/index.
>>> php/Using_the_Gluster_Test_Framework
>>>
>>>
>>>  Do we have plans to run regression on a variety of distributions? Not
>>>> sure how difficult or complex it is to maintain.
>>>>
>>> The primary OS at the moment is CentOS 6.x (mainly due to it
>>> being the primary OS for GlusterFS I think).
>>>
>>> Manu and Harsha have been going through the regression tests
>>> recently, making them more cross platform in order to run on
>>> the BSDs.
>>>
>>> This effort has also highlighted some interesting Linux
>>> specific behaviour in the main GlusterFS code base, and led
>>> to fixes there.
>>>
>>> In short, we're all for running the regression tests on as
>>> many distributions as possible.  If Community members want
>>> to put VM's or something online (medium-long term), I'd be
>>> happy to hook our Jenkins infrastructure up to them to
>>> automatically run tests on them.
>>>
>>> Is that kind of what you're asking? :)
>>>
>>
>> Yup, I will try to get a CentOS 7 instance for running regression tests :)
>>
>> -Lala
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-devel/attachments/20140927/75416a72/attachment-0001.html>