The valgrind logs for ui tests now show the command that had the problem. Because we valgrind ui tests individually, that shows the exact test. Example: http://build.chromium.org/buildbot/waterfall.fyi/builders/Mac%20UI%202%20of%203%20(valgrind)/builds/1057/steps/valgrind%20test:%20ui/logs/stdio shows
Command: /b/slave/chromium-rel-mac-valgrind-ui-2/build/src/xcodebuild/Debug/Chromium.app/Contents/MacOS/Chromium --no-first-run --no-default-browser-check --enable-file-cookies --dom-automation --testing-channel=ChromeTestingInterface:34281.28 --homepage=about:blank --disable-web-resources --user-data-dir=/var/folders/fP/fPz9MO3KEtySRZwaMV0nrk+++TM/-Tmp-/org.chromium.421eY9/test_user_data --metrics-recording-only --enable-logging --test-name=V8BenchmarkTest.Perf 20 bytes in 1 blocks are definitely lost in loss record 1,138 of 5,972 operator new(unsigned long) (sers/chrome-bot/valgrind-10771/coregrind/m_replacemalloc/vg_replace_malloc.c:220) getAllCarbonLazyValues2000() CLVVisitValuesForKey INIT_ResourceManager CurResFile NPAPI::(anonymous namespace)::ReadSTRPluginInfo(FilePath const&, __CFBundle*, WebPluginInfo*) (/b/slave/chromium-rel-mac-valgrind-ui-2/build/src/webkit/glue/plugins/plugin_lib_mac.mm:128) ... so you know that the error happened in V8BenchmarkTest.Perf. (It's a bit annoying that the commandline is so long, and the test name is at the end of the long line. I'd be happy to improve the presentation of the test name if folks want, just let me know.) --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
