Attention is currently required from: laforge. fixeria has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/29216 )
Change subject: bts: update expected-results.xml ......................................................................
Patch Set 1:
(4 comments)
File bts/expected-results.xml:
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/29216/comment/3308f27d_6a71c... PS1, Line 22: Rx unexpected Downlink DCCH Known bug (no ticket though), needs to be fixed in the SUT.
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/29216/comment/51d6dc19_452ce... PS1, Line 57:
do we really expect this test case to fail?
This one is a bit special: the SUT is behaving correctly, but the testcase has wrong expectations. From what I remember, it started to fail since I implemented interference reporting for PDCH timeslots. Fixing the testsuite is not trivial, so back then I left this for later.
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/29216/comment/cc002c81_1db00... PS1, Line 84:
likewise here? is this not a real bug or possibly even a regression? I'm very careful with patches […]
This one is a real bug (tracked in https://osmocom.org/issues/5242). I introduced TC_ipa_crcx_ack_addr to demonstrate it, and it's expected to fail until it's fixed.
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/29216/comment/ae2f4266_c266c... PS1, Line 134: NSVCI { 1234, 0 } does not match { 1234, 5678 } This is also a known bug, but I don't think we have a ticket for it.