aboutsummaryrefslogtreecommitdiffhomepage
path: root/tools/valgrind.supp
diff options
context:
space:
mode:
authorGravatar msarett <msarett@google.com>2016-01-04 11:35:43 -0800
committerGravatar Commit bot <commit-bot@chromium.org>2016-01-04 11:35:43 -0800
commitc149f0e36e0ca0ff35ec6e2f79419b58d529db40 (patch)
treef647726a8d28daec63a3bd61812bddd016924021 /tools/valgrind.supp
parent4abb0c11da669a40d126c6b7698e37732e052d84 (diff)
On Valgrind bots, print a message every 20 minutes
I believe that the timeout failure on the Valgrind bot occurs because we skip many tests consecutively without printing any output. Skipping these tests requires non-trivial work. Printing a message every 20 minutes will avoid timeouts. BUG=skia:4740 GOLD_TRYBOT_URL= https://gold.skia.org/search2?unt=true&query=source_type%3Dgm&master=false&issue=1554193002 Review URL: https://codereview.chromium.org/1554193002
Diffstat (limited to 'tools/valgrind.supp')
-rw-r--r--tools/valgrind.supp12
1 files changed, 12 insertions, 0 deletions
diff --git a/tools/valgrind.supp b/tools/valgrind.supp
index 5aee804dd8..4e2dd35f92 100644
--- a/tools/valgrind.supp
+++ b/tools/valgrind.supp
@@ -12,6 +12,18 @@
fun:main
}
+# Intentional thread / memory leak in nanobench.
+{
+ nanobench_keepalive_thread_leak
+ Memcheck:Leak
+ match-leak-kinds: possible
+ ...
+ fun:_ZN8SkThreadC1EPFvPvES0_
+ fun:_ZL15start_keepalivev
+ fun:_Z14nanobench_mainv
+ fun:main
+}
+
# Third party lib, driver issues.
{
ati_driver_bug_1