Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(7516)

Unified Diff: chrome/test/data/valgrind/ui_tests.gtest-tsan.txt

Issue 345039: Don't run reference tests under Valgrind (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src/
Patch Set: Created 11 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « chrome/test/data/valgrind/ui_tests.gtest.txt ('k') | chrome/test/data/valgrind/ui_tests.gtest_mac.txt » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: chrome/test/data/valgrind/ui_tests.gtest-tsan.txt
===================================================================
--- chrome/test/data/valgrind/ui_tests.gtest-tsan.txt (revision 30697)
+++ chrome/test/data/valgrind/ui_tests.gtest-tsan.txt (working copy)
@@ -1,3 +0,0 @@
-# The reference builds give numerous reports under ThreadSanitizer
-# TODO(timurrrr): do we need to run ReferenceTests under Valgrind at all?
-DromaeoReferenceTest.Perf
« no previous file with comments | « chrome/test/data/valgrind/ui_tests.gtest.txt ('k') | chrome/test/data/valgrind/ui_tests.gtest_mac.txt » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698