I assume we build with --enable-gnfs turned on. Unlikely that its not, but
just pointing it out as initially I ran into some failures due to gNFS
server not coming due to lake of relevant libraries.
On Thu, Mar 15, 2018 at 3:46 PM, Raghavendra Gowdappa
wrote:
> Providing
Providing more links to failure:
https://build.gluster.org/job/experimental-periodic/227/console
https://build.gluster.org/job/regression-test-burn-in/3836/console
On Thu, Mar 15, 2018 at 3:39 PM, Raghavendra Gowdappa
wrote:
> I can reproduce the failure even without my
I can reproduce the failure even without my patch on master. Looks like
this test resulted in failures earlier too.
[1] http://lists.gluster.org/pipermail/gluster-devel/2015-May/044932.html
[2] See mail to gluster-maintainers with subj: "Build failed in Jenkins:
regression-test-burn-in #3836"
When the test works it takes less than 60 seconds. If it needs more than
200 seconds, that means there's an actual issue.
On Wed, Mar 14, 2018 at 10:16 AM, Raghavendra Gowdappa
wrote:
> All,
>
> I was trying to debug a regression failure [1]. When I ran test locally on
> my
All,
I was trying to debug a regression failure [1]. When I ran test locally on
my laptop, I see some warnings as below:
++ gluster --mode=script --wignore volume get patchy nfs.mount-rmtab
++ xargs dirname
++ awk '/^nfs.mount-rmtab/{print $2}'
dirname: missing operand
Try 'dirname --help' for