commit b9df8df70fde84bd13558011bad6dfbbeb714599
author Bryan C. Mills <bcmills@google.com> Thu Jul 18 17:41:45 2019 -0400
committer Bryan C. Mills <bcmills@google.com> Mon Jul 22 21:43:31 2019 +0000
tree 82fc3c4af08de511dca6f5b02f1224c864805340
parent 5e21032b3d179a8bc0d9e70e4725629defad9d8b

doc/go1.13: mention the effect of testing.Init on package initialization

Fixes #31859

Change-Id: I228ed93f9466d1a22f8796964f5d2f056ab9b62f
Reviewed-on: https://go-review.googlesource.com/c/go/+/186818
Run-TryBot: Bryan C. Mills <bcmills@google.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Ian Lance Taylor <iant@golang.org>
Reviewed-by: Caleb Spare <cespare@gmail.com>
Reviewed-by: Daniel Martí <mvdan@mvdan.cc>

doc/go1.13.html

diff --git a/doc/go1.13.html b/doc/go1.13.html
index 11190a1..9dead68 100644
--- a/doc/go1.13.html
+++ b/doc/go1.13.html
@@ -841,8 +841,10 @@
     </p>
 
     <p><!-- CL 173722 -->
-      Testing flags are now registered in the new <a href="/pkg/testing/#Init"><code>Init</code></a> function.
-      As a result, testing flags are now only registered when running a test binary.
+      Testing flags are now registered in the new <a href="/pkg/testing/#Init"><code>Init</code></a> function,
+      which is invoked by the generated <code>main</code> function for the test.
+      As a result, testing flags are now only registered when running a test binary,
+      and packages that call <code>flag.Parse</code> during package initialization may cause tests to fail.
     </p>
 
 </dl><!-- testing -->