<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <br>
    <div class="moz-cite-prefix">On 07/20/2015 12:45 PM, Niels de Vos
      wrote:<br>
    </div>
    <blockquote
      cite="mid:20150720071518.GY29861@ndevos-x240.usersys.redhat.com"
      type="cite">
      <pre wrap="">On Mon, Jul 20, 2015 at 09:25:15AM +0530, Ravishankar N wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">I'll take a look.
</pre>
      </blockquote>
      <pre wrap="">
Thanks. I'm actually not sure if this is a arbiter.t issue, maybe I
blamed it too early? Its the first test that gets executed, and no
others are tried after it failed.

Niels


</pre>
      <blockquote type="cite">
        <pre wrap="">Regards,
Ravi

On 07/20/2015 03:07 AM, Niels de Vos wrote:
</pre>
        <blockquote type="cite">
          <pre wrap="">I have seen several occurences of failures in arbiter.t now. This is one
of the errors:

    <a class="moz-txt-link-freetext" href="https://build.gluster.org/job/rackspace-regression-2GB-triggered/12626/consoleFull">https://build.gluster.org/job/rackspace-regression-2GB-triggered/12626/consoleFull</a>

    [21:20:20] ./tests/basic/afr/arbiter.t ..
    not ok 7 Got "N" instead of "Y"
    not ok 15
    not ok 16 Got "" instead of "1"
    not ok 23 Got "" instead of "1"
    not ok 25 Got "0" when not expecting it
    not ok 26
    not ok 34 Got "0" instead of "1"
    not ok 35 Got "0" instead of "1"
    not ok 41 Got "" instead of "1"
    not ok 47 Got "N" instead of "Y"
    Failed 10/47 subtests
    [21:20:20]
    Test Summary Report
    -------------------
    ./tests/basic/afr/arbiter.t (Wstat: 0 Tests: 47 Failed: 10)
      Failed tests:  7, 15-16, 23, 25-26, 34-35, 41, 47</pre>
        </blockquote>
      </blockquote>
    </blockquote>
    <br>
    <br>
    <br>
    <blockquote type="cite"><br>
    </blockquote>
    <br>
    <font color="#3333ff"><tt>So the test #7 that failed is "16
        EXPECT_WITHIN $UMOUNT_TIMEOUT "Y" force_umount $M0"</tt><tt><br>
      </tt><tt>
        Looking at mnt-glusterfs-0.log, I see that the unmount has
        already happened before the actual command was run, at least
        from the time stamp logged by G_LOG() function.</tt><tt><br>
      </tt><tt>
      </tt><tt><br>
      </tt><tt>
        [2015-07-19 21:16:21.784293] I
        [fuse-bridge.c:4946:fuse_thread_proc] 0-fuse: unmounting
        /mnt/glusterfs/0</tt><tt><br>
      </tt><tt>
        [2015-07-19 21:16:21.784542] W
        [glusterfsd.c:1214:cleanup_and_exit]
        (--&gt;/lib64/libpthread.so.0(+0x79d1) [0x7fc3f41c49d1]
        --&gt;glusterfs(glusterfs_sigwaiter+0xe4) [0x409734]
        --&gt;glusterfs(cleanup_and_exit+0x87) [0x407ba7] ) 0-: received
        signum (15), shutting down</tt><tt><br>
      </tt><tt>
        [2015-07-19 21:16:21.784571] I [fuse-bridge.c:5645:fini] 0-fuse:
        Unmounting '/mnt/glusterfs/0'.</tt><tt><br>
      </tt><tt>
        [2015-07-19 21:16:21.785817332]:++++++++++
        G_LOG:./tests/basic/afr/arbiter.t: TEST: 15 ! stat
        /mnt/glusterfs/0/.meta/graphs/active/patchy-replicate-0/options/arbiter-count

        ++++++++++</tt><tt><br>
      </tt><tt>
        [2015-07-19 21:16:21.796574975]:++++++++++
        G_LOG:./tests/basic/afr/arbiter.t: TEST: 16 Y force_umount
        /mnt/glusterfs/0 ++++++++++</tt><tt><br>
      </tt><tt>
      </tt><tt><br>
      </tt><tt>
        I have no clue as to why that could have happened because
        appending to the gluster log files using G_LOG() is done
        *before* the test is executed.</tt><tt> In all my trial runs,
        the G_LOG message gets logged first, followed by the logs
        relevant to the actual command being run.<br>
        <br>
      </tt><tt>
      </tt><tt><br>
      </tt><tt>FWIW, <a class="moz-txt-link-freetext" href="http://review.gluster.org/#/c/11114/">http://review.gluster.org/#/c/11114/</a> changed made
        the following change to arbiter.t  amongst other test cases :</tt><tt><br>
      </tt><tt><br>
        -TEST umount $M0</tt><tt><br>
      </tt><tt>+EXPECT_WITHIN $UMOUNT_TIMEOUT "Y" force_umount $M0</tt><tt><br>
      </tt><tt><br>
        But I'm not sure doing a umount -f has any impact for fuse
        mounts.</tt><tt><br>
      </tt><tt><br>
      </tt></font><tt><font color="#3333ff">Regards,<br>
        Ravi</font><br>
    </tt><tt>
    </tt><br>
    <blockquote
      cite="mid:20150720071518.GY29861@ndevos-x240.usersys.redhat.com"
      type="cite">
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">
    Files=1, Tests=47, 243 wallclock secs ( 0.04 usr  0.00 sys + 15.22 cusr  3.48 csys = 18.74 CPU)
    Result: FAIL


Who could have look at this?

Thanks,
Niels
_______________________________________________
Gluster-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a>
<a class="moz-txt-link-freetext" href="http://www.gluster.org/mailman/listinfo/gluster-devel">http://www.gluster.org/mailman/listinfo/gluster-devel</a>
</pre>
        </blockquote>
        <pre wrap="">
</pre>
      </blockquote>
    </blockquote>
    <br>
  </body>
</html>