Jaroslava Fiedlerova
3491a044ff
CI: Refactor log collection, collect also (COTS) UE logs Refactor log handling in CI: collect according to currently used XML files. This makes it homogeneous in the pipelines, and avoids accidental overwriting (as happens in phytest-timing), as well as harmonizing the log placement (e.g., no YAML lookup in Ping/Iperf). Allow to trace and archive UE logs (e.g., Quectel via QLog, Amarisoft UE logs). By default, no logs will be collected as of this MR, as many files are big. Various cleanup in Jenkinsfiles, some bugfixes, add unit tests.
In this directory and subdirectories are various CI code test cases and helper scripts.
Unit test
This repository contains unit tests. To run them, switch to the parent
directory, i.e., ci-scripts/, and run
python3 -m unittest tests/*.py
To run individual unit tests, start them like so:
python tests/build.py -v
python tests/cmd.py -v
python tests/corenetwork.py -v
python tests/deployment.py -v
python tests/iperf-analysis.py -v
python tests/ping-iperf.py -v
The logs will indicate if all tests passed. tests/deployment.py requires
these images to be present:
oai-ci/oai-nr-ue:develop-12345678oai-ci/oai-gnb:develop-12345678
It will try to download oaisoftwarealliance/oai-{gnb,nr-ue}:develop
automatically and retag the images.
test-runner test
This is not a true test, because the results need to be manually inspected. To run this "test", run
./run.sh
inside the test-runner/ directory (important!).