test(ci): retry Windows teardown EPERM and restart evaluate misses (#17780)

Restart-survival polls treated a recycled renderer as a hard failure.
Wrap those evaluates so "Execution context was destroyed" is a pending
miss. Windows package-lane teardowns after a force-kill used rmSync
with force:true only, which does not absorb EPERM; put them on the
shared maxRetries:8 policy.
This commit is contained in:
Neil
2026-08-31 18:53:01 -07:00
committed by GitHub
parent eff317939a
commit f116d2ca2a
18 changed files with 548 additions and 433 deletions
@@ -1,5 +1,6 @@
import { spawnSync } from 'node:child_process'
import { mkdir, mkdtemp, rm, writeFile } from 'node:fs/promises'
import { mkdir, mkdtemp, writeFile } from 'node:fs/promises'
import { removeTree } from '../../shared/windows-transient-lock-removal'
import { tmpdir } from 'node:os'
import { join } from 'node:path'
import { describe, expect, it } from 'vitest'
@@ -113,7 +114,7 @@ describe('WSL CLI PowerShell boundary', () => {
expect(exitResult.error).toBeUndefined()
expect(exitResult.status).toBe(23)
} finally {
await rm(root, { recursive: true, force: true })
await removeTree(root)
}
}
)