+++ This bug was initially created as a clone of Bug #1289845 +++ Description of problem: I am seeing regression failure [1]. The test which is failing is [2]. On my local machine the test always succeeds and even in the console output [1], the test has succeeded when run in debug mode for the second time. My changes are [3] which seems to be unrelated to [2]. [1] https://build.gluster.org/job/rackspace-regression-2GB-triggered/16575/consoleFull [2] ./tests/bugs/tier/bug-1279376-rename-demoted-file.t [3] review.gluster.org/12594 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Vijay Bellur on 2015-12-09 09:15:58 EST --- REVIEW: http://review.gluster.org/12926 (tests/tier: spurious failure in rename test) posted (#1) for review on master by N Balachandran (nbalacha) --- Additional comment from Vijay Bellur on 2015-12-09 21:02:23 EST --- REVIEW: http://review.gluster.org/12926 (tests/tier: spurious failure in rename test) posted (#2) for review on master by Dan Lambright (dlambrig) --- Additional comment from Vijay Bellur on 2015-12-09 23:53:35 EST --- REVIEW: http://review.gluster.org/12926 (tests/tier: spurious failure in rename test) posted (#3) for review on master by N Balachandran (nbalacha) --- Additional comment from Vijay Bellur on 2015-12-10 09:43:22 EST --- COMMIT: http://review.gluster.org/12926 committed in master by Dan Lambright (dlambrig) ------ commit aeaee78c4ec88f3c00efe22edc796102e03291da Author: N Balachandran <nbalacha> 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. Change-Id: Ieccc736f387fcf6afaa72fa9918adb6dd34f2c8a BUG: 1289845 Signed-off-by: N Balachandran <nbalacha> Reviewed-on: http://review.gluster.org/12926 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Dan Lambright <dlambrig> Tested-by: Dan Lambright <dlambrig>
REVIEW: http://review.gluster.org/12958 (tests/tier: spurious failure in rename test) posted (#1) for review on release-3.7 by N Balachandran (nbalacha)
REVIEW: http://review.gluster.org/12958 (tests/tier: spurious failure in rename test) posted (#2) for review on release-3.7 by N Balachandran (nbalacha)
COMMIT: http://review.gluster.org/12958 committed in release-3.7 by Dan Lambright (dlambrig) ------ commit 7ef768acf706b2f08bbb2b48ef75d9abcc66b5be Author: N Balachandran <nbalacha> Date: Sun Dec 13 11:43:18 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. Change-Id: I7fa9f511c96aa2bc00e4d41d479f67018d369329 BUG: 1291046 Signed-off-by: N Balachandran <nbalacha> Reviewed-on: http://review.gluster.org/12958 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Dan Lambright <dlambrig> Tested-by: Dan Lambright <dlambrig>
"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/ 2. run-tests.sh 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.7.7, please open a new bug report. glusterfs-3.7.7 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user