Miscellaneous Projects » Core testing infrastructure

When looking at the build artifacts of ttcn3-bsc-tests, the osmo-bsc log is less than 50kb, the ttcn3 logs are about 100 kb, but the bts-omldummy logs are more than 3 Mb.

When I leave the ttcn3-bsc-tests docker containers running for a while (as I often used to do),
the osmo-bts-omldummy logs can easily end up filling the entire file system.
I solved it for me by completely muting the omldummy log output in a private branch.

Anyway, it could make sense to tune down the omldummy log output a bit, because who is going to read those megabytes?
A couple mb per build isn't that critical, but still it is larger than the other logs by a factor of 100,
so one could say it is out of balance. What is interesting about the omldummy logs anyway?

pespin please consider this and change something or reason about it and reject the issue, because your patch started producing those logs:

commit ad4fa373a87b0c2a2468759a4aa1e9082d996661
Author:     Pau Espin Pedrol <pespin@sysmocom.de>

    bsc: Store osmo-bts-omldummy logs out of docker container

    Change-Id: I0c02c4a9311122c3fe8ca877e02043f697723281