[ https://issues.apache.org/jira/browse/HBASE-14030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905738#comment-14905738 ]
Hadoop QA commented on HBASE-14030: ----------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12762004/HBASE-14030-v9.patch against master branch at commit 5e26ae043dde217aeda29d9b67e290728adade89. ATTACHMENT ID: 12762004 {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 23 new or modified tests. {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0 2.7.1) {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 protoc{color}. The applied patch does not increase the total number of protoc compiler warnings. {color:red}-1 javadoc{color}. The javadoc tool appears to have generated 8 warning messages. {color:red}-1 checkstyle{color}. The applied patch generated 1832 checkstyle errors (more than the master's current 1807 errors). {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:red}-1 lineLengths{color}. The patch introduces the following lines longer than 100: + public void setIncrTimestampMap(HashMap<String, HashMap<String, String>> newTableSetTimestampMap) { + public static BackupContext fromByteArray(byte[] data) throws IOException, ClassNotFoundException { + public BackupHandler(BackupContext backupContext, BackupManager backupManager, Configuration conf) { + if (!conf.getBoolean(HConstants.BACKUP_ENABLE_KEY, HConstants.BACKUP_ENABLE_DEFAULT)) throw new BackupException( + public void writeRegionServerLastLogRollResult(String server, String fileName) throws IOException { + throw new IOException("data from HBASE_BACKUP is corrupted: " + Arrays.toString(flds)); + if (savedStartCode == null || previousTimestampMins == null || previousTimestampMins.isEmpty()) { + LOG.info("Setting configuration for restore with LoadIncrementalHFile: hbase.rpc.timeout to " + + calculatedMillis / milliSecInMin + " minutes, to handle the number of files in backup " {color:green}+1 site{color}. The mvn post-site goal succeeds with this patch. {color:red}-1 core tests{color}. The patch failed these unit tests: org.apache.hadoop.hbase.master.procedure.TestWALProcedureStoreOnHDFS {color:red}-1 core zombie tests{color}. There are 1 zombie test(s): at org.apache.hadoop.hbase.regionserver.TestHRegion.testFlushCacheWhileScanning(TestHRegion.java:3756) Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/15700//testReport/ Release Findbugs (version 2.0.3) warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/15700//artifact/patchprocess/newFindbugsWarnings.html Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/15700//artifact/patchprocess/checkstyle-aggregate.html Javadoc warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/15700//artifact/patchprocess/patchJavadocWarnings.txt Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/15700//console This message is automatically generated. > HBase Backup/Restore Phase 1 > ---------------------------- > > Key: HBASE-14030 > URL: https://issues.apache.org/jira/browse/HBASE-14030 > Project: HBase > Issue Type: Umbrella > Reporter: Vladimir Rodionov > Assignee: Vladimir Rodionov > Attachments: HBASE-14030-v0.patch, HBASE-14030-v1.patch, > HBASE-14030-v10.patch, HBASE-14030-v2.patch, HBASE-14030-v3.patch, > HBASE-14030-v4.patch, HBASE-14030-v5.patch, HBASE-14030-v6.patch, > HBASE-14030-v7.patch, HBASE-14030-v8.patch, HBASE-14030-v9.patch > > > This is the umbrella ticket for Backup/Restore Phase 1. See HBASE-7912 design > doc for the phase description. -- This message was sent by Atlassian JIRA (v6.3.4#6332)