On our deb10fr VMs we have the modified kernel HDLC module supporting
the frame relay MTU up to 1700 bytes, so let's extend our tests to cover
that. Mainline kernels only support 1500 bytes.
Depends: osmo-ttcn3-hacks.git I8e38ecf6b270c81bd73ee43b1fa0b259a999c14b
Change-Id: Id25532edbf5e1a918ad038723da464723d6f03f0
FRNET_Tests is not a test suite, but just a stub against which we
execute FR_Tests. Hence, we don't want it to generate a junit-xml,
as that doesn't contain any errors and only upsets our jenkins
test results analyzer, assuming the tests have failed.
Change-Id: Idec2bf8da30ccd211b21901d56979143ce3a172f
Requires: osmo-ttcn3-hacks.git Id296e62fb86731492d42370173a48f217b2fbdc0
Since Id35f40d05f3e081f32fddbf1fa34cb338db452ca, osmo-pcu also
depends on libosmoctrl. Debian based images work just fine,
because they depend on libosmocore-dev, while for CentOS we
need to specify all sub-libraries explicitly.
Change-Id: I6cccb77432b2b8fcb9f90c5205f7f1fb9dc41910
Change the whole vty configuration for NS to be more flexible
and support more setups. Old configurations are invalid.
For further information see:
https://osmocom.org/projects/libosmocore/wiki/Network_service_(NS)
Depends-on: Ie9306ab4d4738c2c57a69987086e22771b30657e (osmo-sgsn)
Change-Id: I65fb4e52d22617cf8488d8ab77c970f84995560d
the jenkins.sh script was copied from the SGSN test suite and still
mentioned sgsn at several places when actually intending to mention
gbproxy.
Change-Id: I8709121d8501da4afc1c8dda70356096d331a9b0
Prepare to add debian10-repo-install-test. Make it consistent with
centos8-repo-install-test.
Related: OS#4969
Change-Id: I2ea18997019ebaa013c258996f5131386bcd6426
Make debian-repo-install-test simpler before copying it for debian10.
Don't install Release.key, as it is getting downloaded on demand in the
related repo-install-test script since osmo-ci
I91e7a208d8f5cb50f8baa2fde0eb979aae91da8f.
Related: OS#4969
Change-Id: Ia2ba9de264531502e2b0b9f42d7a4ecd34375851
Starting from build #245 [1] all test cases fail due to DTE:
RAW_NS.ttcnpp:62 Dynamic test case error:
Text encoder: Encoding an unbound integer value.
This happens because fields 'data_weight' and 'signalling_weight'
are both unbound for two additional NS providers. Fix this.
[1] https://jenkins.osmocom.org/jenkins/view/TTCN3-centos/job/TTCN3-centos-pcu-test-sns/245/
Change-Id: I401f53bddd81e8386c01392d9a59c3b5ca8e9802
Fixes: Ic607b3edc3bf724a8b2dbd6be8c806002c229509
also, only change those values from their default values that are
neccessary to change; fall-back on the defaults whenever possible.
Change-Id: I5fba21ddf1854ed2b4f829785ab016dfa284456e
This follows the change implemented in osmo-ttcn3-hacks.git
If0e404bdf2c30a5e18748695608611be83f61109 to use data-only
and signalling-only NS-VCs on the SGSN side
Change-Id: I58f8a6d1c8d01551d366bd7d0dbfb892cce512ae
Requires: osmo-ttcn3-hacks.git If0e404bdf2c30a5e18748695608611be83f61109
Related: OS#4953
In upstream I9798e639b4bc8658482945970775b012b5840779 we introduce
two additional fields per NSVC (data_weight, signalling_weight). Make
sure those are specified everywhere.
Related: OS#4953
Requires: osmo-ttcn3-hacks.git I9798e639b4bc8658482945970775b012b5840779
Change-Id: Ic607b3edc3bf724a8b2dbd6be8c806002c229509
With the change to NS_Provider the configruation has to be extended to also include
the other nsvcs.
osmo-ttcn3-hacks: c316572db111 ("RAW_NS: rework NS connection to use NS_Provider")
Change-Id: I8020f808c06054ee38427de65b8c3867817d4ad2
PATH isn't overwritten anymore when jenkins runs docker in osmo-ci.git's
master-builds.yml / gerrit-verifications.yml, therefore we can remove
this hack.
Change-Id: I5bff98f7af1a2f2de88c8d96d1e30de960057d01
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