Repository navigation
Code coverage build fails to instrument file in use #7417
Description
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=976256&view=logs&j=12b34f85-96db-5b04-05cf-faf2be278867
Build error leg or test failing: Windows_x64 / Windows_x64 Build_Debug / Run All Tests.
Pull request: #7414
Error Message
Fill the error message using step by step known issues guidance.
{
"ErrorMessage": "",
"ErrorPattern": ["Unable to instrument module", "The process cannot access the file .* because it is being used by another process."],
"BuildRetry": false,
"ExcludeConsoleLog": false
}Known issue validation
Build: 🔎
Result validation: ❌ There was a problem creating a known issue. Check the exception message and proceed accordingly: Invalid pattern ' The process cannot access the file .*\Microsoft.ML.TestFramework.pdb' because it is being used by another process.' at offset 40. Unrecognized escape sequence \\M.
Validation performed at: 3/12/2025 1:10:33 AM UTC
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 0 | 0 |
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=976256
Error message validated: [ The process cannot access the file .*\\Microsoft.ML.TestFramework.pdb' because it is being used by another process.]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 3/12/2025 5:28:06 PM UTC
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 0 | 0 |
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=976256
Error message validated: [Unable to instrument module The process cannot access the file .* because it is being used by another process.]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 3/12/2025 5:30:54 PM UTC
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 0 | 0 |
Report
| Build | Repository | Step Name | Console log | Pull Request |
|---|---|---|---|---|
| 1619784 | dotnet/machinelearning | Run All Tests. | Log | #7753 |
| 1617972 | dotnet/machinelearning | Run All Tests. | Log | |
| 1614217 | dotnet/machinelearning | Run All Tests. | Log | #7744 |
| 1613533 | dotnet/machinelearning | Run All Tests. | Log | #7743 |
| 1608882 | dotnet/machinelearning | Run All Tests. | Log | #7733 |
| 1607506 | dotnet/machinelearning | Run All Tests. | Log | #7713 |
| 1607125 | dotnet/machinelearning | Run All Tests. | Log | #7729 |
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 0 | 7 |
Activity
hiSandog commentedon Jul 9, 2026
A useful next step would be a minimal fixture for Code coverage build fails to instrument file in use that includes one failing input and one nearby control case. That would make it clear whether the fix addresses the reported edge case without widening behavior unexpectedly.
20Analysis/KnownIssueJsonStepByStep.mdis a useful concrete anchor because it is named directly in the report.rosebyte commentedon Sep 9, 2026
triage: we will take a look when we will be inspecting CI