Oliver Draese created HIVE-22617:
Summary: Re-Enable PreCommit test
org.apache.hadoop.hive.ql.TestMTQueries.testMTQueries1
Key: HIVE-22617
URL: https://issues.apache.org/jira/browse/HIVE-22617
Oliver Draese created HIVE-22616:
Summary: Disable PreCommit test
org.apache.hadoop.hive.ql.TestMTQueries.testMTQueries1
Key: HIVE-22616
URL: https://issues.apache.org/jira/browse/HIVE-22616
Project
day, October 19, 2016 at 14:20
> *To: *Wei Zheng
> *Cc: *"dev@hive.apache.org"
> *Subject: *Re: Precommit test on a feature branch
>
>
>
> Done. I added the hive-14535-mr2.properties file.
>
>
>
> You can now attach a patch like 'HIVE--hive-145
Great! Thanks! So this is where I will be looking for my Jenkins job?
https://builds.apache.org/view/H-L/view/Hive/job/HIVE-Branch-Test/
Thanks,
Wei
From: Sergio Pena
Date: Wednesday, October 19, 2016 at 14:20
To: Wei Zheng
Cc: "dev@hive.apache.org"
Subject: Re: Precommit test on
Thanks,
>
> Wei
>
>
>
> *From: *Sergio Pena
> *Date: *Wednesday, October 19, 2016 at 13:15
> *To: *Wei Zheng
> *Cc: *"dev@hive.apache.org"
> *Subject: *Re: Precommit test on a feature branch
>
>
>
> There are 2 ways:
>
>
>
> A) Execu
Thanks Sergio. The branch we want to do test on is “hive-14535”. Appreciate
your help!
Thanks,
Wei
From: Sergio Pena
Date: Wednesday, October 19, 2016 at 13:15
To: Wei Zheng
Cc: "dev@hive.apache.org"
Subject: Re: Precommit test on a feature branch
There are 2 ways:
A) Execute
16 at 12:53 PM, Wei Zheng wrote:
> Is there a way to run precommit test against a feature branch?
>
>
>
>
>
> Thanks,
>
> Wei
>
Is there a way to run precommit test against a feature branch?
Thanks,
Wei
Ptest is working now. !!!
On Thu, Jul 7, 2016 at 4:04 PM, Sergio Pena
wrote:
> I'm taking a look. Seems the ptest server is down for an unknown reason,
> not accepting ssh connections.
>
> On Wed, Jul 6, 2016 at 3:06 PM, Wei Zheng wrote:
>
>> Can someone take a look please?
>>
>>
>> + java -cp
I'm taking a look. Seems the ptest server is down for an unknown reason,
not accepting ssh connections.
On Wed, Jul 6, 2016 at 3:06 PM, Wei Zheng wrote:
> Can someone take a look please?
>
>
> + java -cp 'target/hive-ptest-1.0-classes.jar:target/lib/*'
> org.apache.hive.ptest.api.client.PTestCli
Can someone take a look please?
+ java -cp 'target/hive-ptest-1.0-classes.jar:target/lib/*'
org.apache.hive.ptest.api.client.PTestClient --endpoint
http://ec2-50-18-27-0.us-west-1.compute.amazonaws.com:8181/hive-ptest-1.0
--logsEndpoint http://ec2-50-18-27-0.us-west-1.compute.amazonaws.com/log
Created HIVE-13402 to disable the tests. Have narrowed it down to 3 hanging
tests. From what I understand the TestVectorTimestampExpressions tests have
already been fixed.
On Tue, Mar 29, 2016 at 10:27 AM, Ashutosh Chauhan
wrote:
> I agree with disabling these tests till we are able to fix it. S
I agree with disabling these tests till we are able to fix it. Since bug
seems to be in spark runtime, it may take a little while to fix it.
Increased run time for QA till then would be waste of resources.
Thanks,
Ashutosh
On Tue, Mar 29, 2016 at 9:06 AM, Siddharth Seth wrote:
> Thanks Szehon.
Thanks Szehon. Should we disable the tests while the issue is resolved.
There's a backlog of 17 patches - which will take over 2 days to run at
this point.
Also, HIVE-13365 ended up running for over 8 hours yesterday. Maybe we
should put a cap on max runtime for a single run. Anyone know how to do
Yea we looked at it before.. its tracked by HIVE-13223, caused by
HIVE-13040.
Because it hangs these tests take 2 hours max now before they are killed,
hence each run taking over 3 hours.
Ashutosh is looking I believe, I havent had a chance to take a look myself.
Szehon
On Mon, Mar 28, 2016 at
There's several tests which are failing consistently. Should we disable
these and create blocker jiras to fix and enable thees for the next
release. The list of test is at the end of the mail.
Also, each pre-commit run seems to be taking over 3 hours. Is this normal ?
Having test results come back
>
>> HIVE-11786
>> HIVE-11684
>> HIVE-11976
>> HIVE-11973
>> HIVE-11995
>>
>> - Prasanth
>>
>>> On Oct 1, 2015, at 5:00 PM, Szehon Ho wrote:
>>>
>>> Hm.. I'll take a look.
>>>
>>> On Thu, O
:
> >
> > Hm.. I'll take a look.
> >
> > On Thu, Oct 1, 2015 at 2:58 PM, Prasanth Jayachandran <
> > pjayachand...@hortonworks.com> wrote:
> >
> >> For HIVE-11928, precommit test ran but when it tried to post back the
> test
> >> re
orks.com> wrote:
>
>> For HIVE-11928, precommit test ran but when it tried to post back the test
>> result to JIRA, it failed with the following exception
>>
>>
>> ATTACHMENT ID: 12764451 - PreCommit-HIVE-TRUNK-Build
>> 2015-10-01 13:16:51,702 ERROR
Hm.. I'll take a look.
On Thu, Oct 1, 2015 at 2:58 PM, Prasanth Jayachandran <
pjayachand...@hortonworks.com> wrote:
> For HIVE-11928, precommit test ran but when it tried to post back the test
> result to JIRA, it failed with the following exception
>
>
> ATTACHMEN
For HIVE-11928, precommit test ran but when it tried to post back the test
result to JIRA, it failed with the following exception
ATTACHMENT ID: 12764451 - PreCommit-HIVE-TRUNK-Build
2015-10-01 13:16:51,702 ERROR JIRAService.postComment:176 Encountered error
attempting to post comment to HIVE
Not really sure. Checked the build box's client-side locales and they are
pretty standard (en_US.UTF8). I think if its a client side issue, it would
be saying "Error converting UTF-8 to native", but its the other way around,
saying "Error converting native to UTF8". But I'm not an expert on this
this was added in https://issues.apache.org/jira/browse/HIVE-9272. The
build bot ran fine with the patch. I also ran "mvn clean package install
-Phadoop-2,dist -DskipTests".
Does anyone have ideas on why this is an issue?
On Wed, Jan 21, 2015 at 10:52 AM, Brock Noland wrote:
> Thank you Szeho
Thank you Szehon! I also could not reproduce manually. I went and did
rm -rf $(svn status --no-ignore)
svn status --no-ignore
manually. I hope that fixes it.
On Tue, Jan 20, 2015 at 11:23 PM, Szehon Ho wrote:
> The builds have been hitting some strange error in trying to update the
> sour
The builds have been hitting some strange error in trying to update the
source in svn due to the new test files added in hcatalog in different
locales.
I wasn't able to reproduce the issue manually and dont know the exact
cause, but just FYI that the builds are broken now.
Thanks
Szehon
++ svn s
tch precommit test from local to local-cluster [Spark Branch]
>
>
> Key: HIVE-8795
> URL: https://issues.apache.org/jira/browse/HIVE-8795
> Project: Hive
>
is is possible.
> Switch precommit test from local to local-cluster [Spark Branch]
>
>
> Key: HIVE-8795
> URL: https://issues.apache.org/jira/browse/HIVE-8795
> Project: Hive
case?
> Switch precommit test from local to local-cluster [Spark Branch]
>
>
> Key: HIVE-8795
> URL: https://issues.apache.org/jira/browse/HIVE-8795
> Project: Hive
>
l-cluster. The default can be still
spark.master=local, so that devs are not required to have such settings in
their environments for unit tests, unless one wants to test with local-cluster
specifically. I assume this can be achieved.
> Switch precommit test from local to local-cluster [
work (after Rui and my
attempts) as some spark code was looking for a spark script in a predefined
path. Did something change in the meantime?
> Switch precommit test from local to local-cluster [Spark Branch]
>
>
>
[
https://issues.apache.org/jira/browse/HIVE-8795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuefu Zhang reassigned HIVE-8795:
-
Assignee: Szehon Ho
> Switch precommit test from local to local-cluster [Spark Bra
k? I think we we can make this
configurable so that pre-commit test runs with local-cluster while developers
still use local (default). Thanks.
> Switch precommit test from local to local-cluster [Spark Branch]
>
>
>
[
https://issues.apache.org/jira/browse/HIVE-8795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuefu Zhang updated HIVE-8795:
--
Issue Type: Sub-task (was: Task)
Parent: HIVE-7292
> Switch precommit test from local to lo
Xuefu Zhang created HIVE-8795:
-
Summary: Switch precommit test from local to local-cluster [Spark
Branch]
Key: HIVE-8795
URL: https://issues.apache.org/jira/browse/HIVE-8795
Project: Hive
Issue
[
https://issues.apache.org/jira/browse/HIVE-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuefu Zhang reassigned HIVE-6293:
-
Assignee: Xuefu Zhang
> Not all minimr tests are executed or reported in precommit test
sts are executed or reported in precommit test run
> ---
>
> Key: HIVE-6293
> URL: https://issues.apache.org/jira/browse/HIVE-6293
> Project: Hive
> Issue Type:
test failures, and leave this to track
the other issue.
> Not all minimr tests are executed or reported in precommit test run
> ---
>
> Key: HIVE-6293
> URL: https://issues.apache.org/ji
ch to fix those failures for now so that all miniMR
tests can be enabled for the build. I'll create a separated JIRA to track the
proposal of separate directory for miniMR tests.
> Not all minimr tests are executed or reported in p
d, just not in the error message. They should use a
different directory like:
hdfs://tmp/test_load_hdfs_file_with_space
> Not all minimr tests are executed or reported in precommit test run
> ---
>
>
ported_table.q-load_hdfs_file_with_space_in_the_name.q-and-1-more/TEST-TestMinimrCliDriver-groupby2.q-import_exported_table.q-load_hdfs_file_with_space_in_the_name.q-and-1-more-TEST-org.apache.hadoop.hive.cli.TestMinimrCliDriver.xml
> Not all minimr tests are executed or reported in p
s are executed or reported in precommit test run
> ---
>
> Key: HIVE-6293
> URL: https://issues.apache.org/jira/browse/HIVE-6293
> Project: Hive
> Issue Type:
all tests are enabled, all
complaining ${system:test.dfs.mkdir} in the script. However, these tests passed
locally, and the system var is defined in qtest pom.xml. What's wrong with
ptest for not taking this var?
> Not all minimr tests are executed or reported in precom
ange would be required.
> Not all minimr tests are executed or reported in precommit test run
> ---
>
> Key: HIVE-6293
> URL: https://issues.apache.org/jira/browse/HIVE-6293
>
mr tests are executed or reported in precommit test run
> ---
>
> Key: HIVE-6293
> URL: https://issues.apache.org/jira/browse/HIVE-6293
> Project: Hive
> Issue T
r tests are executed or reported in precommit test run
> ---
>
> Key: HIVE-6293
> URL: https://issues.apache.org/jira/browse/HIVE-6293
> Project: Hive
> Issue Type:
or of the file move.
> Not all minimr tests are executed or reported in precommit test run
> ---
>
> Key: HIVE-6293
> URL: https://issues.apache.org/jira/browse/HIVE-6293
>
.org/confluence/display/Hive/MiniMR+and+PTest2 to expain
this. I linked it from the Precommit page and the FAQ.
> Not all minimr tests are executed or reported in precommit test run
> ---
>
> Key: HIVE-6293
>
Xuefu Zhang created HIVE-6293:
-
Summary: Not all minimr tests are executed or reported in
precommit test run
Key: HIVE-6293
URL: https://issues.apache.org/jira/browse/HIVE-6293
Project: Hive
Thanks for the info, Brock.
Yesterday I submitted a couple of patches, expecting to get the result this
morning. However, they didn't run. I had to manually submit the request
this morning. Right now they are waiting in queue.
--Xuefu
On Fri, Nov 8, 2013 at 9:48 AM, Brock Noland wrote:
> AFAI
AFAIK they are running just fine. Last night that was not the case because
of a price spike in EC2 spot instances (going to be improved via
https://issues.apache.org/jira/browse/HIVE-5782).
Long story short, they are queued right now and we can eliminate the
queueing once https://issues.apache.or
Hi,
It seems that pre-commit tests are not running. I wonder if anyone knows
why?
Thanks,
Xuefu
Look in the html. The grep command looks at raw html.
On Sep 14, 2013 12:53 AM, "Jason Dere" wrote:
> I notice that in the Jiras where I add NO PRECOMMIT TESTS, if I remove
> that line from the description and upload a patch the pre commit build
> system still won't pick up this patch for testing
I notice that in the Jiras where I add NO PRECOMMIT TESTS, if I remove that
line from the description and upload a patch the pre commit build system still
won't pick up this patch for testing. For example, in the build output:
+ JIRA_TEXT=/tmp/tmp.voD5s6RxFu
+ trap 'rm -f /tmp/tmp.voD5s6RxFu' E
53 matches
Mail list logo
