You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@joeloff@MiYanni as template owners. I see a few options for fixing this:
shut down dotnet in between tests (not sure what side effect this would have)
Set the BaseIntermediateOutputPath for each build of the shared project (only fixes 10 tests and doesn't affect locking of the build output, only the obj)
Copy the test project to a unique folder before building (this is what the other sdk tests do but there isn't existing infrastructure for this in the templating tests).
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=336802
Build error leg or test failing: Microsoft.DotNet.Cli.New.IntegrationTests.TemplateDiscoveryTests.CanRunDiscoveryTool
Pull request: #33949
Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=336802
Error message validated:
error : The process cannot access the file
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/12/2023 4:34:24 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: