hi, I fully agree with Marcel.
As previously stated (on Jukka's reference discussion) I think we need to see the failures each time, otherwise we don't react accordingly. The proper way to handle a failure is to create a jira issue and mark the test as ignored, this practice also keeps the noise down on the list. The spam filter situation is unfortunate, I've also been seeing huge amounts of moderation emails caused by travis (basically each notification hits the spam filter). Is there a way to correct that on a larger scale, rather than approving each one manually? best, alex On Tue, May 14, 2013 at 3:46 PM, Jukka Zitting <jukka.zitt...@gmail.com>wrote: > Hi, > > On Tue, May 14, 2013 at 4:36 PM, Marcel Reutegger <mreut...@adobe.com> > wrote: > > the last travis notification I got via the oak-dev list was from > yesterday for a > > successful build [0]. travis is broken or this is due to how we > configure the > > travis build. all builds after 1521 failed [1] and I really think it's > better we get > > notifications for every failure and not just when the result changes. we > can > > still mark tests with ignore if we are not able to quickly fix an issue. > > See [1] for a recent related thread. My position is still that a > single failure notification should be enough to alert us about a > problem with the build. > > The problem here seems rather to be that we never got even the single > notification about build #1522 going bad. It didn't even hit the > moderation queue of oak-dev@, which leads me to suspect that Apache's > spam filters may be capturing at least some of the HTML notifications > sent by Travis. > > Changing the configuration to send notifications for all failing > builds may help work around such a problem with spam filters, but a > better solution would be nice. > > [1] http://markmail.org/message/gfhjotihhxsiw7pi > > BR, > > Jukka Zitting >
