aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2019-07-11osmocom-bb-host-master: install python-enum as fake_trx dependencyAlexander Couzens1-1/+2
62825cc8eb4e26d58d32a0af72b17256b185af61 (osmocom-bb) started to use the python module enum which not part of the standard libary of python 2. Change-Id: I70b7f1b43a1e121114a924c09614d6eddc801881
2019-07-10ttcn3-*: enable GSMTAP loggingOliver Smith17-0/+51
Configure each osmo-* program to send GSMTAP log output to the IP of the docker container, which runs the testsuite (and therefore runs tcpdump). Related: https://lists.osmocom.org/pipermail/openbsc/2019-June/012946.html Change-Id: I99e74f6ffb5b7d566cec35995bf067df414968d8
2019-07-05clean up the net and attached containers to ensure reliable test startsEric Wild1-0/+10
We can't create the net if it exists, and it can't be removed until all attached containers are dead, so ensure this is the case upon net creation. This fixes test failures due to stale nets and half-killed test runs. Change-Id: Id6d13b233ebfd808d8dfe83b6d1d1ba20c3392c8
2019-07-02debian-stretch-build-dist: new DockerfileOliver Smith3-0/+59
Provide all build dependencies needed to pass ./configure of most Osmocom repositories. This will be used to run osmo-release-tarballs.sh in jenkins. Related: OS#3870 Change-Id: I991fe41a1f55ccd6a66815ec3d7f239850397d9a
2019-06-30ggsn: Set correct name for osmo-ggsn log filePau Espin Pedrol1-1/+1
Change-Id: I65803bdd4d2bcd79c690841bfc3cc62c8260289d
2019-06-28ttcn3-mgw-test-latest: disable conn_timeout_testOliver Smith2-0/+5
Depends: I8bbf15baa45679d5812a5a9184520ef9b9e73bba (osmo-ttcn3-hacks) Change-Id: I05ff77246462ba90e8704969e0982662027ad630
2019-06-27regen_doc: check OSMO_INTERACT_VTY, fix defaultOliver Smith1-1/+6
Change default from osmo-interact-vty.py to osmo_interact_vty.py, which is the name of the script in osmo-python-tests.git. Check if that script is in PATH before building and running the docker container. Change-Id: I763c7379b710160e0155f1fde091137754141335
2019-06-24Have only one bts/bsc configured in osmo-bsc and bscnatDaniel Willmann2-194/+0
The way our counter reporting works is that each counter group is reported even if the same one exists multiple times. To avoid that change the default config (used by regen_doc.sh) to only configure one bts / bsc. Change-Id: I57468d983580b5ed4f15961ac1eac9bed9096556 Related: OS#1700
2019-06-24osmo-sgsn-master: Bind to localhost instead of a specific IP by defaultDaniel Willmann1-3/+3
This does not break ttcn3-sgsn-test since it uses a custom config file with the correct IPs. Change-Id: I2a922139c50d06217e5e6105ea65bf673daa10a8 Related: OS#1700
2019-06-24osmo-mgw: Bind to 0.0.0.0 by defaultDaniel Willmann1-2/+2
Don't bind to a specific IP otherwise starting osmo-mgw will fail (if we don't configure that exact IP address) Related: OS#1700 Change-Id: Ic5828957a29d4f317e1ebf4f03b5f5359f6250e8
2019-06-24ttcn3-{hlr,mgw,pcu}-test: log to fileOliver Smith4-0/+41
Add missing file output which all other tests already have. Related: OS#4067 Change-Id: Ifb4a39e6e2987f4dc04369508fe0dff0913a02ff
2019-06-24redmine: migrate from 3.4 to 3.4-passengerHarald Welte1-1/+1
This provides much more reasonable performance on our high-end server Change-Id: Idaa19566d1d5ac4ea0ff0296d57d1f9ca2bd599b
2019-06-19regen_doc.sh: Add optional parameter to customize docker executionDaniel Willmann1-1/+3
The osmo-nitb-master image can run not only osmo-nitb, but also osmo-bsc_nat. In that case we can't use the default command from Dockerfile, but should provide our own. This argument makes it possible to do so. Change-Id: I52c3cb2cdcfb143e71ac2c1aa40bb466e41a0f5c Related: OS#1700
2019-06-19osmo-nitb-master: Add default config file for osmo-bsc_natDaniel Willmann3-0/+65
Change-Id: I44bb395009582f5e1399f277e15203553c2dcf78 Related: OS#1700
2019-06-18Add script to regenerate VTY and counter documentationDaniel Willmann7-0/+53
This script needs access to the VTY interface, so I changed some remaining config files to bind the VTY interface to 0.0.0.0. There are a couple of services that do that already. Related: OS#1700 Change-Id: Ic5cf7f59de0c18d4c5568b89433c2b11db2a72a5
2019-06-13jenkins-common.sh: Don't rebuild debian-stretch-build during fix_permsHarald Welte1-1/+4
When fixing the permissions at the end of a test run, it really doesn't matter if we're running a current debian-stretch-build image, or if we are using an ancient one. All we need is a 'chmod' binary. Change-Id: Ib008ee72f40aeefb307c0ba74a57b70daae9d07b Related: OS#4060
2019-06-11bscnat: Bind bsc-nat CTRL on 0.0.0.0Pau Espin Pedrol1-0/+3
Other tests already do it, and allows using the CTRL iface in docker setups where 127.0.0.1 is not used. Change-Id: I6f16dc322d38f9f0870241f3416c81df8ec5481b
2019-06-04ttcn3-bts-tests: Add BTS_Tests_LAPDm.control to config fileHarald Welte1-0/+1
There's a number of new tests that aren't executed yet. Change-Id: I3bfb4483f39d4dbf3f506f86470e4f2d3b6b7af2
2019-06-03ttcn3-*: Enable extended-timestamp in VTY cfgPau Espin Pedrol9-1/+10
Having extended-timestamp allows for easier matching between osmo-*.log files and pcap traces. Change-Id: I98cdc0adc24edc966d5648d2c215c6ad7c749209
2019-05-31msc: Disable osmux for ttcn3-msc-test-latestPau Espin Pedrol2-0/+5
Latest tagged version of osmo-msc doesn't support "osmux on/off" VTY commands, so we have to enable osmux use on that version to avoid most TTCN3 tests failing during set up phase. Depends: osmo-ttcn3-hacks.git I53d58b2d905905ebf1df322d0389b3715a48212f Change-Id: I6b3be3981978661de2fa90be130f6f1811a3d1f9
2019-05-31bsc: Fix: Disable osmux for ttcn3-bsc-test-sccplite-latestPau Espin Pedrol1-0/+1
Recent commit added bits to disable "osmux on/off" vty commands on "-latest" tested, but forgot to add required line in sccplite/BSC_Tests.cfg for sed command in jenkins.sh script to work. Fixes: 2cdab85e5f42c876a3024ca2154c67c21d1d78cc Change-Id: I9b4ce2d7151d65b4c83417a59fd01672971b3937
2019-05-29ttcn3-bts-test: Execute OML tests without BSCHarald Welte3-3/+126
Run the testsuite one more time; this time for OML tests which require us to run without a BSC. We can run those with trxcon and omso-bts-trx and don't need virtphy for them. Related: OS#4031 Depends: osmo-ttcn3-hacks I82bb85b684d2db3a6b1e96a68ffde03e22affa6b Change-Id: I97db9c74c56ca93c75e5e5226955799cd945eec0
2019-05-29ttcn3-bts-test: Add virtphy based PCUIF testsHarald Welte3-3/+142
Some tests require GPRS features not yet present in trxcon, so we have to fall back using virtphy. Change-Id: I2f17f03194a4dfa0abca51b0d3e22b3934d08a9a
2019-05-29ttcn3-bts-test/jenkins.sh: Move start of containers into shell functionsHarald Welte1-46/+61
Change-Id: If9ac580aa5f0745468f69d413aa732891acb4a1c
2019-05-29osmoocm-bb-host-master: Build virtphy, not only trxconHarald Welte1-0/+5
There are some BTS_Tests which (so far) don't yet work with trxcon hence require virtphy. Change-Id: I0aabd73e2778b9144aa7945f25cae5cefea4111b
2019-05-29ttcn3-sgsn: Run log_merge.sh after testsPau Espin Pedrol1-2/+5
Change-Id: If03422bb8fb126fe6f204a4f8bc6edf0cbb7f194
2019-05-28bsc: Disable osmux for ttcn3-bsc-test-latestPau Espin Pedrol3-0/+8
Latest tagged version of osmo-bsc doesn't support "osmux on/off" VTY commands, so we have to enable osmux use on that version to avoid most TTCN3 tests failing during set up phase. Depends: osmo-ttcn3-hacks I61e4c59b2926f3f70cb6d0190a8683861e54179a Change-Id: I745b210f43cb147d323a15f78c294f70ee077729
2019-05-27ttcn3-bscnat: Prepare cfgs for VTY & Osmux supportPau Espin Pedrol3-0/+6
* Adding "osmux on" for each BSC will be required to enable Osmux later on, but still it doesn't change behavior now because Osmux must be enabled globally too (will be done through VTY). * Set up correct bind and remote IP addr to have VTY working later on. * Use extended timestamp to have subsecond accuracy to match with pcap easily. Change-Id: I794a17bdeaff9ab9316d7a6acb1e58dfd815b645
2019-05-23ttcn3-bts-test: Fix BSC VTY access from test suiteHarald Welte2-0/+2
Some tests, particularly those for SMSCB, want to access the BSC VTY. This was enabled in the ttcn3 code, but the configs we're using in the docker environment didn't properly refelect that yet. Change-Id: I6b6e8b47bfe85c15fb57a25b649029f872477146
2019-05-23ttcn3-bscnat-test: Use unique sub-network 172.18.15.0/24Harald Welte3-11/+11
For some reason, the bscnat tests were using the same subnet as the sip-connector tests, causing address clashes when trying to execute both test suites simultaneously: + echo Creating network ttcn3-sip-test Creating network ttcn3-sip-test + docker network create --internal --subnet 172.18.11.0/24 ttcn3-sip-test Error response from daemon: Pool overlaps with other one on this address space Change-Id: I62b01b4b291ed9d729139fcf9b0102459e7f5a6a
2019-05-22Fix git checkout for branches and commitsOliver Smith24-24/+48
Replace 'git checkout -f -B $BRANCH origin/$BRANCH && \' in all Dockerfiles that accept branch variables ($OSMO_TTCN3_BRANCH, $OSMO_MGW_BRANCH, ...) with the following: git checkout $BRANCH && \ (git symbolic-ref -q HEAD && git reset --hard origin/$BRANCH || exit 1); \ This allows using branch names and commit hashes in the $BRANCH variables. Using commits is needed for the bisect script added in [1]. The second line ("(git symbolic...") checks if we are in detached HEAD state after the checkout, and if we are not, pulls in all new commits from origin/$BRANCH. Note that it ends in ';' instead of '&&', because the command in the next line should be executed even if "git symbolic-ref" does not exit with 0 (detached HEAD state). Here is an example, to illustrate that the new command does the right thing. Clone a repository and be 50 commits behind origin/master: $ git clone "https://git.osmocom.org/osmo-mgw" $ cd osmo-mgw $ git reset --hard origin/master~50 With BRANCH="master": $ git checkout master && \ (git symbolic-ref -q HEAD && git reset --hard origin/master || exit 1); \ echo "done" Already on 'master' ... done $ git status Your branch is up-to-date with 'origin/master'. With BRANCH="85978d": $ git checkout 85978d && \ (git symbolic-ref -q HEAD && git reset --hard origin/85978d || exit 1); \ echo "done" Note: checking out '85978d'. ... done $ git status HEAD detached at 85978dad Related previous changes: * [2] made it work for commit hashes, but broke using branch names other than master, and pulling in new commits from master * [3] made branches other than master work again, but did not fix pulling in new commits from master * [4] reverted [3] and the git checkout related part from [2] [1] Change-Id: I11f7e61a9b30d58a0fdfcaf77dde447806bf661f [2] Change-Id: If3bc5fae07cf63c4fef68306be4c4328660bc869 [3] Change-Id: I2ff745c8d19b777d876170d5717c082ceb68a1f3 [4] Change-Id: Ie6da0f9ea96f11407e38545a6b3cf22ef9cadc25 Related: OS#4015 Change-Id: I4004980baf0b7d6096702b6f3067ccbdb369a28c
2019-05-21osmo-bts-test: Enable BTS_Tests_SMSCB.control for CBCH testingHarald Welte1-0/+1
Support for this was introdcued in osmo-ttcn3-hacks Change-Id If4b5a906a0841c0a8c3d7c4e9e5a3d1208ecf16a, but as we have a separate .cfg file here, we must update it, too. Change-Id: Iab0e9a46a8ee429619e9ef9159a631dc44ab5aeb
2019-05-21Revert "Simplify git checkout, allow branches and commits"Harald Welte26-47/+47
Unfortuately this commit will check out *local* master (i.e. the previous checkout) rather than the origin/master as it's supposed to be. This means that ever since merging this patch, our ttcn3 tests were running some "undefined" stale versions and not current master. This reverts commit 26565bb729549152ce8fa89f59df02f37c907c27. Change-Id: Ie6da0f9ea96f11407e38545a6b3cf22ef9cadc25
2019-05-16RFC: allow to set configuration and/or specific testcasesAlexander Couzens2-5/+11
Allows to pass the configuration file and/or tests to start-testsuite.sh. This way a single test can be specified by the command line. If this RFC gets accepted, I would convert all other Docker.files Change-Id: I17e480321f1e7bfa287349f438ff6990e30f1114
2019-05-07Simplify git checkout, allow branches and commitsOliver Smith26-47/+47
Replace the following statements: a) "git checkout -f -B $BRANCH origin/$BRANCH" b) "git checkout -f -B $BRANCH $BRANCH" with: c) "git checkout -f $BRANCH" Regarding a), we don't need to specify 'origin/' for each branch, since we are cloning the repositories in the same Dockerfile, and therefore we know for sure that there is only one remote and branch names won't be ambiguous. Removing the 'origin/' allows to put commit hashes into the branch variables (like done in the new bisect script [1]). Version b) does not work with branch names: $ git checkout -f -B osmith/check-imei-before-lu osmith/check-imei-before-lu fatal: Cannot update paths and switch to branch 'osmith/check-imei-before-lu' at the same time. Did you intend to checkout 'osmith/check-imei-before-lu' which can not be resolved as commit? New version c) works with both commits and branches, and it is shorter. [1] Change-Id: I11f7e61a9b30d58a0fdfcaf77dde447806bf661f Change-Id: I2ff745c8d19b777d876170d5717c082ceb68a1f3
2019-05-07debian-*-build: don't download "Release" fileOliver Smith2-2/+0
Stop jenkins jobs from failing, due to the download errors we are getting from time to time, by simply not downloading these files. They are redundant, because we are already running 'docker build --pull' before trying to build the debian-*-build images [1], and the docker images are released at least as often, as the "Release" file gets updated [2]. This is in line with how it is done in osmo-ci.git. [1]: Change-Id: I1076bbb7d77bdc99f5d60d641c09ce965fb9dfc6 [2]: https://hub.docker.com/_/debian Change-Id: Ieedb310814412f235e56bdc65517404842eac00f
2019-05-05gr-gsm-master/Dockerfile: use the official archlinux/base imageVadim Yanitskiy1-1/+1
According to [1], the image 'base/archlinux' has been deprecated. It's recommended to use the official ArchLinux docker image [2]. [1] https://hub.docker.com/r/base/archlinux [2] https://hub.docker.com/r/archlinux/base Change-Id: I7e5d57662e9d8ca2b5037c24427ce1c44de15813
2019-05-02debian-stretch-titan: install procpsAlexander Couzens1-0/+1
The ttcn3-tcpdump-stop.sh uses `ps` to find out if tcpdump is still running. Change-Id: I8db4ad2262a3a734201e39bc065c1c383738992c
2019-05-01ttcn3-msc-test: Execute MSC_Tests_Iu.controlHarald Welte1-0/+1
The new IuCS related tests have been added as 'MSC_Tests_Iu' module to take advantage of the hierarchical display format in the Jenkins tests results analyzer. Let's execute them. Change-Id: I80ccfce4874d14039bbcb273c3b450db2a7780dd
2019-04-30ttcn3-msc-tests: Add IuCS for one simulated RNCHarald Welte3-1/+19
We need to update the MSC_Tests.cfg as well as the osmo-stp.cfg to provsion a virtual RNC link. As the new RNC uses routing key 2, we shift the MSC routing key to 3. Change-Id: I10a249b1a851436fd3c20face6ccc94b304bd3e4
2019-04-26Add script to bisect test failures with ttcn3 and dockerDaniel Willmann1-0/+53
With this script you can now use docker ttcn3 test results to bisect a regression and find the offending commit. Use like this from the osmo-* git repository: $ git bisect start <bad-rev> <good-rev> $ git bisect run ~/scm/osmo/docker-playground/osmo-bisect.sh <component-to-test> <testcase> e.g.: $ git bisect run ~/scm/osmo/docker-playground/osmo-bisect.sh bsc BSC_Tests.TC_ho_in_fail_no_detect Change-Id: I11f7e61a9b30d58a0fdfcaf77dde447806bf661f
2019-04-25Add OSMO_*_BRANCH environment variables for build argsDaniel Willmann13-13/+40
Previously we could only set OSMO_TTCN3_BRANCH as environment variable to build a test other than master. This patch adds environment variables for all osmo-*-master images which allow docker tests to be executed for an arbitrary commit. The origin/ prefix from the git checkout command is removed so the *_BRANCH variable doesn't have to contain branch names, but van also contain arbitrary commits. This shouldn't have any adverse effect as we only have one remote in the checkout. Change-Id: If3bc5fae07cf63c4fef68306be4c4328660bc869
2019-04-21debian-stretch-titan: include libfftranscode for our Iu related testsHarald Welte1-0/+9
Change-Id: Ifd7d682df90f1b17823d8358a8a498f149e4591b
2019-04-17Use ftp.debian.org as a "blind workaround" for trouble with ftp.deHarald Welte2-2/+2
We get a lot of build failures recently like this: Step 3/4 : ADD http://ftp.de.debian.org/debian/dists/stretch/Release /tmp/Release ADD failed: Get http://ftp.de.debian.org/debian/dists/stretch/Release: dial tcp 141.76.2.4:80: i/o timeout ../make/Makefile:44: recipe for target 'docker-build' failed make: *** [docker-build] Error 1 make: Leaving directory '<https://jenkins.osmocom.org/jenkins/job/ttcn3-sip-test/ws/debian-stretch-build'> + exit 1 Let's hope that this works around the connectivity problems with ftp.de.debian.org Change-Id: I5a0eb058d95372c44fce042de90c4127a3021a93
2019-04-05nplab-m3ua-test: support running without jenkinsOliver Smith1-1/+1
Don't use $WORKSPACE anymore, use $VOL_BASE_DIR like in every other jenkins.sh in this repository. Make it possible to run jenkins.sh outside of jenkins (where $WORKSPACE is not set), because jenkins_common.sh will set up $VOL_BASE_DIR to point to /tmp/logs. Change-Id: I200b4ee1760a879cbc0a80a30a062a3f2a8e703d
2019-04-05nplab-m3ua-test: add sigtran-tests dependencyOliver Smith1-0/+1
Make sure to build sigtran-tests before building nplab-m3ua-tests. This has been working by coincidence without the dependency so far, because nplab-sua-test had the dependency listed and that test ran on the same host. Change-Id: I9df1d2b188e86b3c99c6ec793b6eb644ab3c27c9
2019-04-04gitignore: add .releaseOliver Smith1-0/+1
Ignore .release files generated by make/Makefile. Change-Id: I9ea8e4326f6da2ff95cf45999637c89f884a9e19
2019-04-04make/Makefile: fix recursive 'PULL' errorOliver Smith1-1/+1
Don't abort with the following error, when running 'make' without setting the PULL environment variable: ../make/Makefile:20: *** Recursive variable 'PULL' references itself (eventually). Stop. This fixes a regression from Change-Id I1076bbb7d77bdc99f5d60d641c09ce965fb9dfc6. Related: OS#3869 Change-Id: I4b4772e9ed6e07ab00943154265c9cbdea22a2f5
2019-04-02jenkins-common.sh: pull upstream base imagesOliver Smith2-2/+13
Prevent building docker images on top of outdated Debian images, where the package download feeds have been disabled. Use 'docker build --pull' instead of 'docker build', whenever the "FROM" line in the Dockerfile does not contain '$USER' (meaning this is an upstream image). Checking the FROM line is necessary, as downloading '$USER' images will fail (we never upload those). Related: OS#3869 Change-Id: I1076bbb7d77bdc99f5d60d641c09ce965fb9dfc6
2019-03-30Switch all osmo-*-master and ttcn3-*-test from jessie to stretchHarald Welte31-46/+46
Jessie will be EOL in June 2019, let's make the switch to stretch before that. Change-Id: I37a534d07081f3d321869c86d49d03171c8da0c6
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-14 01:50:42 +0000