Hive QA commented on HIVE-14891:

Here are the results of testing the latest attachment:

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

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

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'
2016-10-14 03:11:13.999
+ [[ -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 
+ export 'ANT_OPTS=-Xmx1g -XX:MaxPermSize=256m '
+ ANT_OPTS='-Xmx1g -XX:MaxPermSize=256m '
+ export 'M2_OPTS=-Xmx1g -XX:MaxPermSize=256m -Dhttp.proxyHost=localhost 
+ M2_OPTS='-Xmx1g -XX:MaxPermSize=256m -Dhttp.proxyHost=localhost 
+ cd /data/hiveptest/working/
+ tee /data/hiveptest/logs/PreCommit-HIVE-Build-1553/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'
2016-10-14 03:11:14.001
+ cd apache-github-source-source
+ git fetch origin
+ git reset --hard HEAD
HEAD is now at 5353161 HIVE-14835: Improve ptest2 build time (Prasanth 
Jayachandran reviewed by Sergio Pena)
+ 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 5353161 HIVE-14835: Improve ptest2 build time (Prasanth 
Jayachandran reviewed by Sergio Pena)
+ git merge --ff-only origin/master
Already up-to-date.
+ date '+%Y-%m-%d %T.%3N'
2016-10-14 03:11:14.835
+ 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 
Going to apply patch with: patch -p1
patching file 
patching file 
patching file 
patching file 
patching file 
patching file 
patching file 
patching file 
+ [[ maven == \m\a\v\e\n ]]
+ rm -rf /data/hiveptest/working/maven/org/apache/hive
+ mvn -B clean install -DskipTests -T 4 -q 
[ERROR] Failed to execute goal on project hive-shims-scheduler: Could not 
resolve dependencies for project 
org.apache.hive.shims:hive-shims-scheduler:jar:2.2.0-SNAPSHOT: The following 
artifacts could not be resolved: 
org.apache.hadoop:hadoop-yarn-server-nodemanager:jar:2.7.2: Failure to find 
org.apache.hadoop:hadoop-yarn-server-resourcemanager:jar:2.7.2 in 
http://www.datanucleus.org/downloads/maven2 was cached in the local repository, 
resolution will not be reattempted until the update interval of datanucleus has 
elapsed or updates are forced -> [Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :hive-shims-scheduler
+ exit 1

This message is automatically generated.

ATTACHMENT ID: 12833268 - PreCommit-HIVE-Build

> Parallelize TestHCatStorer
> --------------------------
>                 Key: HIVE-14891
>                 URL: https://issues.apache.org/jira/browse/HIVE-14891
>             Project: Hive
>          Issue Type: Sub-task
>          Components: HCatalog, Testing Infrastructure
>    Affects Versions: 2.1.0
>            Reporter: Vaibhav Gumashta
>            Assignee: Vaibhav Gumashta
>         Attachments: HIVE-14891.1.patch
> Currently TestHCatStorer runs as a parameterized test, where it runs the same 
> tests for each storage format but within the same junit test case. This 
> prevents it from being parallelized using ptest where parallelism granularity 
> is at a test case level. Instead of using parameterized tests, it makes sense 
> to create a new test case for each storage format.

This message was sent by Atlassian JIRA

Reply via email to