-
Notifications
You must be signed in to change notification settings - Fork 11
Description
We spotted an increasing number of CI failures using vscode-test that seem to be flaky and likely caused by some timing issues. Example of run at https://github.com/ansible/vscode-ansible/actions/runs/21067364468/job/60587877011#step:16:779 exact error listed below, error that is causing the entire pipeline to fail.
Error: ENOTEMPTY: directory not empty, rmdir '/tmp/vsc-coverage-8b22aabc-fead-4441-9101-bbff43f023b2'
Some change is needed in order to prevent this from happening. Sadly we also discovered some time ago that there is no way to configure coverage options inside .vscode-test.mjs files as they only allow vscode-test specific settings and mocha settings but not settings for the coverage framework (only cli args work and they are very limiting).
The code comes from
vscode-test-cli/src/cli/coverage.mts
Line 23 in 044359f
| public readonly targetDir = join(tmpdir(), `vsc-coverage-${randomUUID()}`); |
and apparently it should be possible to configure
tempDirectory for coverage but is not.