From 1893fda277bc9bbad7bcea8aaf6c81a95d9750d3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Franc=CC=A7ois=20Pottier?= <francois.pottier@inria.fr>
Date: Wed, 12 Mar 2025 18:13:30 +0100
Subject: [PATCH] CHANGES.

---
 CHANGES.md | 27 +++++++++++++++++++++------
 1 file changed, 21 insertions(+), 6 deletions(-)

diff --git a/CHANGES.md b/CHANGES.md
index f0cbc97..0545dc2 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -2,12 +2,27 @@
 
 ## 2025/MM/DD
 
-* In random testing mode, use a single counter and clock for all tests,
-  instead of starting afresh every time a smaller value of `fuel` is set.
-  This affects the information messages that are emitted once every second.
-
-* Eliminated the internal error `Argh -- reached max environment size`,
-  which under infrequent circumstances could appear.
+* The new functions `run_afl` and `run_random` can be used to start Monolith's
+  testing engine without allowing Monolith to parse the command line.
+  The function `main`, which parses the command line and starts testing,
+  can still be used. (Contributed by Gabriel Scherer.)
+
+* If the command line is parsed via `main` then the command line option
+  `--timeout <seconds>` is supported. In random testing mode (only), this
+  option causes testing to stop after the specified time limit has been
+  reached. The process then terminates with an exit code of either 0 (which
+  means no failure scenarios were detected) or 1 (which means that one or more
+  failure scenarios were detected).
+
+* In random testing mode, a single counter and clock is now used for all
+  tests, whereas previously a fresh counter and clock would be created every
+  time a smaller value of `fuel` was adopted. This affects the information
+  messages that are emitted once every second.
+  (Contributed by Gabriel Scherer.)
+
+* The internal error `Argh -- reached max environment size`,
+  which under infrequent circumstances could appear,
+  has been eliminated.
 
 ## 2024/11/26
 
-- 
GitLab