Red Hat Bugzilla – Bug 1278539
ec-readdir.t is failing consistently
Last modified: 2017-03-08 05:55:48 EST
+++ This bug was initially created as a clone of Bug #1276989 +++
Description of problem:
if we run ec-readdir.t in a loop it fails. This only happens on mainline not on 3.7. So some regression is the reason. For now moving to bad-tests
Version-Release number of selected component (if applicable):
Steps to Reproduce:
--- Additional comment from Vijay Bellur on 2015-11-01 21:35:01 EST ---
REVIEW: http://review.gluster.org/12481 (tests: Move ec-readdir.t to bad tests) posted (#1) for review on master by Pranith Kumar Karampuri (firstname.lastname@example.org)
--- Additional comment from Vijay Bellur on 2015-11-02 06:43:16 EST ---
COMMIT: http://review.gluster.org/12481 committed in master by Raghavendra Talur (email@example.com)
Author: Pranith Kumar K <firstname.lastname@example.org>
Date: Mon Nov 2 07:56:51 2015 +0530
tests: Move ec-readdir.t to bad tests
Signed-off-by: Pranith Kumar K <email@example.com>
Tested-by: Raghavendra Talur <firstname.lastname@example.org>
Reviewed-by: Raghavendra Talur <email@example.com>
I see the test failing repeatedly on 3.7, so copy the bug/fix.
"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 was accidentally moved from POST to MODIFIED via an error in automation, please see firstname.lastname@example.org with any questions
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.