The other test which frequently fails for me.

https://issues.apache.org/jira/browse/ASTERIXDB-1145

Regards,
Abdullah.

Amoudi, Abdullah.

On Sun, Nov 8, 2015 at 2:05 PM, Ildar Absalyamov <[email protected]
> wrote:

> Abdullah,
>
> What’s the other one? Maybe I will be lucky enough to trigger the failure
> with it.
>
> > On Nov 8, 2015, at 15:44, abdullah alamoudi <[email protected]> wrote:
> >
> > Hi Ildar,
> > This is one of the test cases. There is another one as well.
> > I think that I have seen it happen on my local machine as well but I am
> not
> > sure :)
> >
> > If there is a way to attach the debugger to Jenkins, let's wait and see
> > what Ian says.
> >
> > Cheers,
> > Abdullah.
> >
> > Amoudi, Abdullah.
> >
> > On Sun, Nov 8, 2015 at 12:59 PM, Ildar Absalyamov <
> > [email protected]> wrote:
> >
> >> Abdullah,
> >>
> >> I believe you are talking about that issue
> >> https://issues.apache.org/jira/browse/ASTERIXDB-1159? <
> >> https://issues.apache.org/jira/browse/ASTERIXDB-1159?>
> >> I am an assignee on this one, but I was not able to reproduce it locally
> >> on master. Does the build fail only on Jenkins, or that happens locally
> as
> >> well?
> >> In the former case is there a way to attach debugger to the build
> running
> >> on Jenkins? If I recall Ian introduced such opportunity.
> >>
> >>> On Nov 8, 2015, at 14:33, abdullah alamoudi <[email protected]>
> wrote:
> >>>
> >>> Hi all,
> >>> Can we do something about these frequently failing test cases? I don't
> >>> think aborting and re-triggering the build is an acceptable way to
> handle
> >>> them.
> >>>
> >>> If you're assigned one of these sporadically failing test cases,
> please,
> >>> make it your first priority.
> >>>
> >>> Amoudi, Abdullah.
> >>
> >> Best regards,
> >> Ildar
> >>
> >>
>
> Best regards,
> Ildar
>
>

Reply via email to