The testsuite is running in bullseye for some time, so build the Osmocom
programs in bullseye as well.
Depends: docker-playground I4cd05ef2c164dfb765ee365ab38b8dfd4f955ac6
Change-Id: Ie5be8dc976fb8ff37b6712f1cba434b2114c4bf8
For some reason, on Arch Linux:
$ file /bin/sh
/bin/sh: symbolic link to bash
$ sh --version
GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu)
the '--trx' arguments are getting passed incorrectly:
$ ./fake_trx.py TRX1@127.0.0.1:5700/1
TRX2@127.0.0.1:5700/2
TRX3@127.0.0.1:5700/3
fake_trx: error: unrecognized arguments: TRX1@127.0.0.1:5700/1
TRX2@127.0.0.1:5700/2
TRX3@127.0.0.1:5700/3
Let's send each argument separately.
Change-Id: Ibf28ac013c426baba491af45e2ae46f37685a402
Rename 3G+2G.deps to all.deps and remove the parameter from
gen_makefile.py. Create new Makefile targets for the various use cases,
usually we build either 'cn-bsc' or 'usrp'. The next patch will add more
projects to all.deps.
This change brings the Makefile logic closer to how it is actually used,
one build directory that is building most Osmocom projects. New projects
can be added to all.deps on demand, but then we have it in the
repository and not just a local change that we add temporarily to the
3G+2G.deps file when we need to build a specific project.
Extend all.deps with projects needed by ttcn3.sh, so it doesn't need to
write its custom .deps file anymore.
Change-Id: I6394882f67eecda3d2c03a97d3119657f7d3873f
Merge build_osmo_program_osmodev into build_osmo_programs and change the
logic, so make only needs to run once. This saves a few seconds for each
test iteration.
Change-Id: Ie2cf7a93395f5ad04159f523d0d0f091303aaa57
On my system, when building all components in docker, some of the C tests
don't pass (but they do pass on jenkins.osmocom.org, which runs a
similar setup). Do the easy workaround and just disable C tests, the
point of ttcn3.sh is to have fast ttcn-3 test iterations anyway, running
the C tests additionally slow each iteration down. One can run the C
tests before submitting changes, e.g. by building with osmo-dev without
ttcn3.sh.
Change-Id: I946635f1ec09f23428965f3db514027f64921fe4
Remove leftovers from before refactoring in
Iecba5391dafc353058d369deb513b156534face1. No need to build these with
osmo-dev, as they are part of the osmocom-bb docker container that gets
built via ttcn3-bts-test/jenkins.sh.
Change-Id: I99ec4ff9caf34d1ddd7efde2f5ae2342a6984689
Replace the previous approach of building outside of docker and mounting
everything inside docker while running tests, with also building
everything inside docker. This prevents incompatibilities between host
system and docker (e.g. different glibc). As nice side-effect,
/usr/local is not filled up anymore.
Change-Id: Ib6db8ffd916c788c9de0b3d51c82e1d7bb3f6828
Fix for Osmocom programs using system's shared libraries, instead of the
ones mounted into /usr/local.
For example, for osmo-bsc the libosmocore installed in the
osmo-bsc-master docker container would be used (installed via apt from
OBS nightly) instead of the version that osmo-dev built from source.
Change-Id: I0dd7fb544ca59cb1df19fc3d73cfd07f3374e123
Add the image suffix to the marker in run_docker() which indicates if
the testsuite docker container was already built (with all its
dependencies), so the script doesn't assume that everything is already
built if using without IMAGE_SUFFIX first and then switching to
IMAGE_SUFFIX=latest.
Add an usage example to README for IMAGE_SUFFIX=latest.
Change-Id: I867740831810324a7f5906a0548f0d04ecb9a0a1
Speed up tests by not running a separate docker instances first that
lists installed packages.
Depends: docker-playground Iaafb81e9ee94850ae3b6318574ad5370d74a2838
Change-Id: I3d9976d07f088e2d106d23259889a4bffe1abbcb
Make logic to install the file simpler while at it, and allow it to
create /usr/local/bin if it doesn't exist (I just had that).
Change-Id: I497b9e8909a419f5b5286fcccce9d8a1ba9d515c
Instead of trying to run everything outside of docker, just build the
docker containers and then mount /usr/local and osmo-ttcn3-hacks from
the host system into the docker containers. This way, we can just use
the same configs as the official jenkins jobs are using, while still
having a short test-cycle once the docker containers are built for the
first time. I've decided to implement this, because it was not feasible
to maintain the separate configs.
Depends: docker-playground I8d1f78aee926f8f6ec0b704e16639bc83f525816
Change-Id: Iecba5391dafc353058d369deb513b156534face1
Build testsuite, SUT and dependencies and run everything with one
command. Example usage:
$ ./ttcn3/ttcn3.sh msc
So far, it works at least with:
hlr, mgw, msc, pcu, pcu-sns, sgsn
Change-Id: I6b4bf2743adeec1a950d5f090a690182b991cf49