Re: BUG #8271: Configure warning: sys/ucred.h: present but cannot be compiled
От | Andrew Dunstan |
---|---|
Тема | Re: BUG #8271: Configure warning: sys/ucred.h: present but cannot be compiled |
Дата | |
Msg-id | 51D034CE.2050608@dunslane.net обсуждение исходный текст |
Ответ на | Re: BUG #8271: Configure warning: sys/ucred.h: present but cannot be compiled (Andres Freund <andres@2ndquadrant.com>) |
Ответы |
Re: BUG #8271: Configure warning: sys/ucred.h: present but cannot be compiled
|
Список | pgsql-bugs |
On 06/30/2013 09:20 AM, Andres Freund wrote: > On 2013-06-30 15:17:20 +0200, Andres Freund wrote: >> Andrew: Could we perhaps check for the "Report this to" bit in the >> buildfarm? > FWIW: I checked that there are no other reports on HEAD atm. > I'm not sure what you're asking here. Where exactly do you thing buildfarm failures should be reported? There are four mailing lists that get buildfarm status reports: * <http://lists.pgfoundry.org/mailman/listinfo/pgbuildfarm-status-all> gets a summary of every single reported build * <http://lists.pgfoundry.org/mailman/listinfo/pgbuildfarm-status-fail> gets a summary of every build that fails * <http://lists.pgfoundry.org/mailman/listinfo/pgbuildfarm-status-chngs> gets a summary of every build that results in a status change * <http://lists.pgfoundry.org/mailman/listinfo/pgbuildfarm-status-green> gets a summary of every build that results in a status change to or from green (a.k.a. OK) These are available in digest form. What we could possibly add is a feature to email a committer about a commit included in the changeset of a failing build. The main trick would be to avoid flooding the committers, so that a commit would only be notified once. Magnus has suggested something like this previously, but I haven't looked at it much - I can again. It might not be too hard. cheers andrew
В списке pgsql-bugs по дате отправления: