Avoid performing Android OMR1 dex compile workaround on local builds
The workaround causes perf regressions on the bots because it is compiling the dex in the background. This is expected, so ignore the workaround on local builds. This also pushes compiling the dex to after startup in a best effort task, to hopefully not compete with any crucial startup tasks and avoid wiping any compiled dex before loading the chrome split. Bug: 1160025, 1160029, 1159608 Change-Id: I704a3c3027ac13b7dc461a18bcc4e18f6e99c62d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2597890 Commit-Queue: Clark DuVall <cduvall@chromium.org> Commit-Queue: Andrew Grieve <agrieve@chromium.org> Reviewed-by:Andrew Grieve <agrieve@chromium.org> Auto-Submit: Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#838505}
Showing
Please register or sign in to comment