fix(bazel/browsers): exclude a log file that chromium writes to on linux causing cache misses

[kormide]

@devversion I think this is the source of cache misses I'm seeing in angular/angular#47161. In unsandboxed execution (which is the case for targets run under RBE, right?) chromium will write to this log file each run in under the external dir causing remote cache misses on successive builds.

[josephperrott]

LGTM

[kormide]

As a potential workaround, in my protractor config file I tried passing the flags --disable-logging and --disable-and-delete-previous-log however they had no effect. Perhaps those flags don't work on the current version of chromium supported.

Passing --log-level=3 helped to keep this file empty, but it still gets created when it doesn't exist after a fresh bazel run..

[angular-robot]

This PR was merged into the repository by commit 7af5d34.

[devversion]

Do we need a similar thing for e.g. Mac or Windows?

[kormide]

I'm not sure. I'll test both and report back.

[kormide]

@devversion It doesn't appear to cause cache misses on Windows.

On OSX, I can't determine due to other issues. Using bazel-provided chromium in unsandboxed execution fails early because it can't build runfiles due to all of the files with spaces in them. If I exclude all of those files, then the runfiles can be built but chromium fails, probably because it needs some of those files.

It's not clear to me why it works with sandboxed execution on OSX but fails when run outside of the sandbox. My understanding was that using --nobuild_runfile_links fixed the runfiles with spaces issue but that doesn't seem to work for unsandboxed execution.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}