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
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 th
On 2023-02-21 Tu 05:27, Nazir Bilal Yavuz wrote:
Hi,
On Tue, 21 Feb 2023 at 04:48, 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. Is there any way to sup
Hi,
On Tue, 21 Feb 2023 at 04:48, 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. Is there any way to suppress that, or at least only
> print some r
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 approv
