On 19/05/14 09:06, Herbert Duerr wrote: > On 16.05.2014 11:10, Herbert Duerr wrote: >> On 15.05.2014 07:54, Ariel Constenla-Haile wrote: >>> On Tue, Apr 15, 2014 at 08:42:12AM +0000, [email protected] wrote: >>>> Hi! , The openoffice-linux64-nightly builder has just completed a run >>>> >>>> STATUS: Success >>>> [...] >>> >>> This last mail was from a month ago, aren't the build bots sending this >>> notification any longer? >> >> [...] >> So the main suspect is AOO's custom messageFormatter. Maybe it throws an >> exception that is internally caught by the buildbot software? Since we >> don't have access (AFAIK) to the buildbot's stderr output we have to >> guess. In revision 908989 I disabled our custom messageFormatter for >> now. Let's see how if we can narrow down the problem in this way. > > So my hypothesis that the custom message formatter caused the problem > was apparently correct: The messages are now sent again after I > (temporarily?) changed the mail notifier configuration to use the > default message formatter. The difference can be seen in [1] (default) > and [2] (custom). The default formatter produces a quite good message so > that I suggest to keep it as is. Fixing the original problem when access > to stderr or the bbot's internal log isn't available isn't worth the > trouble.
+1 for the easy way, using the default formatter Juergen > > [1] > http://mail-archives.apache.org/mod_mbox/openoffice-commits/201404.mbox/%3C20140401083733.90BA5C015E%40aegis.apache.org%3E > > [2] > http://mail-archives.apache.org/mod_mbox/openoffice-commits/201405.mbox/%[email protected]%3E > > > Herbert > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
