-
Notifications
You must be signed in to change notification settings - Fork 18k
dashboard: mail being sent too eagerly #3683
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
Weird. The code is there to only notify on an ok->bad transition. Not sure why it decided to stop working now. http://code.google.com/p/go/source/browse/misc/dashboard/app/build/notify.go?spec=svnf82e8102025c9866f250ceb667a06fe3dbe50446&name=f82e8102025c&r=f82e8102025c9866f250ceb667a06fe3dbe50446#32 |
This happened again overnight with the 3 freebsd/386 mails that should have been 1. Can you add some logging to the app, recording the builder result that triggered the mail? For example instead of returning ok, present, the function could just return the *Result and then you could check r != nil && r.OK in the test instead of present && ok. Doing that would mean you're holding the result and can log it as a reason to send the mail. In fact it would be nice to log the entire result string. |
I've done what you described. Let's see what happens. http://code.google.com/p/go/source/detail?r=d137b2a8007ae64eaeeeec0156f8d2a9eb2b5903 |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Attachments:
The text was updated successfully, but these errors were encountered: