[
https://issues.apache.org/jira/browse/HIVE-21392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787607#comment-16787607
]
Hive QA commented on HIVE-21392:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12961138/HIVE-21392.patch
{color:red}ERROR:{color} -1 due to build exiting with an error
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/16401/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/16401/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-16401/
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'
2019-03-08 06:58:24.996
+ [[ -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-16401/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'
2019-03-08 06:58:24.999
+ cd apache-github-source-source
+ git fetch origin
+ git reset --hard HEAD
HEAD is now at bd95a2f HIVE-21376: Incompatible change in Hive bucket
computation (Jesus Camacho Rodriguez, reviewed by Ashutosh Chauhan)
+ git clean -f -d
Removing standalone-metastore/metastore-server/src/gen/
+ git checkout master
Already on 'master'
Your branch is up-to-date with 'origin/master'.
+ git reset --hard origin/master
HEAD is now at bd95a2f HIVE-21376: Incompatible change in Hive bucket
computation (Jesus Camacho Rodriguez, reviewed by Ashutosh Chauhan)
+ git merge --ff-only origin/master
Already up-to-date.
+ date '+%Y-%m-%d %T.%3N'
2019-03-08 06:58:26.154
+ rm -rf ../yetus_PreCommit-HIVE-Build-16401
+ mkdir ../yetus_PreCommit-HIVE-Build-16401
+ git gc
+ cp -R . ../yetus_PreCommit-HIVE-Build-16401
+ mkdir /data/hiveptest/logs/PreCommit-HIVE-Build-16401/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
fatal: corrupt patch at line 7
fatal: corrupt patch at line 7
fatal: corrupt patch at line 7
The patch does not appear to apply with p0, p1, or p2
+ result=1
+ '[' 1 -ne 0 ']'
+ rm -rf yetus_PreCommit-HIVE-Build-16401
+ exit 1
'
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12961138 - PreCommit-HIVE-Build
> Misconfigurations of DataNucleus log in log4j.properties
> --------------------------------------------------------
>
> Key: HIVE-21392
> URL: https://issues.apache.org/jira/browse/HIVE-21392
> Project: Hive
> Issue Type: Improvement
> Components: Logging
> Affects Versions: 2.0.0
> Reporter: Chen Zhi
> Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-21392.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the patch ofÂ
> [HIVE-12020|https://issues.apache.org/jira/browse/HIVE-12020], we changed the
> DataNucleus related logging configuration from nine fine-grained loggers with
> three coarse-grained loggers (DataNucleus, Datastore and JPOX). As Prasanth
> Jayachandran
> [explain|https://issues.apache.org/jira/browse/HIVE-12020?focusedCommentId=15025612&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15025612],
> these three loggers are the top-level logger in DataNucleus, so that we
> don't need to specify other loggers for DataNucleus. However, according to
> the
> [documents|http://www.datanucleus.org/products/accessplatform/logging.html]
> and [source
> codes|https://github.com/datanucleus/datanucleus-core/blob/master/src/main/java/org/datanucleus/util/NucleusLogger.java#L108]
> of DataNucleus, the top-level logger in DataNucleus is `DataNucleus`.
> Therefore, we just need to keep the right one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
