| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
me some headache :-)
change the ping packet length, so the last packet will have exactly 100 bytes (at least on Windows)
svn path=/trunk/; revision=24998
|
|
|
|
|
|
|
|
| |
script not include /usr/sbin, or is ping installed somewhere other than
where it is on my Solaris "machine"? Try explicitly running it as
/usr/sbin/ping on Solaris.
svn path=/trunk/; revision=23670
|
|
|
|
|
|
| |
definition now. Comment out the corresponding test case
svn path=/trunk/; revision=23546
|
|
|
|
|
|
|
| |
in suite-clopts as well. Allow it to be set externally. This should fix
the "test" failure in the Solairs builder.
svn path=/trunk/; revision=23399
|
|
|
|
|
|
| |
stdout' test back in for tshark
svn path=/trunk/; revision=23110
|
|
|
|
|
|
| |
we can get that working
svn path=/trunk/; revision=23095
|
|
|
|
| |
svn path=/trunk/; revision=23020
|
|
|
|
| |
svn path=/trunk/; revision=22708
|
|
|
|
|
|
|
| |
Hopefully the windows buildbot will be OK with these tests disabled
temporarily.
svn path=/trunk/; revision=22660
|
|
|
|
| |
svn path=/trunk/; revision=21811
|
|
|
|
|
|
| |
now.
svn path=/trunk/; revision=21791
|
|
|
|
| |
svn path=/trunk/; revision=21311
|
|
|
|
| |
svn path=/trunk/; revision=20715
|
|
|
|
| |
svn path=/trunk/; revision=20589
|
|
|
|
|
|
|
|
|
| |
suite-capture.sh which were causing some
of tests to fail;
The stdout tests still tend to fail:
some issue with flushing the stdout pipe ??
svn path=/trunk/; revision=20200
|
|
|
|
|
|
| |
Add additional error output in case any other problems
svn path=/trunk/; revision=20197
|
|
|
|
|
|
|
| |
packets" test fails during the run-tests step of the
buildbot windows build ...
svn path=/trunk/; revision=20191
|
|
|
|
|
|
|
|
| |
this by generating some ICMP packets before each test. Add an "icmp"
capture filter to each test to better control the test conditions.
Fixup whitespace.
svn path=/trunk/; revision=20115
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Check for an "all" argument at startup. If it's present,
then proceed with testing.
- Add a platform check. Use it to handle cases where we can't run
as a normal user, e.g. trying to capture under Linux.
- Add a "Skipped" result.
svn path=/trunk/; revision=19461
|
|
|
|
|
|
|
|
|
| |
[tshark from a fifo]
I've even gone so far as to add a unit test for it
ULFL: as mkfifo isn't available on Win32 (not even cygwin), make this test configurable in config.sh
svn path=/trunk/; revision=19457
|
|
|
|
|
|
| |
don't use promiscuous mode as default (my Win32 WLAN card won't capture any packets with it - might probably be better for other users as well)
svn path=/trunk/; revision=19455
|
|
|
|
| |
svn path=/trunk/; revision=18495
|
|
|
|
|
|
|
|
|
|
|
| |
ethereal.com -> wireshark.org
mailing lists and addresses
ETHEREAL -> WIRESHARK
Man pages
Automake/Autoconf names
svn path=/trunk/; revision=18271
|
|
|
|
| |
svn path=/trunk/; revision=18268
|
|
|
|
| |
svn path=/trunk/; revision=18207
|
|
|
|
| |
svn path=/trunk/; revision=18197
|
|
|
|
| |
svn path=/trunk/; revision=16969
|
|
|
|
| |
svn path=/trunk/; revision=16964
|
|
|
|
| |
svn path=/trunk/; revision=16959
|
|
simple bash scripts) of the ethereal/tethereal command line parameters. See the file README.test for details.
svn path=/trunk/; revision=16788
|