[Bugs] [Bug 1200174] Make it easier to identify regression test failures
bugzilla at redhat.com
bugzilla at redhat.com
Tue Mar 10 14:48:16 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1200174
--- Comment #3 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/9842 committed in master by Vijay Bellur
(vbellur at redhat.com)
------
commit 9d6fab69105d866786d26d3d09158163ab5189c5
Author: Niels de Vos <ndevos at redhat.com>
Date: Mon Mar 9 18:39:07 2015 -0400
tests: add a helper script to identify line-numbers and commands of
test-cases
Use the tests/utils/testn.sh after a regression test failed to identify
what command/line number belongs to the test-number.
Jenkins will have something like this in the console output:
Test Summary Report
-------------------
./tests/bugs/quota/bug-1087198.t
Failed test: 18
Call the script like:
$ ./tests/utils/testn.sh ./tests/bugs/quota/bug-1087198.t 18
56 TEST grep -e "\"Usage crossed....
BUG: 1200174
Change-Id: I661c1178d7f5bc50fd40679232c65734c2bc5477
Original-author: Pranith Kumar K <pkarampu at redhat.com>
Signed-off-by: Niels de Vos <ndevos at redhat.com>
Reviewed-on: http://review.gluster.org/9842
Reviewed-by: Dan Lambright <dlambrig at redhat.com>
Tested-by: Gluster Build System <jenkins at build.gluster.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=yeI9VgnGS8&a=cc_unsubscribe
More information about the Bugs
mailing list