Red Hat Bugzilla – Bug 1289845
spurious failure of bug-1279376-rename-demoted-file.t
Last modified: 2016-06-16 09:49:41 EDT
Description of problem:
I am seeing regression failure . The test which is failing is . On my local machine the test always succeeds and even in the console output , the test has succeeded when run in debug mode for the second time. My changes are  which seems to be unrelated to .
Version-Release number of selected component (if applicable):
Steps to Reproduce:
REVIEW: http://review.gluster.org/12926 (tests/tier: spurious failure in rename test) posted (#1) for review on master by N Balachandran (firstname.lastname@example.org)
REVIEW: http://review.gluster.org/12926 (tests/tier: spurious failure in rename test) posted (#2) for review on master by Dan Lambright (email@example.com)
REVIEW: http://review.gluster.org/12926 (tests/tier: spurious failure in rename test) posted (#3) for review on master by N Balachandran (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/12926 committed in master by Dan Lambright (email@example.com)
Author: N Balachandran <firstname.lastname@example.org>
Date: Wed Dec 9 19:36:42 2015 +0530
tests/tier: spurious failure in rename test
bug-1279376-rename-demoted-file.t fails sometimes
The fix is based on the assumption that the test
failed because the demotion happened too quickly.
Signed-off-by: N Balachandran <email@example.com>
Tested-by: NetBSD Build System <firstname.lastname@example.org>
Tested-by: Gluster Build System <email@example.com>
Reviewed-by: Dan Lambright <firstname.lastname@example.org>
Tested-by: Dan Lambright <email@example.com>
"tests" component is for tests framework only.
File a bug under test component if you find a bug in
1. any of the *.rc files under tests/
For everything else, the bug should be filed on
1. component which is being tested by .t file if the .t file requires fix.
2. component which is causing a valid .t file to fail in regression.
I have used my best judgement here to move the bug to right component.
In case of ambiguity, I have placed the blame on the .t file component.
Please consider test bugs under the same backlog list that tracks other bugs in your component.
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.
glusterfs-3.8.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.