| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-www(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Buildfarm server is failing to collect some reports |
| Date: | 2026-08-12 02:56:34 |
| Message-ID: | 2d122dee-3c33-4c66-9d9b-50c5ea86fd21@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On 2026-08-11 Tu 9:35 PM, Tom Lane wrote:
> I wondered why my animals were showing wildly inconsistent
> last-report times on different branches. The answer seems
> to be that some of the reports are getting dropped by the
> server. Here's log output from the most recent case on
> longfin:
>
> -----
> Query for: stage=OK&animal=longfin&ts=1786479121
> Target: https://buildfarm.postgresql.org/cgi-bin/pgstatus.pl/.256h.ce7e2d2fd90b3c35beec0b9d5727c77ccedbf714a77be116b2a281dcee2cd296
> Status Line: 500 Server closed connection without sending any data back
> Content:
> Server closed connection without sending any data back at /System/Library/Perl/Extras/5.34/Net/HTTP/Methods.pm line 391.
>
> Web txn failed with status: 1
> -----
>
> The other reports look similar.
>
> It looks like this has happened at least ten times today,
> across all four of my animals. I'm not seeing indications
> that it happened before today.
>
>
The only errors I see on the buildfarm logs are from a single host which
is attempting to upload logs that are too large. I assume that's not
yours, will confirm if you let me have the address privately.
Otherwise, it's apparently an infrastructure problem.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2026-08-12 11:45:50 | Re: Buildfarm server is failing to collect some reports |
| Previous Message | Tom Lane | 2026-08-12 01:35:24 | Buildfarm server is failing to collect some reports |