Description of problem: Existing geo-rep regressino test suite is rigorous time consuming. A simple geo-rep regression test suite is required to give results soon to developers for the patchset. Version-Release number of selected component (if applicable): mainline How reproducible: Always Steps to Reproduce: On patch submission Actual results: Takes long time around 45 minutes. Expected results: It should not take so much time. It should be simple and faster. Additional info:
REVIEW: http://review.gluster.org/11058 (tests: New simple geo-rep regression test suite) posted (#1) for review on master by Kotresh HR (khiremat)
REVIEW: http://review.gluster.org/11058 (tests: New simple geo-rep regression test suite) posted (#2) for review on master by Kotresh HR (khiremat)
COMMIT: http://review.gluster.org/11058 committed in master by Venky Shankar (vshankar) ------ commit dace4bbd0fdce567703a1a8d2d74a0a3f166f334 Author: Kotresh HR <khiremat> Date: Thu May 28 19:26:00 2015 +0530 tests: New simple geo-rep regression test suite This is a new simple regression test suite for geo-replication. This is written keeping in mind the run time for regression test. The existing regression test suite is rigorous one and could be run nightly. Hence the existing geo-rep tests are being removed as part of this. Also re-enable geo-rep regression with this patch. Thanks Aravinda for initial template and plan. Change-Id: If544ac295eaf67ac66e0b071903cc1096e71d437 BUG: 1227624 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/11058 Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Aravinda VK <avishwan>
REVIEW: http://review.gluster.org/11907 (tests: Fix return value in geo-rep tests) posted (#1) for review on master by Kotresh HR (khiremat)
REVIEW: http://review.gluster.org/11907 (tests: Fix return value in geo-rep tests) posted (#2) for review on master by Kotresh HR (khiremat)
REVIEW: http://review.gluster.org/11907 (tests: Fix return value in geo-rep tests) posted (#3) for review on master by Venky Shankar (vshankar)
REVIEW: http://review.gluster.org/11907 (tests: Fix return value in geo-rep tests) posted (#4) for review on master by Kotresh HR (khiremat)
COMMIT: http://review.gluster.org/11907 committed in master by Venky Shankar (vshankar) ------ commit e012bdc721945fb6d996e3f67881a705ef966026 Author: Kotresh HR <khiremat> Date: Thu Aug 13 13:11:32 2015 +0530 tests: Fix return value in geo-rep tests Remove the function 'data_tests' and TEST each fop in testcase itself to determine the exact test that fails. Change-Id: Iffc3e2ac3b0fc0c7c64259fcdff8f27b146dcb9b BUG: 1227624 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/11907 Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Jeff Darcy <jdarcy>
REVIEW: http://review.gluster.org/12072 (tests: Remove geo-rep tests from bad tests) posted (#1) for review on master by Kotresh HR (khiremat)
COMMIT: http://review.gluster.org/12072 committed in master by Jeff Darcy (jdarcy) ------ commit 2a568e0c0fd3f23a94cc87bf4c0bd07aaa65d5a5 Author: Kotresh HR <khiremat> Date: Tue Sep 1 11:24:09 2015 +0530 tests: Remove geo-rep tests from bad tests Remove 'tests/geo-rep/georep-basic-dr-rsync.t' and 'tests/geo-rep/georep-basic-dr-tarssh.t' from bad tests as it passes on linux machines. It is disabled only in NetBSD untill portability issues are fixed. (https://bugzilla.redhat.com/show_bug.cgi?id=1257847) Also add increase sleep timining to let the data sync. Change-Id: Ifc831353a345bcf5605fc4dfba693df891bb6d5b BUG: 1227624 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/12072 Reviewed-by: Raghavendra Talur <rtalur> Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System <jenkins.org>
"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.8.0, please open a new bug report. glusterfs-3.8.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] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user
*** Bug 1101111 has been marked as a duplicate of this bug. ***