You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@druid.apache.org by Aditya Mishra <ad...@gmail.com> on 2019/10/28 07:07:04 UTC
Query regarding Travis build failures
Hi, I have observed a weird behavior from Travis builds,
The following two builds ran on the exact same source (with difference of
blank lines) & broke at two unrelated points without any helpful
information,
https://travis-ci.org/apache/incubator-druid/builds/603316688
https://travis-ci.org/apache/incubator-druid/builds/603445329
Note that the logs of previous build failures did guide me towards
improving my code, but at this point, I'm unsure whether this is known
behavior or something related to my implementation of the new feature.
Any guidance would be appreciated.
Thanks & Regards
Aditya
Re: Query regarding Travis build failures
Posted by Aditya Mishra <ad...@gmail.com>.
Thanks a lot!
Both of the builds I mentioned above fully passed after rerun.
& apology from my end,
after writing the mail, I had triggered just one more dummy build to see if
I can infer anything from it, which again failed at a strange spot
https://travis-ci.org/apache/incubator-druid/builds/603787412
Thus, the Pull Request is still showing a cross next to it
https://github.com/apache/incubator-druid/pull/8719
In any case, I'm freezing the code right here till any updates are required
from reviews.
Thanks & regards
Aditya
On Mon, 28 Oct, 2019, 10:49 pm Surekha Saharan, <su...@imply.io>
wrote:
> Restarted failing tests.
>
> On Mon, Oct 28, 2019 at 9:42 AM Chi Cao Minh <ch...@imply.io> wrote:
>
> > Hi Aditya,
> >
> > Some of the integration tests may be flaky (likely in your case since you
> > didn’t make any functional changes between the runs). If you don’t push
> > another commit, one of the Druid committers can retrigger the flaky
> Travis
> > job to see if the subsequent run is successful.
> >
> > Thanks,
> > Chi
> >
> >
> > > On Oct 28, 2019, at 12:07 AM, Aditya Mishra <ad...@gmail.com>
> > wrote:
> > >
> > > Hi, I have observed a weird behavior from Travis builds,
> > > The following two builds ran on the exact same source (with difference
> of
> > > blank lines) & broke at two unrelated points without any helpful
> > > information,
> > >
> > > https://travis-ci.org/apache/incubator-druid/builds/603316688
> > > https://travis-ci.org/apache/incubator-druid/builds/603445329
> > >
> > > Note that the logs of previous build failures did guide me towards
> > > improving my code, but at this point, I'm unsure whether this is known
> > > behavior or something related to my implementation of the new feature.
> > >
> > > Any guidance would be appreciated.
> > >
> > > Thanks & Regards
> > > Aditya
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@druid.apache.org
> > For additional commands, e-mail: dev-help@druid.apache.org
> >
> >
>
Re: Query regarding Travis build failures
Posted by Surekha Saharan <su...@imply.io>.
Restarted failing tests.
On Mon, Oct 28, 2019 at 9:42 AM Chi Cao Minh <ch...@imply.io> wrote:
> Hi Aditya,
>
> Some of the integration tests may be flaky (likely in your case since you
> didn’t make any functional changes between the runs). If you don’t push
> another commit, one of the Druid committers can retrigger the flaky Travis
> job to see if the subsequent run is successful.
>
> Thanks,
> Chi
>
>
> > On Oct 28, 2019, at 12:07 AM, Aditya Mishra <ad...@gmail.com>
> wrote:
> >
> > Hi, I have observed a weird behavior from Travis builds,
> > The following two builds ran on the exact same source (with difference of
> > blank lines) & broke at two unrelated points without any helpful
> > information,
> >
> > https://travis-ci.org/apache/incubator-druid/builds/603316688
> > https://travis-ci.org/apache/incubator-druid/builds/603445329
> >
> > Note that the logs of previous build failures did guide me towards
> > improving my code, but at this point, I'm unsure whether this is known
> > behavior or something related to my implementation of the new feature.
> >
> > Any guidance would be appreciated.
> >
> > Thanks & Regards
> > Aditya
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@druid.apache.org
> For additional commands, e-mail: dev-help@druid.apache.org
>
>
Re: Query regarding Travis build failures
Posted by Chi Cao Minh <ch...@imply.io>.
Hi Aditya,
Some of the integration tests may be flaky (likely in your case since you didn’t make any functional changes between the runs). If you don’t push another commit, one of the Druid committers can retrigger the flaky Travis job to see if the subsequent run is successful.
Thanks,
Chi
> On Oct 28, 2019, at 12:07 AM, Aditya Mishra <ad...@gmail.com> wrote:
>
> Hi, I have observed a weird behavior from Travis builds,
> The following two builds ran on the exact same source (with difference of
> blank lines) & broke at two unrelated points without any helpful
> information,
>
> https://travis-ci.org/apache/incubator-druid/builds/603316688
> https://travis-ci.org/apache/incubator-druid/builds/603445329
>
> Note that the logs of previous build failures did guide me towards
> improving my code, but at this point, I'm unsure whether this is known
> behavior or something related to my implementation of the new feature.
>
> Any guidance would be appreciated.
>
> Thanks & Regards
> Aditya
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@druid.apache.org
For additional commands, e-mail: dev-help@druid.apache.org