aboutsummaryrefslogtreecommitdiffstats
path: root/ttcn3-msc-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-16ttcn3-msc: Force MNCCv6 on ttcn3-msc-test-latestPau Espin Pedrol2-0/+3
Default is MNCCv7 since osmo-ttcn3-hacks.git I5448ff931ec33f24f4837a51376f1703fe97683b, but latest tagged version of osmo-msc only supports MNCCv6. Change-Id: Iaac2f5453214dfcf6efd070f6ea1212a7833eb1b
2020-09-15ttcn3-msc: Update module params against new osmo-ttcn3-hacks.gitPau Espin Pedrol2-1/+3
module param mp_enable_osmux_test is dropped in osmo-ttcn3-hacks.git I8bc0551ec91a5fd8ea2f291a1e16a06a739c7a75. module param mp_enable_crashing_tests is introduced in osmo-ttcn3-hacks.git I46f1066323e19dfe708402a8c9c68e257f62751c. Change-Id: I22bb43ba6d15eabcc731a2c3ef7aabc4f250d508
2020-08-30ttcn3-msc: Enable osmo-msc SS7 multi-homing and IPv6 features in testsPau Espin Pedrol3-0/+18
Change-Id: I784eb033a4887c5a9f2bfaa52aa39cb86cdf13ce
2020-08-27jenkins-common.sh: Add function to print docker network related parametersPau Espin Pedrol1-4/+5
Change-Id: Ie00561de7a4494065156a124565e2190151e6019
2020-08-19msc: Disable expecting CommonID when testing 'latest'Harald Welte2-0/+3
As of osmo-ttcn3-hacks.git Change-Id I4976d9bb1f07c8ab4ffa02848414f8ddd1bdfd3f the test suite expects the MSC to send a CommonID to the BSC. As older/existing tagged osmo-msc don't do that, we needt odisable that check when verifying 'latest'. Change-Id: If2e4cc41cb7b5758a78d694d62b34390a08e6387 Related: OS#2969
2020-08-14migrate ttcn3-msc-test from 172.18.1.0/24 to 172.18.20.0/24Harald Welte5-23/+23
When introducing IPv6 support, we map the third digit of the IPv4 address (X) to the 6th byte of an IPv6 prefix "fd02:db8:X::/64" However, the docker daemon seems to use "fd02:db8:1::/64" internally for its default network, so creating a docker network with the same IP address is failing. Let's move the MSC test suite to another sub-net (1->20) to avoid related problems. Change-Id: I9c5f9b96d5523eae09f3f2e6c813e9e0d047f9ab
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-07-08ttcn3-msc-test latest: do not require VLR cell id match in latest buildNeels Hofmeyr2-0/+7
Depends: Ie410714a96353f74a52a104c56fa0a08683e0004 (osmo-msc) Change-Id: I052fea208021509e12826c50474b96474e7a58c2
2020-06-22MSC_Tests.cfg: tweak commentsNeels Hofmeyr1-6/+6
Change-Id: If5f9cff03f078987c5b9051f8d63c239bf92ddb7
2020-06-21collect core dumps: '--ulimit core=-1' and WORKDIR=/data everywhereNeels Hofmeyr1-0/+3
Change-Id: Ief73b53ed9da6f5af82975bc36d851277d5d3185
2020-06-02ttcn3-msc-test: fix osmo-msc.cfg: make it work with latestVadim Yanitskiy1-1/+1
Unfortunately, we have to revert a part of change [1], because it broke ttcn3-msc-test-latest. The reason is that the latest release of osmo-msc does not support 'timer vlr T3212 30'. Change-Id: Iaeb6f1ffee9286394654bc3cf9d985ace7829110
2020-06-01osmo-{bsc,msc}.cfg: eliminate 'periodic location update 30'Vadim Yanitskiy1-1/+1
This parameter has been deprecated in both osmo-msc and osmo-bsc. Change-Id: I6d33c6d9c43078ee9961d3b076386188ec45be0f
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
2019-11-20Update ttcn3-*/jenkins.sh to log stdout+stderr of process to log filePau Espin Pedrol3-5/+5
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 Pedrol2-0/+2
gsmtap log won't be sending any message unless it is allowed by "logging filter all 1". Change-Id: Ibf8062c0d962f2572a07623e6f06936df0d42c67
2019-08-19ttcn3-bsc/msc: Drop fixups for latest releases not supporting osmuxPau Espin Pedrol1-4/+0
Last releases of osmo-bsc and osmo-bsc already support Osmux, so we can drop those lines as indicated. Change-Id: Id6a18f2d691f6e9234a5a0cf91ed5c840a6394de
2019-07-10ttcn3-*: enable GSMTAP loggingOliver Smith2-0/+6
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-03ttcn3-*: Enable extended-timestamp in VTY cfgPau Espin Pedrol2-0/+2
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-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-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-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-14cosmetic: remove excess space at line endPhilipp Maier1-1/+1
Change-Id: I36a1b9f87f1671844e78a84121e84272e8f1d373
2019-01-28ttcn3-*-test: don't hardcode /usr/local/bin/Oliver Smith1-1/+1
Remove hardcoded /usr/local/bin/ paths from jenkins.sh. This caused the *-latest tests to fail, as they have the Osmocom binaries in /usr/bin instead of /usr/local/bin. Related: OS#3767 Change-Id: I9d1427e66028ffd15fed211b2dab5adc37718666
2018-12-12MSC: use config file for mncc pathMax2-1/+2
Use config file parameter instead of command line option for MNCC socket path. Change-Id: I689cfb3bad09b76859ef7e42c1312c636eebe637
2018-10-26jenkins.sh: IMAGE_SUFFIX, docker_images_require()Oliver Smith1-2/+9
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 Welte2-60/+60
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-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-04-18bsc + msc: Add missing BSSAP_Configuration.transport fieldHarald Welte1-0/+2
After merging Change-Id: Ie844c4de62e0ef5d5c4c366185968211a7f6d676 in osmo-ttcn3-hacks, the module parameters for BSSAP configuration require one extra argument. Change-Id: I2a0011bc6f7bdf013005d1ea36da591673344eed Related: OS#2544
2018-04-17ttcn3-*-test: Remove cherry-pick of CCM related HACKHarald Welte1-1/+0
This is no longer needed as the fix for https://osmocom.org/issues/2718 has been merged to master of osmo-ttcn3-hacks Change-Id: Ia0c1c134405fdbce1c65059d705827f1a643e774 Related: OS#2718
2018-04-14ttcn3-msc-test: Add SMPP config bitsHarald Welte1-0/+6
Change-Id: I595a1ca2d47667e654f8a0a69bfe98c91ac58d39
2018-03-29MSC_Tests: Fix routing key in ttcn3-msc-testPhilipp Maier1-1/+1
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 keys. - Keep the routing key of virt-bsc1-0 and assign routing key 1 to virt-bsc1-0 Change-Id: I1380ba389dc777cdac84677588b85759cad4bc14
2018-03-29msc: Fix osmo-stp.cfgHarald Welte1-2/+2
In Change-Id: Ie7780750f7032453951f6849ecee6ab7cc34e8c2 we not only introduced a MSC_Tests.default with syntax errors, but also a osmo-stp.cfg with syntax errors :(( Change-Id: If7a7ff3d7ddb255654d14fe17033390214fe5341
2018-03-28ttcn3-msc-test: update configurationPhilipp Maier2-7/+28
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 Change-Id: Ie7780750f7032453951f6849ecee6ab7cc34e8c2 Depends: osmo-ttcn3-hacks I52a4c8118828c1605cf672889982f987568ad17d Related: OS#1609
2018-03-18ttcn3-msc-test: Disable MM INFOHarald Welte1-1/+1
In the past, MM INFO transmission was broken, so the tests were written without expecting it. Now, the bug in osmo-msc has been fixed. 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
2018-03-18ttcn3-msc-test: fix MNC/MCC to match MSC_Tests.ttcnHarald Welte1-2/+2
We recently introduced verification of the MCC/MNC, and the osmo-msc.cfg MCC/MNC settings mis-matched those of MSC_Tests.ttcn resulting in lots of test failures.
2018-03-18ttcn*test: use log_merge.sh to generate per-testcase merged logsHarald Welte1-1/+1
2018-03-13Add *.control to the [EXECUTE] statement of all ttcn3 test suitesHarald Welte1-0/+1
In osmo-ttcn3-hacks, we have removed the *.control from the *.default files, so let's add it here in the config files. You can now change the tests to be executed by simply editing the config here.
2018-02-19jenkins.sh: Fix trailing whitespacePau Espin Pedrol1-2/+2
2018-02-19*-test: jenkins.sh: Print junit output at the endPau Espin Pedrol1-0/+1
2018-02-18ttcn3-msc-test: remove correct unix domain socket dirHarald Welte1-1/+1
2018-02-18ttcn3-msc-test: remove unix domain socket dir from both containersHarald Welte1-1/+1
generated by cgit v1.2.3 (git 2.25.1) at 2024-09-25 03:01:16 +0000