iCurrently we install inetutils-ping in some docker images and
iputils-ping in others; let's make it more uniform to avoid running
different implementations in different images.
The iputils-ping provides further linux-specific features, such as the
"-I interface" param, which is used by some images, so let's pick that
one everywhere.
Change-Id: If11a1c2ae1115b585b6a44a45e9569c16856d8c4
This Dockerfile allows building a given repo and branch of
titan.core.git which can then be used by any ttcn-*-test/ environment by
simply changing its Dockerfile "FROM" line from
$REGISTRY/$USER/debian-bullseye-titan to
$REGISTRY/$USER/debian-bullseye-titan-mater.
This is useful to debug or develop titan.core or test whether a given
testsuite works fine with a newer version of titan.core.
Change-Id: I19ee98a319ccad167d06c4f183fe80ecac909483
The following warning message appears when running apt-key:
apt-key is deprecated. Manage keyring files in trusted.gpg.d instead
The apt-key man page mentions that the "use of apt-key is deprecated,
except for the use of apt-key del in maintainer scripts to remove
existing keys from the main keyring". What's more, "apt-key will last
be available in Debian 11 and Ubuntu 22.04".
Additionally, while the deprecation message says to "manage keyring
files in trusted.gpg.d instead", the Debian wiki states otherwise.
It's recommended to store the keys in /usr/share/keyrings instead,
and then use the 'signed-by' option to reference them.
ee284d5917
Change-Id: I1cae4f49e72f5e4f9d703cdb8f6d117e18e3567c
Don't use the "operstate" sysfs attribute to determine if an interface
is "up", use the actual UP-flag (0x01) in the "flags" sysfs attribute.
The "operstate" attribute may at least occasionally be "unknown" and
remain in that state (causing jenkins jobs to wait indefinitely), while
the flags (which we don't look at before this patch) indicates it is "up".
This is a fixup to the below commit:
commit d2014603a7
Author: Harald Welte <laforge@osmocom.org>
Date: Wed Feb 3 22:05:43 2021 +0100
debian-stretch-titan: Wait for interface to be _up_ not just its existance
Change-Id: Ib5c3bbe470ce874217437c2518df5ae07f0d8301
Closes: OS#5803
Other remotes are mirrors of gerrit one, which means there's some delay
between pushing some ref to the gerrit remote and having them available
in the mirrors.
Hence, it becomes annoying while developing and new stuff to test is
pushed. Let's simply use gerrit since it's the master remote.
Change-Id: Ic87c196f8b91a3a3e6ddde2cca36482ce7070df7
When downloading the deps/Makefile, use gitea instead of the obsolete
and now defunct cgit deep-link
Change-Id: Ifbcb992e70a1faefc3829df28f8bf4dfaf2143e1
Related: OS#5670
These files are in .gitignore and get generated at the end of running
'make'. Remove them to have less cluttered 'git grep' output.
Change-Id: Ie5bf05220359ac0941f62cc86ed843363548784a
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