I don't quite know how to solve the problem. When IN_PROC_BROWSER_TEST is used, a launcher that will isolate the test cases should be used (like running them in forked processes or reloading a dll). However, currently only browser_tests binary does that. Other users, sync_integration_tests and interactive_ui_tests, don't. This is a fantastic recipe for flakiness. In-process browser test carries a lot of state, all the singletons, etc. It does cause problems if not cleaned up properly, and I removed that kind of problem from unit_tests (and introduced ALLOW_IN_PROC_BROWSER_TEST to prevent the problem from growing).
The problem is, that the mentioned binaries mix UI tests with browser tests. So it's not trivially possible to use browser_tests launcher for them (or maybe it is?). What do you think? --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
