I get the following logspam when I try running tests:

...
12-03 21:16:55.375 17433 17466 W chromium: [1203/211655.374413:WARNING:trace_startup_config.cc(189)] The trace config file does not exist.
...

This comes from here [1], but I'm not sure why we see this, since the tests I'm running don't do any Tracing. This logspam happens for seemingly any test (e.g., AwSettingsTest#testBlockNetworkLoadsWithHttpResources in Chromium, also repros for AndroidX tests).

Tim, is this expected? Is this a bug in our AW's tracing layer, or perhaps in the tracing component itself?

[1] https://cs.chromium.org/chromium/src/components/tracing/common/trace_startup_config.cc?l=189&rcl=99b4b74d7041a442705831c39aafbf136fb56fb8