LayoutTests/fast/profiler/start-but-dont-stop-profiling-expected.txt - Issue 14195011: Removed WONTFIX 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: LayoutTests/fast/profiler/start-but-dont-stop-profiling-expected.txt

Issue 14195011: Removed WONTFIX tests (Closed) Base URL: svn://svn.chromium.org/blink/trunk

Patch Set: Created 7 years, 8 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

« LayoutTests/TestExpectations ('K') | « LayoutTests/fast/profiler/start-but-dont-stop-profiling.html ('k') | LayoutTests/fast/profiler/stop-profiling-after-setTimeout.html » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: LayoutTests/fast/profiler/start-but-dont-stop-profiling-expected.txt

diff --git a/LayoutTests/fast/profiler/start-but-dont-stop-profiling-expected.txt b/LayoutTests/fast/profiler/start-but-dont-stop-profiling-expected.txt

deleted file mode 100644

index 4dbc12dd9137b4cb43621eb69e2b1ea42e10004b..0000000000000000000000000000000000000000

--- a/LayoutTests/fast/profiler/start-but-dont-stop-profiling-expected.txt

+++ /dev/null

@@ -1,5 +0,0 @@

-This page's JavaScript calls console.profile() but not console.profileEnd().

-To run this test manually, load it in the browser then load the WebInspector and look at the profile. You should see the profile running (when that feature is implemented 6060556). Then navigate to another page and check the WebInspector again. Safari should not have crashed and the Inspector should not show a profile (unless we allow cross-load profiling in the future 5951478 & 5954912).