From ea48e980dd93f0f9467aeb39d69b61e154d59070 Mon Sep 17 00:00:00 2001 From: Simon Marchi Date: Fri, 22 Mar 2024 14:28:37 -0400 Subject: [PATCH] flt.utils.muxer: don't reset clock expectation when seeking beginning When seeking the beginning, there is no reason to reset the clock expectations. The clocks seen after a seek beginning should be compatible with those seen before. Signed-off-by: Simon Marchi Change-Id: I2ea587ea7b7f62ae509632836ae4364292903001 Reviewed-on: https://review.lttng.org/c/babeltrace/+/12148 Reviewed-by: Philippe Proulx Tested-by: jenkins --- src/plugins/utils/muxer/msg-iter.cpp | 4 ---- 1 file changed, 4 deletions(-) diff --git a/src/plugins/utils/muxer/msg-iter.cpp b/src/plugins/utils/muxer/msg-iter.cpp index 63b08c2d..99ffdeb2 100644 --- a/src/plugins/utils/muxer/msg-iter.cpp +++ b/src/plugins/utils/muxer/msg-iter.cpp @@ -219,10 +219,6 @@ void MsgIter::_seekBeginning() _mHeap.clear(); _mUpstreamMsgItersToReload.clear(); - /* Also reset clock class expectation */ - _mClkClsExpectation = _ClkClsExpectation::ANY; - _mExpectedClkClsUuid.reset(); - /* Make each upstream message iterator seek */ for (auto& upstreamMsgIter : _mUpstreamMsgIters) { /* This may throw! */ -- 2.34.1