DevTools: move tracing based Timeline out of experiment

DevTools: move tracing based Timeline out of experiment

Layout tests have been updated to work with the new backend and some of them have been deleted as there are already counterparts under inspector/timeline/tracing.

BUG=398785, 399531

[yurys, 2014-08-21 13:02:41]

ptal

[alph, 2014-08-21 13:13:40]

lgtm

https://codereview.chromium.org/481403002/diff/80001/LayoutTests/inspector/ti...
File LayoutTests/inspector/timeline/timeline-coalescing-expected.txt (right):

https://codereview.chromium.org/481403002/diff/80001/LayoutTests/inspector/ti...
LayoutTests/inspector/timeline/timeline-coalescing-expected.txt:26: coalesced
record's childHasWarnings(): undefined
shouldn't it be true/false?

https://codereview.chromium.org/481403002/diff/80001/Source/devtools/front_en...
File Source/devtools/front_end/timeline/TimelinePanel.js (left):

https://codereview.chromium.org/481403002/diff/80001/Source/devtools/front_en...
Source/devtools/front_end/timeline/TimelinePanel.js:60: this._model = new
WebInspector.TimelineModelImpl();
Are there two classes still used?

[yurys, 2014-08-21 14:18:42]

https://codereview.chromium.org/481403002/diff/80001/LayoutTests/inspector/ti...
File LayoutTests/inspector/timeline/timeline-coalescing-expected.txt (right):

https://codereview.chromium.org/481403002/diff/80001/LayoutTests/inspector/ti...
LayoutTests/inspector/timeline/timeline-coalescing-expected.txt:26: coalesced
record's childHasWarnings(): undefined
On 2014/08/21 13:13:39, alph wrote:
> shouldn't it be true/false?

Good catch. Since the logic we detect synchronous events has changed the test
input data needed to be updated accordingly. We used to mark Layout event as
synchronous if it had non-empty stack-trace, current implementation checks if it
the Layout event is inside some script event as stack collection may be off.

https://codereview.chromium.org/481403002/diff/80001/Source/devtools/front_en...
File Source/devtools/front_end/timeline/TimelinePanel.js (left):

https://codereview.chromium.org/481403002/diff/80001/Source/devtools/front_en...
Source/devtools/front_end/timeline/TimelinePanel.js:60: this._model = new
WebInspector.TimelineModelImpl();
On 2014/08/21 13:13:40, alph wrote:
> Are there two classes still used?

No. I'm going to remove them in one of the following CLs.

[yurys, 2014-08-21 14:18:53]

The CQ bit was checked by yurys@chromium.org

[commit-bot: I haz the power, 2014-08-21 14:20:31]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/yurys@chromium.org/481403002/100001

[yurys, 2014-08-21 14:46:24]

The CQ bit was unchecked by yurys@chromium.org

[yurys, 2014-08-21 14:51:50]

In offline discussion we decided to break this in several steps:
1. Copy new version of existing timeline tests into separate folder so that they
are executed with tracing based implementation while old tests continue to run
with the old timeline implementation.
2. Replace "Timeline on trace events" experiment with "Old Timeline" or
something so that tracing based Timeline is used by default.
3. Collect feedback in a couple of dev channel releases and if everything goes
well remove the experiment along with the old Timeline code.