Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Ief73b53ed9da6f5af82975bc36d851277d5d3185
|
|
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
|
|
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
|
|
Change-Id: I0754a7c3c9f9caa65d33bb0a404b53f826cd0a75
|
|
This way we can actually tests TPDU transmission from a simulated
remsim client through the real bankd into a simulated SIM card.
Change-Id: I584e4c5e3d120bfbd26ade545fe41e541308f26a
|
|
The default filename pattern of the JUnit log plugins of TTCN-3 is
"junit-xml-%u.xml" where %u represents the PID of the process. This
is typically a good idea as the PID doesn't wrap that quickly. However,
if you're executing a new docker container for every test suite run,
then chances are high that two subsequent runs of the test suite
container might end up with the same PID and hence the smae filename.
This results in the output file being overwritten, which is what's
responsible for many missing RemsimServer_Tests results on the
jenkins.osmocom.org test results analyzer.
Change-Id: I9b6d1b5a943eb4e058ad2bf7cf8acee7b70e68b6
Closes: OS#4205
|
|
This way we get VTY parsing failures as well as backtraces upon process
crash.
Related: OS#4212
Change-Id: I3d9f6de638dbc07391a32c6a0cbd469dc5adf2b5
|
|
Change-Id: I05090f408b04aae24c23978da831e9f844d723a3
|