summaryrefslogtreecommitdiffstats
path: root/.mailmap
diff options
context:
space:
mode:
authorSteven Rostedt (Red Hat) <rostedt@goodmis.org>2014-01-18 19:52:13 -0500
committerSteven Rostedt <rostedt@goodmis.org>2014-01-18 19:52:13 -0500
commit961d9caceea2d5350a15c17b7d3ffc24c08c9b09 (patch)
tree98f23aac6527f45c77cdda83e44a2d677e078017 /.mailmap
parentc75d22d9c675c4c77d87ff36de6e5023f14724ef (diff)
downloadtalos-obmc-linux-961d9caceea2d5350a15c17b7d3ffc24c08c9b09.tar.gz
talos-obmc-linux-961d9caceea2d5350a15c17b7d3ffc24c08c9b09.zip
ktest: Add BISECT_TRIES to bisect test
For those cases that it takes several tries to hit a bug, it would be useful for ktest.pl to try a test multiple times before it considers the test as a pass. To accomplish this, BISECT_TRIES ktest config option has been added. It is default to one, as most of the time a bisect only needs to try a test once. But the user can now up this to make ktest run a given test multiple times. The first failure that is detected will set a bisect bad. It only repeats on success. Note, as with all race bugs, there's no guarantee that if it succeeds, it is really a good bisect. But it helps in case the bug is somewhat reliable. You can set BISECT_TRIES to zero, and all tests will be considered good, unless you also set BISECT_MANUAL. Suggested-by: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud