The arcade dependency update in dotnet/arcade-validation#5637 (arcade 11.0.0-beta.26329.1) pulls in a NuGet change (NuGet/NuGet.Client#7020) that incorrectly holds file locks when deterministic timestamps are enabled. This causes the BuildShouldUseDotNetCertifcateIfSet and BuildShouldNotChangeNonMicrosoft400CertsWhenSigning tests in src/Validation/tests/RepoTests.cs to fail on Windows during cleanup with:
System.IO.IOException : The process cannot access the file 'FooPackage.dll' because it is being used by another process.
As a temporary workaround, /p:DeterministicTimestamp=false is passed to the test repo build in TestRepoBuilder.Build. This mirrors the workaround applied in the VMR (dotnet/dotnet#7331).
Once the underlying NuGet file-lock issue is resolved and flowed into arcade, remove the workaround and re-enable deterministic timestamps in arcade-validation.
The arcade dependency update in dotnet/arcade-validation#5637 (arcade
11.0.0-beta.26329.1) pulls in a NuGet change (NuGet/NuGet.Client#7020) that incorrectly holds file locks when deterministic timestamps are enabled. This causes theBuildShouldUseDotNetCertifcateIfSetandBuildShouldNotChangeNonMicrosoft400CertsWhenSigningtests insrc/Validation/tests/RepoTests.csto fail on Windows during cleanup with:As a temporary workaround,
/p:DeterministicTimestamp=falseis passed to the test repo build inTestRepoBuilder.Build. This mirrors the workaround applied in the VMR (dotnet/dotnet#7331).Once the underlying NuGet file-lock issue is resolved and flowed into arcade, remove the workaround and re-enable deterministic timestamps in arcade-validation.