You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by Sushanth Sowmyan <kh...@gmail.com> on 2017/05/05 05:05:04 UTC

pre-commit jenkins issues

Hi,

It looks like the precommit queue is currently having issues :
https://builds.apache.org/job/PreCommit-HIVE-Build/

See builds# 5041,5042,5043 - It looks like it takes about 8 hours
waiting for the tests to finish running and to report back, and kills
it as it exceeds a 500minute time out, and returns without results. Is
anyone able to look into this to see what is going on?

Thanks!
-Sush

Re: pre-commit jenkins issues

Posted by Sushanth Sowmyan <kh...@gmail.com>.

Thanks! It looks like it's chugging away now. :)

On May 5, 2017 08:22, "Sergio Pena" <se...@cloudera.com> wrote:

> I restarted hiveptest and seems is working now. There was a hiccup on the
> server while using the libraries to create the slave nodes.
>
> On Fri, May 5, 2017 at 12:05 AM, Sushanth Sowmyan <kh...@gmail.com>
> wrote:
>
> > Hi,
> >
> > It looks like the precommit queue is currently having issues :
> > https://builds.apache.org/job/PreCommit-HIVE-Build/
> >
> > See builds# 5041,5042,5043 - It looks like it takes about 8 hours
> > waiting for the tests to finish running and to report back, and kills
> > it as it exceeds a 500minute time out, and returns without results. Is
> > anyone able to look into this to see what is going on?
> >
> > Thanks!
> > -Sush
> >
>

Re: pre-commit jenkins issues

Posted by Sergio Pena <se...@cloudera.com>.

I restarted hiveptest and seems is working now. There was a hiccup on the
server while using the libraries to create the slave nodes.

On Fri, May 5, 2017 at 12:05 AM, Sushanth Sowmyan <kh...@gmail.com>
wrote:

> Hi,
>
> It looks like the precommit queue is currently having issues :
> https://builds.apache.org/job/PreCommit-HIVE-Build/
>
> See builds# 5041,5042,5043 - It looks like it takes about 8 hours
> waiting for the tests to finish running and to report back, and kills
> it as it exceeds a 500minute time out, and returns without results. Is
> anyone able to look into this to see what is going on?
>
> Thanks!
> -Sush
>