ProcessTests.Test[Peak]WorkingSet[64] fail on Fedora 39

[tmds]

On the upcoming version of Fedora (Oct 23), these tests fail.

On Linux, these values are read from the VmHWM and VmRSS fields in /proc/<pid>/status.

I debugged this, and it seems that both VmHWM, and VmRSS are zero just after the process started. Both the values do become non-zero at a later moment.

Fedora uses the just released Linux kernel 6.2.0.
As other distros adopt this kernel, they will probably show the same test failure.

afaik tests in Microsoft CI run in containers, which means the kernel stays at the version of the host even when the container images are updated for a new distro version.
So the test failure may not occur in CI for quite some time.

I'll look into adding a RetryHelper and verify that fixes the test failure.

cc @omajid

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

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

Issue Details

---

On the upcoming version of Fedora (Oct 23), these tests fail.

On Linux, these values are read from the VmHWM and VmRSS fields in /proc/<pid>/status.

I debugged this, and it seems that both VmHWM, and VmRSS are zero just after the process started. Both the values do become non-zero at a later moment.

Fedora uses the just released Linux kernel 6.2.0.
As other distros adopt this kernel, they will probably show the same test failure.

afaik tests in Microsoft CI run in containers, which means the kernel stays at the version of the host even when the container images are updated for a new distro version.
So the test failure may not occur in CI for quite some time.

I'll look into adding a RetryHelper and verify that fixes the test failure.

cc @omajid

Author:	tmds
Assignees:	-
Labels:	area-System.Diagnostics.Process
Milestone:	-