GitLab

With the addition of ToGNString(pretty=True) (crrev.com/c/2231505),
.info files can be pretty printed. Since .info files are committed into
 upstream and downstream repos, so we'll need to regenerate these files,
and commit them (with multiple CLs).

However, during Android Chrome build aar.py is called with the flag
--assert-file-info to ensure .aar files are consistent with existing
.info files,  by regenerating .info data, followed by direct string
comparisons.

To facilitate migration, this CL weakens --assert-file-info by removing
all whitespaces before comparison. This is temporary; the CL will be
reverted once migration completes.

Bug: 1074446
Change-Id: I1633410267190a5c59b72bd52f58c86e6210463f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2235973Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Samuel Huang <huangs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#776088}