Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id AAAF5200C89 for ; Sat, 3 Jun 2017 23:11:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A94A6160BCD; Sat, 3 Jun 2017 21:11:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id F157D160BB5 for ; Sat, 3 Jun 2017 23:11:08 +0200 (CEST) Received: (qmail 58844 invoked by uid 500); 3 Jun 2017 21:11:08 -0000 Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@phoenix.apache.org Delivered-To: mailing list dev@phoenix.apache.org Received: (qmail 58825 invoked by uid 99); 3 Jun 2017 21:11:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Jun 2017 21:11:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 9B5BA1A0028 for ; Sat, 3 Jun 2017 21:11:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id rVt3PKtwSKZb for ; Sat, 3 Jun 2017 21:11:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 967B65FB8F for ; Sat, 3 Jun 2017 21:11:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id A06E4E00CD for ; Sat, 3 Jun 2017 21:11:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2793220DF5 for ; Sat, 3 Jun 2017 21:11:04 +0000 (UTC) Date: Sat, 3 Jun 2017 21:11:04 +0000 (UTC) From: "Hadoop QA (JIRA)" To: dev@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (PHOENIX-3896) Fix test failures related to tracing changes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 03 Jun 2017 21:11:09 -0000 [ https://issues.apache.org/jira/browse/PHOENIX-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036094#comment-16036094 ] Hadoop QA commented on PHOENIX-3896: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12871124/PHOENIX-3896.004.patch against master branch at commit 2d40241b5c5c0287dca3dd2e2476db328bb7e7de. ATTACHMENT ID: 12871124 {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 6 new or modified tests. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:red}-1 javadoc{color}. The javadoc tool appears to have generated 47 warning messages. {color:red}-1 release audit{color}. The applied patch generated 5 release audit warnings (more than the master's current 0 warnings). {color:red}-1 lineLengths{color}. The patch introduces the following lines longer than 100: + LOG.warn("No receiver has been initialized for TraceWriter. Traces will not be written."); + LOG.error("Tracing will NOT be pursued. New connection failed for tracing Table: " + tableName, e); + TraceWriter traceWriter = new TraceWriter(options.getTableName(), options.getTracingThreadPoolSize(), options.getTracingBatchSize()); {color:red}-1 core tests{color}. The patch failed these unit tests: ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.UpgradeIT ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.MutableIndexFailureIT Test results: https://builds.apache.org/job/PreCommit-PHOENIX-Build/996//testReport/ Release audit warnings: https://builds.apache.org/job/PreCommit-PHOENIX-Build/996//artifact/patchprocess/patchReleaseAuditWarnings.txt Javadoc warnings: https://builds.apache.org/job/PreCommit-PHOENIX-Build/996//artifact/patchprocess/patchJavadocWarnings.txt Console output: https://builds.apache.org/job/PreCommit-PHOENIX-Build/996//console This message is automatically generated. > Fix test failures related to tracing changes > -------------------------------------------- > > Key: PHOENIX-3896 > URL: https://issues.apache.org/jira/browse/PHOENIX-3896 > Project: Phoenix > Issue Type: Bug > Reporter: James Taylor > Assignee: Karan Mehta > Attachments: PHOENIX-3896.001.patch, PHOENIX-3896.002.patch, PHOENIX-3896.003.patch, PHOENIX-3896.004.patch > > > Looks like our unit tests are breaking after these commits: > - PHOENIX-3248 Enable HBase server-side scan metrics to be returned to client and surfaced through metrics > - PHOENIX-3752 Remove hadoop metrics integration from the tracing framework > For example, see https://builds.apache.org/job/Phoenix-master/1628/ and https://builds.apache.org/job/Phoenix-4.x-HBase-1.1/405/. > -- This message was sent by Atlassian JIRA (v6.3.15#6346)