Actions
Bug #6403
closedregression since osmo_io migration
Start date:
03/14/2024
Due date:
% Done:
100%
Spec Reference:
Description
Ever since we merged the osmo_io patch for libosmo-sigtran, it seems that SCCP_Tests.TC_process_rx_ludt is no longer passign, see
https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-sccp-test/
This test used to be a bit unstable in the past, but I triggered it two more times today, and all three (1x automatic, 2x manual) are consistent: This test no longer passes.
Updated by laforge about 1 month ago
Timeout waiting for { sio := { ni := '00'B, prio := '00'B, si := '0011'B }, opc := 1, dpc := 23, sls := 0, data := { longudata := { messageType := 19, protClass := { class := '0000'B, messageHandling := '0000'B }, hopCounter := ?, pointer1 := ?, pointer2 := ?, pointer3 := ?, pointer4 := ?, calledPAddress := { paramLength := 4, addr := '431700CA'O }, callingPAddress := { paramLength := 4, addr := '430100CA'O }, longData := { paramLength := ?, data := '7CFCD998E1CF76329F1AE289A79D7F27E2BB372BC048D3F46E5C64C004E2E625760A0B40C47B0E00CE3E78DDC6D57010C5450BD4734623870A5FB6A67D114FFCCF7F9877B9FC86832D1B1291569AD9CAF89261849389B6126378477110F12665AA8A064575A4525DB41873AD9088F52DFE87BC835784D3767BDC0C322797F673EE661E8175AE09D5463D6AABA5A1E572DCCC97631DCEF96D08797EBAC9251347765B1E6A2BB0C173BF1A911EBF4634AC413835A805D6A257038D0823A069A4944F284FF7313655931EAB92B2341577E7F1E02162E41A3D3D938744E77193F9F7695D83561533328A51D57602631C846EE757D035055BE2ADD9B97D11898CC3C85524032A339814C624E97CBECBF1C9B1C59EF0613D4A3DC61B51FCFF9668A2BD7FEF5DF420B53D78CFBAFAAFCA203259FD3ADD37CF34321CDC229D3F74768EFF669DA33725D6AB44A3B9C708967C2FF43BFBC4899D2EBED640BC2DF76A6C95215B858ED15098BE715FA3AE8DE1C84FD491F4EC89333B8D90684E126F563275773FF10C038F81DD249D396A11AE3FFC87EA17A6A01CEBC98B1BD6BA2352C78F59BC85B4B75F4F9718E68CA8CDDA7BBF7C320468BB0803A396611D54F43CC6B3C48C14AC759086AF68E8499A01D637B449CA86928B4793184A6F0457E9BD0643E93261688B92C1B7CC479D88760D6C821AB8395C3C11166AFD8298440638DA3017C04AE5F3DB368BEE9225F44C825078BC17DE69202207D204127745B92F65539016EABD63D7FF5D36DE64C1A318AD41DB4CDF8ACB2874F3B6EA040257979B99C4281BAE1BF09AA7A2794EE6961317AED7787C222E7A1179B4A0DD4B3A9A4D8E6CC0F003E31F2C9F1E445A260943811BC9AE26BA1CAC4980F5EE3106E352E1BD0C43946FC096FBA6E72DA556D461ACF023668C39CB69C5231C684FE9C1ED1D6C60FA19C4DCF6AC287248A2A9B722F5B27FB7CC4AC828F5D58C20107804C3952C2156B9242596B47F4E0CD288B175FE390DCF5862DD2518E9C69985D406E531CABFBCF908225E92439D300F6D1E78B674242706FC743D3ED28DA77DC9C9915510714844BF79B13BA07FA4DF4D33943C4F8101CC73E407C5A245B047AF102223E6341D6CD1ACEA4B1B12355D074E57232BA0A2AA0B3FCFD73F29C5558C84E9594929B09BC68EE470536B4B1F6299788B72C1CD419D09D763D0B1271C02717A539CE18F30DFEA1A8E401C46BB0A8187A3C612FF97766E6D15E6CFA8C88A9FED9CCF00330931DBD62A62BA044B2084DAFB4679EE88D46754C8DB67673E70B388ACE2D24DBCAE64F0876FED0087CDD5213D6A8AC8619555FBF4E88C7AE820B2643A443C153990B29D07F97D98E6615430BD001AB12F869503A27F09EECC340E7DAA83991A5EB796D1458EEF'O }, optionalPart := { segmentation := omit, importance := * } ifpresent, eop := { paramName := 0 } ifpresent } } }
SCCP_Tests_RAW.ttcn:535 SCCP_Tests_RAW control part
SCCP_Tests_RAW.ttcn:376 TC_process_rx_ludt testcase
Updated by laforge about 1 month ago
- Status changed from New to In Progress
- Assignee changed from jolly to laforge
- % Done changed from 0 to 30
Updated by laforge about 1 month ago
- % Done changed from 30 to 70
The problem was that we accidentially reduced the msgb allocation sizes when switching to osmo_io. Instead of the libosmo-sigtran value for M3UA (2048 bytes), we now reverted back to the osmo_io default (OSMO_IO_DEFAULT_MSGB_SIZE == 1024).
Updated by laforge about 1 month ago
- Status changed from In Progress to Resolved
- % Done changed from 70 to 100
Applied in changeset libosmo-sccp|471f859d77cf3fb0d280e05e94d69a1bda28a345.
Actions
