Age | Commit message (Collapse) | Author | Files | Lines |
|
Revert "Test: Make capture_step_stdin more verbose." and "Test: more
suite-capture debugging." Tests on the Windows 8.1 builder have been
passing since recommended OS updates were installed on the 24th.
This reverts commits 7f710ef2b54d9eeb06c35ab1bd834f2df0696024 and
f52c3c468a508e1e770c32d479cdd761cb412af8.
Change-Id: I7cf10a38ba001426baea5fc76a34610c3a26ced2
Reviewed-on: https://code.wireshark.org/review/15590
Reviewed-by: Gerald Combs <gerald@wireshark.org>
|
|
In capture_step_stdin, print information about our test capture if we
fail.
Change-Id: I046f9d22b1bb2d52d96926f50379ab51e6279eb3
Reviewed-on: https://code.wireshark.org/review/15125
Reviewed-by: Gerald Combs <gerald@wireshark.org>
|
|
Change-Id: I94967aeabdf2786868c3f7fce9e95633332d4948
Reviewed-on: https://code.wireshark.org/review/15123
Reviewed-by: Gerald Combs <gerald@wireshark.org>
|
|
Add some verbosity to the stdin capture test. Hopefully this will shed
some light on the Windows 8 builder failures.
Change-Id: Ife2bbbaeed7a1e4a7ddd1c1f86322ba25d154f4c
Reviewed-on: https://code.wireshark.org/review/15122
Reviewed-by: Gerald Combs <gerald@wireshark.org>
|
|
c-basic-offset -> sh-basic-offset
Change-Id: I16b19b608fbdb7f0408f7c31871fae746c8c4f50
Reviewed-on: https://code.wireshark.org/review/13683
Reviewed-by: cedric izoard <cedric.izoard@ceva-dsp.com>
Reviewed-by: Anders Broman <a.broman58@gmail.com>
|
|
The default prefix policy on modern versions of Windows prefers IPv6.
This in combination with the fact that our ping target (www.wireshark.org)
currently has both A and AAAA records might result in ICMPv6 traffic
instead of ICMPv4. Update the capture test suite accordingly.
Change-Id: I5c88f24fb9458526ffd44c5003f09247b6999ce7
Reviewed-on: https://code.wireshark.org/review/12553
Reviewed-by: Gerald Combs <gerald@wireshark.org>
|
|
Change-Id: I648d02d41f92c7fd176ce194eee20a2d19643fe0
Reviewed-on: https://code.wireshark.org/review/5985
Reviewed-by: Anders Broman <a.broman58@gmail.com>
|
|
Ping four times a second for ~60 seconds. Save the subprocess PID so that
we can kill it when we're done with each test instead of waiting for it
to finish.
Change-Id: I64f889c700e8a6fa1bc1c3916ef045341ef59cc6
Reviewed-on: https://code.wireshark.org/review/4557
Reviewed-by: Gerald Combs <gerald@wireshark.org>
|
|
Change-Id: Icfd9edb8c6ef7620878bc9d60c8dcc569ad2abad
Reviewed-on: https://code.wireshark.org/review/4434
Reviewed-by: Gerald Combs <gerald@wireshark.org>
|
|
Qt requires Xrender and XKEYBOARD. Unfortunately the Ubuntu and Solaris
buildbots run the test script under Xtightvnc, which provides neither of
those. Only enable the tests on Windows and OS X for now.
Change-Id: I84bc28f810782b862b4dca8fc8df088a4919066d
Reviewed-on: https://code.wireshark.org/review/4430
Reviewed-by: Gerald Combs <gerald@wireshark.org>
|
|
Apparently what works for me doesn't work for the Buildbot users.
Change-Id: I7d3e4f2b89ae8ae3dadc8d92438c0e1923b97ace
Reviewed-on: https://code.wireshark.org/review/4416
Reviewed-by: Gerald Combs <gerald@wireshark.org>
|
|
Make sure the Qt UI quits if WIRESHARK_QUIT_AFTER_CAPTURE is set. Make
sure Bourne shell scripts (*.sh) have UNIX/POSIX line endings. Reduce
some time values so that the tests run faster.
Change-Id: I81df7c6f72d7d807d1856863cbea1bb6326ca711
Reviewed-on: https://code.wireshark.org/review/4407
Tested-by: Gerald Combs <gerald@wireshark.org>
Reviewed-by: Gerald Combs <gerald@wireshark.org>
|
|
Make sure the Qt UI is named "Wireshark" and its executable is named
"wireshark" or "wireshark.exe". Make sure the GTK+ UI is named
"Wireshark 1" or "Wireshark (GTK+)" depending on how much the target
audience is likely to care about UI toolkits. Make sure the GTK+
executable is named "wireshark-gtk" or "wireshark-gtk.exe".
It looks like moving to Qt 5.3 (g978faf3) broke the PortableApps
package. It's likely even more broken now.
Autotools out-of-tree builds also broke on Ubuntu 12.02 (automake
1.11.3) at some point. The first attempt to compile in ui/qt returns
"error: source_file.cpp: No such file or directory". The second attempt
works. Out-of-tree builds work fine on Ubuntu 14.04 (automake 1.14.1).
Tested:
- Nmake builds
- NSIS packaging
- CMake builds (Windows, OS X)
- Autotools build and distcheck
- RPM packaging
To do:
- Test Debian packaging
- Fix PortableApps
Change-Id: I66429870e05fd2d6fc901942477959ed6164fce2
Reviewed-on: https://code.wireshark.org/review/3919
Reviewed-by: Gerald Combs <gerald@wireshark.org>
|
|
(Using sed : sed -i '/^\# \$Id\$/,+1 d') (start with dash)
Change-Id: Ia4b5a6c2302f6a531f6a86c1ec3a2f8205c8c2dd
Reviewed-on: https://code.wireshark.org/review/881
Reviewed-by: Anders Broman <a.broman58@gmail.com>
|
|
DISPLAY environment variable isn't set.
From me: note that this won't be the right thing to do on OS X if we
switch to a toolkit that doesn't use X11, and that this may or may not
be the right thing to do with toolkits using Wayland or Mir directly.
svn path=/trunk/; revision=52182
|
|
filtering is important. Use -2 and -R together in one place where the counting
functionality is important.
svn path=/trunk/; revision=51558
|
|
failures.
svn path=/trunk/; revision=48391
|
|
svn path=/trunk/; revision=47975
|
|
(Maybe this will make the XP buildbot happy so test.sh succeeds again?)
svn path=/trunk/; revision=47969
|
|
(COPYING will be updated in next commit)
svn path=/trunk/; revision=43536
|
|
helpfully ignores G_LOG_LEVEL_INFO and G_LOG_LEVEL_DEBUG messages by
default. If the console_log_level preference includes either of those
two levels set the G_MESSAGES_DEBUG environment variable so that those
messages are printed.
Add checks for various console log messages to the stdin capture suite.
Fixes bug 7265.
svn path=/trunk/; revision=42930
|
|
svn path=/trunk/; revision=41857
|
|
svn path=/trunk/; revision=38784
|
|
svn path=/trunk/; revision=37982
|
|
svn path=/trunk/; revision=37844
|
|
svn path=/trunk/; revision=37838
|
|
svn path=/trunk/; revision=37837
|
|
on the XP buildbot. Use "capture_test_output_print" instead of "cat".
svn path=/trunk/; revision=37825
|
|
svn path=/trunk/; revision=37774
|
|
svn path=/trunk/; revision=37485
|
|
svn path=/trunk/; revision=37416
|
|
svn path=/trunk/; revision=33104
|
|
svn path=/trunk/; revision=28332
|
|
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
|