LayoutTests/inspector-protocol/cpu-profiler/enable-disable-expected.txt - Issue 116273003: Stop recording CPU profiles when Profiler agent is disabled

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: LayoutTests/inspector-protocol/cpu-profiler/enable-disable-expected.txt

Issue 116273003: Stop recording CPU profiles when Profiler agent is disabled (Closed) Base URL: svn://svn.chromium.org/blink/trunk

Patch Set: Comments addressed Created 7 years 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

« no previous file with comments | « LayoutTests/inspector-protocol/cpu-profiler/enable-disable.html ('k') | LayoutTests/inspector-protocol/cpu-profiler/record-cpu-profile.html » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: LayoutTests/inspector-protocol/cpu-profiler/enable-disable-expected.txt

diff --git a/LayoutTests/inspector-protocol/cpu-profiler/enable-disable-expected.txt b/LayoutTests/inspector-protocol/cpu-profiler/enable-disable-expected.txt

new file mode 100644

index 0000000000000000000000000000000000000000..a160ead9f9a7263d09005164cedeb217311b311e

--- /dev/null

+++ b/LayoutTests/inspector-protocol/cpu-profiler/enable-disable-expected.txt

@@ -0,0 +1,10 @@

+Test that profiling can only be started when Profiler was enabled and that Profiler.disable command will stop stop recording all profiles.

+PASS: didFailToStartWhenDisabled

+PASS: didStartFrontendProfile

+PASS: console initiated profile started

+PASS: didStartConsoleProfile

+PASS: didDisableProfiler

+PASS: no front-end initiated profiles found

+PASS: didStopConsoleProfile