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 <simon.marchi@efficios.com>
Change-Id: I2ea587ea7b7f62ae509632836ae4364292903001
Reviewed-on: https://review.lttng.org/c/babeltrace/+/12148
Reviewed-by: Philippe Proulx <eeppeliteloop@gmail.com>
Tested-by: jenkins <jenkins@lttng.org>

diff --git a/src/plugins/utils/muxer/msg-iter.cpp b/src/plugins/utils/muxer/msg-iter.cpp
index 63b08c2dd2e7d3eb630169bb6c701906d9c727cd..99ffdeb21381042b980e5444d086a5a420056dc5 100644 (file)
--- 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! */