This is related to bug 25997. The tests are inherently flakey because
singeltons aren't released between runs, so cached MessageLoop pointers are
bogus. Sometimes they're ok when the order of construction/destruction of
MessageLoop pointers is the same. But if that changes, or other memory
allocations change, the tests start failing.
Just wanted to send a heads up since I spent a day debugging this last week,
and now they're failing again.
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
