Commit Graph

69 Commits (master)

Author SHA1 Message Date
Pau Espin db32c0a431 ttcn3-pcu: Run tests from PCU_Tests_RAW_NS.ttcn
NS tests have been splitted recently into their own module. Make sure we
call tests from the new module.

Depends: osmo-ttcn3-hacks.git If680d1bd7dbfe98829f330c33705e0f13bedf3c7
Change-Id: I3e2ec21c56fbfad5d1af051dcc0d0a9c88d2070a
2019-12-30 14:17:15 +01:00
Pau Espin 436ac6758d ttcn3-cpu: Support VTY prompt used in older versions of osmo-pcu
Change-Id: I8cec3da889623915ca46b5eb1b51bc81195accf9
2019-12-04 17:17:09 +01:00
Pau Espin f10f0e4df8 ttcn3-pcu: Set correct VTY listen addr in PCU_Tests.cfg
Now that osmo-ttcn3-hacks.git I221675721b65b3ab44179e9657da70ba4004d7de
introduced VTY support for PCU_Tests_RAW, we need to use the correct
addr here.

Change-Id: I6807dafd79e58750ffa953da30eb34671aa25808
2019-11-30 09:34:59 +00:00
Pau Espin c3f157b939 Update ttcn3-*/ to log stdout+stderr of process to log file
This way we get VTY parsing failures as well as backtraces upon process

Related: OS#4212
Change-Id: I3d9f6de638dbc07391a32c6a0cbd469dc5adf2b5
2019-11-20 17:17:45 +01:00
Daniel Willmann c66029cd99 Fix ttcn3-pcu-test-latest
Remove the gsmtap-categories that are unknown to the latest osmo-pcu

Change-Id: I4ed750aaa728272fcda09fd23cf172db0e539aa8
2019-10-15 12:55:43 +02:00
Pau Espin 65bc0ae407 ttcn-*: Fix gsmtap log not enabled
gsmtap log won't be sending any message unless it is allowed by "logging
filter all 1".

Change-Id: Ibf8062c0d962f2572a07623e6f06936df0d42c67
2019-10-04 15:50:50 +02:00
Pau Espin 72dd6c9a4a ttcn3-pcu: Enable GSMTAP
Depends on recent commit adding RACH, AGCH and PCH gsmtap categories.

Depends: osmo-pcui.git I4d62f98801af1b0a290d3dd35bd213ccf3151035
Change-Id: I24782f5403266d29aea46ef1d94a431077b194b3
2019-09-30 19:56:21 +02:00
Pau Espin ae42e2e864 ttcn3-pcu: Enable logging color in osmo-pcu.log
Change-Id: I209b03e493bb6b047a46eadd80712259f1d1474d
2019-09-30 19:55:53 +02:00
Oliver Smith c2ed5bb201 ttcn3-*: enable GSMTAP logging
Configure each osmo-* program to send GSMTAP log output to the IP of the
docker container, which runs the testsuite (and therefore runs tcpdump).

Change-Id: I99e74f6ffb5b7d566cec35995bf067df414968d8
2019-07-10 09:34:39 +02:00
Oliver Smith 88a74a5de1 ttcn3-{hlr,mgw,pcu}-test: log to file
Add missing file output which all other tests already have.

Related: OS#4067
Change-Id: Ifb4a39e6e2987f4dc04369508fe0dff0913a02ff
2019-06-24 13:52:06 +00:00
Oliver Smith 61f2be7bd4 Fix git checkout for branches and commits
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 ""
$ 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'
$ 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'.
$ 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-22 11:18:56 +02:00
Harald Welte 06ac6e455e Revert "Simplify git checkout, allow branches and commits"
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 26565bb729.

Change-Id: Ie6da0f9ea96f11407e38545a6b3cf22ef9cadc25
2019-05-21 17:53:11 +02:00
Oliver Smith 26565bb729 Simplify git checkout, allow branches and commits
Replace the following statements:

a) "git checkout -f -B $BRANCH origin/$BRANCH"
b) "git checkout -f -B $BRANCH $BRANCH"


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-07 10:24:52 +02:00
Harald Welte 7c53c9e60d Switch all osmo-*-master and ttcn3-*-test from jessie to stretch
Jessie will be EOL in June 2019, let's make the switch to stretch
before that.

Change-Id: I37a534d07081f3d321869c86d49d03171c8da0c6
2019-03-30 09:56:36 +00:00
Harald Welte cffe1022b5 print branch name and git commit hash during docker container build
This is quite useful when looking at jenkins logs to know which exact
version was built at the time.

Change-Id: Id52c382b454e2beecf46820752aeff15b2c1a0ae
2019-03-29 16:40:40 +00:00
Harald Welte c05330e8b4 PCU: Differentiate between tests with classic and SNS Gb dialects
OsmoPCU needs to have the gb-dialect parameter configured right from
startup.  This means we'll split the ttcn3-pcu-test into two suites,
similarly to how we deal with AoIP / SCCPlite in the ttcn3-bsc-test.

Change-Id: I6e844f9ac4b87e801661fb1a1bdd25a15148f474
2019-03-14 21:38:44 +01:00
Harald Welte 618c7abc72 PCU: Add SNS tests to [EXECUTE] section of config file
Change-Id: I82949f75c65877ca8baf1018a335c03731c0a4e9
2019-02-28 11:27:04 +01:00
Harald Welte 6359c3fe6c ttcn3-pcu-test: Use master branch, not laforge/gb-sns
All required code is now in master, let's use master.

Change-Id: I106184f3f75802ac9a3109408c8eee6597b70caa
2019-02-21 12:02:47 +01:00
Harald Welte eedbb56552 PCU: Add osmo-pcu-* + ttcn3-pcu-test containers
This will enable us to run the PCU testsuite automatically by
jenkins, just like for other Osmocom projects.

Change-Id: Ia8e2ed2e7d03b8afdc7b1e068f94b0544a8112c7
Related: OS#2890
2019-02-20 21:45:07 +00:00