There are a bunch of flaky failures on the DrMemory bots that I fail to understand. The earliest occurence started here: https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Unit%20%28DrMemory%20full%29%20%282%29/builds/10766 with one CL and that particular CL is unrelated to the issues. More details: https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Unit%20%28DrMemory%20full%29%20%282%29/builds/10791 reports several unit failures and these stack traces are not useful to me: https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Unit%20%28DrMemory%20full%29%20%284%29/builds/10379/steps/memory%20test%3A%20unit/logs/64FDD32B9D6AAB31 https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Unit%20%28DrMemory%20full%29%20%284%29/builds/10379/steps/memory%20test%3A%20unit/logs/64FDD32B9D6AAB31 I am having a hard time understanding those...
There are also these browser failures that I fail to understand: For example: https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Browser%20%28DrMemory%20full%29%20%282%29/builds/3563/steps/memory%20test%3A%20browser_tests_2/logs/7A55BCF6BC4F2D8E and the list is at: https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Browser%20%28DrMemory%20full%29%20%282%29/builds/3563
I clobbered the builder and the tester bots have been happy since then.
Comment 1 by isheriff@chromium.org
, May 25 2016