Commit adfa56af authored by dslomov@chromium.org's avatar dslomov@chromium.org

Speculative fix fo MultithreadedParallelIsolates on ARM

It looks like the problem with the test is too many concurrently created isolates.
Cranking the number to 100 on MacOS and Linux produce similar results.

BUG=http://code.google.com/p/v8/issues/detail?id=1375
TBR=vitalyr

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@7869 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
parent 4e18d508
......@@ -52,9 +52,6 @@ test-func-name-inference/PassedAsConstructorParameter: FAIL
##############################################################################
[ $arch == arm ]
# BUG(1375): Test crashes on ARM.
test-lockers/MultithreadedParallelIsolates: 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.
......
......@@ -240,7 +240,11 @@ class IsolateNonlockingThread : public JoinableThread {
// Run many threads each accessing its own isolate without locking
TEST(MultithreadedParallelIsolates) {
#ifdef V8_TARGET_ARCH_ARM
const int kNThreads = 10;
#else
const int kNThreads = 50;
#endif
i::List<JoinableThread*> threads(kNThreads);
for (int i = 0; i < kNThreads; i++) {
threads.Add(new IsolateNonlockingThread());
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment