Re: trunk APR version requirement

2019-11-12 Thread Stefan Eissing
Very happy about this. Thanks a lot!

> Am 12.11.2019 um 16:10 schrieb Yann Ylavic :
> 
> On Tue, Nov 12, 2019 at 3:43 PM Luca Toscano  wrote:
>> 
>> Il giorno mar 12 nov 2019 alle ore 15:24 Eric Covener
>>  ha scritto:
>>> 
 
 1. If travis results look stable this week, turn on e-mail notifications
 to dev@ on Friday.
 
 2. Friday following (22nd), disable the broken bits of buildbot if
 nobody has salvaged it.
>>> 
>>> +1
>> 
>> +1
> 
> +1 (and great job Jo & Luca!)



Re: trunk APR version requirement

2019-11-12 Thread Yann Ylavic
On Tue, Nov 12, 2019 at 3:43 PM Luca Toscano  wrote:
>
> Il giorno mar 12 nov 2019 alle ore 15:24 Eric Covener
>  ha scritto:
> >
> > >
> > > 1. If travis results look stable this week, turn on e-mail notifications
> > > to dev@ on Friday.
> > >
> > > 2. Friday following (22nd), disable the broken bits of buildbot if
> > > nobody has salvaged it.
> >
> > +1
>
> +1

+1 (and great job Jo & Luca!)


Re: trunk APR version requirement

2019-11-12 Thread Luca Toscano
Il giorno mar 12 nov 2019 alle ore 15:24 Eric Covener
 ha scritto:
>
> >
> > 1. If travis results look stable this week, turn on e-mail notifications
> > to dev@ on Friday.
> >
> > 2. Friday following (22nd), disable the broken bits of buildbot if
> > nobody has salvaged it.
>
> +1

+1


Re: trunk APR version requirement

2019-11-12 Thread Eric Covener
>
> 1. If travis results look stable this week, turn on e-mail notifications
> to dev@ on Friday.
>
> 2. Friday following (22nd), disable the broken bits of buildbot if
> nobody has salvaged it.

+1


Re: trunk APR version requirement

2019-11-12 Thread Joe Orton
On Tue, Nov 12, 2019 at 02:39:58PM +0100, Luca Toscano wrote:
> Il giorno mar 12 nov 2019 alle ore 12:40 Joe Orton 
> ha scritto:
> >
> > Thanks to everyone who gave feedback, I made the change to require APR
> > 1.6 in r1869684.  While I kept the Travis builds passing, buildbot broke
> > since it's doing a trunk build against the system APR.  Does anybody
> > know if there is a buildbot slave running Bionic?
> 
> Or maybe we could think about swapping buildbot with Travis and set
> notifications for the latter to dev@. Travis seems working really well
> and after all your recent work IIUC it is already testing way more
> than what buildbot does :)

I'm fine with disabling bb if nobody wants to rescue it - and I didn't 
deliberately sabotage it!  We need to keep the doxygen bb stuff running, 
that has failed to build as well though I think it's only a 
non-reproducible failure, because an existing checkout has been 
reconfigured using the included APR (trunk) and still has objects built 
against APR 1.x.

How about:

1. If travis results look stable this week, turn on e-mail notifications 
to dev@ on Friday.

2. Friday following (22nd), disable the broken bits of buildbot if 
nobody has salvaged it.

Regards, Joe





Re: trunk APR version requirement

2019-11-12 Thread Luca Toscano
Il giorno mar 12 nov 2019 alle ore 12:40 Joe Orton 
ha scritto:
>
> Thanks to everyone who gave feedback, I made the change to require APR
> 1.6 in r1869684.  While I kept the Travis builds passing, buildbot broke
> since it's doing a trunk build against the system APR.  Does anybody
> know if there is a buildbot slave running Bionic?

Or maybe we could think about swapping buildbot with Travis and set
notifications for the latter to dev@. Travis seems working really well
and after all your recent work IIUC it is already testing way more
than what buildbot does :)

Luca


