| commit | 664e383021748324c6066dd7cc27cdb3e306b796 | [log] [tgz] |
|---|---|---|
| author | Pau Espin Pedrol <pespin@sysmocom.de> | Wed Jun 10 19:30:33 2020 +0200 |
| committer | Pau Espin Pedrol <pespin@sysmocom.de> | Wed Jun 10 19:50:12 2020 +0200 |
| tree | 8aba9e3d2526062fbdfbace33131b48e4657ed3c | |
| parent | 3a81a7e4dc2951b2e60adc6b837ce92cad3549be [diff] |
EventLoop: Fix log error "Origin parent loop" during wait() Setting the log.ctx manually is not needed anymore and it's actually harmful since all palces where it was used, a log.Origin already in path was being passed, causing a origin loop. Change-Id: I0511b9f7bc59e3c7f2269ff3155d0c95db58d063
Osmo-GSM-Tester is a software to run automated tests on real hardware, initially foremost to verify that ongoing Osmocom software development continues to work with various BTS models, while being flexibly configurable and extendable to work for other technologies, setups and projects. It can nowadays also be used to run 4G networks with components from different providers.
Find Osmo-GSM-Tester issue tracker and wiki online at https://osmocom.org/projects/osmo-gsm-tester
Simple configuration setups can be found under doc/examples/ directory. A Osmocom's public Osmo-Gsm-Tester configuration setup is also maintained here under sysmocom/ as a reference for others.
Ansible scripts to set up hosts to be used as Osmo-GSM-Tester Main Units or/and Slave Units on the above mentioned setup can be found at https://git.osmocom.org/osmo-ci/tree/ansible, which actually install sample system configuration files from utils/ directory in this same repository.
A sample Docker setup is also maintained publicly at https://git.osmocom.org/docker-playground/tree/osmo-gsm-tester.
For the complete documentation, please refer to Osmo-GSM-Tester User manual, available in sources under doc/manuals/ under this same repository, and prebuilt in pdf form at http://ftp.osmocom.org/docs/latest/osmo-gsm-tester-manual.pdf