+++ This bug was initially created as a clone of Bug #1220016 +++ Description of problem: Some of the bitrot testcases fail spuriously --- Additional comment from Anand Avati on 2015-05-09 02:57:53 EDT --- REVIEW: http://review.gluster.org/10702 (tests: fix bitrot spurious failures) posted (#1) for review on master by Atin Mukherjee (amukherj) --- Additional comment from Anand Avati on 2015-05-09 03:22:55 EDT --- COMMIT: http://review.gluster.org/10702 committed in master by Vijay Bellur (vbellur) ------ commit 988e00f83cb74c908471caf6af9cbce05b7f95c9 Author: Atin Mukherjee <amukherj> Date: Sat May 9 12:23:10 2015 +0530 tests: fix bitrot spurious failures Change-Id: I55bd62480b7ee38cf7b29aeba67b19b0c5bbe2fb BUG: 1220016 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: http://review.gluster.org/10702 Reviewed-by: Pranith Kumar Karampuri <pkarampu> Tested-by: Vijay Bellur <vbellur>
REVIEW: http://review.gluster.org/10705 (tests: fix bitrot spurious failures) posted (#2) for review on release-3.7 by Atin Mukherjee (amukherj)
Atin, This bug seems to be resolved by latest patch merged. If so, can we close it?
"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 GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.