[Bugs] [Bug 1358594] Enable gfapi test cases in Gluster upstream regression

bugzilla at redhat.com bugzilla at redhat.com
Wed Jul 27 16:29:33 UTC 2016


https://bugzilla.redhat.com/show_bug.cgi?id=1358594



--- Comment #9 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14997 committed in master by Jeff Darcy
(jdarcy at redhat.com) 
------
commit 4e1ad2c96ea692e49fb82ce533cdc26818277e8d
Author: Poornima G <pgurusid at redhat.com>
Date:   Mon Jul 25 10:26:58 2016 +0530

    tests: Fix the spurious failure in libgfapi-fini-hang.t

    RCA:
    After running libgfapi-fini-hang, there is a EXPECT_WITHIN which waits
    for PROCESS_UP_TIMEOUT(20s), for the process libgfapi-fini-hang to die.
    Currently EXPECT_WITHIN is returning success even if the process
    libgfapi-fini-hang is alive. This is because "pgrep libgfapi-fini-hang"
    in check_process() is returning 1(no process alive) even if the process
    is alive. Man page of pgrep says "The process name used for matching is
    limited to the 15 characters". Hence changing the name of executable from
    libgfapi-fini-hang to gfapi-hang, so that it falls within the limit.

    As explained the failure is not because there was a hang(logs show that
    glfs_set_volfile_server was still executing), but because EXPECT_WITHIN
    was not really waiting. And hence there was a race between the execution
    of the process libgfapi-fini-hang and the kill.

    Change-Id: I257715865e0d3e5a14f83d1e235c01899e1cae68
    BUG: 1358594
    Signed-off-by: Poornima G <pgurusid at redhat.com>
    Reviewed-on: http://review.gluster.org/14997
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur at redhat.com>
    Reviewed-by: Niels de Vos <ndevos at redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Tested-by: Gluster Build System <jenkins at build.gluster.org>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=06zPgA77E7&a=cc_unsubscribe


More information about the Bugs mailing list