Bug 113385

Summary: [EFL] Remove a duplicated test from TestExpectations
Product: WebKit Reporter: Seokju Kwon <seokju>
Component: WebKit EFLAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: cdumez, gyuyoung.kim, lucas.de.marchi, rakuco, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch
none
Patch none

Seokju Kwon
Reported 2013-03-27 03:26:05 PDT
--lint-test-files warnings: LayoutTests/platform/efl/TestExpectations:1049 Duplicate or ambiguous entry lines LayoutTests/platform/efl/TestExpectations:473 and LayoutTests/platform/efl/TestExpectations:1049. editing/pasteboard/paste-table-cells.html
Attachments
Patch (1.35 KB, patch)
2013-03-27 03:31 PDT, Seokju Kwon 		no flags
DetailsFormatted DiffDiff
Patch (1.55 KB, patch)
2013-03-27 03:41 PDT, Seokju Kwon 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Seokju Kwon
Comment 1 2013-03-27 03:31:26 PDT
Created attachment 195259 [details] Patch
Chris Dumez
Comment 2 2013-03-27 03:36:34 PDT
Comment on attachment 195259 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=195259&action=review > LayoutTests/platform/efl/TestExpectations:-473 > -webkit.org/b/102486 editing/pasteboard/paste-table-cells.html [ Failure ] If you remove this one. Then the test expectation becomes "Missing". However, if I look at the LayoutTests folder, there is an expected result: LayoutTests/editing/pasteboard/paste-table-cells-expected.txt Therefore, the correct expected result is probably "Failure"?
Seokju Kwon
Comment 3 2013-03-27 03:41:41 PDT
Created attachment 195262 [details] Patch
WebKit Review Bot
Comment 4 2013-03-27 04:12:35 PDT
Comment on attachment 195262 [details] Patch Clearing flags on attachment: 195262 Committed r146978: <http://trac.webkit.org/changeset/146978>
WebKit Review Bot
Comment 5 2013-03-27 04:12:43 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.