Engine code of every test server in the process logs through the last server started (Log.SetSink is process-wide), so the busy-log test's file lock is shared with the classes running alongside: a loop that re-took it at once kept a job engine of JobApiTests waiting to log a failure, and its job "running" past the 15 s deadline (once in 40 loaded runs). The test now fills the log with a few megabytes up front, so sending it takes a while, and adds a line about every millisecond during the downloads; it still fails every run against the old endpoint. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC