Bug 506464 - Cancelling an analysis others depend on may have side-effects
Summary: Cancelling an analysis others depend on may have side-effects
Status: NEW
Alias: None
Product: Tracecompass
Classification: Tools
Component: TMF (show other bugs)
Version: 2.0.1   Edit
Hardware: PC Linux
: P3 normal
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Project Inbox CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-24 15:10 EDT by Genevieve Bastien CLA
Modified: 2017-02-05 13:06 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Genevieve Bastien CLA 2016-10-24 15:10:01 EDT
When an analysis depends on another, they are both scheduled at the same time, but if the user cancels the analysis the other depends on, the second one continue to run, but may not receive a valid answer and will throw exceptions.

One example: Run the system call analysis, it will trigger the Active Thread analysis. Cancel the Active Thread Analysis and the system call will throw a bunch of TimeRangeException, because it supposes that the TID analysis is either running, in which case it will wait for it to reach a timestamp greater than its own to ask the TID, or has already run to its full completion.

I think the expected behavior would be that if an analysis is cancelled, all analyses that depend on it should be cancelled too.
Comment 1 Matthew Khouzam CLA 2017-02-05 13:06:29 EST
I noticed you have some patches that fix this, could you add the bug ID to the patches and link the patches here if the bots forget to do their job.