| From: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: meson logs environment |
| Date: | 2023-02-21 10:27:25 |
| Message-ID: | CAN55FZ3rFGtFukRZ+TOb=GunkCEywB8+D=-==k+joTMo=CHijA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Regards,
Nazir Bilal Yavuz
Microsoft
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shiy.fnst@fujitsu.com | 2023-02-21 10:31:29 | RE: "out of relcache_callback_list slots" after multiple calls to pg_logical_slot_get_binary_changes |
| Previous Message | Bharath Rupireddy | 2023-02-21 09:46:39 | Re: Seek for helper documents to implement WAL with an FDW |