[Gluster-devel] Regression with brick multiplex turned on failing or aborted

[Atin Mukherjee]

On Sat, May 27, 2017 at 2:57 PM, Atin Mukherjee <amukherj at redhat.com> wrote:

>
> On Sat, 27 May 2017 at 09:55, Nigel Babu <nigelb at redhat.com> wrote:
>
>> FYI: There are now emails to gluster-maintainers@ about this. If you'd
>> like to help diagnose/fix the problems, please see the job and logs here:
>> https://build.gluster.org/job/regression-test-with-multiplex/
>>
>
> Thank you Nigel for taking this up. It definitely helps to track if any of
> the recent changes has caused regression in brick mux feature. I've been
> following the reports (and so as Jeff I believe). Currently there are two
> failures which every run will report.
>
> ./tests/bugs/glusterd/bug-1406411-fail-add-brick-on-replica-count-change.t
>
> ./tests/features/trash.t
>
>
> Both the failures are RCAed and expect these failures to be fixed in few days time. Nigel did brought to my notice about one of the run where it was waiting on some LVM setup too long and then the run was aborted, but I'm notsure if brick mux has anything to do with it. Any other aborted runs Nigel?
>
>

Though the above two test failures are now been addressed, the result of
the overall runs do not look promising. Too many failures and aborted runs
@ https://build.gluster.org/job/regression-test-with-multiplex/ . I'll be
checking the failures in detail and get back with further updates.


>
>
>> --
>> nigelb
>> _______________________________________________
>> Gluster-devel mailing list
>> Gluster-devel at gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-devel
>
> --
> - Atin (atinm)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20170604/832ce512/attachment.html>