Actions
Bug #4903
closedTons of TTCN3 test failures after osmo-gbproxy "rewrite" patch merge
Start date:
12/12/2020
Due date:
% Done:
100%
Spec Reference:
Description
See https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-gbproxy-test-fr/ and https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-gbproxy-test/
I've been trying to debug this for more than one day now, mostly being delayed by:- existing tcpdump not being able to capture HDLC traffic properly
- pcap file format insufficient for captures of interfaces with multiple link types
- switching to dumpcap revealed tons of problems
- dumpcap not present in images
- dumpcap unable to write to /data in the containers for no known reason
This is all finally resolved now and we get proper .pcapng.gz files as artefacts of the jenkins jobs.
- The test fail with "Timeout waiting for unblock of all BVCs", new component reason: "Timeout waiting for unblock of all BVCs"
- a review of the pcap file confirms this: We see SIG + PTP resets on the RAN side, but only SIG BVC RESET on the SGSN side
- I cannot reproduce those failures when executing the tests locally on my laptop, even with HDLC/dahdi
- When executing single test cases using the exact same (not rebuilt) docker containres on the very same build slave, the tests pass
- when executing the same test case 7 times in a row by those exact same containerse, they also all pass
So all in all, this hints to something related to left-over state in gbproxy between test cases leading to failure by following test cases.
This is plausible as there are now additional objects like the gbproxy_cell and the per-NSE gbproxy_bvc which we may want to clean-up between test runs.
Files
Related issues
Actions