aboutsummaryrefslogtreecommitdiffstats
path: root/tools/test-common.sh
AgeCommit message (Collapse)AuthorFilesLines
2017-04-05A bunch of "{Mac} OS X" -> "macOS" changes.Guy Harris1-5/+5
Avoid anachronisms, however; there was no "macOS 10.0" or even "OS X 10.0", for example. It was "Mac OS X" until 10.8 (although 10.7 was sometimes called "OS X" and sometimes called "Mac OS X"), and it was "OS X" from 10.8 to 10.11. Change-Id: Ie4a848997dcc6c45c2245c1fb84ec526032375c3 Reviewed-on: https://code.wireshark.org/review/20933 Reviewed-by: Guy Harris <guy@alum.mit.edu>
2016-12-10Boost the max CPU time.Guy Harris1-1/+1
See if that lets the big file from bug 13226 pass the test under Valgrind. Change-Id: I76eb0c18809289e3b14ff8071402c31f70d93d42 Ping-Bug: 13226 Reviewed-on: https://code.wireshark.org/review/19189 Reviewed-by: Guy Harris <guy@alum.mit.edu>
2016-11-16Double the fuzz testing memory limit.Gerald Combs1-1/+1
Increase MAX_VMEM to 1000000 in order to accomodate a large capture file in the menagerie and allow some breathing room for future large captures. Change-Id: I61d1a56d30d49af5c25785f8d43f104b6a300da5 Ping-Bug: 13049 Reviewed-on: https://code.wireshark.org/review/18838 Reviewed-by: Gerald Combs <gerald@wireshark.org>
2016-09-24Check for ASAN when fuzzing.Gerald Combs1-0/+9
Try to determine if we passed -fsanitize=address to gcc or clang and adjust the ASAN variable fuzz-test.sh, randpkt-test.sh and test-captures.sh accordingly. Change-Id: I88a34828fb5875e1a74a3b180ffb3da37daac0bd Reviewed-on: https://code.wireshark.org/review/17848 Reviewed-by: Pascal Quantin <pascal.quantin@gmail.com>
2016-03-10Add the pass number to the fuzz failure report.Gerald Combs1-0/+1
When adjusting MAX_PASSES it'd be nice to know how many passes it normally takes to fail. Change-Id: I335c26a1e6847371706da880b83773d142797da9 Reviewed-on: https://code.wireshark.org/review/14389 Reviewed-by: Alexis La Goutte <alexis.lagoutte@gmail.com> Reviewed-by: Michael Mann <mmann78@netscape.net>
2016-03-03Make sure our shell, Perl, & Python tools are executable.Gerald Combs1-0/+0
Change-Id: Ie58978473c4af7a0eaccf3e664c2f44bed2ef202 Reviewed-on: https://code.wireshark.org/review/14331 Reviewed-by: Gerald Combs <gerald@wireshark.org>
2016-01-31plugins: do not import symbols globallyPeter Wu1-1/+1
Clang's ASAN reported an ODR violation when plugins were loaded. Sure enough, symbols did actually get loaded twice: ==5898==ERROR: AddressSanitizer: odr-violation (0x7fffd95a35e0): [1] size=7 'version' plugins/mate/plugin.c:19:31 [2] size=6 'version' plugins/opcua/plugin.c:19:31 After this change, plugins cannot insert new symbols in the global namespace. Change-Id: Ib11f7263e9c586f8e7c1f8f5fb239b20d46ddd2f Reviewed-on: https://code.wireshark.org/review/13260 Reviewed-by: Alexis La Goutte <alexis.lagoutte@gmail.com> Petri-Dish: Alexis La Goutte <alexis.lagoutte@gmail.com> Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org> Reviewed-by: Michael Mann <mmann78@netscape.net>
2015-06-26tools: permit setting BIN_DIR in the environmentEvan Huus1-7/+9
For out-of-tree builds you have to pass the location of your build to our tools like the fuzz script, valgrind script etc. Modify them so that the value can be set in the environment rather than requiring a shell script flag. Set the environment variable in the vagrant provision step, so that the scripts Just Work (TM) in the VM. Change-Id: If8ce6b278176085ba6dd994137b82fc989b80124 Reviewed-on: https://code.wireshark.org/review/9168 Reviewed-by: Evan Huus <eapache@gmail.com>
2015-05-02Try to keep capinfos+ASan from failing.Gerald Combs1-0/+3
Set ASAN_OPTIONS=detect_leaks=0, otherwise all captures show up as invalid in capinfos. Change-Id: I4c2c1e52e9cd8b253cd4c01d0f8770294b66102e Reviewed-on: https://code.wireshark.org/review/7757 Petri-Dish: Gerald Combs <gerald@wireshark.org> Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org> Reviewed-by: Alexis La Goutte <alexis.lagoutte@gmail.com> Reviewed-by: Evan Huus <eapache@gmail.com>
2015-02-06More emem removal.Jeff Morriss1-7/+0
Remove emem's 8-byte-memory-alignment configure check as well as references to all the environment variables emem used. Change-Id: I897aec9e9c68e064454561e7a9f066b18892ec66 Reviewed-on: https://code.wireshark.org/review/6950 Petri-Dish: Alexis La Goutte <alexis.lagoutte@gmail.com> Reviewed-by: Anders Broman <a.broman58@gmail.com>
2015-01-18Nobody uses se_ allocations, so remove the code for them.Guy Harris1-4/+2
Don't check for se_ routines in checkAPIs; the failure to compile or link will suffice to catch attempts to use them. Update comments in another test script to reflect the disappearance of the session allocator. Change-Id: If50d953c7130f48b696bc2dd9d327bea2af49bd4 Reviewed-on: https://code.wireshark.org/review/6638 Reviewed-by: Guy Harris <guy@alum.mit.edu>
2014-05-11It is possible to check out a source tree that is not co-located withJoerg Mayer1-1/+1
the .git repository. First attempts to support that setup. Change-Id: Ie1560c372e23e58fb0e310f681388b5e1a65ba5b Reviewed-on: https://code.wireshark.org/review/1596 Reviewed-by: Jörg Mayer <jmayer@loplof.de>
2014-03-30Fix fuzz-test.sh '-b' option so it works again; Do some other ↵Bill Meier1-1/+17
tools/*test*.sh changes - Add -b option to randpkt-test.sh and test-captures.sh; - Create/ue a common function to do '-x' tests on files/dirs; - Rename exit_error function to ws_exit_error Change-Id: I032c9d784bec1fb6b0717aaad08a061e4d935476 Reviewed-on: https://code.wireshark.org/review/872 Reviewed-by: Bill Meier <wmeier@newsguy.com> Tested-by: Bill Meier <wmeier@newsguy.com>
2014-02-25Get rid of a few more Subversion remnants.Jeff Morriss1-4/+1
Change-Id: I35ff651017e355f92b4f9e6388e90d446f245d0a Reviewed-on: https://code.wireshark.org/review/361 Reviewed-by: Evan Huus <eapache@gmail.com> Reviewed-by: Alexis La Goutte <alexis.lagoutte@gmail.com>
2014-02-14Remove $Id$ and other Subversion leftovers from the tools.Jeff Morriss1-2/+0
There are a few things in here which could still use attention. Don't regenerate anything now. Change-Id: I283c224d3523212144707fca3d6265916cb11792 Reviewed-on: https://code.wireshark.org/review/205 Reviewed-by: Jeff Morriss <jeff.morriss.ws@gmail.com>
2013-12-13Change the exit status of a fuzz failure to 255 so that if you use it with xargsEvan Huus1-1/+1
the failures don't get suppressed. svn path=/trunk/; revision=54071
2013-07-12Add (GPLv2+) license headers to these scripts, assigning the copyright toJeff Morriss1-0/+20
the original author of the scripts (Gerald). svn path=/trunk/; revision=50542
2013-07-08Include the output (fuzz'd) file name in the output when fuzz (or randpkt)Jeff Morriss1-0/+2
testing fails. Useful for when you want to use up a few spare CPU cores running multiple simultaneous fuzz tests... svn path=/trunk/; revision=50449
2013-06-05Add a new environment variable to cause abort()s if we add too many itemsJeff Morriss1-0/+2
to the tree (to separate this case from the generic DISSECTOR_BUG case). Enable this environment variable when fuzz testing. Enable the 3rd (without tree but with a read filter) check (added in r49643) when testing capture files but not when fuzz testing--not sure if we want to add even more to the fuzzbot's work load now (OTOH I've been running it for a while and it hasn't buried me in bugs). svn path=/trunk/; revision=49784
2013-05-30test-common.sh doesn't need to be executable (it is sourced, not executed); ↵Jeff Morriss1-0/+0
remove the svn:executable property. svn path=/trunk/; revision=49626
2013-03-09Remove the wmem slab. It was an optimization mimicking the emem slabEvan Huus1-1/+0
(removed in r48218) which did nothing particularly useful. Also lets us remove another debugging environment variable. svn path=/trunk/; revision=48219
2013-02-14Add an option for bypassing the wmem slab similar to the one forEvan Huus1-0/+1
bypassing the emem slab, to aid in debugging with valgrind. svn path=/trunk/; revision=47656
2013-01-26Forward-port r47305 from trunk-1.8:Gerald Combs1-7/+1
------------------------------------------------------------------------ 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. ------------------------------------------------------------------------ svn path=/trunk/; revision=47307
2013-01-14Try to show what condition triggered a failure.Gerald Combs1-0/+4
svn path=/trunk/; revision=47079
2012-12-28Update wmem documentation for the new allocator.Evan Huus1-0/+2
Use the strict allocator when fuzzing (at least until the fuzz-bot starts running everything under valgrind). svn path=/trunk/; revision=46829
2012-12-07Move a lot of common fuzz-test and randpkt-test code to its own fileGerald Combs1-0/+144
(test-common.sh). Add build information to the error output as suggested in http://www.wireshark.org/lists/wireshark-dev/201212/msg00037.html svn path=/trunk/; revision=46446
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-25 09:10:24 +0000