Attention is currently required from: osmith.
Patch set 1:Code-Review -1
View Change
1 comment:
Patchset:
Patch Set #1:
I think it would be very interesting to understand how this phenomenon happens on your system.
a 5 second round-trip time between sending a RESET from TTCN3 until receiving the ACK from the IUT (BSC) is way too long already. 10s is just ridiculous, IMHO.
So either
- TTCN3 thinks it has sent the message, but it takes a long time until it actually hits the wire,
- your network has some kind of enormous delay, or
- the RESET arrives in time, but something prevents the BSC from receiving/processing the RESET
- or any of the above in the reverse direction for the ACK
We may very well have a bug, if we have a RTT > 5s in test execution. Merging this patch might just plaster over it.
correlating logs with pcap file should hopefully give you an idea of where the majority of the time was spent/wasted.
To view, visit change 29891. To unsubscribe, or for help writing mail filters, visit settings.
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: I76fa91280472b87235cf985af68bc2a6183d5e4a
Gerrit-Change-Number: 29891
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith@sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge@osmocom.org>
Gerrit-Attention: osmith <osmith@sysmocom.de>
Gerrit-Comment-Date: Thu, 27 Oct 2022 13:12:37 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment