On Wed, Aug 31, 2016 at 4:23 PM, Raghavendra Talur <rtalur@xxxxxxxxxx> wrote:
This is not a good long-term idea. That's not the only test we fail on. We fail on that a good number of times, but we also fail on other tests.
-- Hi All,We have a test [1] which is causing hangs in NetBSD. We have not been able to debug the issue yet.It could be because the bash script does not comply with posix guidelines or that there is a bug in the brick code.However, as we have 3.9 merge deadline tomorrow this is causing the test pipeline to grow a lot and needing manual intervention.I recommend we disable this test for now. I request Kaushal to provide pass flags to the patch [2] for faster merge.[1] ./tests/features/lock_revocation.t
This is not a good long-term idea. That's not the only test we fail on. We fail on that a good number of times, but we also fail on other tests.
Have
we confirmed this is not a Gluster bug that we'll be shipping? Because
that'd be quite a terrible thing to ship to our users.
Especially because it also happened in CentOS once, so it's not entirely "a NetBSD problem": https://build.gluster.org/job/centos6-regression/339/console
I've
been trying to get maintainers of the component and the test framework
to look at this bug for weeks now. If we only care about failing tests
enough to disable it right before release, that's going to cause more
technical debt than actually catch any regressions.Especially because it also happened in CentOS once, so it's not entirely "a NetBSD problem": https://build.gluster.org/job/
nigelb
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
