third_party/WebKit/LayoutTests/inspector/tracing/timeline-script-id-expected.txt - Issue 1624783002: DevTools: Switch to using fast stack iterator to collect stacks during timeline recording.

Unified Diff: third_party/WebKit/LayoutTests/inspector/tracing/timeline-script-id-expected.txt

Issue 1624783002: DevTools: Switch to using fast stack iterator to collect stacks during timeline recording. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: 4 landing Created 4 years, 11 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

« third_party/WebKit/LayoutTests/inspector/tracing/timeline-js-callstacks-expected.txt ('K') | « third_party/WebKit/LayoutTests/inspector/tracing/timeline-receive-response-event.html ('k') | third_party/WebKit/LayoutTests/inspector/tracing/timeline-script-tag-1.html » ('j') | third_party/WebKit/LayoutTests/inspector/tracing/timeline-time-stamp-expected.txt » ('J')
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: third_party/WebKit/LayoutTests/inspector/tracing/timeline-script-id-expected.txt

diff --git a/third_party/WebKit/LayoutTests/inspector/tracing/timeline-script-id-expected.txt b/third_party/WebKit/LayoutTests/inspector/tracing/timeline-script-id-expected.txt

index cb22f7f361f91a3d5884859225f8fc07407b2b0f..045524ee7adaf4ed5c2f5146ed6a231c98b20918 100644

--- a/third_party/WebKit/LayoutTests/inspector/tracing/timeline-script-id-expected.txt

+++ b/third_party/WebKit/LayoutTests/inspector/tracing/timeline-script-id-expected.txt

@@ -3,14 +3,14 @@ Test that checks location resolving mechanics for TimerInstall TimerRemove and F

It expects two FunctionCall for InjectedScript, two TimerInstall events, two FunctionCall events and one TimerRemove event to be logged with performActions.js script name and some line number.

detailsTextContent for FunctionCall event: 'undefined'

-detailsTextContent for TimerInstall event: 'performActions.js:3'

-details.textContent for TimerInstall event: 'performActions.js:3'

-detailsTextContent for TimerInstall event: 'performActions.js:4'

-details.textContent for TimerInstall event: 'performActions.js:4'

+detailsTextContent for TimerInstall event: 'performActions.js:1'

pfeldman 2016/01/27 18:38:36 The timer is still installed on the line 3, why di

alph 2016/01/27 22:31:25 Done.

+details.textContent for TimerInstall event: 'performActions.js:1'

+detailsTextContent for TimerInstall event: 'performActions.js:1'

+details.textContent for TimerInstall event: 'performActions.js:1'

detailsTextContent for FunctionCall event: 'performActions.js:7'

details.textContent for FunctionCall event: 'performActions.js:7'

detailsTextContent for FunctionCall event: 'performActions.js:7'

details.textContent for FunctionCall event: 'performActions.js:7'

-detailsTextContent for TimerRemove event: 'performActions.js:11'

-details.textContent for TimerRemove event: 'performActions.js:11'

+detailsTextContent for TimerRemove event: 'performActions.js:7'

+details.textContent for TimerRemove event: 'performActions.js:7'