Actions
Bug #5273
closedttcn3-bts-test-latest: TC_sms_cb_cmd_sdcch8_{1,2}block failing since build 1428 (Oct 4)
Start date:
10/20/2021
Due date:
% Done:
100%
Spec Reference:
Description
BTS_Tests_SMSCB.TC_sms_cb_cmd_sdcch8_1block (from Titan):
Received unexpected CBCH block: { block_type := { spare := '0'B, lpd := '01'B, last_block := false, seq_nr := 0 }, payload := '001000320F1141660C344DD3CBA09A0C000000000000'O } BTS_Tests_SMSCB.ttcn:1104 BTS_Tests_SMSCB control part BTS_Tests_SMSCB.ttcn:545 TC_sms_cb_cmd_sdcch8_1block testcase
BTS_Tests_SMSCB.TC_sms_cb_cmd_sdcch8_2block (from Titan):
Received unexpected CBCH block: { block_type := { spare := '0'B, lpd := '01'B, last_block := false, seq_nr := 1 }, payload := '000102030405060708090A0B0C0D0E0F101213141516'O } BTS_Tests_SMSCB.ttcn:1105 BTS_Tests_SMSCB control part BTS_Tests_SMSCB.ttcn:563 TC_sms_cb_cmd_sdcch8_2block testcase
Note that SDCCH/4+CBCH is not affected, only the SDCCH/8 variants fail.
Updated by pespin over 2 years ago
- Status changed from New to In Progress
- Assignee changed from fixeria to pespin
Test fails only if its previous test is run before:
BTS_Tests_SMSCB.TC_cbc_sdcch4_load_overload BTS_Tests_SMSCB.TC_sms_cb_cmd_sdcch8_1block
Running the test alone everything looks good. It's probably related to some state not properly reset or the test expecting the bts to restart. Looking into it.
Updated by pespin over 2 years ago
- Status changed from In Progress to Feedback
- % Done changed from 0 to 90
Fixed by:
https://gerrit.osmocom.org/c/osmo-bts/+/25841 Reset CBCH state after BTS shutdown
Updated by pespin over 2 years ago
- Status changed from Feedback to Resolved
- % Done changed from 90 to 100
Merged, closing.
Actions