Approach to system testing for Osmocom stack

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Max msuraev at sysmocom.de
Wed Jan 10 14:13:32 UTC 2018


On 10.01.2018 12:55, Harald Welte wrote:
> The question is how many of those log messages do we need/want. In
> order to avoid the risk of 'mobile' blocking on writing to
> stdout/stderr, I think it would be best not to pipe that into other
> processes but write to files (could even be tmpfs!) and process the
> files after the run?

Another option would be to change "log gsmtap" to not duplicate it to stdout/stderr
and use it from mobile.

>
> My attached test program (not using python 'subprocess' as I couldn't find
> a way to make it do non-blocking wait for the child to terminate) runs
> perfectly fine here

Alternative approach would be using asyncio module - one example can be found in
osmo-python-tests/tests/test_py3.py

Just a suggestion though - have not tried either with thousands of processes.

-- 
Max Suraev <msuraev at sysmocom.de> http://www.sysmocom.de/
======================================================================= 
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93 
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B 
* Geschaeftsfuehrer / Managing Director: Harald Welte 







More information about the OpenBSC mailing list