tree f87b652823d2fd3b40ed62b9a79bbfd87419eb5c
parent d724af538c0bb1a9f0c792ebc5d3457a686e14e5
author Scott Graham <scottmg@chromium.org> 1528836409 -0700
committer Scott Graham <scottmg@chromium.org> 1528843054 +0000

Make gn_unittests quiet when there's no errors

--- BEFORE ---

.../gn$ ninja -C out && out/gn_unittests
ninja: Entering directory `out'
ninja: no work to do.
[225/434] NinjaBinaryTargetWriterTest.DupeObjFileErrorERROR Duplicate object file
The target //foo:bar
generates two object files with the same name:
  obj/bar.a.o

It could be you accidentally have a file listed twice in the
sources. Or, depending on how your toolchain maps sources to
object files, two source files with the same name in different
directories could map to the same object file.

In the latter case, either rename one of the files or move one of
the sources to a separate source_set to avoid them both being in
the same target.
[320/434] StringUtils.ExpandStringLiteralIdentifier
hello
hello #1
hello #1/two
hello #1
hello #1one
hello #11
one11
{
  one = 1
}
[1]

A

�
\
\b
"$\
[321/434] StringUtils.ExpandStringLiteralExpressionhello #1
hello #1
[434/434] XmlElementWriter.TestXmlEscape
PASSED

--- AFTER ---

.../gn$ ninja -C out && out/gn_unittests
ninja: Entering directory `out'
ninja: no work to do.
[434/434] XmlElementWriter.TestXmlEscape
PASSED

Change-Id: I373254af11f962e6876963507e8f10e0e258d28d
Reviewed-on: https://gn-review.googlesource.com/1360
Reviewed-by: Brett Wilson <brettw@chromium.org>