Clone osmo-ci.git, and install all files from scripts/* to
/usr/local/bin. Together with osmo-ci
I45bd7ea56849dab839a98cfd52806f7cd288094e, this will make overwriting
PATH obsolete.
Related: OS#4911
Change-Id: I0820f13cd740f7d4a8999d279cef6ae293a67d81
In commit 2279aac6 dumpcap is used to capture pcaps, but dumpcap fails
if the directory isn't writable for everyone.
Commit 62ac27779 only fixed this issue for frame relay, this simply
mirrors the change for ttcn3-gbproxy-test
Change-Id: I11dcf9efd0b06544a82e31dec03fe76e182fd0d3
Related: OS#4518 SYS#5115
In osmo-sgsn Change-Id Id67592aa7712e5e04e7264b2fb8f26d57eb7e69e we
have changed the config file syntax and must adjust here accordingly.
Change-Id: I8770baac2298ee9a71d7428ea30600751783b4f9
Depends: osmo-sgsn Id67592aa7712e5e04e7264b2fb8f26d57eb7e69e
There has been a lot of changes merged to both osmo-{bsc,bts}, so
now the later seems to be respawning faster then before. Because
of that, osmo-bts-trx is now reaching the limit of 500 runs on
Jenkins right in the middle of ttcn3-bts-test execution:
respawn.sh: exiting after 500 runs
causing the remaining test cases to fail due to:
"BTS_Tests.ttcn:253 : Timeout waiting for RSL bring up"
Most likely, the IUT respawns several times in the windows between
the test cases, i.e. after TITAN finishes one test case and before
it starts another. Let's instruct respawn.sh to sleep 1 second
before starting the process again.
Change-Id: I09e5a8e7c4d28424cd0d004a8bae3cf0ade2d838
osmo-gbproxy-master is derived from osmo-sgsn-mater, and the former
needs to be re-built to catch up with osmo-sgsn.git changes (Where
the osmo-gbproxy source code is located)
Change-Id: I8abc9f89d19d657403569b7705cd923342ff300b
For some magic reason, apt segfaults while installing the DEBs:
$ apt install ./libfftranscode0_0.3_${DPKG_ARCH}.deb \
./libfftranscode-dev_0.3_${DPKG_ARCH}.deb
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Segmentation fault (core dumped)
so it kind of confirms the warning about its stability ;)
Change-Id: I7f3288161577b055145afe89de7dff50853760f5
In Change-Id I80de01c96185c60fe2de7a8ffa9daed2669658e1 we introduced
the wrong hdlcnetX device names. We must use each devoce only once,
rather than trying to use hdlcnet1..4 twice.
Change-Id: I56f75995fe94b46b0210de2a4f83e384b4e4ca4f
In Change-Id I80de01c96185c60fe2de7a8ffa9daed2669658e1 we updated
only the osmo-gbproxy.cfg, but noth the GBProxy_Tests.cfg for the
test suite, which of course won't work.
Change-Id: I35603dc76926d76e57993f7eab1354eea8d25dad
Related: SYS#5226
We are using centos8 as distro name instead of centos everywher else
and jenkins-common.sh are expecting that.
Related: OS#4888
Change-Id: I05b012abced5b812e74315ccf64365896412e876
This allows easily changing to another osmocom repo base URL if the
default one is down.
Related: OS#4862
Change-Id: I8010b08f3dabacfb3c13a44eece6c7a490e0742e
Similar to what is already done with DISTRO, which points to given image
of ours based on name. This time we do the same with upstream images,
such as debian:stretch or centos:centos8.
This way, for instance calling docker_images_require
"osmo-bsc-latest-centos8" would try to build the
osmo-bsc-latest/Dockerfile file starting from a centos8 image.
Change-Id: I33cb21aa024396974559fd98f9f3c64e2c351eda
Testing FR support in osmo-gbproxy is a bit more complicated
as it involves the "hdlc" net-devices privded by the hdlc_fr.ko
kernel module.
So we need to
* run on a host with actual hdlc net-devices (e.g. dahdi_dyamic_loc)
* move those net-devices into the containers after starting them
* wait for the net-devices to appear in the containers before starting
either gbproxy or the test suite
Change-Id: Id4b52877db53cb6e59f6d0d3f754aaae633949e8
Using a separate container will allow us to do gbproxy specific things
like waiting for physical net-devices to show up in the docker netns
before actually starting the osmo-gbproxy executable
Change-Id: I5e6351055ac9430f13e43291cf2a9d52683fe6bf
In osmo-ttcn3-hacks.git Change-Id If1220852785853f8a5d8de183d5053ddd6ccb958
we introduce support for multiple NS-VC inside a NS-VCG. This modifies
the configuration structures, and we need to adjust all config files
accordingly.
Change-Id: I6ac250555c3ac2aa8feb70bd3a052aafec5d4210
This is initialized to docker.io, keeping the default behaviour
if not specified. However, it allows us to specify a private
registry later on.
Related: OS#4839
Change-Id: I32d4ee6256033c809108c1b86cb6b6c58d880f49
This is needed on the target remote hosts, where osmo-gsm-tester will
install a copy of the script to run remotely at runtime.
Change-Id: I59151dfe7091628707cd016db42171d22729a60c
The python bindings of gnuradio are used to control a zmq connection
broker between srsENB and srsUE to emulate attenuations.
Change-Id: Ic4e8c4d6a5d1e20dd336ff15868c7c3f51dea323
This part is missing from the already merged
I3394f391a6068ab8afeafa329b69a8ae4ad05cd9
which enabled LCS tests for osmo-bsc.
Change-Id: I873d6e46e00ee0e91b15d719829baff2bf9f115a