Add ping, so ttcn3-tcpdump-start.sh from osmo-ttcn3-hacks.git works as
expected. It is supposed to wait until tcpdump is properly capturing
packets, by generating dummy packets with ping and waiting until the
pcap file gains size. However since ping is currently not installed, it
will just wait 10 seconds before executing tests.
Fix for:
Waiting for packet dumper to start... 0
Waiting for packet dumper to start... 1
Waiting for packet dumper to start... 2
Waiting for packet dumper to start... 3
Waiting for packet dumper to start... 4
Waiting for packet dumper to start... 5
Waiting for packet dumper to start... 6
Waiting for packet dumper to start... 7
Waiting for packet dumper to start... 8
Waiting for packet dumper to start... 9
Related: OS#4969
Change-Id: I46cf22e7eab7dcd4b3835a8c7aa48654aef6c65a
So far we were executing all our TTCN-3 tests from a container
image with Debian stretch (9) plus a custom more recent eclipse-titan
package from the osmocom feed.
Let's update the container base OS from stretch (9) to bullseye (11)
while using the same packaged eclipse-titan version (8.0.0) for running
the tests. So this should be a low-risk change, as titan runtime
remains identical.
I've executed all test suites locally and couldn't see any regressions.
Related: OS#4969
Change-Id: Ib3bdfa3bec8f8ef42c55ca61cdee8fbca923874f
Oliver Smith
Vadim Yanitskiy
Harald Welte