Digest: This seems a bit of the magic of ruby but I vaguely remember having seen this before. I have
either patched or backported a fix. In newer Ruby versions "Digest" has been deprecated. The diff to
"stock" openid 2.3.0 is:
Do not brush over VOL_BASE_DIR with a new temp dir, since jenkins-common.sh has
already figured out where these should run.
Should fix jenkins job build failures for mgw and ggsn, after the merge of
On jenkins, place all logs and manage docker volumes in the workspace instead
of a /tmp/* dir. Use $WORKSPACE/logs as docker volume base to begin with, thus
there needs to be no copy from /tmp to $WORKSPACE/logs.
On non-jenkins runs, place all in a /tmp/* dir still, but also skip copying of
the logs: just have a /tmp/logs symlink to the last tmpdir.
In Change-Id: I1dc299407c61b1c865035add44067b8ab89001b3
a VTY interface was added to osmo-ttcn3-hacks.git, but
it was missed to update the config file here for the dockerized
execution, rendering us with broken test builds ever since.
The openid support doesn't allow to add custom providers but we like the
convenience of a single click. Take the official docker image and patch
the HTML template. It seems to have changed little over the time, and it
might continue like that...
I have filed https://bugs.chromium.org/p/gerrit/issues/detail?id=8828 so
that we can drop this hack in the future...
To remove code dup and prepare a change to where logs are written, add
collect_logs() to jenkins_common.sh and call that from each jenkins.sh after
the tests are done.
The 'rm -rf' is already done before a test starts. No need to do that again
after each test.
After merging Change-Id: Ie844c4de62e0ef5d5c4c366185968211a7f6d676
in osmo-ttcn3-hacks, the module parameters for BSSAP configuration
require one extra argument.
Te make scripts will generate docker images like
"$username/foobar-test". When depending on an previous image,
the $username must match or the build will about with image not found.
All three BTS are configured for ARFCN 871 and BSIC 63, which causes trouble
for handover tests. Set BSICs to 10, 11 and 12 (not 0,1,2 to mark the
distinction from the cell_identity).
It wasn't a problem so far since we cheated by passing the BTS target number
from VTY. But as soon as we will start identifying handover target cells by
ARFCN+BSIC exclusively, TC_ho_int would fall on its face without this patch.
See also: osmo-ttcn3-hacks I2ea8889ea40953f5a23eab40db52585556a410bc
The 'laforge/trx' branch of OsmocomBB was used to make basic
TTCN3 tests, such as the 'max_ta', work ASAP. Now all required
changes and some bug fixes have been merged to the 'master'.
$(PWD) reflects the dir of 'make' invocation, $(CURDIR) the dir stepped into.
So obtain the current dir from $(CURDIR) instead of $(PWD).
So far, when doing 'make -C osmo-foo-maser', the image's name would be derived
from the root dir's basename and all images were tagged as 'docker-playground'.
With this fix, 'make -C' from anywhere still tags with the proper name.
osmo-ttcn3-hacks adds configuration of the CTRL interface in
I502b4891e6720ae2fb251c03542f707880a6f728. We need proper IP addresses here for
the f_ipa_ctrl_start() to work.
WARNING: This commit has to be merged "at the same time" as
I502b4891e6720ae2fb251c03542f707880a6f728 or the jenkins ttcn3-bts-tests will
a) if we want to set a modulepar mp_ctrl_ip here, it needs to be added to
b) if we have the f_ipa_ctrl_start() in osmo-ttcn3-hacks, we need to configure
the proper IP and bind interface here, or all tests will fail because
f_ipa_ctrl_start() cannot connect.
the routink key for virt-bsc0-0 and virt-bsc1-0 is the same
(0), virt-bsc0-0 and virt-bsc1-0 should use different routing
- Keep the routing key of virt-bsc1-0 and assign routing key 1
In osmo-ttcn3-hacks Change-Id I52a4c8118828c1605cf672889982f987568ad17d
we introduced changes to the BSSAP_Adapter, but the config file for
the BSC hasn't been updated accordingly here.
In Change-Id: Ie7780750f7032453951f6849ecee6ab7cc34e8c2 we not only
introduced a MSC_Tests.default with syntax errors, but also a
osmo-stp.cfg with syntax errors :((
The MSC_Tests.ttcn testsuite is now able to present multiple BSC
to the MSC (IUT). This change requires the configuration files
of osmo-stp and of the testsuite to be changed.
- update MSC_Tests.cfg to present up to two BSCs to the MSC
- update osmo-stp.cfg to support the additional connection
from the testsuite
Depends: osmo-ttcn3-hacks I52a4c8118828c1605cf672889982f987568ad17d
This uses the debian-nginx container "ankitrgadiya/cgit:debian-nginx"
and adds pygments for syntax highlighting, as well as the osmocom
commit filter for linking to gerrit change-ids as well as
The configuration of osmo-bsc currently only supports halfrate
traffic channels. In order to test assignments which contain
half rate codecs we also have to have halfrate channels available.
Allow the osmo-bsc-main docker container to reach the virtual MGW set up by the
The module parameter mp_test_ip sets the IP address at which the virtual
services are set up to listen for connections -- currently actually only the
virtual MGW. Set this to 172.18.2.203 instead of using the default 127.0.0.1.
This fixes the second half of the disconnect between BSC and virtual MGW in
this docker setup. The first half is Ib53f000ec7e717b14a3e5df6e803d3d0950b937f
The osmo-bsc-main docker container is run in a separate docker container and
cannot reach the virtual MGW set up by the ttcn3-bsc-tests.
From ttcn3-bsc-tests/jenkins.sh it is clear that the tests are run at IP
172.18.2.203. Add this as the 'mgw remote-ip' setting in
This fixes the first half of the disconnect between BSC and virtual MGW in this
docker setup. The second half is I3038481ed0bba1084b63dc6a6d2ff6e970100890.
In the past, MM INFO transmission was broken, so the tests were
written without expecting it. Now, the bug in osmo-msc has been
With the config file enabling it, and the tests not expecting MM INFO,
a lot of them failed. Let's disable MM INFO for now until the tests
can deal with it