tools/layout_tests/test_expectations.txt

# This file should almost always be empty. Normally Chromium test expectations
# are only put here temporarily, and moved to
# src/third_party/WebKit/LayoutTests/TestExpectations where they will remain
# until they are rebaselined.
#
#
# If you are landing a Chromium CL that would break webkit layout tests,
# please follow these steps:
#
# 1. Add expected failures to the bottom of this file, and run your CL through
# various *_layout trybots.  Confirm that the trybot results are green (any
# failures are masked by the expectations you added to this file).
#
# 2. BEFORE landing your Chromium CL, land a WebKit CL adding those same
# expected failures to
# src/third_party/WebKit/LayoutTests/TestExpectations . If you are unable to do
# this yourself, please get a WebKit Committer to do it for you, or at least
# coordinate with a current WebKit Gardener to make sure she is aware of the
# pending breakages.
#
# 3. AFTER you have landed the WebKit test_expectations CL, you can land your
# Chromium CL.  Be sure to include your expected failures in this file, so
# that other tip-of-tree Chromium developers will not be disturbed by your
# change.
#
#
# Every time Chromium's "WebKit Gardener" rolls the WebKit DEPS within
# Chromium, he will delete ALL expectations within this file.  (By then, they
# will be redundant, because you already landed those same expectations in
# src/third_party/WebKit/LayoutTests/TestExpectations . Right?)
#
# EVERYTHING BELOW THIS LINE WILL BE DELETED AT EVERY WEBKIT DEPS ROLL

crbug.com/395882 http/tests/security/xss-DENIED-method-with-iframe-proto.html [ Skip ]
1	# This file should almost always be empty. Normally Chromium test expectations
2	# are only put here temporarily, and moved to
3	# src/third_party/WebKit/LayoutTests/TestExpectations where they will remain
4	# until they are rebaselined.
5	#
6	#
7	# If you are landing a Chromium CL that would break webkit layout tests,
8	# please follow these steps:
9	#
10	# 1. Add expected failures to the bottom of this file, and run your CL through
11	# various *_layout trybots. Confirm that the trybot results are green (any
12	# failures are masked by the expectations you added to this file).
13	#
14	# 2. BEFORE landing your Chromium CL, land a WebKit CL adding those same
15	# expected failures to
16	# src/third_party/WebKit/LayoutTests/TestExpectations . If you are unable to do
17	# this yourself, please get a WebKit Committer to do it for you, or at least
18	# coordinate with a current WebKit Gardener to make sure she is aware of the
19	# pending breakages.
20	#
21	# 3. AFTER you have landed the WebKit test_expectations CL, you can land your
22	# Chromium CL. Be sure to include your expected failures in this file, so
23	# that other tip-of-tree Chromium developers will not be disturbed by your
24	# change.
25	#
26	#
27	# Every time Chromium's "WebKit Gardener" rolls the WebKit DEPS within
28	# Chromium, he will delete ALL expectations within this file. (By then, they
29	# will be redundant, because you already landed those same expectations in
30	# src/third_party/WebKit/LayoutTests/TestExpectations . Right?)
31	#
32	# EVERYTHING BELOW THIS LINE WILL BE DELETED AT EVERY WEBKIT DEPS ROLL
33
34	crbug.com/395882 http/tests/security/xss-DENIED-method-with-iframe-proto.html [ Skip ]
Name	Value
svn:eol-style	LF
svn:mergeinfo	/branches/chrome_webkit_merge_branch/src/webkit/tools/layout_tests/test_lists/win/tests_fixable.txt:3734-4217,4606-5108,5177-5263