Wireshark-commits: [Wireshark-commits] rev 47307: /trunk/tools/ /trunk/tools/: fuzz-test.sh randpkt
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: gerald@xxxxxxxxxxxxx
Date: Sat, 26 Jan 2013 20:36:58 GMT
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=47307

User: gerald
Date: 2013/01/26 12:36 PM

Log:
 Forward-port r47305 from trunk-1.8:
 
   ------------------------------------------------------------------------
   r47305 | gerald | 2013-01-26 12:12:52 -0800 (Sat, 26 Jan 2013) | 6 lines
   Changed paths:
      M /trunk-1.8/tools/fuzz-test.sh
 
   Instead of setting resource limits on the fuzz-test.sh process itself,
   set limits on the TShark subprocess. This should hopefully take care
   of the strange fuzz failures we've seen lately.
 
   Reduce the maximum CPU time to 5 minutes while we're at it.
   ------------------------------------------------------------------------

Directory: /trunk/tools/
  Changes    Path               Action
  +11 -2     fuzz-test.sh       Modified
  +10 -2     randpkt-test.sh    Modified
  +1 -7      test-common.sh     Modified