Project

General

Profile

Bug #3703

sporadic failures of TC_tch_sign_l2_fill_frame test case

Added by stsp 20 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
11/22/2018
Due date:
% Done:

0%

Spec Reference:

Description

We are seeing sporadic failures of TTCN3 BTS test case TC_tch_sign_l2_fill_frame on Jenkins.

Two different instances of such failures are shown below.

The first one looks as if a process on the other side of the L1 interface disappeared:

07:24:28.736125 509 L1CTL_PortType.ttcn:171 Sent on L1CTL to system @L1CTL_Types.L1ctlUlMessage : { header := { msg_type := L1CTL_RESET_REQ (13), flags := { padding := '0000000'B, f_done := false }, padding := '0000'O }, ul_info := omit, ul_info_tbf := omit, ul_info_abs := omit, payload := { reset_req := { reset_type := L1CTL_RES_T_FULL (1), padding := '000000'O } } }
07:24:28.736177 509 L1CTL_PortType.ttcn:208 enc_L1ctlUlMessageLV(): Encoding @L1CTL_Types.L1ctlUlMessageLV: { len := <unbound>, msg := { header := { msg_type := L1CTL_RESET_REQ (13), flags := { padding := '0000000'B, f_done := false }, padding := '0000'O }, ul_info := omit, ul_info_tbf := omit, ul_info_abs := omit, payload := { reset_req := { reset_type := L1CTL_RES_T_FULL (1), padding := '000000'O } } } }
07:24:28.736293 509 L1CTL_PortType.ttcn:208 enc_L1ctlUlMessageLV(): Stream after encoding: '00080D00000001000000'O
07:24:28.736355 509 L1CTL_PortType.ttcn:171 Outgoing message was mapped to @UD_Types.UD_send_data : { data := '00080D00000001000000'O, id := 0 }
07:24:28.736389 509 L1CTL_PortType.ttcn:171 Dynamic test case error: Write error (Broken pipe)
07:24:28.736416 509 L1CTL_PortType.ttcn:171 setverdict(error): none -> error
07:24:28.736435 509 L1CTL_PortType.ttcn:171 Performing error recovery.

https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/309/artifact/logs/bts-tester/BTS_Tests.TC_tch_sign_l2_fill_frame.merged/*view*/

Note that this build run also lacks a pcap file for this test:
https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/309/artifact/logs/bts-tester/

The second one could have the same underlying reason, but the problem occurred while waiting to receive a message rather than sending:

07:19:46.788830 518 L1CTL_PortType.ttcn:176 Timeout T: 2 s
07:19:46.788936 518 L1CTL_PortType.ttcn:177 setverdict(fail): none -> fail reason: "Timeout waiting for RESET.conf", new component reason: "Timeout waiting for RESET.conf" 
07:19:46.788969 518 L1CTL_PortType.ttcn:178 Stopping MTC. The current test case will be terminated.
07:19:46.789001 518 L1CTL_PortType.ttcn:178 Stopping test component execution.

https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/303/artifact/logs/bts-tester/BTS_Tests.TC_tch_sign_l2_fill_frame.merged/*view*/

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)