diff options
| author | Evan Huus <eapache@gmail.com> | 2014-09-03 22:48:46 -0400 |
|---|---|---|
| committer | Michael Mann <mmann78@netscape.net> | 2014-09-04 12:54:16 +0000 |
| commit | 27d1b6addf2d63a7526c231495216484f18a6025 (patch) | |
| tree | 1b303c9d84336bb7460d55b8c8e9f8a6a6f840a2 /tools | |
| parent | 2497482e34a108275f75cd8106e1841b35aab98e (diff) | |
Bump the time limit for valgrind fuzzing
Some captures are still hitting the limit as a false positive.
Bug: 10122
Change-Id: I12dd26ba0f96f44799f5ae642b1f9b0487f86a8a
Reviewed-on: https://code.wireshark.org/review/3982
Reviewed-by: Michael Mann <mmann78@netscape.net>
Diffstat (limited to 'tools')
| -rwxr-xr-x | tools/fuzz-test.sh | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/tools/fuzz-test.sh b/tools/fuzz-test.sh index 4c625cca33..b2d2c9e9a1 100755 --- a/tools/fuzz-test.sh +++ b/tools/fuzz-test.sh @@ -75,9 +75,9 @@ if [ $VALGRIND -eq 1 ]; then RUNNER="`dirname $0`/valgrind-wireshark.sh" COMMON_ARGS="-b $BIN_DIR $COMMON_ARGS" declare -a RUNNER_ARGS=("" "-T") - # Valgrind requires more resources, so permit 1.5x memory and 2.5x time + # Valgrind requires more resources, so permit 1.5x memory and 3x time # (1.5x time is too small for a few large captures in the menagerie) - MAX_CPU_TIME=`expr 5 \* $MAX_CPU_TIME / 2` + MAX_CPU_TIME=`expr 3 \* $MAX_CPU_TIME` MAX_VMEM=`expr 3 \* $MAX_VMEM / 2` else # Not using valgrind, use regular tshark. |