Actions
Bug #4707
closedTC_chan_act_ack_est_ind_noreply fails since build 1076 (two nights ago)
Start date:
08/13/2020
Due date:
% Done:
100%
Spec Reference:
Description
The error message is
Dynamic test case error: Assigning invalid numeric value 127 to a variable of enumerated type @GSM_RR_Types.RR_Cause.
I suspect this relates to
commit 95a5edc308ffce681c1b7414dbdc0af0870247db
Author: Neels Hofmeyr <neels@hofmeyr.de>
Date: Sat Jul 11 02:57:04 2020 +0200
bsc: test RR Channel Release cause codes from Clear Command cause codes
Invoke Clear Command with various Cause codes and verify that the RR Channel
Release reflects them.
Depends: I734cc55c501d61bbdadee81a223b26f9df57f959 (osmo-bsc)
Change-Id: Ie6c99f28b610a67f2d59ec00b3541940e882251b
Updated by laforge over 3 years ago
this seems to be int2enum(oct2int(l3.msgs.rrm.channelRelease.rRCause.valuePart), got_cause);
so basically we receive some RR cause value that is not listed in our enum.
Updated by neels over 3 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
This is a genuine error of OsmoBSC sending an invalid cause code (RSL instead of RR) upon subscriber connection timeout.
This is fixed in https://gerrit.osmocom.org/c/osmo-bsc/+/19627 which was merged four days ago.
The test passes since build 1081 (5 builds ago)
Actions
