Comment #1 on issue 21110 by [email protected]: DiskCacheBackendTest.NewEvictionDisableSuccess4 is flaky http://code.google.com/p/chromium/issues/detail?id=21110
Before I forget: The code that is failing is this: entry1->Close(); entry2->Close(); entry3->Close(); MessageLoop::current()->RunAllPending(); EXPECT_EQ(0, cache_->GetEntryCount()); When the last entry is closed, we post a task to the current thread and that task deletes the cache files. If the task doesn't run the last line fails as shown above. All operations from that task are synchronous, except posting another task to actually delete the files, after they've been moved to another folder (hopefully folder rename). The actual deletion (i.e. the execution of that last task) is irrelevant for the success of the test. In other words, I see no reason for the test to fail sometimes (unless RunAllPending is itself unreliable). I'll take another look after my vacation. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
