Re: Travis in solid red mode again

[Matt Caswell]

On 01/02/2020 00:34, Salz, Rich wrote:
>   
>   >  Could we add a CI check for PRs that confirms that the target branch is
> green in travis?
> 
> Looking at 
> https://docs.travis-ci.com/user/notifications/#conditional-notifications and 
> https://config.travis-ci.com/ref/notifications/email it seems like it should 
> be fairly easy configure builds to do "send email to openssl-commits when 
> builds on master fail"

We already have that.

Matt

RE: Travis in solid red mode again

[Dr. Matthias St. Pierre]

> -Original Message-
> On 01/02/2020 00:34, Salz, Rich wrote:
> >
> >   >  Could we add a CI check for PRs that confirms that the target branch is
> > green in travis?
> >
> > Looking at 
> > https://docs.travis-ci.com/user/notifications/#conditional-notifications 
> > and https://config.travis-
> ci.com/ref/notifications/email it seems like it should be fairly easy 
> configure builds to do "send email to openssl-commits when builds on
> master fail"
> 
> We already have that.

Maybe we should make it a requirement that at least all OTC members subscribe 
to openssl-commits?

Matthias

Re: Travis in solid red mode again

[Dr Paul Dale]

I thought I was subscribed but don’t seem to see the failures.
I do get the (very many) PR activity emails….


Pauli
-- 
Dr Paul Dale | Distinguished Architect | Cryptographic Foundations 
Phone +61 7 3031 7217
Oracle Australia




> On 1 Feb 2020, at 8:35 pm, Dr. Matthias St. Pierre 
>  wrote:
> 
>> -Original Message-
>> On 01/02/2020 00:34, Salz, Rich wrote:
>>> 
 Could we add a CI check for PRs that confirms that the target branch is
>>>green in travis?
>>> 
>>> Looking at 
>>> https://docs.travis-ci.com/user/notifications/#conditional-notifications 
>>> and https://config.travis-
>> ci.com/ref/notifications/email it seems like it should be fairly easy 
>> configure builds to do "send email to openssl-commits when builds on
>> master fail"
>> 
>> We already have that.
> 
> Maybe we should make it a requirement that at least all OTC members subscribe 
> to openssl-commits?
> 
> Matthias
> 

RE: Travis in solid red mode again

[Dr. Matthias St. Pierre]

> I thought I was subscribed but don’t seem to see the failures.
> I do get the (very many) PR activity emails….

You are right, those “[openssl]  update” mails generate a lot
of noise. Do we really need them? If not, we could just deactivate them.
Alternatively, we could move the CI failures to a separate openssl-ci list.

Matthias

Re: Travis in solid red mode again

[Matt Caswell]

On 01/02/2020 11:38, Dr. Matthias St. Pierre wrote:
>> I thought I was subscribed but don’t seem to see the failures.
> 
>> I do get the (very many) PR activity emails….
> 
>  
> 
> You are right, those “[openssl]  update” mails generate a lot
> 
> of noise. Do we really need them? If not, we could just deactivate them.

I regularly look at these, so would like to keep them.

Matt


> 
> Alternatively, we could move the CI failures to a separate openssl-ci list.
> 
>  
> 
> Matthias
> 
>  
> 

Re: Travis in solid red mode again

[Matt Caswell]

On 01/02/2020 10:39, Dr Paul Dale wrote:
> I thought I was subscribed but don’t seem to see the failures.
> I do get the (very many) PR activity emails….

Oh, actually, maybe I'm wrong. Is it just Appveyor that posts failures
and not Travis?

Matt

> 
> 
> Pauli
> -- 
> Dr Paul Dale | Distinguished Architect | Cryptographic Foundations 
> Phone +61 7 3031 7217
> Oracle Australia
> 
> 
> 
> 
>> On 1 Feb 2020, at 8:35 pm, Dr. Matthias St. Pierre
>> mailto:matthias.st.pie...@ncp-e.com>>
>> wrote:
>>
>>> -Original Message-
>>> On 01/02/2020 00:34, Salz, Rich wrote:

> Could we add a CI check for PRs that confirms that the target branch is
    green in travis?

 Looking at
 https://docs.travis-ci.com/user/notifications/#conditional-notifications
 and https://config.travis-
>>> ci.com/ref/notifications/email
>>>  it seems like it should be
>>> fairly easy configure builds to do "send email to openssl-commits
>>> when builds on
>>> master fail"
>>>
>>> We already have that.
>>
>> Maybe we should make it a requirement that at least all OTC members
>> subscribe to openssl-commits?
>>
>> Matthias
>>
> 

RE: Travis in solid red mode again

[Dr. Matthias St. Pierre]

> -Original Message-
> From: Matt Caswell 
> Sent: Sunday, February 2, 2020 12:58 AM
> To: Dr Paul Dale ; Dr. Matthias St. Pierre 
> 
> Cc: Salz, Rich ; openssl-project@openssl.org
> Subject: Re: Travis in solid red mode again
> 
> 
> 
> On 01/02/2020 10:39, Dr Paul Dale wrote:
> > I thought I was subscribed but don’t seem to see the failures.
> > I do get the (very many) PR activity emails….
> 
> Oh, actually, maybe I'm wrong. Is it just Appveyor that posts failures
> and not Travis?

I see both CI's posting in January:

https://mta.openssl.org/pipermail/openssl-commits/2020-January/thread.html

Broken: openssl/openssl#30961 (master - 2de5a5f)   Travis CI
Broken: openssl/openssl#30962 (OpenSSL_1_1_1-stable - 10e166a)   Travis CI
Build failed: openssl master.30389   AppVeyor
Build completed: openssl OpenSSL_1_1_1-stable.30390   AppVeyor
Fixed: openssl/openssl#30966 (master - e7b834b)   Travis CI
Fixed: openssl/openssl#30967 (OpenSSL_1_1_1-stable - 2c52a36)   Travis CI
Build failed: openssl master.30394   AppVeyor
Build completed: openssl OpenSSL_1_1_1-stable.30395   AppVeyor
Build failed: openssl master.30405   AppVeyor
Build completed: openssl master.30406   AppVeyor
Build failed: openssl master.30411   AppVeyor
Build failed: openssl master.30412   AppVeyor