[Mac] In browser tests, do not use a bundled child process executable.
Previously, browser test binaries (e.g. browser_tests, interactive_ui_tests, etc.) set up paths so that child processes would use Chromium Helper.app, which matches the production process launching path. However this prevents the child process from linking in test-only code, because it is a distinct binary from the main test executable that acts as the browser process. This change makes it so that the child process binary is the same as the main test binary, which matches how other platforms behave. Bug: 877992 Cq-Include-Trybots: luci.chromium.try:linux_mojo Change-Id: Ic04f0d47726be89d953ea227b8a104dc7bb88c0f Reviewed-on: https://chromium-review.googlesource.com/1193969 Commit-Queue: Robert Sesek <rsesek@chromium.org> Reviewed-by:Mark Mentovai <mark@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Cr-Commit-Position: refs/heads/master@{#587705}
Showing
Please register or sign in to comment