Bug 1209286

Summary: Spurious regression failures in uss.t
Product: [Community] GlusterFS Reporter: Jeff Darcy <jdarcy>
Component: testsAssignee: Jeff Darcy <jdarcy>
Status: CLOSED DUPLICATE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs, gluster-bugs
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1219028 (view as bug list) Environment:
Last Closed: 2015-05-06 12:57:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1163543, 1219028    

Description Jeff Darcy 2015-04-07 00:43:05 UTC 
The failing test is #26 (line 78), which tries to list .snaps immediately after a mount.
Comment 1 Anand Avati 2015-04-07 00:46:13 UTC 
REVIEW: http://review.gluster.org/10143 (tests: fix spurious regression in uss.t) posted (#1) for review on master by Jeff Darcy (jdarcy)
Comment 2 Anand Avati 2015-04-07 05:37:41 UTC 
COMMIT: http://review.gluster.org/10143 committed in master by Vijay Bellur (vbellur) 
------
commit 2ef9ad2dc5822b9b88243cb7f60816fe1c531e91
Author: Jeff Darcy <jdarcy>
Date:   Mon Apr 6 20:44:09 2015 -0400

    tests: fix spurious regression in uss.t
    
    Sometimes .snaps just doesn't seem to be available right after a
    mount.  I have no idea, but maybe wrapping the next command in an
    EXPECT_WITHIN will cut down on the spurious test failures.
    
    Change-Id: I9bfda9d34e10ff0b783337e700ab8255dc6795ab
    BUG: 1209286
    Signed-off-by: Jeff Darcy <jdarcy>
    Reviewed-on: http://review.gluster.org/10143
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle>
    Reviewed-by: Vijay Bellur <vbellur>
Comment 3 Jeff Darcy 2015-05-06 12:57:48 UTC 
When I checked the git log for release-3.7, I saw that Pranith had submitted an equivalent fix for an equivalent bug.  Marking as a dup.

*** This bug has been marked as a duplicate of bug 1218576 ***