[
https://issues.apache.org/jira/browse/HIVE-14669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16815520#comment-16815520
]
Hive QA commented on HIVE-14669:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12965605/Screen%20Shot%202019-04-11%20at%204.54.41%20PM.png
{color:red}ERROR:{color} -1 due to build exiting with an error
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/16924/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/16924/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-16924/
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-04-11 15:49:18.487
+ [[ -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-16924/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-04-11 15:49:18.490
+ cd apache-github-source-source
+ git fetch origin
+ git reset --hard HEAD
HEAD is now at 6a9e17c HIVE-21427: Syslog storage handler (Prasanth
Jayachandran reviewed by Jason Dere)
+ 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 6a9e17c HIVE-21427: Syslog storage handler (Prasanth
Jayachandran reviewed by Jason Dere)
+ git merge --ff-only origin/master
Already up-to-date.
+ date '+%Y-%m-%d %T.%3N'
2019-04-11 15:49:19.671
+ rm -rf ../yetus_PreCommit-HIVE-Build-16924
+ mkdir ../yetus_PreCommit-HIVE-Build-16924
+ git gc
+ cp -R . ../yetus_PreCommit-HIVE-Build-16924
+ mkdir /data/hiveptest/logs/PreCommit-HIVE-Build-16924/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: unrecognized input
fatal: unrecognized input
fatal: unrecognized input
The patch does not appear to apply with p0, p1, or p2
+ result=1
+ '[' 1 -ne 0 ']'
+ rm -rf yetus_PreCommit-HIVE-Build-16924
+ exit 1
'
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12965605 - PreCommit-HIVE-Build
> Have the actual error reported when a q test fails instead of having to go
> through the logs
> -------------------------------------------------------------------------------------------
>
> Key: HIVE-14669
> URL: https://issues.apache.org/jira/browse/HIVE-14669
> Project: Hive
> Issue Type: Sub-task
> Reporter: Siddharth Seth
> Assignee: Laszlo Bodor
> Priority: Major
> Attachments: 01_mvn_out.png, 02_hive_log.png, HIVE-14469.01.patch,
> Screen Shot 2019-04-11 at 4.54.41 PM.png
>
>
> QTest runs end up invoking CliDriver.processLine. This, in most cases,
> reports a numeric exit code - 0 for success. Non-zero for various different
> error types (which are defined everywhere in the code).
> Internally CliDriver does have more information via CommandResult. A lot of
> this is not exposed though. That's alright for the end user cli - (Command
> line tool translating the error to a code and message). However, it makes
> debugging very difficult for QTests - since the log needs to be looked at
> each time.
> Errors generated by the actual backend execution are mostly available to the
> client, and information about these should show up as well. (If it doesn't -
> we have a usability issues to fix).
> cc [~ekoifman]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
