Chromium Code Reviews| Index: LayoutTests/inspector/tracing/timeline-script-id-expected.txt |
| diff --git a/LayoutTests/inspector/tracing/timeline-script-id-expected.txt b/LayoutTests/inspector/tracing/timeline-script-id-expected.txt |
| index 944b24917b108447b1385576581e7dc3d74a7911..43b8676c7ea17a3d0e7ff4a2084fe5e6e2ef4358 100644 |
| --- a/LayoutTests/inspector/tracing/timeline-script-id-expected.txt |
| +++ b/LayoutTests/inspector/tracing/timeline-script-id-expected.txt |
| @@ -3,6 +3,7 @@ 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. |
| details.textContent for FunctionCall event: 'InjectedScript:1' |
| +details.textContent for FunctionCall event: 'InjectedScript:1' |
|
alph
2015/04/27 18:10:43
Sorry, don't see what makes this test non-flaky.
C
|
| detailsTextContent for TimerInstall event: 'performActions.js:3' |
| details.textContent for TimerInstall event: 'performActions.js:3' |
| detailsTextContent for TimerInstall event: 'performActions.js:4' |