Bug 497440 - XML: Multiple start times of scenarios and states
Summary: XML: Multiple start times of scenarios and states
Status: NEW
Alias: None
Product: Tracecompass
Classification: Tools
Component: TMF (show other bugs)
Version: 2.0.0   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-07-06 22:42 EDT by Genevieve Bastien CLA
Modified: 2016-07-06 22:42 EDT (History)
0 users

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-07-06 22:42:03 EDT
In the scenario history builder, there is a startTime attribute for the scenario and the states. The timestamp of the start is saved there, but when we get the scenario or state start time, it is not this value that is gotten, but the start time of the startTime interval.

This is problematic because in some cases, we may wish to overwrite the startTime of the scenario given the fields of an event. In order to do so, it has to be the value that is taken, not the beginning of the interval.

Use case for this:

I have a web request log where each line represents one request and one of the field is the time taken by the request (in millisecond). I want to generate a segment for that request, but I have only 1 event to do so. By overwriting the startTime of the scenario, when the segment is generated, it should have to correct duration instead of 0.

The other way to solve this use case would be to provide a segmentLength element to the segment instead of assuming scenario start.