aboutsummaryrefslogtreecommitdiffstats
path: root/ttcn3-mgw-test
AgeCommit message (Collapse)AuthorFilesLines
2021-02-11ttcn3: remove /root/projects/git symlinkOliver Smith1-1/+0
Remove leftover from old TTCN-3 build scripts, before refactoring ttcn3 Dockerfiles. This line has already been removed in 357ec806 from 2017 for ggsn-test. In osmo-ttcn3-hacks.git, this is only referenced in the obsolete bin/install.script (looks like we could remove that, together with the rest of the bin dir?). Related: OS#5017 Change-Id: Id23e7fae58ba246916a38aa0a10035d4f67f7588
2020-09-08ttcn3-mgw: Update module param addresses naming to support ipv6Pau Espin Pedrol3-2/+7
Depends: osmo-ttcn3-hacks.git Change-Id Ia393d7175de277ec8fa524ba74bf3b150b74c766 Change-Id: I2840eeee8ae53dc8bdf96ce7b6c76e4c8e0af859
2020-08-27jenkins-common.sh: Add function to print docker network related parametersPau Espin Pedrol1-3/+4
Change-Id: Ie00561de7a4494065156a124565e2190151e6019
2020-08-25ttcn3-mgw-test: Removing the e1 config options on latestDaniel Willmann1-0/+7
Fixes the test failure on ttcn3-mgw-test-latest Change-Id: I3143ba905a77fabd1074dbd618c7ae48fa92a77a
2020-08-18osmo-mgw.cfg: fix config file + add E1 trunkPhilipp Maier1-14/+26
The config file of osmo-mgw has an incorrect indentation. Also no E1 trunk is configured, so that the E1 related tests fail. Lets fix this. Change-Id: I3b19afc0809bd56e9fe0f5e968e1c000d29f4abd
2020-08-13Enable IPv6 in docker networkingHarald Welte1-1/+1
We previously only allocated IPv4 sub-nets to the network segments created with 'docker network'. Let's fix that by assigning both IPv4 and IPv6 address ranges to each docker network. Related: OS#4700 Change-Id: I8802208fddcce1ffa57e5626575d23d02b320d99
2020-06-21collect core dumps: '--ulimit core=-1' and WORKDIR=/data everywhereNeels Hofmeyr1-0/+2
Change-Id: Ief73b53ed9da6f5af82975bc36d851277d5d3185
2020-05-30ttcn3-*-test: remove implicit dependenciesOliver Smith1-2/+0
Don't list debian-stretch-build and debian-stretch-titan as dependencies anymore, now that docker_images_require finds them automatically. Related: OS#4564 Change-Id: I3cb6b693f3dd9df84fb29c0217bb3dae454cc18f
2020-05-06ttcn3-*-test/jenkins*.sh: add $DOCKER_ARGSOliver Smith1-0/+2
Allow to pass options to each "docker run" line in the various jenkins.sh scripts. I'm using this to run the testsuites and Osmocom components in docker with the same configurations as jenkins, but with Osmocom and testsuite binaries built outside and mounted into the containers: DOCKER_ARGS="-v /usr/local:/usr/local:ro -v $hacks:/osmo-ttcn3-hacks:ro" This allows very short test cycles without a second set of configs. The full script that makes use of this feature is in osmo-dev.git, ttcn3/ttcn3.sh. Change-Id: I8d1f78aee926f8f6ec0b704e16639bc83f525816
2020-01-05ttcn3-mgw: Drop not longer existing mp_enable_conn_timeout_testPau Espin Pedrol3-5/+1
It was removed since latest osmo-mgw release is nowadays 1.7.0. Depends: osmo-ttcn3-hacks.git I537c0f5fd6f9e18e111c773c0e42e5f1120ce2f4 Change-Id: Ia457546431e0c3bb3148f4886644ed3fa2513835
2019-11-20Update ttcn3-*/jenkins.sh to log stdout+stderr of process to log filePau Espin Pedrol1-26/+0
This way we get VTY parsing failures as well as backtraces upon process crash. Related: OS#4212 Change-Id: I3d9f6de638dbc07391a32c6a0cbd469dc5adf2b5
2019-10-04ttcn-*: Fix gsmtap log not enabledPau Espin Pedrol1-0/+1
gsmtap log won't be sending any message unless it is allowed by "logging filter all 1". Change-Id: Ibf8062c0d962f2572a07623e6f06936df0d42c67
2019-07-10ttcn3-*: enable GSMTAP loggingOliver Smith1-0/+3
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-06-28ttcn3-mgw-test-latest: disable conn_timeout_testOliver Smith2-0/+5
Depends: I8bbf15baa45679d5812a5a9184520ef9b9e73bba (osmo-ttcn3-hacks) Change-Id: I05ff77246462ba90e8704969e0982662027ad630
2019-06-24ttcn3-{hlr,mgw,pcu}-test: log to fileOliver Smith1-0/+11
Add missing file output which all other tests already have. Related: OS#4067 Change-Id: Ifb4a39e6e2987f4dc04369508fe0dff0913a02ff
2019-06-03ttcn3-*: Enable extended-timestamp in VTY cfgPau Espin Pedrol1-1/+2
Having extended-timestamp allows for easier matching between osmo-*.log files and pcap traces. Change-Id: I98cdc0adc24edc966d5648d2c215c6ad7c749209
2019-05-22Fix git checkout for branches and commitsOliver Smith1-1/+2
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-21Revert "Simplify git checkout, allow branches and commits"Harald Welte1-2/+2
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-07Simplify git checkout, allow branches and commitsOliver Smith1-2/+2
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-03-30Switch all osmo-*-master and ttcn3-*-test from jessie to stretchHarald Welte1-1/+1
Jessie will be EOL in June 2019, let's make the switch to stretch before that. Change-Id: I37a534d07081f3d321869c86d49d03171c8da0c6
2019-03-29print branch name and git commit hash during docker container buildHarald Welte1-0/+1
This is quite useful when looking at jenkins logs to know which exact version was built at the time. Change-Id: Id52c382b454e2beecf46820752aeff15b2c1a0ae
2019-02-20ttcn3-mgw_test: Configure VTY interfacePhilipp Maier2-0/+2
The testsuite did not support VTY access in the past, so VTY access was unconfigured. Lets add the required lines to the configuration files Depends: osmo-mgw If383f81af3306f8f5bdf50152498ae1303d390df Change-Id: Ife949c61156222de3026280071226ef6f5dbd959 Related: OS#3807
2018-10-26jenkins.sh: IMAGE_SUFFIX, docker_images_require()Oliver Smith1-1/+7
Default value "master" of the IMAGE_SUFFIX environment variable can be changed to "latest" to test the latest stable builds instead of the nightly ones. Use docker_images_require() to make sure that the required images are existing and up-to-date before running the tests. Related: OS#3268 Change-Id: Idbb708ab16cb71bab5069127945b63388222369e
2018-09-26ensure well-formed config filesHarald Welte1-23/+23
Change-Id: Id687e63c418e2e955ccbb92f2420a80fc0704ea4
2018-09-06Fix "'laforge/debian-jessie-build' not found"Oliver Smith1-1/+2
Instead of hardcoding laforge's username in all FROM statements in the Dockerfiles, make use of the USER variable (as passed through by the "make/Makefile" with "docker build --build-arg USER=..."). Thanks to fixeria for proposing this fix! This requires running docker-ce, old versions of docker (such as the one in the official repositories of the latest Fedora) don't support variables in the FROM line. But docker-ce can be installed after adding docker's 3rd party repositories. Closes: OS#3457 Change-Id: Ic5f11c8a4e247f632cb6aea6d147e94c53e0130f
2018-07-06ttcn3-*: Merge logfiles no matter resolution of testsPau Espin Pedrol1-2/+4
Previous to this commit, log messages were not being merged if tests were resolved as failed (test-suite.sh ending with exit code != 0), which can happen if at least one test failed. Change-Id: If293fc2d3182ef2a7b997faa8b41129a9dd89c45
2018-05-03ttcn3-{mgw,ggsn}-test: use VOL_BASE_DIR from jenkins-common.shNeels Hofmeyr1-1/+0
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 I8cf6014725ae8ba602be5f3ec31dfb8e49ff993e. Change-Id: Iee034df93bf8e8b995262749cf4654886032af2b
2018-04-24jenkins.sh: have one common function to collect logsNeels Hofmeyr1-5/+1
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. Change-Id: I5d8472ec36b07c828685b1bd7718e31392d168a3
2018-03-28rename mgw-test to ttcn3-mgw-test to align with other containersHarald Welte6-0/+135
Change-Id: If38e95cf40829038c078eb6ecd3df840b2a7b178
generated by cgit v1.2.3 (git 2.25.1) at 2024-09-24 10:14:19 +0000