Hi all,
it could potentially be related to [1], but after looking at [2]:
Traceback (most recent call last):
File "/tmp/osmocom-bb/src/target/trx_toolkit/fake_trx.py", line 543, in <module>
app.run()
File "/tmp/osmocom-bb/src/target/trx_toolkit/fake_trx.py", line 461, in run
self.burst_fwd.forward_msg(trx, msg)
File "/tmp/osmocom-bb/src/target/trx_toolkit/burst_fwd.py", line 70, in forward_msg
trx.handle_data_msg(src_trx, rx_msg, tx_msg)
File "/tmp/osmocom-bb/src/target/trx_toolkit/fake_trx.py", line 255, in handle_data_msg
Transceiver.handle_data_msg(self, msg)
File "/tmp/osmocom-bb/src/target/trx_toolkit/transceiver.py", line 281, in handle_data_msg
self.data_if.send_msg(msg, legacy = True)
File "/tmp/osmocom-bb/src/target/trx_toolkit/data_if.py", line 109, in send_msg
msg.validate()
File "/tmp/osmocom-bb/src/target/trx_toolkit/data_msg.py", line 597, in validate
raise ValueError("RSSI %d is out of range" % self.rssi)
ValueError: RSSI -122 is out of range
I would not think so. Moreover, I've tested [1] locally before submitting.
ValueError: RSSI -122 is out of range
So fake_trx.py crashes due to an out of range RSSI value. RSSI has nothing to do with my recent refactoring changes, I am pretty sure it would have crashed before. I'll prepare a patch to handle such errors properly. Although, it would still be good to investigate where this RSSI value is coming from.
[1] https://git.osmocom.org/osmocom-bb/commit/?id=d4ed09df57b3461470af501e9687ddd80eb78838
[2] https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/966/artifact/logs/fake_trx/