Project

General

Profile

Actions

Bug #5528

closed

osmo-pcap-client test failure in TC_multi_capture

Added by laforge about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
04/12/2022
Due date:
% Done:

100%

Spec Reference:

Description

The last two jenkins executions of TC_multi_capture failed:

https://jenkins.osmocom.org/jenkins/view/All%20no%20Gerrit/job/ttcn3-pcap-client-test/356/console

----- OPCAP_CLIENT_Tests.TC_multi_capture ------
Tue Apr 12 11:40:59 UTC 2022
NOTE: unable to use dumpcap due to missing capabilities or suid bit
Waiting for packet dumper to start... 0
MTC@2e6e239d24fe: External command `../ttcn3-tcpdump-start.sh OPCAP_CLIENT_Tests.TC_multi_capture' was executed successfully (exit status: 0).
MTC@2e6e239d24fe: Test case TC_multi_capture started.
MTC@2e6e239d24fe: Waiting for client-0 connection...
MTC@2e6e239d24fe: Connection from "172.18.31.20":34413
MTC@2e6e239d24fe: Warning: Re-starting timer g_Tguard, which is already active (running or expired).
MTC@2e6e239d24fe: Waiting for client-1 connection...
MTC@2e6e239d24fe: Connection from "172.18.31.20":43313
MTC@2e6e239d24fe: setverdict(pass): none -> pass
MTC@2e6e239d24fe: setverdict(pass): pass -> pass, component reason not changed
MTC@2e6e239d24fe: setverdict(pass): pass -> pass, component reason not changed
MTC@2e6e239d24fe: setverdict(pass): pass -> pass, component reason not changed
MTC@2e6e239d24fe: setverdict(pass): pass -> pass, component reason not changed
MTC@2e6e239d24fe: setverdict(pass): pass -> pass, component reason not changed
MTC@2e6e239d24fe: setverdict(pass): pass -> pass, component reason not changed
MTC@2e6e239d24fe: setverdict(pass): pass -> pass, component reason not changed
MTC@2e6e239d24fe: setverdict(pass): pass -> pass, component reason not changed
MTC@2e6e239d24fe: setverdict(pass): pass -> pass, component reason not changed
MTC@2e6e239d24fe: setverdict(pass): pass -> pass, component reason not changed
MTC@2e6e239d24fe: setverdict(pass): pass -> pass, component reason not changed
MTC@2e6e239d24fe: setverdict(pass): pass -> pass, component reason not changed
MTC@2e6e239d24fe: setverdict(pass): pass -> pass, component reason not changed
MTC@2e6e239d24fe: setverdict(fail): pass -> fail reason: "global guard timeout", new component reason: "global guard timeout" 
MTC@2e6e239d24fe: Setting final verdict of the test case.
MTC@2e6e239d24fe: Local verdict of MTC: fail reason: "global guard timeout" 
MTC@2e6e239d24fe: No PTCs were created.
MTC@2e6e239d24fe: Test case TC_multi_capture finished. Verdict: fail reason: global guard timeout
MTC@2e6e239d24fe: Starting external command `../ttcn3-tcpdump-stop.sh OPCAP_CLIENT_Tests.TC_multi_capture fail'.
Tue Apr 12 11:41:31 UTC 2022
-e ------ OPCAP_CLIENT_Tests.TC_multi_capture fail ------

I cannot reproduce this locally, even in multiple test executions.


Files

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)