Re: Travis in solid red mode again

2020-02-07 Thread Matt Caswell
On 03/02/2020 19:19, Matthias St. Pierre wrote: > Mission accomplished, Travis just turned green again on master  :-) Every one of the last 12 master jobs have failed to complete successfully due to a travis timeout. Apart from the build that is timing out (enable-msan), all the other builds

Re: Travis in solid red mode again

2020-02-03 Thread Matthias St. Pierre
Mission accomplished, Travis just turned green again on master  :-) https://travis-ci.org/openssl/openssl/builds/645563965?utm_source=github_status_medium=notification Thanks to Matt, Richard and everybody else who participated in fixing it. Matthias

Re: Travis in solid red mode again

2020-02-03 Thread Salz, Rich
> 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

Re: Travis in solid red mode again

2020-02-03 Thread Salz, Rich
>Oh, actually, maybe I'm wrong. Is it just Appveyor that posts failures and not Travis? Yes. You need to config travis to mail failures, as I pointed out in my earlier message.

Re: Travis in solid red mode again

2020-02-01 Thread 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 |

Re: Travis in solid red mode again

2020-02-01 Thread 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

RE: Travis in solid red mode again

2020-02-01 Thread 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

Re: Travis in solid red mode again

2020-02-01 Thread 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: >

RE: Travis in solid red mode again

2020-02-01 Thread 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

Re: Travis in solid red mode again

2020-02-01 Thread 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 >

Re: Travis in solid red mode again

2020-01-31 Thread Matt Caswell
On 31/01/2020 22:55, Matt Caswell wrote: > > > On 31/01/2020 17:07, Matthias St. Pierre wrote: >> >> After a much to short green period, Travis has turned to solid red mode >> again: >> >> https://travis-ci.org/openssl/openssl/builds?utm_medium=notification_source=github_status >> >> >> This

Re: Travis in solid red mode again

2020-01-31 Thread Matt Caswell
On 31/01/2020 17:07, Matthias St. Pierre wrote: > > After a much to short green period, Travis has turned to solid red mode > again: > > https://travis-ci.org/openssl/openssl/builds?utm_medium=notification_source=github_status > > > This fact causes a lot of pain for reviewers, because