[ https://issues.apache.org/jira/browse/HIVE-18492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16332704#comment-16332704 ]
Hive QA commented on HIVE-18492: -------------------------------- Here are the results of testing the latest attachment: https://issues.apache.org/jira/secure/attachment/12906794/HIVE-18492.patch {color:red}ERROR:{color} -1 due to build exiting with an error Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/8705/testReport Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/8705/console Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-8705/ Messages: {noformat} Executing org.apache.hive.ptest.execution.TestCheckPhase Executing org.apache.hive.ptest.execution.PrepPhase Tests exited with: NonZeroExitCodeException Command 'bash /data/hiveptest/working/scratch/source-prep.sh' failed with exit status 1 and output '+ date '+%Y-%m-%d %T.%3N' 2018-01-19 18:29:24.456 + [[ -n /usr/lib/jvm/java-8-openjdk-amd64 ]] + export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64 + JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64 + export PATH=/usr/lib/jvm/java-8-openjdk-amd64/bin/:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games + PATH=/usr/lib/jvm/java-8-openjdk-amd64/bin/:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games + export 'ANT_OPTS=-Xmx1g -XX:MaxPermSize=256m ' + ANT_OPTS='-Xmx1g -XX:MaxPermSize=256m ' + export 'MAVEN_OPTS=-Xmx1g ' + MAVEN_OPTS='-Xmx1g ' + cd /data/hiveptest/working/ + tee /data/hiveptest/logs/PreCommit-HIVE-Build-8705/source-prep.txt + [[ false == \t\r\u\e ]] + mkdir -p maven ivy + [[ git = \s\v\n ]] + [[ git = \g\i\t ]] + [[ -z master ]] + [[ -d apache-github-source-source ]] + [[ ! -d apache-github-source-source/.git ]] + [[ ! -d apache-github-source-source ]] + date '+%Y-%m-%d %T.%3N' 2018-01-19 18:29:24.459 + cd apache-github-source-source + git fetch origin >From https://github.com/apache/hive d6c6d96..41a5c06 master -> origin/master + git reset --hard HEAD HEAD is now at d6c6d96 HIVE-18222: Update checkstyle rules to be less peeky (Zoltan Haindrich reviewed by Ashutosh Chauhan) + git clean -f -d + git checkout master Already on 'master' Your branch is behind 'origin/master' by 1 commit, and can be fast-forwarded. (use "git pull" to update your local branch) + git reset --hard origin/master HEAD is now at 41a5c06 HIVE-18482: Copy-paste error in the RelOptHiveTable (Jesus Camacho Rodriguez, reviewed by Ashutosh Chauhan) + git merge --ff-only origin/master Already up-to-date. + date '+%Y-%m-%d %T.%3N' 2018-01-19 18:29:31.074 + rm -rf ../yetus + mkdir ../yetus + git gc + cp -R . ../yetus + mkdir /data/hiveptest/logs/PreCommit-HIVE-Build-8705/yetus + patchCommandPath=/data/hiveptest/working/scratch/smart-apply-patch.sh + patchFilePath=/data/hiveptest/working/scratch/build.patch + [[ -f /data/hiveptest/working/scratch/build.patch ]] + chmod +x /data/hiveptest/working/scratch/smart-apply-patch.sh + /data/hiveptest/working/scratch/smart-apply-patch.sh /data/hiveptest/working/scratch/build.patch error: patch failed: ql/src/java/org/apache/hadoop/hive/ql/exec/tez/WorkloadManager.java:2127 error: repository lacks the necessary blob to fall back on 3-way merge. error: ql/src/java/org/apache/hadoop/hive/ql/exec/tez/WorkloadManager.java: patch does not apply error: src/java/org/apache/hadoop/hive/ql/exec/tez/WorkloadManager.java: does not exist in index error: java/org/apache/hadoop/hive/ql/exec/tez/WorkloadManager.java: does not exist in index The patch does not appear to apply with p0, p1, or p2 + exit 1 ' {noformat} This message is automatically generated. ATTACHMENT ID: 12906794 - PreCommit-HIVE-Build > Wrong argument in the WorkloadManager.resetAndQueryKill() > --------------------------------------------------------- > > Key: HIVE-18492 > URL: https://issues.apache.org/jira/browse/HIVE-18492 > Project: Hive > Issue Type: Bug > Reporter: Oleg Danilov > Priority: Trivial > Attachments: HIVE-18492.patch > > > Caused by HIVE-18088, [~prasanth_j], could you please check this? > {code:java} > private void resetAndQueueKill(Map<WmTezSession, KillQueryContext> > toKillQuery, > KillQueryContext killQueryContext, Map<WmTezSession, GetRequest> toReuse) { > WmTezSession toKill = killQueryContext.session; > ... > if (poolState != null) { > poolState.getSessions().remove(toKill); > poolState.getInitializingSessions().remove(toKill); > ... > {code} > getInitializingSessions() returns List of SessionInitContext, so toKill > definitely can't be in this list and therefore no needs to remove it. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)