aboutsummaryrefslogtreecommitdiffstats
path: root/ttcn3-sip-test
AgeCommit message (Collapse)AuthorFilesLines
2020-01-05ttcn3-sip: Drop unneeded SIP_Tests.cfg modifications for latestPau Espin Pedrol1-4/+0
Latest osmo-sip-connector release 1.4.0 already behaves the same as master. Change-Id: I3c8ef08c7a60e0c83c43ea79e882dfb2d2328fa6
2019-11-28for sip-latest tests, use MNCC version 5Neels Hofmeyr2-0/+5
osmo-sip-connector master and the ttcn3 tests have moved to protocol version 6. While the extension is gracefully handled by the ttcn templates to make do with both protocol versions, the actual protocol version number sent to osmo-sip-connector breaks the tests if it doesn't match. So that master can still run v6 yet also pass 'latest', configure v5 when the version is not 'master'. When 'latest' also moves to v6, we of course can revert this again. Related: Iaca9ed6611fc5ca8ca749bbbefc31f54bea5e925 (osmo-sip-connector) Related: I39d55432776926a385e1b85b21bcdea8180a8946 (osmo-ttcn3-hacks) Change-Id: I2174e90bdea32f06cd3e8298696b93027e7906bc
2019-11-20Update ttcn3-*/jenkins.sh to log stdout+stderr of process to log filePau Espin Pedrol2-4/+4
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-03ttcn3-*: Enable extended-timestamp in VTY cfgPau Espin Pedrol1-0/+1
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-01-28ttcn3-sip-test/jenkins.sh: remove invalid -M argOliver Smith1-1/+1
osmo-sip-connector does not have a -M argument, it was probably confused with osmo-msc's -M, --mncc-sock-path argument. osmo-sip-connector printed out the following when started with -M, but otherwise functioned normally. Because it was started with Docker in background, the message did not get written to the build log. osmo-sip-connector: invalid option -- 'M' Change-Id: Iee983a8aafe8cade67b76927721fc26e5af966d7
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-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-28/+28
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-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-03-27add ttcn3-sip-test containerHarald Welte6-0/+144
Change-Id: Ibfe2a2b47c266788d51e98d64bca7017caf19e29
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-28 02:09:36 +0000