Re: current build failure automated messages

On July 20, Paul Goyette wrote: > For me, I'd be interested in another message that detailed changes in > the sets of Pass/Fail ATF tests. The "New test failures" and "Tests No > Longer Failing" lines are useful for me. As you may have noticed, email is now sent to current-users when an ATF

Re: current build failure automated messages

> Please make it thread properly to the original failure... Should be threaded now. -- Andreas Gustafsson, g...@gson.org

Re: current build failure automated messages

Joerg Sonnenberger wrote: > Please make it thread properly to the original failure... I'll see what I can do about that. -- Andreas Gustafsson, g...@gson.org

Re: current build failure automated messages

On Sun, Jul 31, 2016 at 12:26:58PM +0300, Andreas Gustafsson wrote: > As you may have noticed, the build server now sends email to > current-users not only when the i386 build breaks, but also > when it has been fixed, with the subject line > > Automated report: NetBSD-current/i386 build

Re: current build failure automated messages

As you may have noticed, the build server now sends email to current-users not only when the i386 build breaks, but also when it has been fixed, with the subject line Automated report: NetBSD-current/i386 build success -- Andreas Gustafsson, g...@gson.org

Re: current build failure automated messages

Paul Goyette wrote: > For me, I'd be interested in another message that detailed changes in > the sets of Pass/Fail ATF tests. The "New test failures" and "Tests No > Longer Failing" lines are useful for me. The "new test failures" part I have already implemented some time ago. I have been

Re: current build failure automated messages

Greg Troxel wrote: > I would like to see not only a build-ok message (on transition from fail > to pass), I have now implemented this, and it's being tested on my personal testbed before I deploy it on the TNF one. > but also a fail message on every fresh build during the > failure time, I

Re: current build failure automated messages

On Tue, 19 Jul 2016, Greg Troxel wrote: Andreas Gustafsson writes: I can appreciate that - different people have different preferences and workflows. I'd like to hear the opinions of other developers - if there is a consensus that "build has been fixed" email notifications

Re: current build failure automated messages

Andreas Gustafsson writes: > I can appreciate that - different people have different preferences > and workflows. I'd like to hear the opinions of other developers - > if there is a consensus that "build has been fixed" email notifications > would be useful, I can certainly add

Re: current build failure automated messages

Date:Tue, 19 Jul 2016 12:40:34 +0300 From:Andreas Gustafsson Message-ID: <22413.62866.53313.424...@guava.gson.org> | You don't have to screen scrape the HTML reports - you can get the | underlying data by anonymous rsync, as described in | |

Re: current build failure automated messages

Robert Elz wrote: > | If the page says "Build: OK" at the end, the issue has > | been fixed. At least for me, this is less work overall than it would > | be to handle twice the number of emails. > > I actually cannot imagine that being possible for me, one more e-mail to > delete every few

Re: current build failure automated messages

Date:Sat, 16 Jul 2016 12:15:41 +0300 From:Andreas Gustafsson Message-ID: <22409.64317.493648.115...@guava.gson.org> | It would not be hard to implement, but I'm not sure it would be useful | enough to justify doubling the number of messages to the

Re: current build failure automated messages

Robert Elz wrote: > From time to time there are messages to current-users about > build failures (the messages are generally useful even if sometimes > the content - just what failed - can be most obscure ... but that's > not the point of this message.) > > I was wondering if it would be possible

current build failure automated messages

>From time to time there are messages to current-users about build failures (the messages are generally useful even if sometimes the content - just what failed - can be most obscure ... but that's not the point of this message.) I was wondering if it would be possible to also send "build now