Quartz Unit Test Lock Recovery

Recover from CS2012 DLL lock failures when running Quartz unit tests Use when this capability is needed.

tomevault-io Updated

File contents

Context

On Windows, dotnet test src\Quartz.Tests.Unit\Quartz.Tests.Unit.csproj may fail with CS2012 before tests run because artifacts\obj\Quartz.Tests.Unit\debug\Quartz.Tests.Unit.dll is locked by a lingering VBCSCompiler process.

Pattern

  1. Capture locking PID from CS2012 output.
  2. Stop only that PID (Stop-Process -Id <PID> -Force).
  3. Rerun tests with shared compilation disabled and single-node execution: dotnet test src\Quartz.Tests.Unit\Quartz.Tests.Unit.csproj -m:1 /p:UseSharedCompilation=false

Expected Outcome

Build succeeds and tests execute normally; if failures remain, then they are likely real test/product failures.


Source: quartznet/quartznet — distributed by TomeVault.

tomevault-io/skills-registry/tree/main/quartznet--quartznet--quartznet commit 96437bb8f5

Frequently asked questions

npx skillmds@latest add tomevault-io/quartz-unit-test-lock-recovery