TestTscNoEmitWatch non-deterministic failures

[jakebailey]

https://github.com/microsoft/typescript-go/actions/runs/16840512857/job/47710361159 and https://github.com/microsoft/typescript-go/actions/runs/16893129096/job/47857409642 failed with:

--- FAIL: TestTscNoEmitWatch (0.00s)
    --- FAIL: TestTscNoEmitWatch/semantic_errors_tsc_baseline (0.15s)
        baseline.go:211: the baseline file testdata/baselines/reference/tscWatch/noEmit/semantic-errors.js has changed. (Run `hereby baseline-accept` if the new baseline is correct.)
FAIL
coverage: 28.1% of statements in ./...

--- FAIL: TestTscNoEmitWatch (0.00s)
    --- FAIL: TestTscNoEmitWatch/dts_errors_without_dts_enabled_tsc_baseline (0.22s)
        baseline.go:211: the baseline file testdata/baselines/reference/tscWatch/noEmit/dts-errors-without-dts-enabled.js has changed. (Run `hereby baseline-accept` if the new baseline is correct.)
FAIL
coverage: 28.1% of statements in ./...

So there is still some non-determinism in these tests. Running them repeatedly might surface the problem.

Unfortunately, this caching job does not upload artifacts (it's not supposed to fail).

[sheetalkamat]

Unless i see baselines or repro, its hard to see whats causing this. I havent seen this on my machine or dev boxes i am using

[sheetalkamat]

May be add, baseline diffing it fails to that job to see whats the issue ?

[jakebailey]

I'll make a PR which tries to do that. Theoretically even main may have hit this, since it's random, but extra printing can't hurt.