tests: disable `worker.backgroundclose` to stabilize a test on Windows
authorMatt Harbison <matt_harbison@yahoo.com>
Fri, 04 Oct 2024 12:53:02 -0400
changeset 51955 b8528c8bebf5
parent 51954 b6ce567d5bea
child 51956 3b46e8e6a401
tests: disable `worker.backgroundclose` to stabilize a test on Windows TIL that `worker.enabled=0` doesn't prevent these workers from spinning up. At any rate, there's already a whole lot of conditionalized output following `cat client.log`, the placement of the "starting 4 threads for background file closing" message seems unstable, and we don't care about those worker threads here. Preventing the message is better for test maintenance.
tests/test-clone-stream-revlog-split.t
--- a/tests/test-clone-stream-revlog-split.t	Fri Oct 04 11:22:30 2024 -0400
+++ b/tests/test-clone-stream-revlog-split.t	Fri Oct 04 12:53:02 2024 -0400
@@ -68,7 +68,7 @@
 
   $ ( \
   >    hg clone --debug --stream -U http://localhost:$HGPORT1 \
-  >    clone-while-split > client.log 2>&1; \
+  >    clone-while-split --config worker.backgroundclose=0 > client.log 2>&1; \
   >    touch "$HG_TEST_STREAM_WALKED_FILE_3" \
   > ) &