| From: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: test/modules/test_oat_hooks vs. debug_discard_caches=1 |
| Date: | 2022-11-19 14:07:45 |
| Message-ID: | 1bbb0340-3dbe-717a-4094-a4344238245b@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/19/22 14:51, Andrew Dunstan wrote:
>
> On 2022-11-19 Sa 05:34, Tomas Vondra wrote:
>>
>> I wonder if it'd make sense to have some simple & optional alerting
>> based on how long ago the machine reported the last result. Send e-mail
>> if there was no report for a month or so would be enough.
>
>
> This has been part of the buildfarm for a very long time. See the alerts
> section of the config file.
>
I'm aware of that, but those alerts are not quite what I was asking
about. Imagine the run gets stuck for whatever reason (like infinite
loop somewhere), or maybe the VM fails / gets inaccessible for whatever
reason, perhaps because of some sort of human error so that the cron
does not get run ...
I don't think alerting from the client would catch those cases, but
maybe it's a rare issue and I'm overthinking it.
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-11-19 14:33:22 | Re: test/modules/test_oat_hooks vs. debug_discard_caches=1 |
| Previous Message | Andrew Dunstan | 2022-11-19 13:51:28 | Re: test/modules/test_oat_hooks vs. debug_discard_caches=1 |