Title: [87870] trunk/LayoutTests
- Revision
- 87870
- Author
- [email protected]
- Date
- 2011-06-01 18:05:15 -0700 (Wed, 01 Jun 2011)
Log Message
2011-06-01 Adam Barth <[email protected]>
Move expected result to the correct location. The script put it in the
wrong location.
* platform/chromium-mac/fast/js/property-getters-and-setters-expected.txt: Removed.
* platform/chromium-win/fast/js/property-getters-and-setters-expected.txt: Removed.
* platform/chromium/fast/js/property-getters-and-setters-expected.txt: Copied from LayoutTests/platform/chromium-mac/fast/js/property-getters-and-setters-expected.txt.
Modified Paths
Added Paths
Removed Paths
Diff
Modified: trunk/LayoutTests/ChangeLog (87869 => 87870)
--- trunk/LayoutTests/ChangeLog 2011-06-02 01:00:11 UTC (rev 87869)
+++ trunk/LayoutTests/ChangeLog 2011-06-02 01:05:15 UTC (rev 87870)
@@ -1,5 +1,14 @@
2011-06-01 Adam Barth <[email protected]>
+ Move expected result to the correct location. The script put it in the
+ wrong location.
+
+ * platform/chromium-mac/fast/js/property-getters-and-setters-expected.txt: Removed.
+ * platform/chromium-win/fast/js/property-getters-and-setters-expected.txt: Removed.
+ * platform/chromium/fast/js/property-getters-and-setters-expected.txt: Copied from LayoutTests/platform/chromium-mac/fast/js/property-getters-and-setters-expected.txt.
+
+2011-06-01 Adam Barth <[email protected]>
+
These test time out on debug, probably because drop shadows are slow in debug skia.
* platform/chromium/test_expectations.txt:
Copied: trunk/LayoutTests/platform/chromium/fast/js/property-getters-and-setters-expected.txt (from rev 87866, trunk/LayoutTests/platform/chromium-mac/fast/js/property-getters-and-setters-expected.txt) (0 => 87870)
--- trunk/LayoutTests/platform/chromium/fast/js/property-getters-and-setters-expected.txt (rev 0)
+++ trunk/LayoutTests/platform/chromium/fast/js/property-getters-and-setters-expected.txt 2011-06-02 01:05:15 UTC (rev 87870)
@@ -0,0 +1,36 @@
+This performs a number of different tests on _javascript_ getters and setters.
+
+On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
+
+
+the get set object declaration syntax
+PASS o1.b is 8
+PASS o1.b is 11
+__defineGetter__ and __defineSetter__
+PASS o2.b is 8
+PASS o2.b is 11
+Setting a value without having a setter
+FAIL o3.x = 10; should throw an exception. Was 10.
+Getting a value without having a getter
+PASS o4.x is undefined.
+__lookupGetter__ and __lookupSetter__
+PASS o4.__lookupGetter__('b') is getB
+PASS o4.__lookupSetter__('b') is setB
+__defineGetter__ and __defineSetter__ with various invalid arguments
+PASS o5.__defineSetter__('a', null) threw exception TypeError: Object.prototype.__defineSetter__: Expecting function.
+PASS o5.__defineSetter__('a', o5) threw exception TypeError: Object.prototype.__defineSetter__: Expecting function.
+PASS o5.__defineGetter__('a', null) threw exception TypeError: Object.prototype.__defineGetter__: Expecting function.
+PASS o5.__defineGetter__('a', o5) threw exception TypeError: Object.prototype.__defineGetter__: Expecting function.
+setters and getters with exceptions
+PASS x = o6.x threw exception Exception in get.
+PASS x is 0
+PASS o6.x = 42 threw exception Exception in set.
+Defining a setter should also define a getter for the same property which returns undefined. Thus, a getter defined on the prototype should not be called.
+PASS o7.x is undefined.
+If an object has a property and its prototype has a setter function for that property, then setting the property should set the property directly and not call the setter function.
+PASS o8.numSets is 0
+PASS typeof testObj.getter is 'string'
+PASS successfullyParsed is true
+
+TEST COMPLETE
+
Deleted: trunk/LayoutTests/platform/chromium-mac/fast/js/property-getters-and-setters-expected.txt (87869 => 87870)
--- trunk/LayoutTests/platform/chromium-mac/fast/js/property-getters-and-setters-expected.txt 2011-06-02 01:00:11 UTC (rev 87869)
+++ trunk/LayoutTests/platform/chromium-mac/fast/js/property-getters-and-setters-expected.txt 2011-06-02 01:05:15 UTC (rev 87870)
@@ -1,36 +0,0 @@
-This performs a number of different tests on _javascript_ getters and setters.
-
-On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
-
-
-the get set object declaration syntax
-PASS o1.b is 8
-PASS o1.b is 11
-__defineGetter__ and __defineSetter__
-PASS o2.b is 8
-PASS o2.b is 11
-Setting a value without having a setter
-FAIL o3.x = 10; should throw an exception. Was 10.
-Getting a value without having a getter
-PASS o4.x is undefined.
-__lookupGetter__ and __lookupSetter__
-PASS o4.__lookupGetter__('b') is getB
-PASS o4.__lookupSetter__('b') is setB
-__defineGetter__ and __defineSetter__ with various invalid arguments
-PASS o5.__defineSetter__('a', null) threw exception TypeError: Object.prototype.__defineSetter__: Expecting function.
-PASS o5.__defineSetter__('a', o5) threw exception TypeError: Object.prototype.__defineSetter__: Expecting function.
-PASS o5.__defineGetter__('a', null) threw exception TypeError: Object.prototype.__defineGetter__: Expecting function.
-PASS o5.__defineGetter__('a', o5) threw exception TypeError: Object.prototype.__defineGetter__: Expecting function.
-setters and getters with exceptions
-PASS x = o6.x threw exception Exception in get.
-PASS x is 0
-PASS o6.x = 42 threw exception Exception in set.
-Defining a setter should also define a getter for the same property which returns undefined. Thus, a getter defined on the prototype should not be called.
-PASS o7.x is undefined.
-If an object has a property and its prototype has a setter function for that property, then setting the property should set the property directly and not call the setter function.
-PASS o8.numSets is 0
-PASS typeof testObj.getter is 'string'
-PASS successfullyParsed is true
-
-TEST COMPLETE
-
Deleted: trunk/LayoutTests/platform/chromium-win/fast/js/property-getters-and-setters-expected.txt (87869 => 87870)
--- trunk/LayoutTests/platform/chromium-win/fast/js/property-getters-and-setters-expected.txt 2011-06-02 01:00:11 UTC (rev 87869)
+++ trunk/LayoutTests/platform/chromium-win/fast/js/property-getters-and-setters-expected.txt 2011-06-02 01:05:15 UTC (rev 87870)
@@ -1,36 +0,0 @@
-This performs a number of different tests on _javascript_ getters and setters.
-
-On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
-
-
-the get set object declaration syntax
-PASS o1.b is 8
-PASS o1.b is 11
-__defineGetter__ and __defineSetter__
-PASS o2.b is 8
-PASS o2.b is 11
-Setting a value without having a setter
-PASS o3.x = 10; threw exception TypeError: Cannot set property x of #<Object> which has only a getter.
-Getting a value without having a getter
-PASS o4.x is undefined.
-__lookupGetter__ and __lookupSetter__
-PASS o4.__lookupGetter__('b') is getB
-PASS o4.__lookupSetter__('b') is setB
-__defineGetter__ and __defineSetter__ with various invalid arguments
-PASS o5.__defineSetter__('a', null) threw exception TypeError: Object.prototype.__defineSetter__: Expecting function.
-PASS o5.__defineSetter__('a', o5) threw exception TypeError: Object.prototype.__defineSetter__: Expecting function.
-PASS o5.__defineGetter__('a', null) threw exception TypeError: Object.prototype.__defineGetter__: Expecting function.
-PASS o5.__defineGetter__('a', o5) threw exception TypeError: Object.prototype.__defineGetter__: Expecting function.
-setters and getters with exceptions
-PASS x = o6.x threw exception Exception in get.
-PASS x is 0
-PASS o6.x = 42 threw exception Exception in set.
-Defining a setter should also define a getter for the same property which returns undefined. Thus, a getter defined on the prototype should not be called.
-PASS o7.x is undefined.
-If an object has a property and its prototype has a setter function for that property, then setting the property should set the property directly and not call the setter function.
-PASS o8.numSets is 0
-PASS typeof testObj.getter is 'string'
-PASS successfullyParsed is true
-
-TEST COMPLETE
-
_______________________________________________
webkit-changes mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-changes
