Make TestSetJitCodeEventHandler more resilient.
authormstarzinger <mstarzinger@chromium.org>
Fri, 23 Jan 2015 12:12:12 +0000 (04:12 -0800)
committerCommit bot <commit-bot@chromium.org>
Fri, 23 Jan 2015 12:12:27 +0000 (12:12 +0000)
R=ishell@chromium.org
TEST=cctest/test-api/SetJitCodeEventHandler

Review URL: https://codereview.chromium.org/874493002

Cr-Commit-Position: refs/heads/master@{#26249}

test/cctest/test-api.cc

index 410c2e1..b3d91b0 100644 (file)
@@ -15104,6 +15104,9 @@ UNINITIALIZED_TEST(SetJitCodeEventHandler) {
   i::Isolate* i_isolate = reinterpret_cast<i::Isolate*>(isolate);
   i::Heap* heap = i_isolate->heap();
 
+  // Start with a clean slate.
+  heap->CollectAllAvailableGarbage("TestSetJitCodeEventHandler_Prepare");
+
   {
     v8::HandleScope scope(isolate);
     i::HashMap code(MatchPointers);
@@ -15137,7 +15140,7 @@ UNINITIALIZED_TEST(SetJitCodeEventHandler) {
     }
 
     // Force code movement.
-    heap->CollectAllAvailableGarbage("TestSetJitCodeEventHandler");
+    heap->CollectAllAvailableGarbage("TestSetJitCodeEventHandler_Move");
 
     isolate->SetJitCodeEventHandler(v8::kJitCodeEventDefault, NULL);