Actions
Bug #4628
closedttcn3-bsc-test: TC_ctrl_msc_connection_status failing
Start date:
06/23/2020
Due date:
% Done:
0%
Spec Reference:
Description
https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bsc-test/test_results_analyzer/
The test TC_ctrl_msc_connection_status started failing a few days ago, while TC_ctrl_msc0_connection_status still works. This is probably related to the mscpool work done recently.
Updated by neels almost 4 years ago
- Status changed from New to Stalled
I also noticed this, but the failure is sporadic.
i.e. I can see it fail sometimes, and when trying to reproduce it, it often just passes.
That happens with various tests and usually I don't spend attention on those odd failures.
If this persists after the current general osmo-bsc test fallout season, we may need to make the test more robust against sporadic failure.
Updated by laforge over 3 years ago
- Status changed from Stalled to Resolved
it seems the issue is gone now. At least the last 10+ builds don't show ant issue.
Actions
