Experimental Physics and
Industrial Control System

"Johnson, Andrew N." <[email protected]> · Sun, 16 Sep 2018 01:47:11 +0000

It wasn’t getting caught as spam, but I did change my email address in my ~/.gitconfig and on Github and it appears that signing back into Travis re-enabled emails, so I guess it hadn’t received notification about that change.

I agree that we shouldn’t put emails in the travis.yml file.

I haven’t worked out yet why the Travis build of 3.14 was failing. I tried using GnuMake 3.82 on Friday and couldn’t replicate the failure, but I’m pretty sure that it will occur on the other branches as soon as I merge up so I should probably commit the fix to the 3.14 branch first if we can work out what needs changing.

- Andrew

-- 
Sent from my iPad

> On Sep 14, 2018, at 6:05 PM, Michael Davidsaver <[email protected]> wrote:
> 
>> On 09/14/2018 02:10 PM, Andrew Johnson wrote:
>> So why hasn't Travis been sending me emails about the broken epics-base
>> builds that I've been pushing? It's a shame that the final 3.14.12.8
>> build failed on Travis, but I'm not going to fix it and re-tag. I
>> assumed that the absence of emails from it was an indication of no build
>> problems, but no... (I haven't even checked Appveyor).
>> 
>> I really don't understand how/when Travis (and Appveyor for that matter)
>> decide when they should email me; can anyone explain where/how I should
>> change my settings to ensure that it does?
> 
> https://docs.travis-ci.com/user/notifications/
> 
> maybe @anl.gov is treating these as spam?
> 
>> Travis CI only sends build notifications to email addresses registered on GitHub
> 
> Or maybe you've given github.com a different primary email?
> 
>> The most common cause for not receiving build notifications ...
>> is the use of an email address that’s not registered and verified on GitHub
> 
> 
>> If there’s a setting specified, Travis CI only sends an emails to the addresses specified there, rather than to the committer and author.
> 
> FYI, I've avoided configuring email notifications via .travis.yml because of
> I find this behavior unhelpful in the case pull requests, when the author/committer
> should find out first.

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System