Bug 46976 - 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
Summary: fast/js/sputnik/Conformance/11_Expressions/11.7_Bitwise_Shift_Operators/11.7....
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows XP
: P2 Normal
Assignee: Nobody
URL: http://build.webkit.org/results/Windo...
Keywords: InRadar, LayoutTestFailure, PlatformOnly
Depends on:
Blocks:
 
Reported: 2010-10-01 04:56 PDT by Adam Roben (:aroben)
Modified: 2015-01-15 17:11 PST (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Roben (:aroben) 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
Comment 1 Adam Roben (:aroben) 2010-10-01 05:05:09 PDT 
<rdar://problem/8501934>
Comment 2 Oliver Hunt 2010-10-08 12:43:04 PDT 
When did this start failing?
Comment 3 Adam Roben (:aroben) 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.
Comment 4 Brent Fulgham 2015-01-15 17:11:46 PST 
This is no longer a problem with current WebKit.