Description of problem: 20:09:33 [20:09:37] Running tests in file ./tests/bugs/index/bug-1559004-EMLINK-handling.t 20:09:33 Timeout set is 1200, default 300 20:29:33 ./tests/bugs/index/bug-1559004-EMLINK-handling.t timed out after 1200 seconds 20:29:33 ./tests/bugs/index/bug-1559004-EMLINK-handling.t: bad status 124 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/20699 (tests: Increase timeout to 30 minutes to handle lcov slowness) posted (#1) for review on master by Pranith Kumar Karampuri
COMMIT: https://review.gluster.org/20699 committed in master by "Amar Tumballi" <amarts> with a commit message- tests: Increase timeout to 30 minutes to handle lcov slowness This script on a normal setup takes 15 minutes. With lcov it needs to be increased. Considering we did 1.5X of the default $run_timeout in run-tests.sh, I am doing the same for this script. fixes bz#1614718 Change-Id: Ia571b33ff13deb8cbd8e48561769e876aa0b1aff Signed-off-by: Pranith Kumar K <pkarampu>
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-5.0, please open a new bug report. glusterfs-5.0 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://lists.gluster.org/pipermail/announce/2018-October/000115.html [2] https://www.gluster.org/pipermail/gluster-users/