BTS_Tests.TC_pcu_data_req_imm_ass_pch fails since build 404 (17 days ago)
#2 Updated by msuraev about 1 month ago
- Status changed from New to In Progress
Contrary to my initial expectation, it's unrelated to rach11 patch.
Looking at osmo-bts.log:
last known-good build: pcu_sock.c:480 Data request received: sapi=AGCH arfcn=0 block=0 data=00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13 14 15 16 failing build: pcu_sock.c:480 Data request received: sapi=AGCH arfcn=0 block=0 data=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
It's unclear yet what's causing this 'empty' message or even if it's related to the issue at all.
last known-good build: DL1C <0006> l1sap.c:623 activate confirm chan_nr=UNKNOWN on TS7 trx=0 failing build: DL1C <0006> l1sap.c:623 activate confirm chan_nr=PDCH on TS7 trx=0
is caused by https://gerrit.osmocom.org/c/libosmocore/+/12942 and unlikely to be the cause as it's purely cosmetic.
Most likely cause is one of the patches merged to osmo-ttcn3-hacks around Feb. 19 because the issue appeared at the same time for both ttcn3-bts-test-latest and ttcn3-bts-test.
Note to self - handy commands:
Remove first column with timestamp: cut -d' ' -f2- osmo-bts.log > osmo-bts.log.base Cleanup logs from random jitter noise: grep -v 'TRX Clock Ind: elapsed_us' osmo-bts.log.base | grep -v 'Clock indication: fn' | grep -v 'FN timer expire_count' | grep -v 'GSM clock jitter' | grep -v 'FN slower than TRX' > osmo-bts.no-jitter.base