You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "larsh@apache.org" <la...@apache.org> on 2020/04/08 18:00:08 UTC
No builds on Phoenix-Master jenkins since Feb 19th?
Just looking at the Phoenix Jenkins jobs I noticed that was no build on master since for 3 weeks.
Is that in purpose? There were clearly changes on the master branch since then.
Cheers.
-- Lars
Re: No builds on Phoenix-Master jenkins since Feb 19th?
Posted by Josh Elser <el...@apache.org>.
Thanks Chenglei!!
On 6/21/20 12:00 PM, chenglei@apache.org wrote:
>
>
>
>
>
>
>
>
>
>
>
>
> I observed that when the ITtests hange, the ZK connection exhaustion is caused by ViewUtil.dropChildViews , and I opened a JIRA PHOENIX-5970 to solve it, seems that it works.
>
>
>
>
>
> At 2020-06-19 14:58:27, "Istvan Toth" <st...@apache.org> wrote:
>> The hanging test suite issue has been fixed by Richard Antal's PHOENIX-5962
>> <https://issues.apache.org/jira/browse/PHOENIX-5962> .
>> Tests should be back to normal (that is, they're still flakey as fresh snow)
>>
>> Rajeshbabu, is there an easy way (specific message in the logs) for
>> identifying the ZK connection exhaustion situation?
>>
>> Istvan
>>
>> On Thu, Jun 18, 2020 at 2:49 AM rajeshbabu@apache.org <
>> chrajeshbabu32@gmail.com> wrote:
>>
>>> Just my observation related tests hang or flaky ness is that when there are
>>> connections created which involves zookeeper connection then at some point
>>> of time zookeeper sees too many connections and not allow to create further
>>> connections then the cluster won't be terminated immediately and tests
>>> hangs. We can identify such cases and close the connections properly if
>>> any.
>>>
>>> Thanks,
>>> Rajeshbabu.
>>>
>>> On Tue, Jun 16, 2020, 12:12 PM Istvan Toth <st...@apache.org> wrote:
>>>
>>>> What we really need is getting our test suite (and infra) sorted out.
>>>> Your suggestions are already part of the process, it's just that lately
>>>> everyone ignores them, because the precommit tests have been next to
>>>> useless for a good while.
>>>>
>>>> I think that if developers can be reasonably sure that the precommit
>>>> failure that they see is not some kind of random/known flake, they (we)
>>>> will take them seriously, and not commit until they(we) get it right.
>>>>
>>>> Blocking further commits until the tests are fixed is one drastic, but
>>>> possibly necessary measure to achieve this.
>>>> And once we get them fixed, we will indeed need to be more vigilant in
>>> not
>>>> letting the situation deteriorate.
>>>>
>>>> Istvan
>>>>
>>>> On Mon, Jun 15, 2020 at 7:30 PM Andrew Purtell <ap...@apache.org>
>>>> wrote:
>>>>
>>>>> So it's time to enforce an automatic revert if build fails policy?
>>>>> Ideally, no commit before a precommit passes.
>>>>> If that fails, if someone discovers failing tests and can git bisect to
>>>> the
>>>>> cause, automatic revert of the offending commit.
>>>>>
>>>>> YDYT?
>>>>>
>>>>>
>>>>> On Sun, Jun 14, 2020 at 10:20 PM Istvan Toth
>>> <stoty@cloudera.com.invalid
>>>>>
>>>>> wrote:
>>>>>
>>>>>> Unfortunately you are not missing anything, Lars :(
>>>>>>
>>>>>> What's worse, the tests are not only failing, they even hang since
>>> Jun
>>>> 2.
>>>>>> Master is in a similar state.
>>>>>>
>>>>>> regards
>>>>>> Istvan
>>>>>>
>>>>>> On Sun, Jun 14, 2020 at 12:03 AM larsh@apache.org <la...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Thanks Istvan.
>>>>>>>
>>>>>>> Just checked the builds. Looks like the 4.x builds have not passed
>>> a
>>>>>>> single time since May 20th.
>>>>>>>
>>>>>>> I hope I am missing something... Otherwise this would be pretty
>>>>>>> frustrating. :)
>>>>>>> (Since pleading doesn't appear to help, maybe we should
>>> automatically
>>>>>>> block all commits until all tests pass...?)
>>>>>>>
>>>>>>> -- Lars
>>>>>>>
>>>>>>>
>>>>>>> On Tuesday, April 21, 2020, 5:33:52 AM PDT, Istvan Toth <
>>>>>> stoty@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I've deleted all but the four Phoenix jobs listed in the JIRA.
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> *István Tóth* | Staff Software Engineer
>>>>>> stoty@cloudera.com <https://www.cloudera.com>
>>>>>> [image: Cloudera] <https://www.cloudera.com/>
>>>>>> [image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
>>>>>> Cloudera on Facebook] <https://www.facebook.com/cloudera> [image:
>>>>> Cloudera
>>>>>> on LinkedIn] <https://www.linkedin.com/company/cloudera>
>>>>>> <https://www.cloudera.com/>
>>>>>> ------------------------------
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best regards,
>>>>> Andrew
>>>>>
>>>>> Words like orphans lost among the crosstalk, meaning torn from truth's
>>>>> decrepit hands
>>>>> - A23, Crosstalk
>>>>>
>>>>
>>>
Re: No builds on Phoenix-Master jenkins since Feb 19th?
Posted by "chenglei@apache.org" <ch...@apache.org>.
I observed that when the ITtests hange, the ZK connection exhaustion is caused by ViewUtil.dropChildViews , and I opened a JIRA PHOENIX-5970 to solve it, seems that it works.
At 2020-06-19 14:58:27, "Istvan Toth" <st...@apache.org> wrote:
>The hanging test suite issue has been fixed by Richard Antal's PHOENIX-5962
><https://issues.apache.org/jira/browse/PHOENIX-5962> .
>Tests should be back to normal (that is, they're still flakey as fresh snow)
>
>Rajeshbabu, is there an easy way (specific message in the logs) for
>identifying the ZK connection exhaustion situation?
>
>Istvan
>
>On Thu, Jun 18, 2020 at 2:49 AM rajeshbabu@apache.org <
>chrajeshbabu32@gmail.com> wrote:
>
>> Just my observation related tests hang or flaky ness is that when there are
>> connections created which involves zookeeper connection then at some point
>> of time zookeeper sees too many connections and not allow to create further
>> connections then the cluster won't be terminated immediately and tests
>> hangs. We can identify such cases and close the connections properly if
>> any.
>>
>> Thanks,
>> Rajeshbabu.
>>
>> On Tue, Jun 16, 2020, 12:12 PM Istvan Toth <st...@apache.org> wrote:
>>
>> > What we really need is getting our test suite (and infra) sorted out.
>> > Your suggestions are already part of the process, it's just that lately
>> > everyone ignores them, because the precommit tests have been next to
>> > useless for a good while.
>> >
>> > I think that if developers can be reasonably sure that the precommit
>> > failure that they see is not some kind of random/known flake, they (we)
>> > will take them seriously, and not commit until they(we) get it right.
>> >
>> > Blocking further commits until the tests are fixed is one drastic, but
>> > possibly necessary measure to achieve this.
>> > And once we get them fixed, we will indeed need to be more vigilant in
>> not
>> > letting the situation deteriorate.
>> >
>> > Istvan
>> >
>> > On Mon, Jun 15, 2020 at 7:30 PM Andrew Purtell <ap...@apache.org>
>> > wrote:
>> >
>> > > So it's time to enforce an automatic revert if build fails policy?
>> > > Ideally, no commit before a precommit passes.
>> > > If that fails, if someone discovers failing tests and can git bisect to
>> > the
>> > > cause, automatic revert of the offending commit.
>> > >
>> > > YDYT?
>> > >
>> > >
>> > > On Sun, Jun 14, 2020 at 10:20 PM Istvan Toth
>> <stoty@cloudera.com.invalid
>> > >
>> > > wrote:
>> > >
>> > > > Unfortunately you are not missing anything, Lars :(
>> > > >
>> > > > What's worse, the tests are not only failing, they even hang since
>> Jun
>> > 2.
>> > > > Master is in a similar state.
>> > > >
>> > > > regards
>> > > > Istvan
>> > > >
>> > > > On Sun, Jun 14, 2020 at 12:03 AM larsh@apache.org <la...@apache.org>
>> > > > wrote:
>> > > >
>> > > > > Thanks Istvan.
>> > > > >
>> > > > > Just checked the builds. Looks like the 4.x builds have not passed
>> a
>> > > > > single time since May 20th.
>> > > > >
>> > > > > I hope I am missing something... Otherwise this would be pretty
>> > > > > frustrating. :)
>> > > > > (Since pleading doesn't appear to help, maybe we should
>> automatically
>> > > > > block all commits until all tests pass...?)
>> > > > >
>> > > > > -- Lars
>> > > > >
>> > > > >
>> > > > > On Tuesday, April 21, 2020, 5:33:52 AM PDT, Istvan Toth <
>> > > > stoty@apache.org>
>> > > > > wrote:
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > > I've deleted all but the four Phoenix jobs listed in the JIRA.
>> > > > >
>> > > > >
>> > > >
>> > > > --
>> > > > *István Tóth* | Staff Software Engineer
>> > > > stoty@cloudera.com <https://www.cloudera.com>
>> > > > [image: Cloudera] <https://www.cloudera.com/>
>> > > > [image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
>> > > > Cloudera on Facebook] <https://www.facebook.com/cloudera> [image:
>> > > Cloudera
>> > > > on LinkedIn] <https://www.linkedin.com/company/cloudera>
>> > > > <https://www.cloudera.com/>
>> > > > ------------------------------
>> > > >
>> > >
>> > >
>> > > --
>> > > Best regards,
>> > > Andrew
>> > >
>> > > Words like orphans lost among the crosstalk, meaning torn from truth's
>> > > decrepit hands
>> > > - A23, Crosstalk
>> > >
>> >
>>
Re: No builds on Phoenix-Master jenkins since Feb 19th?
Posted by 程磊 <co...@163.com>.
I observed that when the ITtests hange, the ZK connection exhaustion is caused by ViewUtil.dropChildViews , and I opened a JIRA PHOENIX-5970 to solve it, seems that it works.
At 2020-06-19 14:58:27, "Istvan Toth" <st...@apache.org> wrote:
>The hanging test suite issue has been fixed by Richard Antal's PHOENIX-5962
><https://issues.apache.org/jira/browse/PHOENIX-5962> .
>Tests should be back to normal (that is, they're still flakey as fresh snow)
>
>Rajeshbabu, is there an easy way (specific message in the logs) for
>identifying the ZK connection exhaustion situation?
>
>Istvan
>
>On Thu, Jun 18, 2020 at 2:49 AM rajeshbabu@apache.org <
>chrajeshbabu32@gmail.com> wrote:
>
>> Just my observation related tests hang or flaky ness is that when there are
>> connections created which involves zookeeper connection then at some point
>> of time zookeeper sees too many connections and not allow to create further
>> connections then the cluster won't be terminated immediately and tests
>> hangs. We can identify such cases and close the connections properly if
>> any.
>>
>> Thanks,
>> Rajeshbabu.
>>
>> On Tue, Jun 16, 2020, 12:12 PM Istvan Toth <st...@apache.org> wrote:
>>
>> > What we really need is getting our test suite (and infra) sorted out.
>> > Your suggestions are already part of the process, it's just that lately
>> > everyone ignores them, because the precommit tests have been next to
>> > useless for a good while.
>> >
>> > I think that if developers can be reasonably sure that the precommit
>> > failure that they see is not some kind of random/known flake, they (we)
>> > will take them seriously, and not commit until they(we) get it right.
>> >
>> > Blocking further commits until the tests are fixed is one drastic, but
>> > possibly necessary measure to achieve this.
>> > And once we get them fixed, we will indeed need to be more vigilant in
>> not
>> > letting the situation deteriorate.
>> >
>> > Istvan
>> >
>> > On Mon, Jun 15, 2020 at 7:30 PM Andrew Purtell <ap...@apache.org>
>> > wrote:
>> >
>> > > So it's time to enforce an automatic revert if build fails policy?
>> > > Ideally, no commit before a precommit passes.
>> > > If that fails, if someone discovers failing tests and can git bisect to
>> > the
>> > > cause, automatic revert of the offending commit.
>> > >
>> > > YDYT?
>> > >
>> > >
>> > > On Sun, Jun 14, 2020 at 10:20 PM Istvan Toth
>> <stoty@cloudera.com.invalid
>> > >
>> > > wrote:
>> > >
>> > > > Unfortunately you are not missing anything, Lars :(
>> > > >
>> > > > What's worse, the tests are not only failing, they even hang since
>> Jun
>> > 2.
>> > > > Master is in a similar state.
>> > > >
>> > > > regards
>> > > > Istvan
>> > > >
>> > > > On Sun, Jun 14, 2020 at 12:03 AM larsh@apache.org <la...@apache.org>
>> > > > wrote:
>> > > >
>> > > > > Thanks Istvan.
>> > > > >
>> > > > > Just checked the builds. Looks like the 4.x builds have not passed
>> a
>> > > > > single time since May 20th.
>> > > > >
>> > > > > I hope I am missing something... Otherwise this would be pretty
>> > > > > frustrating. :)
>> > > > > (Since pleading doesn't appear to help, maybe we should
>> automatically
>> > > > > block all commits until all tests pass...?)
>> > > > >
>> > > > > -- Lars
>> > > > >
>> > > > >
>> > > > > On Tuesday, April 21, 2020, 5:33:52 AM PDT, Istvan Toth <
>> > > > stoty@apache.org>
>> > > > > wrote:
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > > I've deleted all but the four Phoenix jobs listed in the JIRA.
>> > > > >
>> > > > >
>> > > >
>> > > > --
>> > > > *István Tóth* | Staff Software Engineer
>> > > > stoty@cloudera.com <https://www.cloudera.com>
>> > > > [image: Cloudera] <https://www.cloudera.com/>
>> > > > [image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
>> > > > Cloudera on Facebook] <https://www.facebook.com/cloudera> [image:
>> > > Cloudera
>> > > > on LinkedIn] <https://www.linkedin.com/company/cloudera>
>> > > > <https://www.cloudera.com/>
>> > > > ------------------------------
>> > > >
>> > >
>> > >
>> > > --
>> > > Best regards,
>> > > Andrew
>> > >
>> > > Words like orphans lost among the crosstalk, meaning torn from truth's
>> > > decrepit hands
>> > > - A23, Crosstalk
>> > >
>> >
>>
Re: No builds on Phoenix-Master jenkins since Feb 19th?
Posted by Istvan Toth <st...@apache.org>.
The hanging test suite issue has been fixed by Richard Antal's PHOENIX-5962
<https://issues.apache.org/jira/browse/PHOENIX-5962> .
Tests should be back to normal (that is, they're still flakey as fresh snow)
Rajeshbabu, is there an easy way (specific message in the logs) for
identifying the ZK connection exhaustion situation?
Istvan
On Thu, Jun 18, 2020 at 2:49 AM rajeshbabu@apache.org <
chrajeshbabu32@gmail.com> wrote:
> Just my observation related tests hang or flaky ness is that when there are
> connections created which involves zookeeper connection then at some point
> of time zookeeper sees too many connections and not allow to create further
> connections then the cluster won't be terminated immediately and tests
> hangs. We can identify such cases and close the connections properly if
> any.
>
> Thanks,
> Rajeshbabu.
>
> On Tue, Jun 16, 2020, 12:12 PM Istvan Toth <st...@apache.org> wrote:
>
> > What we really need is getting our test suite (and infra) sorted out.
> > Your suggestions are already part of the process, it's just that lately
> > everyone ignores them, because the precommit tests have been next to
> > useless for a good while.
> >
> > I think that if developers can be reasonably sure that the precommit
> > failure that they see is not some kind of random/known flake, they (we)
> > will take them seriously, and not commit until they(we) get it right.
> >
> > Blocking further commits until the tests are fixed is one drastic, but
> > possibly necessary measure to achieve this.
> > And once we get them fixed, we will indeed need to be more vigilant in
> not
> > letting the situation deteriorate.
> >
> > Istvan
> >
> > On Mon, Jun 15, 2020 at 7:30 PM Andrew Purtell <ap...@apache.org>
> > wrote:
> >
> > > So it's time to enforce an automatic revert if build fails policy?
> > > Ideally, no commit before a precommit passes.
> > > If that fails, if someone discovers failing tests and can git bisect to
> > the
> > > cause, automatic revert of the offending commit.
> > >
> > > YDYT?
> > >
> > >
> > > On Sun, Jun 14, 2020 at 10:20 PM Istvan Toth
> <stoty@cloudera.com.invalid
> > >
> > > wrote:
> > >
> > > > Unfortunately you are not missing anything, Lars :(
> > > >
> > > > What's worse, the tests are not only failing, they even hang since
> Jun
> > 2.
> > > > Master is in a similar state.
> > > >
> > > > regards
> > > > Istvan
> > > >
> > > > On Sun, Jun 14, 2020 at 12:03 AM larsh@apache.org <la...@apache.org>
> > > > wrote:
> > > >
> > > > > Thanks Istvan.
> > > > >
> > > > > Just checked the builds. Looks like the 4.x builds have not passed
> a
> > > > > single time since May 20th.
> > > > >
> > > > > I hope I am missing something... Otherwise this would be pretty
> > > > > frustrating. :)
> > > > > (Since pleading doesn't appear to help, maybe we should
> automatically
> > > > > block all commits until all tests pass...?)
> > > > >
> > > > > -- Lars
> > > > >
> > > > >
> > > > > On Tuesday, April 21, 2020, 5:33:52 AM PDT, Istvan Toth <
> > > > stoty@apache.org>
> > > > > wrote:
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > I've deleted all but the four Phoenix jobs listed in the JIRA.
> > > > >
> > > > >
> > > >
> > > > --
> > > > *István Tóth* | Staff Software Engineer
> > > > stoty@cloudera.com <https://www.cloudera.com>
> > > > [image: Cloudera] <https://www.cloudera.com/>
> > > > [image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
> > > > Cloudera on Facebook] <https://www.facebook.com/cloudera> [image:
> > > Cloudera
> > > > on LinkedIn] <https://www.linkedin.com/company/cloudera>
> > > > <https://www.cloudera.com/>
> > > > ------------------------------
> > > >
> > >
> > >
> > > --
> > > Best regards,
> > > Andrew
> > >
> > > Words like orphans lost among the crosstalk, meaning torn from truth's
> > > decrepit hands
> > > - A23, Crosstalk
> > >
> >
>
Re: No builds on Phoenix-Master jenkins since Feb 19th?
Posted by "rajeshbabu@apache.org" <ch...@gmail.com>.
Just my observation related tests hang or flaky ness is that when there are
connections created which involves zookeeper connection then at some point
of time zookeeper sees too many connections and not allow to create further
connections then the cluster won't be terminated immediately and tests
hangs. We can identify such cases and close the connections properly if any.
Thanks,
Rajeshbabu.
On Tue, Jun 16, 2020, 12:12 PM Istvan Toth <st...@apache.org> wrote:
> What we really need is getting our test suite (and infra) sorted out.
> Your suggestions are already part of the process, it's just that lately
> everyone ignores them, because the precommit tests have been next to
> useless for a good while.
>
> I think that if developers can be reasonably sure that the precommit
> failure that they see is not some kind of random/known flake, they (we)
> will take them seriously, and not commit until they(we) get it right.
>
> Blocking further commits until the tests are fixed is one drastic, but
> possibly necessary measure to achieve this.
> And once we get them fixed, we will indeed need to be more vigilant in not
> letting the situation deteriorate.
>
> Istvan
>
> On Mon, Jun 15, 2020 at 7:30 PM Andrew Purtell <ap...@apache.org>
> wrote:
>
> > So it's time to enforce an automatic revert if build fails policy?
> > Ideally, no commit before a precommit passes.
> > If that fails, if someone discovers failing tests and can git bisect to
> the
> > cause, automatic revert of the offending commit.
> >
> > YDYT?
> >
> >
> > On Sun, Jun 14, 2020 at 10:20 PM Istvan Toth <stoty@cloudera.com.invalid
> >
> > wrote:
> >
> > > Unfortunately you are not missing anything, Lars :(
> > >
> > > What's worse, the tests are not only failing, they even hang since Jun
> 2.
> > > Master is in a similar state.
> > >
> > > regards
> > > Istvan
> > >
> > > On Sun, Jun 14, 2020 at 12:03 AM larsh@apache.org <la...@apache.org>
> > > wrote:
> > >
> > > > Thanks Istvan.
> > > >
> > > > Just checked the builds. Looks like the 4.x builds have not passed a
> > > > single time since May 20th.
> > > >
> > > > I hope I am missing something... Otherwise this would be pretty
> > > > frustrating. :)
> > > > (Since pleading doesn't appear to help, maybe we should automatically
> > > > block all commits until all tests pass...?)
> > > >
> > > > -- Lars
> > > >
> > > >
> > > > On Tuesday, April 21, 2020, 5:33:52 AM PDT, Istvan Toth <
> > > stoty@apache.org>
> > > > wrote:
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > I've deleted all but the four Phoenix jobs listed in the JIRA.
> > > >
> > > >
> > >
> > > --
> > > *István Tóth* | Staff Software Engineer
> > > stoty@cloudera.com <https://www.cloudera.com>
> > > [image: Cloudera] <https://www.cloudera.com/>
> > > [image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
> > > Cloudera on Facebook] <https://www.facebook.com/cloudera> [image:
> > Cloudera
> > > on LinkedIn] <https://www.linkedin.com/company/cloudera>
> > > <https://www.cloudera.com/>
> > > ------------------------------
> > >
> >
> >
> > --
> > Best regards,
> > Andrew
> >
> > Words like orphans lost among the crosstalk, meaning torn from truth's
> > decrepit hands
> > - A23, Crosstalk
> >
>
Re: No builds on Phoenix-Master jenkins since Feb 19th?
Posted by Istvan Toth <st...@apache.org>.
What we really need is getting our test suite (and infra) sorted out.
Your suggestions are already part of the process, it's just that lately
everyone ignores them, because the precommit tests have been next to
useless for a good while.
I think that if developers can be reasonably sure that the precommit
failure that they see is not some kind of random/known flake, they (we)
will take them seriously, and not commit until they(we) get it right.
Blocking further commits until the tests are fixed is one drastic, but
possibly necessary measure to achieve this.
And once we get them fixed, we will indeed need to be more vigilant in not
letting the situation deteriorate.
Istvan
On Mon, Jun 15, 2020 at 7:30 PM Andrew Purtell <ap...@apache.org> wrote:
> So it's time to enforce an automatic revert if build fails policy?
> Ideally, no commit before a precommit passes.
> If that fails, if someone discovers failing tests and can git bisect to the
> cause, automatic revert of the offending commit.
>
> YDYT?
>
>
> On Sun, Jun 14, 2020 at 10:20 PM Istvan Toth <st...@cloudera.com.invalid>
> wrote:
>
> > Unfortunately you are not missing anything, Lars :(
> >
> > What's worse, the tests are not only failing, they even hang since Jun 2.
> > Master is in a similar state.
> >
> > regards
> > Istvan
> >
> > On Sun, Jun 14, 2020 at 12:03 AM larsh@apache.org <la...@apache.org>
> > wrote:
> >
> > > Thanks Istvan.
> > >
> > > Just checked the builds. Looks like the 4.x builds have not passed a
> > > single time since May 20th.
> > >
> > > I hope I am missing something... Otherwise this would be pretty
> > > frustrating. :)
> > > (Since pleading doesn't appear to help, maybe we should automatically
> > > block all commits until all tests pass...?)
> > >
> > > -- Lars
> > >
> > >
> > > On Tuesday, April 21, 2020, 5:33:52 AM PDT, Istvan Toth <
> > stoty@apache.org>
> > > wrote:
> > >
> > >
> > >
> > >
> > >
> > > I've deleted all but the four Phoenix jobs listed in the JIRA.
> > >
> > >
> >
> > --
> > *István Tóth* | Staff Software Engineer
> > stoty@cloudera.com <https://www.cloudera.com>
> > [image: Cloudera] <https://www.cloudera.com/>
> > [image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
> > Cloudera on Facebook] <https://www.facebook.com/cloudera> [image:
> Cloudera
> > on LinkedIn] <https://www.linkedin.com/company/cloudera>
> > <https://www.cloudera.com/>
> > ------------------------------
> >
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
> - A23, Crosstalk
>
Re: No builds on Phoenix-Master jenkins since Feb 19th?
Posted by Andrew Purtell <ap...@apache.org>.
So it's time to enforce an automatic revert if build fails policy?
Ideally, no commit before a precommit passes.
If that fails, if someone discovers failing tests and can git bisect to the
cause, automatic revert of the offending commit.
YDYT?
On Sun, Jun 14, 2020 at 10:20 PM Istvan Toth <st...@cloudera.com.invalid>
wrote:
> Unfortunately you are not missing anything, Lars :(
>
> What's worse, the tests are not only failing, they even hang since Jun 2.
> Master is in a similar state.
>
> regards
> Istvan
>
> On Sun, Jun 14, 2020 at 12:03 AM larsh@apache.org <la...@apache.org>
> wrote:
>
> > Thanks Istvan.
> >
> > Just checked the builds. Looks like the 4.x builds have not passed a
> > single time since May 20th.
> >
> > I hope I am missing something... Otherwise this would be pretty
> > frustrating. :)
> > (Since pleading doesn't appear to help, maybe we should automatically
> > block all commits until all tests pass...?)
> >
> > -- Lars
> >
> >
> > On Tuesday, April 21, 2020, 5:33:52 AM PDT, Istvan Toth <
> stoty@apache.org>
> > wrote:
> >
> >
> >
> >
> >
> > I've deleted all but the four Phoenix jobs listed in the JIRA.
> >
> >
>
> --
> *István Tóth* | Staff Software Engineer
> stoty@cloudera.com <https://www.cloudera.com>
> [image: Cloudera] <https://www.cloudera.com/>
> [image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
> Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera
> on LinkedIn] <https://www.linkedin.com/company/cloudera>
> <https://www.cloudera.com/>
> ------------------------------
>
--
Best regards,
Andrew
Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
- A23, Crosstalk
Re: No builds on Phoenix-Master jenkins since Feb 19th?
Posted by Istvan Toth <st...@cloudera.com.INVALID>.
Unfortunately you are not missing anything, Lars :(
What's worse, the tests are not only failing, they even hang since Jun 2.
Master is in a similar state.
regards
Istvan
On Sun, Jun 14, 2020 at 12:03 AM larsh@apache.org <la...@apache.org> wrote:
> Thanks Istvan.
>
> Just checked the builds. Looks like the 4.x builds have not passed a
> single time since May 20th.
>
> I hope I am missing something... Otherwise this would be pretty
> frustrating. :)
> (Since pleading doesn't appear to help, maybe we should automatically
> block all commits until all tests pass...?)
>
> -- Lars
>
>
> On Tuesday, April 21, 2020, 5:33:52 AM PDT, Istvan Toth <st...@apache.org>
> wrote:
>
>
>
>
>
> I've deleted all but the four Phoenix jobs listed in the JIRA.
>
>
--
*István Tóth* | Staff Software Engineer
stoty@cloudera.com <https://www.cloudera.com>
[image: Cloudera] <https://www.cloudera.com/>
[image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera
on LinkedIn] <https://www.linkedin.com/company/cloudera>
<https://www.cloudera.com/>
------------------------------
Re: No builds on Phoenix-Master jenkins since Feb 19th?
Posted by "larsh@apache.org" <la...@apache.org>.
Thanks Istvan.
Just checked the builds. Looks like the 4.x builds have not passed a single time since May 20th.
I hope I am missing something... Otherwise this would be pretty frustrating. :)
(Since pleading doesn't appear to help, maybe we should automatically block all commits until all tests pass...?)
-- Lars
On Tuesday, April 21, 2020, 5:33:52 AM PDT, Istvan Toth <st...@apache.org> wrote:
I've deleted all but the four Phoenix jobs listed in the JIRA.
Re: No builds on Phoenix-Master jenkins since Feb 19th?
Posted by Istvan Toth <st...@apache.org>.
I've deleted all but the four Phoenix jobs listed in the JIRA.
Re: No builds on Phoenix-Master jenkins since Feb 19th?
Posted by Istvan Toth <st...@cloudera.com.INVALID>.
Created https://issues.apache.org/jira/browse/PHOENIX-5843 to track this.
On Fri, Apr 10, 2020 at 2:47 AM larsh@apache.org <la...@apache.org> wrote:
> +1 on removing test that are no longer relevant... As long as we keep test
> coverage.
>
>
>
>
>
>
> On Wednesday, April 8, 2020, 10:49:16 PM PDT, Istvan Toth <
> stoty@apache.org> wrote:
>
>
>
>
>
> Yes, the tests are (and have been for some time) in a horrible shape for
> all branches and profiles.
>
> I've spent a few days on it, and now at least we are at the point where the
> test runs do not hang indefinitely, or get randomly killed, but
> there are still a lot of flaky tests, and unexplained random failures.
>
> Been too optimistic, I've just seen a recent 4.x run test hang. Fortunately
> it's a spurious test that I'm about to move to the PQS repo in a few
> minutes.
>
> We do get a few successful test runs on each branch / profile combination,
> but they are few and far between.
>
> We do have a lot of old and no longer relevant jobs in Apache. I have
> deactivated a few myself. I support removing them to reduce confusion.
> I think that the only relevant ones are:
>
>
> https://builds.apache.org/view/M-R/view/Phoenix/job/PreCommit-PHOENIX-Build/
> https://builds.apache.org/view/M-R/view/Phoenix/job/Phoenix-4.x-matrix/
> https://builds.apache.org/view/M-R/view/Phoenix/job/Phoenix-master-matrix/
> and possibly
> https://builds.apache.org/view/M-R/view/Phoenix/job/PhoenixFindTestTimeout/
> though I haven't looked into the last one.
>
>
> István
>
> On Thu, Apr 9, 2020 at 1:30 AM larsh@apache.org <la...@apache.org> wrote:
>
> > Thanks Josh.
> >
> > unfortunately
> >
> >
> https://builds.apache.org/view/M-R/view/Phoenix/job/Phoenix-master-matrix/
> >
> > has not passed a single time (at least for the past 15 runs)
> >
> > -- Lars
> >
> >
> > On Wednesday, April 8, 2020, 2:14:47 PM PDT, Josh Elser <
> elserj@apache.org>
> > wrote:
> >
> >
> >
> >
> > It looks like the Phoenix-Master[1] build is now defunct after Istvan's
> > hbase profile work. New job over in [2] which is a matrix job for all of
> > HBase 2.0, 2.1, and 2.2.
> >
> > I think the question is whether or not we want to keep the old job
> > around? I think the answer is "no".
> >
> > [1] https://builds.apache.org/view/M-R/view/Phoenix/job/Phoenix-master/
> > [2]
> >
> https://builds.apache.org/view/M-R/view/Phoenix/job/Phoenix-master-matrix/
> >
> > On 4/8/20 2:00 PM, larsh@apache.org wrote:
> > > Just looking at the Phoenix Jenkins jobs I noticed that was no build on
> > master since for 3 weeks.
> > > Is that in purpose? There were clearly changes on the master branch
> > since then.
> > >
> > > Cheers.
> > >
> > > -- Lars
> > >
> >
>
--
*István Tóth* | Staff Software Engineer
stoty@cloudera.com <https://www.cloudera.com>
[image: Cloudera] <https://www.cloudera.com/>
[image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera
on LinkedIn] <https://www.linkedin.com/company/cloudera>
<https://www.cloudera.com/>
------------------------------
Re: No builds on Phoenix-Master jenkins since Feb 19th?
Posted by "larsh@apache.org" <la...@apache.org>.
+1 on removing test that are no longer relevant... As long as we keep test coverage.
On Wednesday, April 8, 2020, 10:49:16 PM PDT, Istvan Toth <st...@apache.org> wrote:
Yes, the tests are (and have been for some time) in a horrible shape for
all branches and profiles.
I've spent a few days on it, and now at least we are at the point where the
test runs do not hang indefinitely, or get randomly killed, but
there are still a lot of flaky tests, and unexplained random failures.
Been too optimistic, I've just seen a recent 4.x run test hang. Fortunately
it's a spurious test that I'm about to move to the PQS repo in a few
minutes.
We do get a few successful test runs on each branch / profile combination,
but they are few and far between.
We do have a lot of old and no longer relevant jobs in Apache. I have
deactivated a few myself. I support removing them to reduce confusion.
I think that the only relevant ones are:
https://builds.apache.org/view/M-R/view/Phoenix/job/PreCommit-PHOENIX-Build/
https://builds.apache.org/view/M-R/view/Phoenix/job/Phoenix-4.x-matrix/
https://builds.apache.org/view/M-R/view/Phoenix/job/Phoenix-master-matrix/
and possibly
https://builds.apache.org/view/M-R/view/Phoenix/job/PhoenixFindTestTimeout/
though I haven't looked into the last one.
István
On Thu, Apr 9, 2020 at 1:30 AM larsh@apache.org <la...@apache.org> wrote:
> Thanks Josh.
>
> unfortunately
>
> https://builds.apache.org/view/M-R/view/Phoenix/job/Phoenix-master-matrix/
>
> has not passed a single time (at least for the past 15 runs)
>
> -- Lars
>
>
> On Wednesday, April 8, 2020, 2:14:47 PM PDT, Josh Elser <el...@apache.org>
> wrote:
>
>
>
>
> It looks like the Phoenix-Master[1] build is now defunct after Istvan's
> hbase profile work. New job over in [2] which is a matrix job for all of
> HBase 2.0, 2.1, and 2.2.
>
> I think the question is whether or not we want to keep the old job
> around? I think the answer is "no".
>
> [1] https://builds.apache.org/view/M-R/view/Phoenix/job/Phoenix-master/
> [2]
> https://builds.apache.org/view/M-R/view/Phoenix/job/Phoenix-master-matrix/
>
> On 4/8/20 2:00 PM, larsh@apache.org wrote:
> > Just looking at the Phoenix Jenkins jobs I noticed that was no build on
> master since for 3 weeks.
> > Is that in purpose? There were clearly changes on the master branch
> since then.
> >
> > Cheers.
> >
> > -- Lars
> >
>
Re: No builds on Phoenix-Master jenkins since Feb 19th?
Posted by Istvan Toth <st...@apache.org>.
Yes, the tests are (and have been for some time) in a horrible shape for
all branches and profiles.
I've spent a few days on it, and now at least we are at the point where the
test runs do not hang indefinitely, or get randomly killed, but
there are still a lot of flaky tests, and unexplained random failures.
Been too optimistic, I've just seen a recent 4.x run test hang. Fortunately
it's a spurious test that I'm about to move to the PQS repo in a few
minutes.
We do get a few successful test runs on each branch / profile combination,
but they are few and far between.
We do have a lot of old and no longer relevant jobs in Apache. I have
deactivated a few myself. I support removing them to reduce confusion.
I think that the only relevant ones are:
https://builds.apache.org/view/M-R/view/Phoenix/job/PreCommit-PHOENIX-Build/
https://builds.apache.org/view/M-R/view/Phoenix/job/Phoenix-4.x-matrix/
https://builds.apache.org/view/M-R/view/Phoenix/job/Phoenix-master-matrix/
and possibly
https://builds.apache.org/view/M-R/view/Phoenix/job/PhoenixFindTestTimeout/
though I haven't looked into the last one.
István
On Thu, Apr 9, 2020 at 1:30 AM larsh@apache.org <la...@apache.org> wrote:
> Thanks Josh.
>
> unfortunately
>
> https://builds.apache.org/view/M-R/view/Phoenix/job/Phoenix-master-matrix/
>
> has not passed a single time (at least for the past 15 runs)
>
> -- Lars
>
>
> On Wednesday, April 8, 2020, 2:14:47 PM PDT, Josh Elser <el...@apache.org>
> wrote:
>
>
>
>
> It looks like the Phoenix-Master[1] build is now defunct after Istvan's
> hbase profile work. New job over in [2] which is a matrix job for all of
> HBase 2.0, 2.1, and 2.2.
>
> I think the question is whether or not we want to keep the old job
> around? I think the answer is "no".
>
> [1] https://builds.apache.org/view/M-R/view/Phoenix/job/Phoenix-master/
> [2]
> https://builds.apache.org/view/M-R/view/Phoenix/job/Phoenix-master-matrix/
>
> On 4/8/20 2:00 PM, larsh@apache.org wrote:
> > Just looking at the Phoenix Jenkins jobs I noticed that was no build on
> master since for 3 weeks.
> > Is that in purpose? There were clearly changes on the master branch
> since then.
> >
> > Cheers.
> >
> > -- Lars
> >
>
Re: No builds on Phoenix-Master jenkins since Feb 19th?
Posted by "larsh@apache.org" <la...@apache.org>.
Thanks Josh.
unfortunately
https://builds.apache.org/view/M-R/view/Phoenix/job/Phoenix-master-matrix/
has not passed a single time (at least for the past 15 runs)
-- Lars
On Wednesday, April 8, 2020, 2:14:47 PM PDT, Josh Elser <el...@apache.org> wrote:
It looks like the Phoenix-Master[1] build is now defunct after Istvan's
hbase profile work. New job over in [2] which is a matrix job for all of
HBase 2.0, 2.1, and 2.2.
I think the question is whether or not we want to keep the old job
around? I think the answer is "no".
[1] https://builds.apache.org/view/M-R/view/Phoenix/job/Phoenix-master/
[2]
https://builds.apache.org/view/M-R/view/Phoenix/job/Phoenix-master-matrix/
On 4/8/20 2:00 PM, larsh@apache.org wrote:
> Just looking at the Phoenix Jenkins jobs I noticed that was no build on master since for 3 weeks.
> Is that in purpose? There were clearly changes on the master branch since then.
>
> Cheers.
>
> -- Lars
>
Re: No builds on Phoenix-Master jenkins since Feb 19th?
Posted by Josh Elser <el...@apache.org>.
It looks like the Phoenix-Master[1] build is now defunct after Istvan's
hbase profile work. New job over in [2] which is a matrix job for all of
HBase 2.0, 2.1, and 2.2.
I think the question is whether or not we want to keep the old job
around? I think the answer is "no".
[1] https://builds.apache.org/view/M-R/view/Phoenix/job/Phoenix-master/
[2]
https://builds.apache.org/view/M-R/view/Phoenix/job/Phoenix-master-matrix/
On 4/8/20 2:00 PM, larsh@apache.org wrote:
> Just looking at the Phoenix Jenkins jobs I noticed that was no build on master since for 3 weeks.
> Is that in purpose? There were clearly changes on the master branch since then.
>
> Cheers.
>
> -- Lars
>