-
Evan Stade authored
Having a target named "browsertests" means that trying to compile browsertests from the command line, i.e. ninja -C out/Release browsertests will work, when the user probably meant to type ninja -C out/Release browser_tests So the name of the payments target is changed to browser_tests, which is one of two conventions throughout the rest of Chrome. (The other being myfeature_browsertests, which also avoids the afore-mentioned issue.) Now if the user tries to compile `browsertests`, they will see ninja: error: unknown target 'browsertests' Bug: none Change-Id: Ia6b679847744d7edfbfae3b0e20e395e9a4e226b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574751 Auto-Submit: Evan Stade <estade@chromium.org> Reviewed-by:
Rouslan Solomakhin <rouslan@chromium.org> Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org> Commit-Queue: Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#834345}
2872db0c