Skip to content
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 failure System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: Asynchronous) #73925

Closed
v-wenyuxu opened this issue Aug 15, 2022 · 5 comments · Fixed by #74083 or #74484
Assignees
Labels
arch-arm64 area-System.IO blocking-clean-ci-optional Blocking optional rolling runs JitStress CLR JIT issues involving JIT internal stress modes os-windows test-failure
Milestone

Comments

@v-wenyuxu
Copy link

Run: runtime-coreclr libraries-jitstress 20220814.1

Failed test:

net7.0-windows-Release-arm64-CoreCLR_checked-no_tiered_compilation-Windows.10.Arm64v8.Open
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: Asynchronous)
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: None)

net7.0-windows-Release-arm64-CoreCLR_checked-jitstress1_tiered-Windows.10.Arm64v8.Open
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: Asynchronous)
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: None)

net7.0-windows-Release-arm64-CoreCLR_checked-jitminopts-Windows.10.Arm64v8.Open
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: Asynchronous)
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: None)

net7.0-windows-Release-arm64-CoreCLR_checked-jitstress1-Windows.10.Arm64v8.Open
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: Asynchronous)
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: None)

net7.0-windows-Release-arm64-CoreCLR_checked-jitstress2-Windows.10.Arm64v8.Open
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: Asynchronous)
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: None)

Error message:

System.IO.IOException : The process cannot access the file '\?\PhysicalDrive0' because it is being used by another process.


Stack trace
   at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options) in /_/src/libraries/System.Private.CoreLib/src/Microsoft/Win32/SafeHandles/SafeFileHandle.Windows.cs:line 114
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable`1 unixCreateMode) in /_/src/libraries/System.Private.CoreLib/src/Microsoft/Win32/SafeHandles/SafeFileHandle.Windows.cs:line 47
   at System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(FileOptions options) in /_/src/libraries/System.IO.FileSystem/tests/RandomAccess/GetLength.cs:line 48
   at InvokeStub_RandomAccess_GetLength.ReturnsActualLengthForDevices(Object, Object, IntPtr*)
   at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)
@ghost ghost added the untriaged New issue has not been triaged by the area owner label Aug 15, 2022
@ghost
Copy link

ghost commented Aug 15, 2022

Tagging subscribers to this area: @dotnet/area-system-io
See info in area-owners.md if you want to be subscribed.

Issue Details

Run: runtime-coreclr libraries-jitstress 20220814.1

Failed test:

net7.0-windows-Release-arm64-CoreCLR_checked-no_tiered_compilation-Windows.10.Arm64v8.Open
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: Asynchronous)
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: None)

net7.0-windows-Release-arm64-CoreCLR_checked-jitstress1_tiered-Windows.10.Arm64v8.Open
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: Asynchronous)
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: None)

net7.0-windows-Release-arm64-CoreCLR_checked-jitminopts-Windows.10.Arm64v8.Open
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: Asynchronous)
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: None)

net7.0-windows-Release-arm64-CoreCLR_checked-jitstress1-Windows.10.Arm64v8.Open
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: Asynchronous)
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: None)

net7.0-windows-Release-arm64-CoreCLR_checked-jitstress2-Windows.10.Arm64v8.Open
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: Asynchronous)
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: None)

Error message:

System.IO.IOException : The process cannot access the file '\?\PhysicalDrive0' because it is being used by another process.


Stack trace
   at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options) in /_/src/libraries/System.Private.CoreLib/src/Microsoft/Win32/SafeHandles/SafeFileHandle.Windows.cs:line 114
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable`1 unixCreateMode) in /_/src/libraries/System.Private.CoreLib/src/Microsoft/Win32/SafeHandles/SafeFileHandle.Windows.cs:line 47
   at System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(FileOptions options) in /_/src/libraries/System.IO.FileSystem/tests/RandomAccess/GetLength.cs:line 48
   at InvokeStub_RandomAccess_GetLength.ReturnsActualLengthForDevices(Object, Object, IntPtr*)
   at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)
Author: v-wenyuxu
Assignees: -
Labels:

area-System.IO

Milestone: -

@v-wenyuxu v-wenyuxu added arch-arm64 os-windows JitStress CLR JIT issues involving JIT internal stress modes blocking-clean-ci-optional Blocking optional rolling runs and removed area-System.IO untriaged New issue has not been triaged by the area owner labels Aug 15, 2022
@danmoseley
Copy link
Member

1ae7c5f

Cc @virzak

@virzak
Copy link
Contributor

virzak commented Aug 15, 2022

Should we catch IOException in the test case and rethrow unless the message contains a string: "because it is being used by another process"

I don't have better ideas and it seems that there are no other test cases for physical drives, so no blueprint on how to test them.

@adamsitnik

@virzak
Copy link
Contributor

virzak commented Aug 15, 2022

Ideally, should probably use AttachVirtualDisk function and run all test cases against a virtual drive...

@ghost
Copy link

ghost commented Aug 15, 2022

Tagging subscribers to this area: @dotnet/area-system-io
See info in area-owners.md if you want to be subscribed.

Issue Details

Run: runtime-coreclr libraries-jitstress 20220814.1

Failed test:

net7.0-windows-Release-arm64-CoreCLR_checked-no_tiered_compilation-Windows.10.Arm64v8.Open
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: Asynchronous)
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: None)

net7.0-windows-Release-arm64-CoreCLR_checked-jitstress1_tiered-Windows.10.Arm64v8.Open
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: Asynchronous)
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: None)

net7.0-windows-Release-arm64-CoreCLR_checked-jitminopts-Windows.10.Arm64v8.Open
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: Asynchronous)
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: None)

net7.0-windows-Release-arm64-CoreCLR_checked-jitstress1-Windows.10.Arm64v8.Open
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: Asynchronous)
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: None)

net7.0-windows-Release-arm64-CoreCLR_checked-jitstress2-Windows.10.Arm64v8.Open
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: Asynchronous)
- System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(options: None)

Error message:

System.IO.IOException : The process cannot access the file '\?\PhysicalDrive0' because it is being used by another process.


Stack trace
   at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options) in /_/src/libraries/System.Private.CoreLib/src/Microsoft/Win32/SafeHandles/SafeFileHandle.Windows.cs:line 114
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable`1 unixCreateMode) in /_/src/libraries/System.Private.CoreLib/src/Microsoft/Win32/SafeHandles/SafeFileHandle.Windows.cs:line 47
   at System.IO.Tests.RandomAccess_GetLength.ReturnsActualLengthForDevices(FileOptions options) in /_/src/libraries/System.IO.FileSystem/tests/RandomAccess/GetLength.cs:line 48
   at InvokeStub_RandomAccess_GetLength.ReturnsActualLengthForDevices(Object, Object, IntPtr*)
   at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)
Author: v-wenyuxu
Assignees: -
Labels:

arch-arm64, area-System.IO, os-windows, JitStress, blocking-clean-ci-optional

Milestone: -

@jeffhandley jeffhandley added this to the Future milestone Aug 15, 2022
@jeffhandley jeffhandley added the needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration label Aug 15, 2022
adamsitnik added a commit to adamsitnik/runtime that referenced this issue Aug 17, 2022
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Aug 17, 2022
@adamsitnik adamsitnik self-assigned this Aug 17, 2022
@adamsitnik adamsitnik removed the needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration label Aug 17, 2022
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Aug 17, 2022
danmoseley pushed a commit that referenced this issue Aug 18, 2022
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Aug 24, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Sep 23, 2022
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Jun 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.