diff options
| author | Evan Huus <eapache@gmail.com> | 2014-05-10 23:54:37 -0400 |
|---|---|---|
| committer | Evan Huus <eapache@gmail.com> | 2014-05-11 21:13:06 +0000 |
| commit | ff466a9b920507c34068b2cc6f42b32049948183 (patch) | |
| tree | c5848faffd8485bb1924a2f9bca6f840e0ba3267 /tools | |
| parent | 03f75ddfeebe41e07adadfba20e0ebe30da95490 (diff) | |
Increase time permitted when fuzzing with valgrind.
The capture on bug 10098 times out but I don't see any culprits for bad loops or
anything - I think the capture is just too big. I'd prefer somebody else take a
look at it to verify I'm not missing anything before submitting this.
Bug:10098
Change-Id: I2cc43fd6ac9afaa345e7d31184483a9732fd6bf0
Reviewed-on: https://code.wireshark.org/review/1583
Reviewed-by: Gerald Combs <gerald@wireshark.org>
Reviewed-by: Evan Huus <eapache@gmail.com>
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 4d18a94d7f..d3922c2e3e 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 2x time + # Valgrind requires more resources, so permit 1.5x memory and 2.5x time # (1.5x time is too small for a few large captures in the menagerie) - MAX_CPU_TIME=`expr 2 \* $MAX_CPU_TIME` + MAX_CPU_TIME=`expr 5 \* $MAX_CPU_TIME / 2` MAX_VMEM=`expr 3 \* $MAX_VMEM / 2` else # Not using valgrind, use regular tshark. |