Author: [email protected]
Date: Wed Mar 11 07:29:21 2009
New Revision: 1492

Modified:
    branches/bleeding_edge/test/cctest/cctest.status
    branches/bleeding_edge/test/cctest/test-api.cc

Log:
Temporarily disable tests that no longer work on the ARM simulator.

Exclude the tests from the threaded tests because I don't want to
disable those on ARM.

The issue is that the simulator keeps the C++ and the JavaScript stack
separated.  This is not a problem on the real hardware and the tests
pass on our ARM box.
Review URL: http://codereview.chromium.org/42069

Modified: branches/bleeding_edge/test/cctest/cctest.status
==============================================================================
--- branches/bleeding_edge/test/cctest/cctest.status    (original)
+++ branches/bleeding_edge/test/cctest/cctest.status    Wed Mar 11 07:29:21  
2009
@@ -39,3 +39,11 @@

  # BUG(240): Test seems flaky on ARM.
  test-api/RegExpInterruption: SKIP
+
+# BUG(271): After exception propagation changes that compares pointers
+# into the stack, these tests fail on the arm simulator (but pass on
+# the arm hardware) because the JS stack is not combined with the C
+# stack in the simulator.  Disabling while we consider how to solve
+# the issue for the simulator.
+test-api/ExceptionOrder: PASS || FAIL
+test-api/TryCatchInTryFinally: PASS || FAIL

Modified: branches/bleeding_edge/test/cctest/test-api.cc
==============================================================================
--- branches/bleeding_edge/test/cctest/test-api.cc      (original)
+++ branches/bleeding_edge/test/cctest/test-api.cc      Wed Mar 11 07:29:21 2009
@@ -1760,7 +1760,11 @@

  // Test that a try-finally block doesn't shadow a try-catch block
  // when setting up an external handler.
-THREADED_TEST(TryCatchInTryFinally) {
+//
+// TODO(271): This should be a threaded test. It was disabled for the
+// thread tests because it fails on the ARM simulator.  Should be made
+// threadable again when the simulator issue is resolved.
+TEST(TryCatchInTryFinally) {
    v8::HandleScope scope;
    Local<ObjectTemplate> templ = ObjectTemplate::New();
    templ->Set(v8_str("CCatcher"),
@@ -1913,7 +1917,11 @@
  // Each entry is an activation, either JS or C.  The index is the count at  
that
  // level.  Stars identify activations with exception handlers, the @  
identifies
  // the exception handler that should catch the exception.
-THREADED_TEST(ExceptionOrder) {
+//
+// TODO(271): This should be a threaded test. It was disabled for the
+// thread tests because it fails on the ARM simulator.  Should be made
+// threadable again when the simulator issue is resolved.
+TEST(ExceptionOrder) {
    v8::HandleScope scope;
    Local<ObjectTemplate> templ = ObjectTemplate::New();
    templ->Set(v8_str("check"), v8::FunctionTemplate::New(JSCheck));

--~--~---------~--~----~------------~-------~--~----~
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to