Bug 59673 - Chromium test failures after r85142
Summary: Chromium test failures after r85142
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 55965
Blocks:
  Show dependency treegraph
 
Reported: 2011-04-27 22:42 PDT by Kenneth Russell
Modified: 2013-04-09 16:27 PDT (History)
3 users (show)

See Also:


Attachments
Temporarily suppress test failures. (1.34 KB, patch)
2011-04-27 22:56 PDT, Kenneth Russell
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Kenneth Russell 2011-04-27 22:42:46 PDT
After r85142 the following tests are failing on Chromium:

fast/dom/Window/get-set-properties.html
fast/dom/Window/window-property-shadowing.html
http/tests/history/cross-origin-replace-history-object-child.html

The first two seem to need simple rebaselines. The third might be a more involved failure.
Comment 1 Kenneth Russell 2011-04-27 22:56:17 PDT
Created attachment 91431 [details]
Temporarily suppress test failures.
Comment 2 Kenneth Russell 2011-04-27 23:00:05 PDT
Committed r85161: <http://trac.webkit.org/changeset/85161>
Comment 4 Adam Barth 2011-04-27 23:17:34 PDT
These almost certainly just need new baselines.
Comment 5 Robert Hogan 2011-04-28 11:18:26 PDT
re http/tests/history/cross-origin-replace-history-object-child.html, all Chrome results have a variation of:

CONSOLE MESSAGE: line 24: Uncaught TypeError: Cannot convert object after attempt to clear: [object History] primitive value

I'm not sure if this is expected.
Comment 6 Kenneth Russell 2011-04-28 11:47:17 PDT
(In reply to comment #5)
> re http/tests/history/cross-origin-replace-history-object-child.html, all Chrome results have a variation of:
> 
> CONSOLE MESSAGE: line 24: Uncaught TypeError: Cannot convert object after attempt to clear: [object History] primitive value
> 
> I'm not sure if this is expected.

Agreed, this looks like a deeper failure. We definitely should not blindly rebaseline over this one.
Comment 7 Dirk Pranke 2012-03-30 16:23:01 PDT
the first two tests are no longer failing.
Comment 8 Stephen Chenney 2013-04-09 16:27:59 PDT
Marking test failures as WontFix. Bug is still accessible and recording in TestExpectations.