test/inspector/cpu-profiler/enable-disable.js - Issue 2713023004: [inspector] added reconnect method for tests

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: test/inspector/cpu-profiler/enable-disable.js

Issue 2713023004: [inspector] added reconnect method for tests (Closed)

Patch Set: addressed comments Created 3 years, 10 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

« src/inspector/v8-runtime-agent-impl.cc ('K') | « test/inspector/cpu-profiler/coverage.js ('k') | test/inspector/cpu-profiler/record-cpu-profile.js » ('j') | test/inspector/runtime/runtime-restore.js » ('J')
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: test/inspector/cpu-profiler/enable-disable.js

diff --git a/test/inspector/cpu-profiler/enable-disable.js b/test/inspector/cpu-profiler/enable-disable.js

index 3ed1b74b36bdb346b4da7616eca4ad640b138301..b342a162c4a8b10f30513220a819c06c6143863e 100644

--- a/test/inspector/cpu-profiler/enable-disable.js

+++ b/test/inspector/cpu-profiler/enable-disable.js

@@ -2,7 +2,7 @@

// Use of this source code is governed by a BSD-style license that can be

// found in the LICENSE file.

-print("Test that profiling can only be started when Profiler was enabled and that Profiler.disable command will stop recording all profiles.");

+InspectorTest.log("Test that profiling can only be started when Profiler was enabled and that Profiler.disable command will stop recording all profiles.");

Protocol.Profiler.start().then(didFailToStartWhenDisabled);

disallowConsoleProfiles();