1.39.0 logs have DEBUG log level info and can't be changed to INFO, which makes them 1000x bigger

mikamikaWolt commented 1 week ago

Is there an existing issue for this?

[X] I have searched the existing issues and didn't find mine.

Steps to reproduce

Run any flow on a local machine on 1.36.0 and 1.39.0, then compare maestro.log from two runs.

Actual results

maestro has test suite logs in /.maestro/tests//maestro.log Now it contains DEBUG logs, mostly from io.grpc.netty.NettyClientHandler.log. It can't be turned off, but this makes the log file much bigger. For example, my short sign in to the app test on 1.36.0 has 8KB log, but with 1.39.0 it is a whopping 4 MB. This makes it too expensive to store logs as an artifact in CI or send them with test reports somewhere.

Expected results

The default log level should be INFO as before. Log level should be available to configure.

About app

Any mobile app: problem is with maestro logs, not with the app.

About environment

macOS 15.1

Logs

``` ```

Maestro version

1.39.0

How did you install Maestro?

install script (https://get.maestro.mobile.dev)

Anything else?

No response

linear[bot] commented 1 week ago

MA-2517 1.39.0 logs have DEBUG log level info and can't chnaged to INFO, which makes them 1000x bigger

Fishbowler commented 1 week ago

The ask is to make log levels configurable. Perhaps we can go one better, by redirecting the Netty GRPC logging to a separate file? Would need a bit of juggling in how LogConfig.kt is called, but looks achievable.

mobile-dev-inc / maestro