I observed this while reviewing PR #861. If a test suite uses mocks.init() and also uses skipOnWin, skipOnWin should output stderr indicating the test is skipped, but the message is actually suppressed by mocks.

We can fix this by capturing process.stderr.write on startup, within utils.js, instead of using console.warn() directly.