Reviewers: Jakob, ulan,

Message:
Update cctest status.

The following cases passed for both ia32 and ARM
-test-debug/DebuggerAgent:
-test-debug/DebuggerAgentProtocolOverflowHeader:
-test-sockets/Socket:

There is only one fail: cctest/test-threads/ThreadJoinSelf. It seems that
thread.join does not stop in Android. This is the only fail when running make
android_ia.release.check. I might spend some time on it after the Mac build
done.

Description:
Android test runner: Update cctest status

Please review this at https://chromiumcodereview.appspot.com/10802030/

SVN Base: http://v8.googlecode.com/svn/branches/bleeding_edge/

Affected files:
  M     test/cctest/cctest.status


Index: test/cctest/cctest.status
===================================================================
--- test/cctest/cctest.status   (revision 12136)
+++ test/cctest/cctest.status   (working copy)
@@ -54,7 +54,7 @@
 test-weakmaps/Shrinking: FAIL

##############################################################################
-[ $arch == arm || $arch == android_arm ]
+[ $arch == arm || $arch == android_arm || $arch == android_ia32 ]

# 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
@@ -62,14 +62,16 @@
 test-api/OutOfMemory: SKIP
 test-api/OutOfMemoryNested: SKIP

-# BUG(355): Test crashes on ARM.
+# On android there is no /tmp directory.
+test-log/LogAccessorCallbacks: SKIP
+test-log/LogCallbacks: SKIP
+
+# platform-tls.h does not contain an ANDROID-related header
+test-platform-tls/FastTLS: SKIP
+
+# BUG(355): Test crashes on ARM and IA32.
 test-log/ProfLazyMode: SKIP

-# BUG(945): Socket connect fails on ARM
-test-debug/DebuggerAgent: SKIP
-test-debug/DebuggerAgentProtocolOverflowHeader: SKIP
-test-sockets/Socket: SKIP
-
 # BUG(1075): Unresolved crashes.
 test-serialize/Deserialize: SKIP
 test-serialize/DeserializeFromSecondSerializationAndRunScript2: SKIP


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

Reply via email to