See 
<https://builds.apache.org/job/Flume-trunk-hbase-1/371/display/redirect?page=changes>

Changes:

[szaboferee] FLUME-2988 Kafka Sink metrics missing eventDrainAttemptCount

------------------------------------------
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on H33 (ubuntu xenial) in workspace 
<https://builds.apache.org/job/Flume-trunk-hbase-1/ws/>
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > http://git-wip-us.apache.org/repos/asf/flume.git # timeout=10
Fetching upstream changes from http://git-wip-us.apache.org/repos/asf/flume.git
 > git --version # timeout=10
 > git fetch --tags --progress http://git-wip-us.apache.org/repos/asf/flume.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse origin/trunk^{commit} # timeout=10
Checking out Revision d8638afd314368128f244b6f53559f09a0d83097 (origin/trunk)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f d8638afd314368128f244b6f53559f09a0d83097
Commit message: "FLUME-2988 Kafka Sink metrics missing eventDrainAttemptCount"
 > git rev-list --no-walk e43000609c2dc357d49fb6aaf375b9ed633fb4e0 # timeout=10
[Flume-trunk-hbase-1] $ /bin/bash -xe /tmp/jenkins7426688088440551432.sh
+ 
OLD_ES_DATA=<https://builds.apache.org/job/Flume-trunk-hbase-1/ws/flume-ng-sinks/flume-ng-elasticsearch-sink/data>
+ '[' -d 
<https://builds.apache.org/job/Flume-trunk-hbase-1/ws/flume-ng-sinks/flume-ng-elasticsearch-sink/data>
 ']'
+ 
OLD_HIVE_DATA=<https://builds.apache.org/job/Flume-trunk-hbase-1/ws/flume-ng-sinks/flume-hive-sink/metastore_db>
+ '[' -d 
<https://builds.apache.org/job/Flume-trunk-hbase-1/ws/flume-ng-sinks/flume-hive-sink/metastore_db>
 ']'
Parsing POMs
ERROR: Failed to parse POMs
java.io.IOException: remote file operation failed: 
<https://builds.apache.org/job/Flume-trunk-hbase-1/ws/> at 
hudson.remoting.Channel@34011fe:H33: hudson.remoting.ProxyException: 
hudson.maven.MavenModuleSetBuild$MavenExecutionException: 
org.apache.maven.project.ProjectBuildingException: Some problems were 
encountered while processing the POMs:
[FATAL] Non-parseable POM 
<https://builds.apache.org/job/Flume-trunk-hbase-1/ws/flume-ng-configuration/pom.xml>:
 only whitespace content allowed before start tag and not 0 (position: 
START_DOCUMENT seen 0... @1:1)  @ line 1, column 1
[FATAL] Non-parseable POM 
<https://builds.apache.org/job/Flume-trunk-hbase-1/ws/flume-ng-clients/flume-ng-log4jappender/pom.xml>:
 only whitespace content allowed before start tag and not 0 (position: 
START_DOCUMENT seen 0... @1:1)  @ line 1, column 1

        at hudson.FilePath.act(FilePath.java:1043)
        at hudson.FilePath.act(FilePath.java:1025)
        at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:986)
        at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:691)
        at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
        at hudson.model.Run.execute(Run.java:1794)
        at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
        at hudson.model.ResourceController.execute(ResourceController.java:97)
        at hudson.model.Executor.run(Executor.java:429)
Caused by: hudson.remoting.ProxyException: 
hudson.maven.MavenModuleSetBuild$MavenExecutionException: 
org.apache.maven.project.ProjectBuildingException: Some problems were 
encountered while processing the POMs:
[FATAL] Non-parseable POM 
<https://builds.apache.org/job/Flume-trunk-hbase-1/ws/flume-ng-configuration/pom.xml>:
 only whitespace content allowed before start tag and not 0 (position: 
START_DOCUMENT seen 0... @1:1)  @ line 1, column 1
[FATAL] Non-parseable POM 
<https://builds.apache.org/job/Flume-trunk-hbase-1/ws/flume-ng-clients/flume-ng-log4jappender/pom.xml>:
 only whitespace content allowed before start tag and not 0 (position: 
START_DOCUMENT seen 0... @1:1)  @ line 1, column 1

        at 
hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1391)
        at 
hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1125)
        at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2918)
        at hudson.remoting.UserRequest.perform(UserRequest.java:212)
        at hudson.remoting.UserRequest.perform(UserRequest.java:54)
        at hudson.remoting.Request$2.run(Request.java:369)
        at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:748)
        Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to 
H33
                at 
hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)
                at 
hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
                at hudson.remoting.Channel.call(Channel.java:955)
                at hudson.FilePath.act(FilePath.java:1036)
                at hudson.FilePath.act(FilePath.java:1025)
                at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:986)
                at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:691)
                at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
                at hudson.model.Run.execute(Run.java:1794)
                at 
hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
                at 
hudson.model.ResourceController.execute(ResourceController.java:97)
                at hudson.model.Executor.run(Executor.java:429)
Caused by: hudson.remoting.ProxyException: 
org.apache.maven.project.ProjectBuildingException: Some problems were 
encountered while processing the POMs:
[FATAL] Non-parseable POM 
<https://builds.apache.org/job/Flume-trunk-hbase-1/ws/flume-ng-configuration/pom.xml>:
 only whitespace content allowed before start tag and not 0 (position: 
START_DOCUMENT seen 0... @1:1)  @ line 1, column 1
[FATAL] Non-parseable POM 
<https://builds.apache.org/job/Flume-trunk-hbase-1/ws/flume-ng-clients/flume-ng-log4jappender/pom.xml>:
 only whitespace content allowed before start tag and not 0 (position: 
START_DOCUMENT seen 0... @1:1)  @ line 1, column 1

        at 
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:364)
        at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361)
        at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:331)
        at 
hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1328)
        ... 10 more
[WARNINGS] Skipping publisher since build result is FAILURE
Archiving artifacts
[JIRA] Updating issue FLUME-2988

Reply via email to