diff --git a/NEWS b/NEWS
index 72a12671..c3bfe3a8 100644
--- a/NEWS
+++ b/NEWS
@@ -32,16 +32,11 @@ GNU Autoconf NEWS - User visible changes.
   for large files and/or timestamps after 2038 are *available*
   but not enabled by default.
 
+  This is the cause of the AC_SYS_LARGEFILE, AC_SYS_YEAR2038, and/or
+  AC_SYS_YEAR2038_RECOMMENDED testsuite failures on some systems.
   See <https://savannah.gnu.org/support/index.php?110983> for details
   and a workaround.
 
-*** “autoconf: forbidden tokens, basic” testsuite failure
-
-  We believe this is another subtle bug in autom4te’s handling of
-  timestamps that are very close together.  It only happens on some
-  operating systems and/or some file systems.  It can safely be ignored.
-  See <https://savannah.gnu.org/support/index.php?110986> for more detail.
-
 *** “Substitute and define special characters” testsuite failure
 
   We believe this to be a bug in some versions of NetBSD /bin/sh.
diff --git a/tests/tools.at b/tests/tools.at
index 84109d6c..7209ba90 100644
--- a/tests/tools.at
+++ b/tests/tools.at
@@ -474,11 +474,17 @@ configure.ac:5: error: possibly undefined macro: _AS@&t@_BAR
 configure.ac:6: error: possibly undefined macro: d@&t@nl
 ]])
 
+# On a file system with coarse timestamp resolution (1 or 2s),
+# configure and autom4te's cache files can easily have equal
+# timestamps, in which case autom4te will consider the cache
+# to be stale.  Ensure configure's timestamp is newer.
 AT_MTIME_DELAY
+touch configure
 
-# A second run (without --force) should succeed and yield only the
-# warnings about AC_INIT and AC_OUTPUT.
-AT_CHECK_M4([autoconf], 0, [],
+# Since warnings are replicated from the cache but "possibly undefined
+# macro" errors are not, a second run, without --force, should succeed
+# and should yield only the warnings about AC_INIT and AC_OUTPUT.
+AT_CHECK_M4([autoconf --verbose], 0, [],
 [[trailer.m4: warning: AC_INIT was never used
 trailer.m4: warning: AC_OUTPUT was never used
 ]])