You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by Brock Noland <br...@cloudera.com> on 2014/03/06 19:17:52 UTC
Hung Precommit Jenkins Jobs
Ashutosh informed me that the precommit build was hung. Long story
short, PTest2 had completed. For example, see this job which took 8
hours:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1636/
That correpsonds to:
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-Build-1637/execution.txt
which if you scroll all the way to the bottom, you will note it
finished long before that:
2014-03-06 05:48:22,194 INFO PTest.run:207 Executed 5358 tests
2014-03-06 05:48:22,194 INFO PTest.run:209 PERF: Phase ExecutionPhase
took 101 minutes
2014-03-06 05:48:22,194 INFO PTest.run:209 PERF: Phase PrepPhase took 5 minutes
2014-03-06 05:48:22,194 INFO PTest.run:209 PERF: Phase ReportingPhase
took 0 minutes
2014-03-06 05:48:22,194 INFO JIRAService.postComment:136 Comment:
{color:red}Overall{color}: -1 at least one tests failed
....
Long story short, it looks like Bigtop Jenkins is not as reliable as
we would like.
Re: Hung Precommit Jenkins Jobs
Posted by Brock Noland <br...@cloudera.com>.
AFAICT this version/installation of Jenkins does not support the time limits.
Ultimately it'd be nice to perhaps run Jenkins on the current master
host we have. That would give us dedicated executors and allow us full
control over the installation.
On Fri, Mar 7, 2014 at 1:07 AM, Thejas Nair <th...@hortonworks.com> wrote:
> Would it be possible/help to set a time limit for the job in this jenkins job ?
>
>
> On Thu, Mar 6, 2014 at 10:17 AM, Brock Noland <br...@cloudera.com> wrote:
>> Ashutosh informed me that the precommit build was hung. Long story
>> short, PTest2 had completed. For example, see this job which took 8
>> hours:
>>
>> http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1636/
>>
>> That correpsonds to:
>>
>> http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-Build-1637/execution.txt
>>
>> which if you scroll all the way to the bottom, you will note it
>> finished long before that:
>>
>> 2014-03-06 05:48:22,194 INFO PTest.run:207 Executed 5358 tests
>> 2014-03-06 05:48:22,194 INFO PTest.run:209 PERF: Phase ExecutionPhase
>> took 101 minutes
>> 2014-03-06 05:48:22,194 INFO PTest.run:209 PERF: Phase PrepPhase took 5 minutes
>> 2014-03-06 05:48:22,194 INFO PTest.run:209 PERF: Phase ReportingPhase
>> took 0 minutes
>> 2014-03-06 05:48:22,194 INFO JIRAService.postComment:136 Comment:
>>
>> {color:red}Overall{color}: -1 at least one tests failed
>> ....
>>
>>
>> Long story short, it looks like Bigtop Jenkins is not as reliable as
>> we would like.
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
Re: Hung Precommit Jenkins Jobs
Posted by Thejas Nair <th...@hortonworks.com>.
Would it be possible/help to set a time limit for the job in this jenkins job ?
On Thu, Mar 6, 2014 at 10:17 AM, Brock Noland <br...@cloudera.com> wrote:
> Ashutosh informed me that the precommit build was hung. Long story
> short, PTest2 had completed. For example, see this job which took 8
> hours:
>
> http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1636/
>
> That correpsonds to:
>
> http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-Build-1637/execution.txt
>
> which if you scroll all the way to the bottom, you will note it
> finished long before that:
>
> 2014-03-06 05:48:22,194 INFO PTest.run:207 Executed 5358 tests
> 2014-03-06 05:48:22,194 INFO PTest.run:209 PERF: Phase ExecutionPhase
> took 101 minutes
> 2014-03-06 05:48:22,194 INFO PTest.run:209 PERF: Phase PrepPhase took 5 minutes
> 2014-03-06 05:48:22,194 INFO PTest.run:209 PERF: Phase ReportingPhase
> took 0 minutes
> 2014-03-06 05:48:22,194 INFO JIRAService.postComment:136 Comment:
>
> {color:red}Overall{color}: -1 at least one tests failed
> ....
>
>
> Long story short, it looks like Bigtop Jenkins is not as reliable as
> we would like.
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.