You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@impala.apache.org by Bharath Vissapragada <bh...@cloudera.com> on 2018/10/15 20:24:18 UTC

Issues launching gerrit-verify-dry-run job?

It is hung on "Waiting for jenkinks.impala.io...." for a while and
eventually responds with a HTTP 504. Tried it on two different machines and
two different browsers.

Anyone else facing this issue?

Re: Issues launching gerrit-verify-dry-run job?

Posted by Fredy Wijaya <fw...@cloudera.com>.
It works now. Thanks!

On Mon, Oct 15, 2018 at 3:57 PM Jim Apple <jb...@cloudera.com> wrote:

> I turned it off and back on again. Give it a try.
>
> On Mon, Oct 15, 2018 at 1:32 PM Fredy Wijaya <fw...@cloudera.com> wrote:
>
> > Same issue here.
> >
> > On Mon, Oct 15, 2018 at 3:24 PM Bharath Vissapragada <
> > bharathv@cloudera.com>
> > wrote:
> >
> > > It is hung on "Waiting for jenkinks.impala.io...." for a while and
> > > eventually responds with a HTTP 504. Tried it on two different machines
> > and
> > > two different browsers.
> > >
> > > Anyone else facing this issue?
> > >
> >
>

Re: Issues launching gerrit-verify-dry-run job?

Posted by Jim Apple <jb...@cloudera.com>.
I turned it off and back on again. Give it a try.

On Mon, Oct 15, 2018 at 1:32 PM Fredy Wijaya <fw...@cloudera.com> wrote:

> Same issue here.
>
> On Mon, Oct 15, 2018 at 3:24 PM Bharath Vissapragada <
> bharathv@cloudera.com>
> wrote:
>
> > It is hung on "Waiting for jenkinks.impala.io...." for a while and
> > eventually responds with a HTTP 504. Tried it on two different machines
> and
> > two different browsers.
> >
> > Anyone else facing this issue?
> >
>

Re: Issues launching gerrit-verify-dry-run job?

Posted by Fredy Wijaya <fw...@cloudera.com>.
Same issue here.

On Mon, Oct 15, 2018 at 3:24 PM Bharath Vissapragada <bh...@cloudera.com>
wrote:

> It is hung on "Waiting for jenkinks.impala.io...." for a while and
> eventually responds with a HTTP 504. Tried it on two different machines and
> two different browsers.
>
> Anyone else facing this issue?
>