Bug 53022

Summary: [chromium] Remove non-flaky tests from test expectation file
Product: WebKit Reporter: imasaki
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: commit-queue, dimich, jianli, levin
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Other   
OS: OS X 10.5   
Attachments:
Description Flags
Patch
none
Patch none

imasaki
Reported 2011-01-24 10:39:05 PST
Remove non-flaky tests from test expectation file
Attachments
Patch (3.02 KB, patch)
2011-01-24 10:43 PST, imasaki 		no flags
DetailsFormatted DiffDiff
Patch (1.76 KB, patch)
2011-01-24 11:06 PST, imasaki 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
imasaki
Comment 1 2011-01-24 10:43:43 PST
Created attachment 79937 [details] Patch
Jian Li
Comment 2 2011-01-24 10:53:46 PST
Comment on attachment 79937 [details] Patch Please add "[chromium]" prefix to the bug title and the description in ChangeLog.
imasaki
Comment 3 2011-01-24 11:06:49 PST
Created attachment 79939 [details] Patch
Jian Li
Comment 4 2011-01-24 11:09:22 PST
Compared with your 1st patch, some tests are not removed in your 2nd patch? Why?
imasaki
Comment 5 2011-01-24 11:19:43 PST
After submitting the 1st patch, I have change my mind to remove just 2 tests (instead of 6 tests) to be safe. 2nd patch is to remove just 2 tests (media/video-seek-past-end-playing.html,media/video-source-moved.html)
WebKit Commit Bot
Comment 6 2011-01-24 12:10:28 PST
The commit-queue encountered the following flaky tests while processing attachment 79939 [details]: http/tests/security/cross-origin-css.html bug 53035 (author: cevans@google.com) The commit-queue is continuing to process your patch.
WebKit Commit Bot
Comment 7 2011-01-24 12:11:10 PST
Comment on attachment 79939 [details] Patch Clearing flags on attachment: 79939 Committed r76540: <http://trac.webkit.org/changeset/76540>
WebKit Commit Bot
Comment 8 2011-01-24 12:11:15 PST
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.