| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Andrew Dunstan <adunstan(at)postgresql(dot)org>, pgbuildfarm(at)rjuju(dot)net |
| Subject: | what's going on with lapwing? |
| Date: | 2025-03-03 19:38:06 |
| Message-ID: | CA+TgmoYEAm-KKZibAP3hSqbTFTjUd47XtVcf3xSFDpyecXX9uQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
lapwing has been failing sepgsql-check for over a month, but there's
no log file:
I feel like something must be broken with logfile collection in the
buildfarm client, because I keep seeing failures like this where
there's no log to view. It's hard to know whether this is a
configuration issue with this BF member or whether something actually
needs fixing. In any case, we should try to figure out what's going on
here.
Apologies if this has been discussed elsewhere and I have missed it.
Pointers appreciated.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matheus Alcantara | 2025-03-03 19:43:07 | Re: SQL:2023 JSON simplified accessor support |
| Previous Message | James Hunter | 2025-03-03 19:19:59 | Re: int64 support in List API |