Bug 82921

Summary: CSS 2.1 failure: at-import-009.htm fails
Product: WebKit Reporter: Robert Hogan <robert>
Component: CSSAssignee: Robert Hogan <robert>
Status: RESOLVED FIXED    
Severity: Normal CC: dglazkov, macpherson, menard, robert, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 47141    
Attachments:
Description Flags
Patch
koivisto: review+, webkit.review.bot: commit-queue-
Archive of layout-test-results from ec2-cr-linux-04 none

Robert Hogan
Reported 2012-04-02 11:53:30 PDT
..
Attachments
Patch (27.30 KB, patch)
2012-04-02 12:52 PDT, Robert Hogan
koivisto: review+
webkit.review.bot: commit-queue-
Archive of layout-test-results from ec2-cr-linux-04 (6.59 MB, application/zip)
2012-04-02 13:51 PDT, WebKit Review Bot
no flags
Robert Hogan
Comment 1 2012-04-02 12:52:13 PDT
Antti Koivisto
Comment 2 2012-04-02 12:55:03 PDT
Comment on attachment 135160 [details] Patch r=me
Robert Hogan
Comment 3 2012-04-02 13:07:48 PDT
(In reply to comment #2) > (From update of attachment 135160 [details]) > r=me Thanks. There's an error in two of the expected results files which I will correct before landing. I think I must have run the final check on the tests with --reset-results or something dumb.
WebKit Review Bot
Comment 4 2012-04-02 13:51:01 PDT
Comment on attachment 135160 [details] Patch Attachment 135160 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/12312680 New failing tests: css2.1/20110323/at-import-004.htm css2.1/20110323/at-import-001.htm
WebKit Review Bot
Comment 5 2012-04-02 13:51:06 PDT
Created attachment 135175 [details] Archive of layout-test-results from ec2-cr-linux-04 The attached test failures were seen while running run-webkit-tests on the chromium-ews. Bot: ec2-cr-linux-04 Port: <class 'webkitpy.common.config.ports.ChromiumXVFBPort'> Platform: Linux-2.6.35-28-virtual-x86_64-with-Ubuntu-10.10-maverick
Robert Hogan
Comment 6 2012-04-03 13:14:56 PDT
Note You need to log in before you can comment on or make changes to this bug.