-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test failed: System.IO.Tests.EncryptDecrypt.EncryptDecrypt_Read #12339
Comments
@karelz Someone want to investigate this corefx test failure? |
@wfurt can you please help? |
That seems like environmental issue. |
Test failed again: OS & Arch: Mode: Log:
|
Test failed again: OS & Arch: Mode: Log:
|
Job: OS & Arch: Mode: Note: Log:
|
Job: OS & Arch: Mode: Note: Log:
|
No repro now |
This has happened again here: https://dev.azure.com/dnceng/public/_build/results?buildId=1427004&view=results Consider adding some diagnostics - with this rare occurrence it might be impossible to find out what's going otherwise |
I don't think this is arm64 specific since I got two instances on amd64 |
cc: @dotnet/area-system-io |
adding system.io for initial investigation due to comment
|
Once in a while I hit it on my Win 10 Dev machine. All we do on our side is to just call the Windows sys-calls: runtime/src/libraries/System.Private.CoreLib/src/System/IO/FileSystem.Windows.cs Lines 13 to 27 in 83661ff
I have no idea how EncryptFile/DecryptFile are implemented on the Windows side. We should most probably reach out to the right Team and ask for guidance. |
I'm guessing the EFS service isn't started. From looking at the code, it seems that API calls like EncryptFile use RPC to connect to the "EFS" service. I expect that this attempts to start the service if it's not started. It's impossible for us (or OS folks) to say why this failed without more info, although perhaps the event log might give a clue. One possibility could be to modify the test so if this issue occurs, use ServiceController in the test to dump whether the EFS service is started, and possibly attempt to start it to see whether that succeeds. |
candidate for built-in retry? Alternatively add probe test and make it conditional...? |
Failed again in: runtime-libraries-coreclr outerloop 20220607.3 Failed test:
Error message:
|
That last failure looks different. |
Failed again in: runtime-libraries-coreclr outerloop 20220712.5 Failed test:
Error message:
|
Failed again in : runtime-libraries-coreclr outerloop 20220724.3 Failed test:
Error message:
|
Note there's two issues here. The encryption seems to have been mitigated by the code I added to ensure the service is started. Now put up a PR to retry the decrypt. |
What's the code you are referring to here? |
Job:
https://ci.dot.net/job/dotnet_coreclr/job/master/view/arm64/job/jitstress/job/arm64_cross_checked_windows_nt_corefx_tieredcompilation_tst/26/
Failed tests:
System.IO.Tests.EncryptDecrypt.EncryptDecrypt_Read
Log:
Runfo Tracking Issue: System.IO.Tests.EncryptDecrypt.EncryptDecrypt_Read
Build Result Summary
The text was updated successfully, but these errors were encountered: