| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-www(at)lists(dot)postgresql(dot)org |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Buildfarm server is failing to collect some reports |
| Date: | 2026-08-12 01:35:24 |
| Message-ID: | 2575433.1786498524@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2026-08-12 02:56:34 | Re: Buildfarm server is failing to collect some reports |
| Previous Message | Tristan Partin | 2026-08-11 20:08:44 | Broken SSH Key Parsing |