aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2022-02-02WIP: Add ttcn3-ggsn-ogs testsuitepespin/gtp1Pau Espin Pedrol10-0/+1133
Change-Id: Ib90bb9ecc0cc2172defa8f4806601dcd80a2985b
2022-02-02treewide: use almalinux instead of centos8Oliver Smith7-9/+9
CentOS Linux 8 is EOL, attempting to install packages in it results in an error. CentOS Linux is a rebuild of RHEL (stable versions). The CentOS projects recommends to use CentOS Stream instead, which is a build of the "public development branch for RHEL". After the early EOL was announced on 2020-12-08, alternative projects AlmaLinux and Rocky Linux have been established as binary compatible forks of RHEL 8 (stable versions). Both Alma and Rocky seem to be solid projects, see related Wikipedia articles and their sources. Pick Alma and adjust the whole tree to use the almalinux:8 docker image instead of centos:centos8. Fix for: Error: Failed to download metadata for repo 'appstream': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried Related: SYS#5818 Related: https://www.centos.org/cl-vs-cs/ Related: https://www.centos.org/centos-linux-eol/ Related: https://bugs.centos.org/view.php?id=18394 Related: https://en.wikipedia.org/wiki/AlmaLinux Related: https://en.wikipedia.org/wiki/Rocky_Linux Change-Id: I30e1a773b901b1d2187214445116c7f2aecc4e36
2022-01-31ttcn3-bsc-test-sccplite: set OSMO_SUT_{HOST,PORT}Vadim Yanitskiy1-0/+2
This enables the test suite to obtain talloc reports between the test case executions, which get stored together with the PCAP files. Change-Id: I4e5474e8fc51d2ba8a0baca68e11df1346d7d4ab
2022-01-31ttcn3-bsc-test-vamos: set OSMO_SUT_{HOST,PORT}Vadim Yanitskiy1-0/+2
This enables the test suite to obtain talloc reports between the test case executions, which get stored together with the PCAP files. Change-Id: Ia9525778fcecc60177be651624e2b2cf9bc75422
2022-01-29ttcn3-pgw-test: fix jenkins.sh: do not use bash specific syntaxVadim Yanitskiy1-1/+1
On some systems /bin/sh is a symbolic link to bash, so everything works fine. On systems where /bin/sh is a real sh, copy fails: cp: cannot access 'open5gs-{smf,upf,nrf}.yaml': No such file or directory Change-Id: I64e9ddefdb6deb21b3bce3bc1af875a92919e6c9 Related: SYS#5602
2022-01-26ttcn3-bsc-test/jenkins.sh: fix '--ulimit core=-1' set twiceVadim Yanitskiy1-1/+0
Change-Id: I3223f8f4cc09797de44971215a94fc62ad8d263b
2022-01-26osmo-uecups-master: add more complete osmo-uecups-daemon.cfgVadim Yanitskiy1-0/+15
Change-Id: I16e3f60485039efd3b965009608982c27511b680 Related: SYS#5602
2022-01-26osmo-uecups-master/Dockerfile: fix copy-pasted ARG OSMO_BSC_BRANCHVadim Yanitskiy1-4/+4
Change-Id: Id713ddd24b7ba674d1a2035a0b3b62b1b9d26d9e Related: SYS#5602
2022-01-26ttcn3-pgw-test: set '--ulimit core=-1' for osmo-uecups-daemonVadim Yanitskiy1-0/+1
Change-Id: I16f4eefa2bb48486c139ca63f2a48346f0532a8c Related: SYS#5602
2022-01-26ttcn3-pgw-test: set '--ulimit core=-1' for open5gs-{nrf,upf,smf}Vadim Yanitskiy1-0/+3
Change-Id: I2da2d502f339fc4cbea8fa72414eeaeb6078dfd9 Related: SYS#5602
2022-01-26ttcn3-pgw-test: add Dockerfile, jenkins.sh and configs for open5gsHarald Welte9-0/+1318
Change-Id: I69e2f5be8204cc4fd0cc0f4eb019ef1104121b60 Tweaked-By: Vadim Yanitskiy <vyanitskiy@sysmocom.de> Related: SYS#5602
2022-01-17gerrit: Upgrade to 3.4.3Harald Welte1-1/+1
Change-Id: I91ebd53ea7279f76950cde959ffa2472d8f78593 Closes: OS#5404
2022-01-17gerrit: upgrade to 3.3.9 based containerHarald Welte1-1/+1
... primarily as intermediate step towards 3.4 Related: OS#5404 Change-Id: Iabb36f0754773dc2e8a5be7d44979b85034e2d01
2022-01-05Use osmo-hnbgw from osmo-hnbgw.git instead of osmo-iuh.gitPau Espin Pedrol3-10/+12
Starting with release 1.2.0 of both repos, osmo-hnbgw binary is in osmo-hnbgw.git, not osmo-iuh.git anymore. Change-Id: I4ac6ede6a5b25ada211674bf3c46d79d7720a4bc
2021-12-24osmo-hnodeb-master: no longer depend on libgtpPau Espin Pedrol1-1/+0
Newer osmo-hnodeb no longer depend on libgtp, get rid od the dependency. Depends: osmo-hnodeb.git Change-Id I53ad4915aaed3bc7574036e963be10514e370fe2 Related: SYS#5516 Change-Id: I4e223823d08c7e9e17d87f54d9554429d31c8091
2021-12-24osmo-remsim-test-latest: install client-shellOliver Smith1-0/+2
Fix for failing ttcn3-remsim-test-latest, in osmo-remsim-client.log: /bin/sh: 1: osmo-remsim-client-shell: not found Change-Id: Ia3041ea6f19ebe53e05117806acf88d3f86d4479
2021-12-23jenkins-common.sh: add d9 to upstream_distro funcOliver Smith1-0/+1
After the default UPSTREAM_DISTRO was changed from debian:stretch to debian:bullseye, the "debian9-repo-install-test" container has gotten built with bullseye instead of stretch. This is the reason for failures of the jenkins job Osmocom-repo-install-debian9 we have seen over the past days. With this patch applied, it runs through again: https://jenkins.osmocom.org/jenkins/job/Osmocom-repo-install-debian9/339/ Change-Id: I98a19184ba936114c03cd5cc4f54a3173cbd9cfe
2021-12-17osmo-ggsn-*: install iproute2 for kernel testsOliver Smith2-0/+2
Add the package providing "ip", as debian bullseye doesn't have it installed by default anymore. Fix for: /kernel-test/qemu-ifup.sh: 9: ip: not found Related: OS#4969 Change-Id: I95560868a899169bf0cb05a02d5034d9a77b6af7
2021-12-17scripts/kernel-test/run-qemu.sh: update qemu argsOliver Smith1-1/+1
Get rid of -nodefconfig, it has been removed in qemu 3.1. We are supposed to use -no-user-config instead, which we already do. Fix for this error we see since migrating to debian-bullseye: qemu-system-x86_64: -nodefconfig: invalid option Related: OS#4969 Related: https://qemu.readthedocs.io/en/stable/about/removed-features.html#nodefconfig-removed-in-3-1 Change-Id: I4a00f90980bf6d141ef8d86786e08d405db6db0b
2021-12-16debian-bullseye-titan: install pingOliver Smith1-0/+1
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
2021-12-16debian-bullseye-titan: sort pkgs alphabeticallyOliver Smith1-4/+4
Change-Id: Id5e1d6a3a1705234f25e7c346e2fcf1d3741570d
2021-12-16Add Dockerfile for OpenBTS-UMTSVadim Yanitskiy2-0/+69
Change-Id: Ibbab5973b84047ee7654a5fb2a8e4b36e1d43847
2021-12-16debian-bullseye-obs-latest: new imageOliver Smith3-1/+30
Add missing container for -latest tests. Currently this causes the -latest tests to fail. Related: OS#4969 Change-Id: I1230e87784bc21b5a6424db0bd8734181ead9bfd
2021-12-16sctp-test: Upgrade to bullseyeHarald Welte1-3/+3
Change-Id: I681802fd779530878c2d2358ebf90b8e2adb4870
2021-12-16nplab: Switch from stretch to busterHarald Welte5-10/+12
The test suites require guile-2.0 so we have to stay with buster and cannot upgrade to bullseye (guile-3.0 only). Related: OS#4969 Change-Id: I30c05efbc6c7a21cad71b207e723ef958f1ac9be
2021-12-16Switch ttcn3-* master tests from Debian stretch to bullseysHarald Welte2-9/+13
So far we were using ancient Debian 9 (stretch) for our IUT containers. Let's upgrade that to Debian 11 (bullseye). Related: OS#4969 Change-Id: Ic6bece9cb695e6eccfcb1e83fdbf1048724a3cf9
2021-12-16titan: move from debian-stetch-titan to debian-bullseye-titanHarald Welte30-27/+27
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
2021-12-16jenkins-common.sh: non-jenkins: unique build tagOliver Smith1-2/+2
Support running multiple TTCN-3 testsuites in parallel when the jenkins.sh scripts get called from outside of jenkins too. Closes: OS#5358 Change-Id: Iaaf5719f758553687f2ab57975be275e7ac07e36
2021-12-15nplab-*test: Fix printing of junit on stdoutHarald Welte2-2/+2
Before this patch the printing of the junit.xml to stdout fails: + collect_logs + cat '/tmp/tmp.CzafJpQyw8/*/junit-*.log' cat: '/tmp/tmp.CzafJpQyw8/*/junit-*.log': No such file or directory + true Change-Id: I600d3bdb3de23ef6f381cd5b81e2b851856b2b9b
2021-12-15bsc-test: Reduce log verbosity of osmo-stpHarald Welte1-5/+5
I don't really see the point of crating 19 MBytes of logs for every ttcn3-bsc-* test run that consists mainly of debug messages about sending a message from left to right. osmo-stp is not the IUT here, but merely a part of the test fixture. Let's reduce log verbosity. Change-Id: If1d22814d89c4e52b3b7804110256d896b7cc99f
2021-12-15debian-{buster,stretch}-*: Explicitly specify DISTRO variablesHarald Welte7-0/+14
It seems a manual 'make' in the respective directories no longer works, as always the default distro is used as upstream reference. Let's work around this by adding DISTRO variable assignments to the respective makefiles. Change-Id: I8769d504ca7afde07d4a0ad1f03aaaec892bf576
2021-12-15Add debian-bullseye-build containerHarald Welte1-0/+70
Change-Id: Ie2c75f30a5fc46979812ddfbea349e3d2fa91a7d
2021-12-15sync debian-buster-build with debian-stretch-buildHarald Welte2-3/+18
Change-Id: I6f871613fc4e8dd069cbe8c4a0ef3d1725be8c7a
2021-12-15osmo-remsim-latest: add logic for centos pkgsOliver Smith1-6/+17
Change-Id: If888f69fdcd349c71da06a0f0cf2b6b2f6319fb8
2021-12-15osmo-remsim-latest: fix apt install commandOliver Smith1-1/+1
Adjust to the renamed subpackage in the "apt install" command to fix: E: Unable to locate package osmo-remsim-client Related: osmo-remsim I6c634572af5036fd7f9ce1fee6d1474e06bdaa5a Related: https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-remsim-test-latest/253/console Change-Id: I349111f4dd968f8e4de9598cc35aa99df221e06b
2021-12-15hnodeb: Update Dockerfile, configs with new deps, configsPau Espin Pedrol4-0/+12
Pull in libgtp, configure LL socket, etc. Change-Id: I5b223149cbbea16e4ccd9b3874874c6366fe7969
2021-12-14ttcn3-{sgsn,ggsn}-test: set OSMO_SUT_{HOST,PORT}Vadim Yanitskiy2-0/+6
This enables the test suite to obtain talloc reports between the test case executions, which get stored together with the PCAP files. Change-Id: I61fef7763e6445c231ff2664036e243a9ac96ff6 Related: Icd4c2d80db934535d499598282ed9416d8088163
2021-12-14ttcn3-bts-test/osmo-bts.cfg: use default {fn,rts}-advance valuesVadim Yanitskiy1-2/+0
It's better if we run ttcn3-bts-test with the default values, given that they were significantly reduced some time ago. Change-Id: If8438adfdbc506d2b6b7858ea8a0ea859ba246a1 Related: I7da3d0948f38e12342fb714b29f8edc5e9d0933d (osmo-bts) Related: OS#4487
2021-12-13debian-stretch-build-dist: add python3-nwdiagOliver Smith1-0/+1
Recent versions of osmo-gsm-manuals need python3-nwdiag instead of the python2 version. Install that too to successfully run the configure script. Related: OS#5347 Related: https://jenkins.osmocom.org/jenkins/job/Osmocom-release-tarballs/920/console Change-Id: I127bd3855d44ccc68a5b0c4d83147fb470cc10c9
2021-12-13osmo-pcap-latest: fix install path for centosOliver Smith1-1/+1
Adjust to the package not being split in rpm packaging. This was not noticed before, because we did not run TTCN-3 tests for osmo-pcap with CentOS8. Related: SYS#5754 Change-Id: I775776ff7f358fee3d085f814c295c49225f5170
2021-12-13osmo-pcap-master: doesn't need libosmo-netifOliver Smith1-2/+1
Don't attempt to install libosmo-netif in this Dockerfile. I've noticed this because we want to build osmo-pcap for CentOS7 with this container to run the TTCN-3 tests, and we don't have libosmo-netif for CentOS7. Add pkgconfig(libosmogb), which is required to build osmo-pcap according to configure.ac. In Debian, this gets installed as part of libosmocore-dev. Related: SYS#5754 Change-Id: I9c3a3b43ee7c25c06042f3303b9edb4005e7db31
2021-12-13debian-stretch-build-dist: osmo-uecups depsOliver Smith1-0/+1
Related: OS#5347 Change-Id: I19b6b0363aeeb89ab6aac2b125359589e6b9b5a7
2021-12-13debian-stretch-build-dist: osmo-remsim depsOliver Smith1-0/+2
Related: OS#5347 Change-Id: I8fd4b9d3734dd3bc0e3fca8ceaedda2aedc6a055
2021-12-13debian-stretch-build-dist: osmo-pcap depsOliver Smith1-0/+1
Related: OS#5347 Change-Id: If0f00dd09ce0db6a05972a564474a707d2d3174b
2021-12-13debian-stretch-build-dist: osmo-hnodeb depsOliver Smith1-0/+2
Related: OS#5347 Change-Id: I9d708d86bf29f9fca0446fb990c606780bd7a1cb
2021-12-13debian-stretch-build-dist: osmo-gsm-manuals depsOliver Smith1-0/+8
Add dependencies for osmo-gsm-manuals, so we can build the release tarballs for it (autoreconf -fi; ./configure; make dist-bzip2) in the related jenkins job. During update of the list of projects for which we build these tarballs, it became apparent that it was missing. Following patches will add dependencies needed to build release tarballs for all other projects that were missing from the list. Related: OS#5347 Change-Id: Iba2e71b2e757bc527561d0f3e4a1af5f024a3cd7
2021-12-11Add centos7 containersOliver Smith5-0/+115
Related: SYS#5754 Change-Id: Iadf3d0d7143c2d81ea5e87fd07a3f4cd9239cb46
2021-12-11osmo-pcap-latest: fix typo in Dockerfile: s/clint/client/Vadim Yanitskiy1-1/+1
This patch fixes 'ttcn3-pcap-client-test-latest' job on Jenkins. Change-Id: Ibf472ec712624b16adff4b0f043771f257e7d71f
2021-12-03jenkins-common.sh: pull registry.osmocom.org imgsOliver Smith1-1/+3
Pull debian-stretch-titan from registry.osmocom.org if the repository is enabled. Otherwise the image gets only pulled the first time, and does not get updated once it becomes outdated. Fixes: OS#5336 Change-Id: I1cf998c21e4ee1f723c3b783703e339328377f3e
2021-12-03jenkins-common.sh: fix redundant titan image buildOliver Smith1-0/+10
Do not build debian-stretch-titan, when registry.osmocom.org is enabled. The image that would be built at this point is not useful, since other images like ttcn3-msc-test will use the debian-stretch-titan image from the registry instead of the one that was just built locally. Related: OS#5336 Change-Id: I7127e3ebac3a6a985c3ba50ba8c7cb8c5de978d9
generated by cgit v1.2.3 (git 2.25.1) at 2024-09-23 22:15:23 +0000