Bug 42369

Summary: Chromium test expectations update after ES5 Object.freeze and Object.seal implementation.
Product: WebKit Reporter: Mads Ager <ager>
Component: New BugsAssignee: Mads Ager <ager>
Status: RESOLVED FIXED    
Severity: Normal    
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Other   
OS: OS X 10.5   
Attachments:
Description Flags
Patch
none
Patch jorlow: review+

Mads Ager
Reported 2010-07-15 06:53:58 PDT
Chromium test expectations update after ES5 Object.freeze and Object.seal implementation.
Attachments
Patch (6.14 KB, patch)
2010-07-15 06:58 PDT, Mads Ager 		no flags
DetailsFormatted DiffDiff
Patch (6.69 KB, patch)
2010-07-15 07:26 PDT, Mads Ager 		jorlow: review+
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Mads Ager
Comment 1 2010-07-15 06:58:33 PDT
Created attachment 61652 [details] Patch
Jeremy Orlow
Comment 2 2010-07-15 07:04:57 PDT
Comment on attachment 61652 [details] Patch Normally we'd rather have you check in chromium baselines, but since the output simply says PASS or FAIL, setting our expectations like this actually seems reasonable. But you shoudl explain all of this in detail in a bug and replace BUG_RICOW with the bug number. BUG_* is only for temporary entries.
Mads Ager
Comment 3 2010-07-15 07:26:00 PDT
Created attachment 61656 [details] Patch
Jeremy Orlow
Comment 4 2010-07-15 07:29:36 PDT
Comment on attachment 61656 [details] Patch r=me
Mads Ager
Comment 5 2010-07-15 07:37:31 PDT
Committed r63424: <http://trac.webkit.org/changeset/63424>
Note You need to log in before you can comment on or make changes to this bug.