segmentstore: fix incorrect iteration order in segment history
authorLoïc Prieur-Drevon <loic.prieurdrevon@gmail.com>
Thu, 27 Apr 2017 16:12:01 +0000 (12:12 -0400)
committerGenevieve Bastien <gbastien+lttng@versatic.net>
Thu, 18 May 2017 19:43:17 +0000 (15:43 -0400)
commitd66a5f05a9ec63173f62a4f03ca75a2550327f29
treea0541a6ddcc3db90ee886a31377dcc905ffd7851
parentbaeb1f54fe876f9afa806ca1134e0827740e41c2
segmentstore: fix incorrect iteration order in segment history

The initial values for minEnd and maxStart times would lead to
incorrect orders during tree build.
Also, the bounds for the node are now serialized.
Add a test to ensure the order is right.

Change-Id: I0c0811f725fbdb3c06e45685f511fac060876b6d
Signed-off-by: Loïc Prieur-Drevon <loic.prieurdrevon@gmail.com>
Reviewed-on: https://git.eclipse.org/r/95945
Tested-by: Genevieve Bastien <gbastien+lttng@versatic.net>
Reviewed-by: Hudson CI
Reviewed-by: Matthew Khouzam <matthew.khouzam@ericsson.com>
Reviewed-by: Jean-Christian Kouame <jean-christian.kouame@ericsson.com>
Reviewed-by: Genevieve Bastien <gbastien+lttng@versatic.net>
analysis/org.eclipse.tracecompass.analysis.timing.ui.swtbot.tests/src/org/eclipse/tracecompass/analysis/timing/ui/swtbot/tests/table/SegmentTableTest.java
statesystem/org.eclipse.tracecompass.segmentstore.core.tests/perf/org/eclipse/tracecompass/segmentstore/core/tests/perf/SegmentStoreBenchmark.java
statesystem/org.eclipse.tracecompass.segmentstore.core.tests/src/org/eclipse/tracecompass/segmentstore/core/tests/htStore/SegmentTreeCoreNodeTest.java
statesystem/org.eclipse.tracecompass.segmentstore.core.tests/src/org/eclipse/tracecompass/segmentstore/core/tests/htStore/SegmentTreeNodeTest.java
statesystem/org.eclipse.tracecompass.segmentstore.core/src/org/eclipse/tracecompass/internal/segmentstore/core/segmentHistoryTree/SegmentTreeNode.java
This page took 0.024834 seconds and 5 git commands to generate.