From 8a6899f95af7a59b52530e1ca2d662b40ed0abe1 Mon Sep 17 00:00:00 2001 From: Amar Tumballi Date: Sat, 15 Jun 2019 21:23:13 +0530 Subject: clang-scan: make the threashold as 65 from 140 So, we just need to watch for job failure if the number goes up. Currently the number is 61, and around 55 of them are marked as false positives. Change-Id: I37ea5d3f27401c79d8f7b34b1ab9d67b3166e34a Signed-off-by: Amar Tumballi --- build-gluster-org/jobs/clang.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'build-gluster-org') diff --git a/build-gluster-org/jobs/clang.yml b/build-gluster-org/jobs/clang.yml index 714dbcd..dce5a11 100644 --- a/build-gluster-org/jobs/clang.yml +++ b/build-gluster-org/jobs/clang.yml @@ -19,7 +19,7 @@ publishers: - scan-build: mark-unstable: true - threshold: 140 + threshold: 65 - post-tasks: - matches: - log-text: Building remotely -- cgit