From: | "Tristan Partin" <tristan(at)neon(dot)tech> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Andres Freund" <andres(at)anarazel(dot)de>, <pgsql-hackers(at)postgresql(dot)org>, "Peter Eisentraut" <peter(at)eisentraut(dot)org> |
Subject: | Re: meson: Stop using deprecated way getting path of files |
Date: | 2023-12-04 20:26:42 |
Message-ID: | CXFTYO2HO502.1LVU41KCXAXIU@neon.tech |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon Dec 4, 2023 at 2:10 PM CST, Tom Lane wrote:
> "Tristan Partin" <tristan(at)neon(dot)tech> writes:
> > On Fri Dec 1, 2023 at 12:16 PM CST, Tristan Partin wrote:
> >>> Ok, so what I found is that we still have build farm animals using
> >>> Python 3.4, specifically the AIX machines. There was also at least one
> >>> Python 3.5 user too. Note that this was a manual check.
>
> > I think I'll probably work on a tool for querying information out of the
> > build farm tonight to make tasks like this much more automated.
>
> Not sure what you were using, but are you aware that SQL access to the
> buildfarm database is available to project members? My own stock
> approach to checking on this sort of thing is like
>
> select * from
> (select sysname, snapshot, unnest(string_to_array(log_text, E'\n')) as l
> from build_status_log join snapshots using (sysname, snapshot)
> where log_stage = 'configure.log') ss
> where l like 'checking for builtin %'
This looks useful. I had no idea about this. Can you send me any
resources for setting this up? My idea was just to do some web scraping.
--
Tristan Partin
Neon (https://neon.tech)
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2023-12-04 20:58:02 | Re: trying again to get incremental backup |
Previous Message | Andrew Dunstan | 2023-12-04 20:11:47 | Re: Remove MSVC scripts from the tree |