Opened 12 years ago

Closed 10 years ago

#38 closed defect (fixed)

T3Q seems to hang with positioning test suite

Reported by: phdmakk Owned by: phdmakk
Priority: major Milestone: v1.0.x Series
Component: T3Q Version: 1.0
Keywords: Cc:

Description

  • Investigate report from V.Bardaux:
    • We have an issue with T3Q when analysing our positioning test suite.We have introduced new test cases but T3Q is hanging when parsing the file POS_T3Qissue\Positioning\ EUTRA_Positioning_Testcases.ttcn. We‘ve been waiting for more than 2 hours but there was no response at all.
  • Report back findings

Change History (3)

comment:1 Changed 12 years ago by phdmakk

The problem appears to be:

    SRB.send(cas_SRB_NasPdu_REQ(eutra_Cell1,
                                tsc_SRB2,
                                cs_TimingInfo_Now,
                                cs_NAS_Request(tsc_SHT_IntegrityProtected_Ciphered,
                                               cs_DL_GENERIC_NAS_TRANSPORT(tsc_LCS_MessageContainer,
                                                                           cs_GenericMsgContainer(f_EncodeRegister (cs_RegisterMT (cs_TI_MT,
                                                                                                                                   cs_FacilityIE_tlv (f_EncodeComponents (cs_Components (cs_InvokeComponent (cs_InvokeLocNotification (tsc_InvokeId,
                                                                                                                                                                                                                                       notifyLocationAllowed,
                                                                                                                                                                                                                                       f_Get_LcsClientAddress (px_LcsClientAddressTOA,
                                                                                                                                                                                                                                                               px_LcsClientAddressNPI,
                                                                                                                                                                                                                                                               px_LcsClientAddressDigits),
                                                                                                                                                                                                                                       f_CharPacking_IA5toGsm7Bit (px_LcsClientName, USSD_Packing))))))))),
                                                                           omit))));

and similar, TRex still has some issues with ambiguities in the TTCN-3 grammar which manifest themselves in particularly long nested parameter lists.

To be fixed...

comment:2 Changed 12 years ago by phdmakk

  • Status changed from new to accepted

comment:3 Changed 10 years ago by phdmakk

  • Resolution set to fixed
  • Status changed from accepted to closed

While these issues persist with current implementation, future major update is expected to reduce their impact. Meanwhile, users have been advised to consider restructuring and simplifying the parameter lists, which beside processing time improvements would also bring along improved readability and understandability of the code (which at times included 18+ nested parameterised items). The users reported back significant improvements in both processing times and understandability. Thus, this issue can be considered resolved for the time being.

Note: See TracTickets for help on using tickets.