Open gwr opened 1 month ago
Tagging subscribers to this area: @dotnet/area-system-diagnostics-process See info in area-owners.md if you want to be subscribed.
Is this not getting skipped correctly?
Is this not getting skipped correctly?
Maybe not? Or maybe I exposed it for the SunOS port. Anyway, with the fix, this passes for me, and should also on FreeBSD and OSX (because they all share that Process.BSD.cs file)
Description
In the SunOS port I'm working on (See https://github.com/dotnet/runtime/pull/105403) I'm sharing this file
src/libraries/System.Diagnostics.Process/src/System/Diagnostics/Process.BSD.cs
with FreeBSD, OSX, etc. During my testing I discovered a bug and have a fix to suggest.The bug is that for a new Process object (for which there is no Unix process ID started yet) the calls to
GetWorkingSetLimits
andSetWorkingSetLimits
are meant to throwSystem.InvalidOperationException
but they throwSystem.PlatformNotSupportedException
instead. Here's the test output:Same for
MinWorkingSet
Reproduction Steps
Run the
System.Diagnostics.Process
tests and look for these failures:Expected behavior
These should pass.
Actual behavior
They fail as shown above.
Regression?
no
Known Workarounds
Disable those tests, or add this suggested fix:
Configuration
Sorry for the minimal detail here, but the file involved currently affects: FreeBSD, OSX (and when I'm further along, SunOS).
Other information
No response