chocolatey
Tests for locked files seems to behave strangely under .Net 4.8.
What You Are Seeing?
The test choco install.Force Installing a Package that is already installed (with a read/delete locked file).Should not have been able to delete the rollback fail when run on Windows 10+ or Windows Server 2022.
This appears to be related to .Net 4.8 (left: Server 2022 where the test fails, right: Server 2019 where the test passes):
What is Expected?
The test should pass as it does on Windows Server 2016 and 2019.
How Did You Get This To Happen? (Steps to Reproduce)
Configured the Vagrantfile in the tests directory to use StefanScherer/windows_10 instead of StefanScherer/windows_2019.
Output Log
I don't have an output log at the moment.
Some discussion around this from the PR where we brought up that this might be a change to .Net https://github.com/chocolatey/choco/pull/2598#discussion_r851303811
Reopened this issue. Although the tests work in the updated Vagrantfile, we still don't have an understanding of what is happening under .Net 4.8 to cause the test to fail and so the issue is still valid.
:tada: This issue has been resolved in version 2.0.0 :tada:
The release is available on:
Your GitReleaseManager bot :package::rocket:
