meson logs environment

Started by Andrew Dunstanalmost 3 years ago5 messages
#1Andrew Dunstan
andrew@dunslane.net

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).

cheers

andrew

--
Andrew Dunstan
EDB:https://www.enterprisedb.com

#2Nazir Bilal Yavuz
byavuz81@gmail.com
In reply to: Andrew Dunstan (#1)
Re: meson logs environment

Hi,

On Tue, 21 Feb 2023 at 04:48, Andrew Dunstan <andrew@dunslane.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

#3Andrew Dunstan
andrew@dunslane.net
In reply to: Nazir Bilal Yavuz (#2)
Re: meson logs environment

On 2023-02-21 Tu 05:27, Nazir Bilal Yavuz wrote:

Hi,

On Tue, 21 Feb 2023 at 04:48, Andrew Dunstan<andrew@dunslane.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

#4Andres Freund
andres@anarazel.de
In reply to: Andrew Dunstan (#1)
Re: meson logs environment

Hi,

On 2023-02-20 20:47:59 -0500, Andrew Dunstan 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.

It doesn't seem unnecessary to me, at all. It's what you need to rerun the
test in a precise way.

Greetings,

Andres Freund

#5Andrew Dunstan
andrew@dunslane.net
In reply to: Andres Freund (#4)
Re: meson logs environment

On 2023-02-26 Su 12:59, Andres Freund wrote:

Hi,

On 2023-02-20 20:47:59 -0500, Andrew Dunstan 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.

It doesn't seem unnecessary to me, at all. It's what you need to rerun the
test in a precise way.

Well, clearly I'm not the only person who is concerned about it - see
the upstream issue Nazir referred to. In any case, I have got a
procedure in my meson buildfarm client for filtering the inherited
environment to accomodate this verbosity, so there's no need to do
anything else here.

cheers

andrew

--
Andrew Dunstan
EDB:https://www.enterprisedb.com