| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: meson logs environment |
| Date: | 2023-02-21 12:47:13 |
| Message-ID: | f53927f2-32ac-d358-d017-b13f28a1bd27@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-02-21 Tu 05:27, Nazir Bilal Yavuz wrote:
> Hi,
>
> On Tue, 21 Feb 2023 at 04:48, Andrew Dunstan<andrew(at)dunslane(dot)net> wrote:
>>
>> I've noticed that `meson test` logs the complete environment in meson_logs/testlog.txt. That seems unnecessary and probably undesirable for the buildfarm client. Is there any way to suppress that, or at least only print some relevant subset? (The buildfarm client itself only reports an approved set of environment variables).
> There is an open issue on the meson:
> https://github.com/mesonbuild/meson/issues/5328 and I confirm that
> `env --ignore-environment PATH="$PATH" meson test` prevents
> environment variables from being logged.
>
Ouch, OK, I'll do something like that. The fact that this issue has been
open since 2019 is not encouraging.
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nazir Bilal Yavuz | 2023-02-21 13:11:19 | Re: Refactor calculations to use instr_time |
| Previous Message | David Geier | 2023-02-21 12:02:35 | Re: Parallel Bitmap Heap Scan reports per-worker stats in EXPLAIN ANALYZE |