Bug #2890
OsmoPCU TTCN-3 test suite not executed by jenkins
100%
Description
We do have a very limited/initial testsuite for OsmoPCU in the 'gprs_gb' subdirectory. It uses a virt_phy based approach and L1CTL emulation to simulate the radio/MS side of things. It uses a custom TTCN-3 implementation for NS/BSSGP/LLC on the Gb side.
Related issues
History
#1 Updated by laforge almost 2 years ago
- Priority changed from Normal to High
#2 Updated by laforge over 1 year ago
- Tags set to TTCN3
#3 Updated by laforge over 1 year ago
#5 Updated by laforge over 1 year ago
- Assignee changed from laforge to msuraev
#6 Updated by msuraev over 1 year ago
- Status changed from New to In Progress
This will require changes to docker-playground, not sure about osmo-ci - will have to check how jenkins jobs for other ttcn3 tests are created.
#7 Updated by msuraev about 1 year ago
- Related to Bug #1742: Regression in egprs patch series added
#8 Updated by msuraev about 1 year ago
- Status changed from In Progress to Stalled
Depends on gerrit 11370 and 11600.
#9 Updated by msuraev about 1 year ago
- Related to Bug #3268: execute TTCN3 test suites against "latest" feeds added
#10 Updated by msuraev about 1 year ago
Seems like the tests were migrated to pcu/ directory in a meantime.
#11 Updated by msuraev about 1 year ago
The trivial patch to enable this is available in https://gerrit.osmocom.org/#/c/osmo-ci/+/11603/
However this requires making proper infrastructure at docker-playground first.
Would it make sense to assign this to stsp - he was working on this recently and got at least some tests working locally?
#12 Updated by msuraev about 1 year ago
- Related to Bug #2388: OsmoPCU sends BVC-RESET over NS-VC which is still in state BLOCKED added
#13 Updated by stsp about 1 year ago
One problem is that PCU tests don't pass reliably unless components are started in a particular sequence.
This patch addresses one such known issue: https://gerrit.osmocom.org/c/libosmocore/+/11833
