Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 71A33EBD1 for ; Wed, 16 Jan 2013 18:39:26 +0000 (UTC) Received: (qmail 37547 invoked by uid 500); 16 Jan 2013 18:39:25 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 37483 invoked by uid 500); 16 Jan 2013 18:39:25 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 37475 invoked by uid 99); 16 Jan 2013 18:39:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Jan 2013 18:39:25 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of saint.ack@gmail.com designates 209.85.214.41 as permitted sender) Received: from [209.85.214.41] (HELO mail-bk0-f41.google.com) (209.85.214.41) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Jan 2013 18:39:19 +0000 Received: by mail-bk0-f41.google.com with SMTP id jg9so890652bkc.14 for ; Wed, 16 Jan 2013 10:38:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=XS2uUDDr+4Q5G8b1/uA1pjA1FrdTyT8PeOuphZC2M7k=; b=gpby9FNEEdUy22NiCRNwA2ltqFcoV62Y9IVF4z3NEXvr5YigbJ8DAEUlT8SggZaQOJ 0J5K5bJaM8Z2eSTrOGXFS1mF4WenhV76xwZT9VGRG44lalmomE8FQ4FKLUe92J1Ti3mA lgJP/0ql63WuXea4zhyW+YbrfTKfh/4Pyld2k1xGclWn58PTXAx9uNLCphEL63dJFT5R SSkDD8beg18EPWG3r7qOEQgq3EtXcv/WkXGq1+ca2a2Wwa46YwfnHH9KAG+nZmLl94Pd xTzaT4Zhv0IDK9NTPoRi807bcFS2JCddYw/3iefSND3i7XCzyb22xNpH79mw5OtPnac3 ycRw== MIME-Version: 1.0 X-Received: by 10.204.4.145 with SMTP id 17mr779393bkr.34.1358361537818; Wed, 16 Jan 2013 10:38:57 -0800 (PST) Sender: saint.ack@gmail.com Received: by 10.205.39.135 with HTTP; Wed, 16 Jan 2013 10:38:57 -0800 (PST) Date: Wed, 16 Jan 2013 10:38:57 -0800 X-Google-Sender-Auth: QHvheFoOysnXWPkrIVjsbYEvrtc Message-ID: Subject: Findbugs From: Stack To: HBase Dev List Content-Type: multipart/alternative; boundary=001517588e78f02f2f04d36c3057 X-Virus-Checked: Checked by ClamAV on apache.org --001517588e78f02f2f04d36c3057 Content-Type: text/plain; charset=UTF-8 Findbug count is starting to rise again. Us fellas doing the committing have let a few slip through. We need to be more vigilant. What is the best way evaluating a patch post commit when findbugs warnings is not zero? As soon as one findbugs item comes in, because findbugs still reports many issues masked by the tolerated count over in dev-tools/test.patch#OK_FINDBUGS_WARNINGS, it is hard to figure the culprit given findbugs:findbugs dumps out xml with OK_FINDBUGS_WARNINGS issues. Any pointers? Meantime let me set the warnings back to zero. St.Ack --001517588e78f02f2f04d36c3057--