[ 
https://issues.apache.org/jira/browse/HIVE-19685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16496987#comment-16496987
 ] 

Hive QA commented on HIVE-19685:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12925570/hive-19685.patch

{color:red}ERROR:{color} -1 due to build exiting with an error

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/11390/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/11390/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-11390/

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-05-31 18:37:54.619
+ [[ -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-11390/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-05-31 18:37:54.622
+ cd apache-github-source-source
+ git fetch origin
+ git reset --hard HEAD
HEAD is now at 338a2d4 HIVE-19529: Vectorization: Date/Timestamp NULL issues 
(Matt McCline, reviewed by Teddy Choi)
+ git clean -f -d
+ git checkout master
Already on 'master'
Your branch is up-to-date with 'origin/master'.
+ git reset --hard origin/master
HEAD is now at 338a2d4 HIVE-19529: Vectorization: Date/Timestamp NULL issues 
(Matt McCline, reviewed by Teddy Choi)
+ git merge --ff-only origin/master
Already up-to-date.
+ date '+%Y-%m-%d %T.%3N'
2018-05-31 18:37:55.822
+ rm -rf ../yetus_PreCommit-HIVE-Build-11390
+ mkdir ../yetus_PreCommit-HIVE-Build-11390
+ git gc
+ cp -R . ../yetus_PreCommit-HIVE-Build-11390
+ mkdir /data/hiveptest/logs/PreCommit-HIVE-Build-11390/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: standalone-metastore/pom.xml:80
Falling back to three-way merge...
Applied patch to 'standalone-metastore/pom.xml' with conflicts.
Going to apply patch with: git apply -p0
error: patch failed: standalone-metastore/pom.xml:80
Falling back to three-way merge...
Applied patch to 'standalone-metastore/pom.xml' with conflicts.
U standalone-metastore/pom.xml
+ result=1
+ '[' 1 -ne 0 ']'
+ rm -rf yetus_PreCommit-HIVE-Build-11390
+ exit 1
'
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12925570 - PreCommit-HIVE-Build

> OpenTracing support for HMS
> ---------------------------
>
>                 Key: HIVE-19685
>                 URL: https://issues.apache.org/jira/browse/HIVE-19685
>             Project: Hive
>          Issue Type: New Feature
>          Components: Metastore
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Major
>         Attachments: hive-19685.patch, hive-19685.patch, trace.png
>
>
> When diagnosing performance of metastore operations it isn't always obvious 
> why something took a long time. Using a tracing framework can provide an 
> end-to-end view of an operation including time spent in dependent systems (eg 
> filesystem operations, RDBMS queries, etc). This JIRA proposes to integrate 
> OpenTracing, which is a vendor-neutral tracing API into the HMS server and 
> client.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to