-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Minor - P4
-
Affects Version/s: None
-
Component/s: None
-
None
-
DevProd Build
-
Fully Compatible
-
Windows
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Problem
dbtest on all four Windows variants of mongodb-mongo-v4.4 (windows, windows-debug, enterprise-windows, enterprise-windows-inmem) system-fails on every activated run since 2026-08-31. No tests fail; the failing command is the "run diskstats" background monitor (task step 2).
Root cause
"run diskstats" (function defined at etc/evergreen.yml:751 @ 241f229ba7) runs on Windows:
typeperf -cf disk_counters.txt -si 5 -o mongo-diskstats
The command has no working_dir, so mongo-diskstats.csv is written into the agent's host-persistent scratch directory. Every recycled Windows host already has this file from a previous task that used "run diskstats", so typeperf prompts The file "mongo-diskstats.csv" already exists, overwrite? [y/n], reads EOF (background commands have no stdin), and exits with code 183 (ERROR_ALREADY_EXISTS). The agent fails any task whose background command exits non-zero, so the task is marked system-failed: Background command 'shell.exec' in function 'run diskstats' (step 2 of 5)' failed ... exited with code 183.
Verified via the task system logs of the 10/14 and 08/31 failures (identical prompt line) and the "Disk Stats" artifacts, which are stale files from previous tasks. The Linux/OSX branches of the same function redirect with > (truncate), so only Windows is affected.
Fix
Drop {- func: "run diskstats"} from the dbtest and unittests task groups on the v4.4 branch (lines 4139 and 4209 @ 241f229ba7). Master removed this function entirely in SERVER-64802 (2022-03); v4.4 and v5.0 are the only branches still carrying it. dbtest on v4.4 Windows variants has never passed since the task was added (~2025-12), so no CI signal is lost.
Alternative (not chosen): make the script idempotent (rm -f the output file before invoking typeperf, or set working_dir: src).
v5.0 carries the same latent pattern, but its windows-debug variant is a "-suggested" variant that does not run dbtest on mainline, so no change is needed there.
References
- BF-46815 (tracked build failure; 4 BFGs on 10/14, recurrence on every run since 08/31)
- Failing task (10/14, windows-debug): mongodb_mongo_v4.4_windows_debug_dbtest_241f229ba7bf0b7e3e47e62acd31e7c54726fdd3_26_10_14_13_26_21