Index: test/mozilla/mozilla.status |
diff --git a/test/mozilla/mozilla.status b/test/mozilla/mozilla.status |
index 62af106afbfdb146c17a6a62198dc4c709a6ca99..aa864ce0b86fc837cfd4a6b979e7b7fd8f111989 100644 |
--- a/test/mozilla/mozilla.status |
+++ b/test/mozilla/mozilla.status |
@@ -42,13 +42,12 @@ |
# debugging. |
# -------------------------------------------------------------------- |
- |
-##################### NEEDS INVESTIGATION ############## |
- |
-# BUG(2893): These tests started to fail after i18n support was turned on. Need |
-# to investigate why. |
[ |
[ALWAYS, { |
+ ##################### NEEDS INVESTIGATION ############## |
+ |
+ # BUG(2893): These tests started to fail after i18n support was turned on. |
+ # Need to investigate why. |
'ecma_3/Number/15.7.4.3-02': [PASS, FAIL], |
'ecma_3/Date/15.9.5.5-02': [PASS, FAIL], |
@@ -76,7 +75,7 @@ |
'js1_2/function/Number': [SKIP], |
# TODO(2018): Temporarily allow timeout in debug mode. |
- 'js1_5/GC/regress-203278-2': [PASS, ['mode == debug', TIMEOUT, FAIL]], |
+ 'js1_5/GC/regress-203278-2': [PASS, ['mode == debug', TIMEOUT, NO_VARIANTS, FAIL]], |
##################### SLOW TESTS ##################### |
@@ -104,11 +103,11 @@ |
##################### FLAKY TESTS ##################### |
# These tests time out in debug mode but pass in product mode |
- 'js1_5/Regress/regress-360969-03': [PASS, ['mode == debug', TIMEOUT]], |
- 'js1_5/Regress/regress-360969-04': [PASS, ['mode == debug', TIMEOUT]], |
- 'js1_5/Regress/regress-360969-05': [PASS, ['mode == debug', TIMEOUT]], |
- 'js1_5/Regress/regress-360969-06': [PASS, ['mode == debug', TIMEOUT]], |
- 'js1_5/extensions/regress-365527': [PASS, ['mode == debug', TIMEOUT]], |
+ 'js1_5/Regress/regress-360969-03': [PASS, ['mode == debug', TIMEOUT, NO_VARIANTS]], |
+ 'js1_5/Regress/regress-360969-04': [PASS, ['mode == debug', TIMEOUT, NO_VARIANTS]], |
+ 'js1_5/Regress/regress-360969-05': [PASS, ['mode == debug', TIMEOUT, NO_VARIANTS]], |
+ 'js1_5/Regress/regress-360969-06': [PASS, ['mode == debug', TIMEOUT, NO_VARIANTS]], |
+ 'js1_5/extensions/regress-365527': [PASS, ['mode == debug', TIMEOUT, NO_VARIANTS]], |
'js1_5/Regress/regress-280769-3': [PASS, ['mode == debug', FAIL]], |
'js1_5/Regress/regress-203278-1': [PASS, ['mode == debug', FAIL]], |
@@ -117,7 +116,7 @@ |
'js1_5/GC/regress-278725': [PASS, ['mode == debug', FAIL]], |
# http://b/issue?id=1206983 |
'js1_5/Regress/regress-367561-03': [PASS, ['mode == debug', FAIL]], |
- 'ecma/Date/15.9.5.10-2': [PASS, FAIL, ['mode == debug', TIMEOUT]], |
+ 'ecma/Date/15.9.5.10-2': [PASS, FAIL, ['mode == debug', TIMEOUT, NO_VARIANTS]], |
# These tests create two Date objects just after each other and |
# expects them to match. Sometimes this happens on the border |
@@ -167,13 +166,13 @@ |
'js1_5/Array/regress-99120-01': [PASS, FAIL], |
'js1_5/Array/regress-99120-02': [PASS, FAIL], |
'js1_5/Regress/regress-347306-01': [PASS, FAIL], |
- 'js1_5/Regress/regress-416628': [PASS, FAIL, ['mode == debug', TIMEOUT]], |
+ 'js1_5/Regress/regress-416628': [PASS, FAIL, ['mode == debug', TIMEOUT, NO_VARIANTS]], |
# The following two tests assume that daylight savings time starts first |
# Sunday in April. This is not true when executing the tests outside |
- # California! In Denmark the adjustment starts one week earlier!. Tests based |
- # on shell that use dates in this gap are flaky. |
+ # California! In Denmark the adjustment starts one week earlier. |
+ # Tests based on shell that use dates in this gap are flaky. |
'ecma/Date/15.9.5.10-1': [PASS, FAIL], |
'ecma/Date/15.9.5.12-1': [PASS, FAIL], |
'ecma/Date/15.9.5.14': [PASS, FAIL], |
@@ -188,7 +187,7 @@ |
# Tests that sorting arrays of ints is less than 3 times as fast |
# as sorting arrays of strings. |
- 'js1_5/extensions/regress-371636': [PASS, FAIL, ['mode == debug', TIMEOUT]], |
+ 'js1_5/extensions/regress-371636': [PASS, FAIL, ['mode == debug', TIMEOUT, NO_VARIANTS]], |
# Tests depend on GC timings. Inherently flaky. |
@@ -274,14 +273,18 @@ |
# PCRE's match limit is reached. SpiderMonkey hangs on the first one, |
# JSC returns true somehow. Maybe they up the match limit? There is |
# an open V8 bug 676063 about this. |
- 'ecma_3/RegExp/regress-330684': [TIMEOUT], |
+ # TODO(yangguo): Hangs on complex regexp. Please investigate if this gives |
+ # any useful coverage. |
+ 'ecma_3/RegExp/regress-330684': [SKIP], |
# This test contains a regexp that runs exponentially long. Spidermonkey |
# standalone will hang, though apparently inside Firefox it will trigger a |
# long-running-script timeout. JSCRE passes by hitting the matchLimit and |
# just pretending that an exhaustive search found no match. |
- 'ecma_3/RegExp/regress-307456': [PASS, TIMEOUT], |
+ # TODO(yangguo): Hangs on complex regexp. Please investigate if this gives |
+ # any useful coverage. |
+ 'ecma_3/RegExp/regress-307456': [SKIP], |
# We do not detect overflow in bounds for back references and {} |
@@ -485,9 +488,9 @@ |
'ecma_3/Unicode/uc-001': [FAIL_OK], |
- # A non-breaking space doesn't match \s in a regular expression. This behaviour |
- # matches JSC. All the VMs have different behaviours in which characters match |
- # \s so we do the same as JSC until they change. |
+ # A non-breaking space doesn't match \s in a regular expression. This |
+ # behaviour matches JSC. All the VMs have different behaviours in which |
+ # characters match \s so we do the same as JSC until they change. |
'ecma_3/Unicode/uc-002': [PASS, FAIL_OK], |
@@ -531,8 +534,8 @@ |
# Tests if future reserved keywords of ECMA-262, edition 3 emit warnings. We |
- # implement the edition 5 behaviour and fail on use of edition 5 future reserved |
- # keywords as identifiers. |
+ # implement the edition 5 behaviour and fail on use of edition 5 future |
+ # reserved keywords as identifiers. |
'js1_5/Regress/regress-240317': [FAIL_OK], |
@@ -607,14 +610,14 @@ |
# category. |
# This fails because we don't handle Function.prototype.apply with very large |
- # numbers of arguments (depending on max stack size). 350256-02 needs more than |
- # 4Mbytes of stack space. |
+ # numbers of arguments (depending on max stack size). 350256-02 needs more |
+ # than 4Mbytes of stack space. |
'js1_5/Array/regress-350256-02': [FAIL], |
# This test seems designed to fail (it produces a 700Mbyte string). |
# We fail on out of memory. The important thing is not to crash. |
- 'js1_5/Regress/regress-303213': [FAIL, ['mode == debug', TIMEOUT]], |
+ 'js1_5/Regress/regress-303213': [FAIL, ['mode == debug', TIMEOUT, NO_VARIANTS]], |
# This test fails since we now throw in String.prototype.match when apply |
# is given null or undefined as this argument (and so does firefox nightly). |
@@ -748,12 +751,15 @@ |
'js1_5/extensions/toLocaleFormat-01': [FAIL_OK], |
'js1_5/extensions/toLocaleFormat-02': [FAIL_OK], |
- 'js1_5/extensions/regress-330569': [TIMEOUT], |
- 'js1_5/extensions/regress-351448': [TIMEOUT], |
+ # TODO(yangguo): Both tests have complex regular expressions (nested (.*)* |
+ # and the like). Please investigate if these tests provide any coverage. |
+ # Furthermore, an exception is expected which is not thrown by v8. |
+ 'js1_5/extensions/regress-330569': [SKIP], |
+ 'js1_5/extensions/regress-351448': [SKIP], |
# In the 64-bit version, this test takes longer to run out of memory |
# than it does in the 32-bit version when attempting to generate a huge |
# error message in debug mode. |
- 'js1_5/extensions/regress-336410-1': [FAIL_OK, ['mode == debug and arch == x64', TIMEOUT]], |
+ 'js1_5/extensions/regress-336410-1': [FAIL_OK, ['mode == debug and arch == x64', TIMEOUT, NO_VARIANTS]], |
##################### DECOMPILATION TESTS ##################### |
@@ -832,7 +838,7 @@ |
# BUG(1040): Allow this test to timeout. |
- 'js1_5/GC/regress-203278-2': [PASS, TIMEOUT], |
+ 'js1_5/GC/regress-203278-2': [PASS, TIMEOUT, NO_VARIANTS], |
}], # 'arch == arm or arch == a64' |
@@ -852,7 +858,7 @@ |
# BUG(1040): Allow this test to timeout. |
- 'js1_5/GC/regress-203278-2': [PASS, TIMEOUT], |
+ 'js1_5/GC/regress-203278-2': [PASS, TIMEOUT, NO_VARIANTS], |
}], # 'arch == mipsel' |
['arch == a64 and simulator_run == True', { |