From: iposva@chromium.org <iposva@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Date: Wed, 13 May 2009 18:35:55 +0000 (+0000)
Subject: - Update cctest.status to reflect that we cannot expect OutOfMemory exceptions
X-Git-Tag: upstream/4.7.83~24120
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=032681a057c143714a137540b9af5ca91ba9a1a8;p=platform%2Fupstream%2Fv8.git

- Update cctest.status to reflect that we cannot expect OutOfMemory exceptions
  in all situations.

Review URL: http://codereview.chromium.org/114025

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1940 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
---

diff --git a/test/cctest/cctest.status b/test/cctest/cctest.status
index 7b43c8d..93e348b 100644
--- a/test/cctest/cctest.status
+++ b/test/cctest/cctest.status
@@ -40,6 +40,12 @@ test-spaces/LargeObjectSpace: PASS || FAIL
 # BUG(240): Test seems flaky on ARM.
 test-api/RegExpInterruption: SKIP
 
+# We cannot assume that we can throw OutOfMemory exceptions in all situations.
+# Apparently our ARM box is in such a state. Skip the test as it also runs for
+# a long time.
+test-api/OutOfMemory: SKIP
+test-api/OutOfMemoryNested: SKIP
+
 [ $simulator == arm ]
 
 # BUG(271): During exception propagation, we compare pointers into the