Re: modify bugzilla resolved statuses?

2019-11-12 Thread Yann Ylavic
On Tue, Nov 12, 2019 at 2:01 PM Daniel Gruno  wrote:
>
> On 12/11/2019 13.57, Eric Covener wrote:
> > On Tue, Nov 12, 2019 at 7:47 AM Daniel Gruno  wrote:
> >>
> >> On 12/11/2019 13.29, Eric Covener wrote:
> >>> Is there a way to add new sub-statuses under Resolved in our bugzilla?
> >>>
> >>> It would be nice to have something kind of neutral for things that are
> >>> essentially answered questions rather than "invalid" or
> >>> "worksforsome".  I think "invalid" is kind of impolite and invites
> >>> argumentation.
> >>>
> >>
> >> Yes, how about 'INFORMATIONPROVIDED' ?
> >
> > That helps, or even "CLOSED"
> >
>
> Added both for good measure :)

I quite like Eric's subliminal s/worksforme/worksforsome/ too, if as easy :)


Re: modify bugzilla resolved statuses?

2019-11-12 Thread Daniel Gruno

On 12/11/2019 13.57, Eric Covener wrote:

On Tue, Nov 12, 2019 at 7:47 AM Daniel Gruno  wrote:


On 12/11/2019 13.29, Eric Covener wrote:

Is there a way to add new sub-statuses under Resolved in our bugzilla?

It would be nice to have something kind of neutral for things that are
essentially answered questions rather than "invalid" or
"worksforsome".  I think "invalid" is kind of impolite and invites
argumentation.



Yes, how about 'INFORMATIONPROVIDED' ?


That helps, or even "CLOSED"



Added both for good measure :)


Re: modify bugzilla resolved statuses?

2019-11-12 Thread Eric Covener
On Tue, Nov 12, 2019 at 7:47 AM Daniel Gruno  wrote:
>
> On 12/11/2019 13.29, Eric Covener wrote:
> > Is there a way to add new sub-statuses under Resolved in our bugzilla?
> >
> > It would be nice to have something kind of neutral for things that are
> > essentially answered questions rather than "invalid" or
> > "worksforsome".  I think "invalid" is kind of impolite and invites
> > argumentation.
> >
>
> Yes, how about 'INFORMATIONPROVIDED' ?

That helps, or even "CLOSED"


Re: modify bugzilla resolved statuses?

2019-11-12 Thread Daniel Gruno

On 12/11/2019 13.29, Eric Covener wrote:

Is there a way to add new sub-statuses under Resolved in our bugzilla?

It would be nice to have something kind of neutral for things that are
essentially answered questions rather than "invalid" or
"worksforsome".  I think "invalid" is kind of impolite and invites
argumentation.



Yes, how about 'INFORMATIONPROVIDED' ?


modify bugzilla resolved statuses?

2019-11-12 Thread Eric Covener
Is there a way to add new sub-statuses under Resolved in our bugzilla?

It would be nice to have something kind of neutral for things that are
essentially answered questions rather than "invalid" or
"worksforsome".  I think "invalid" is kind of impolite and invites
argumentation.

-- 
Eric Covener
cove...@gmail.com


Re: trunk APR version requirement

2019-11-12 Thread Joe Orton
Thanks to everyone who gave feedback, I made the change to require APR 
1.6 in r1869684.  While I kept the Travis builds passing, buildbot broke 
since it's doing a trunk build against the system APR.  Does anybody 
know if there is a buildbot slave running Bionic?

Regards, Joe



buildbot failure in on httpd-trunk

2019-11-12 Thread buildbot
The Buildbot has detected a new failure on builder httpd-trunk while building . 
Full details are available at:
https://ci.apache.org/builders/httpd-trunk/builds/4251

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: bb_slave6_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'httpd-trunk-on-commit' 
triggered this build
Build Source Stamp: [branch httpd/httpd/trunk] 1869684
Blamelist: jorton,lgentis

BUILD FAILED: failed configure

Sincerely,
 -The Buildbot