Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

statesystem: Do not reduce time range condition for root nodes #157

Merged
merged 1 commit into from
Sep 30, 2024

Conversation

PatrickTasse
Copy link
Contributor

In HistoryBackEndIterator, do not reduce the time range condition for queuing children nodes when the current node is the root node, as its time range is not finalized during construction.

Fixes #156

[Fixed] Do not reduce time range condition for root nodes

In HistoryBackEndIterator, do not reduce the time range condition for
queuing children nodes when the current node is the root node, as its
time range is not finalized during construction.

Fixes eclipse-tracecompass#156

[Fixed] Do not reduce time range condition for root nodes

Signed-off-by: Patrick Tasse <[email protected]>
Copy link
Contributor

@arfio arfio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the node checked is the parent node, then it should not restrict the query as it will always match the last event timestamp. In the case of CTF, I noticed that the end time of the trace does not match the last event timestamp, that is due to the fact that the end timestamp of the trace is set according to packet end times which are usually "packet flushing timestamp".

In any case, this change looks good to me ! Thank you.

@PatrickTasse PatrickTasse merged commit a19e13c into eclipse-tracecompass:master Sep 30, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

HistoryTreeBackendIterator skips nodes during construction
2 participants