On Mon, Oct 5, 2009 at 8:18 PM, Matt Mueller <[email protected]> wrote: > > This night xp purify failed with a bunch of new leaks: > http://build.chromium.org/buildbot/waterfall/builders/XP%20Unit%20(purify)/builds/5856/steps/purify%20test:%20unit/logs/stdio > > After looking at the stdio for the 10th time I finally saw that the > test didn't exit cleanly, which would explain why atexit and singleton > stuff showed up so much in the leaks.
Yes, any time the tests crash, you can't trust any memory leak errors from Purify. Unfortunately, so far we haven't found a clean way to detect crashes from these scripts. It gets complicated when there are multiple child processes, etc. > The last lines were: > [----------] 2 tests from DnsMasterTest > [ RUN ] DnsMasterTest.ConcurrentLookupTest > ERROR:root:src/build\Release\unit_tests.exe exited with non-zero > result code -1073741819 > > Is this sufficient to blame the flakiness on that test, or are the > logs buffered so it might have actually died in some other test? This should be sufficient. We collect all of the output from the test and flush it all. So this is the test it crashed on. Erik --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
