Bug 46976

Summary: fast/js/sputnik/Conformance/11_Expressions/11.7_Bitwise_Shift_Operators/11.7.3_The_Unsigned_Right_Shift_Operator/S11.7.3_A2.3_T1.html failing in Release builds on Windows
Product: WebKit Reporter: Adam Roben (:aroben) <aroben>
Component: JavaScriptCoreAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: barraclough, bfulgham, ggaren, msaboff, oliver
Priority: P2 Keywords: InRadar, LayoutTestFailure, PlatformOnly
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Windows XP   
URL: http://build.webkit.org/results/Windows%20Release%20(Tests)/r68874%20(4655)/fast/js/sputnik/Conformance/11_Expressions/11.7_Bitwise_Shift_Operators/11.7.3_The_Unsigned_Right_Shift_Operator/S11.7.3_A2.3_T1-pretty-diff.html

Adam Roben (:aroben)
Reported 2010-10-01 04:56:27 PDT
fast/js/sputnik/Conformance/11_Expressions/11.7_Bitwise_Shift_Operators/11.7.3_The_Unsigned_Right_Shift_Operator/S11.7.3_A2.3_T1.html is failing in Release builds on Windows. Here's the diff: --- /home/buildbot/slave/WebKit-BuildSlave/win-release-tests/build/layout-test-results/fast/js/sputnik/Conformance/11_Expressions/11.7_Bitwise_Shift_Operators/11.7.3_The_Unsigned_Right_Shift_Operator/S11.7.3_A2.3_T1-expected.txt 2010-10-01 03:59:44.903174100 -0700 +++ /home/buildbot/slave/WebKit-BuildSlave/win-release-tests/build/layout-test-results/fast/js/sputnik/Conformance/11_Expressions/11.7_Bitwise_Shift_Operators/11.7.3_The_Unsigned_Right_Shift_Operator/S11.7.3_A2.3_T1-actual.txt 2010-10-01 03:59:44.901174000 -0700 @@ -1,6 +1,6 @@ S11.7.3_A2.3_T1 -PASS +FAIL SputnikError: #1.2: ToNumber(first expression) is called first, and then ToNumber(second expression) TEST COMPLETE
Attachments
Add attachment proposed patch, testcase, etc.
Adam Roben (:aroben)
Comment 1 2010-10-01 05:05:09 PDT
<rdar://problem/8501934>
Oliver Hunt
Comment 2 2010-10-08 12:43:04 PDT
When did this start failing?
Adam Roben (:aroben)
Comment 3 2010-10-11 04:44:01 PDT
(In reply to comment #2) > When did this start failing? I don't know, but the build.webkit.org logs should help us figure it out.
Brent Fulgham
Comment 4 2015-01-15 17:11:46 PST
This is no longer a problem with current WebKit.
Note You need to log in before you can comment on or make changes to this bug.