[wasm] Work around System.Diagnostics.Tests.StopwatchTests.GetTimestamp failure

[radical]

.. by sleeping for 5ms on wasm, instead of 1ms. Thanks to @danmoseley for the suggestion.

Issue: #62021

[dotnet-issue-labeler]

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

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Issue: #62021

Author:	radical
Assignees:	-
Labels:	arch-wasm
Milestone:	-

[danmoseley]

Why disable it? just add some slop for Browser only, such as 5ms. That will be higher value than having no coverage and it may be the long term fix.

[radical]

Why disable it? just add some slop for Browser only, such as 5ms. That will be higher value than having no coverage and it may be the long term fix.

I'm fine with either. Just trying to avoid the test failures on CI runs ;)

If that sounds acceptable to others, then I can update the PR.

[danmoseley]

I doubt they'd object 😺

[radical]

I doubt they'd object 😺

heh sorry, I was being lazy, and trying to avoid reading the details of the issue! I'll update the PR :)

[radical]

/azp run runtime-manual

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[radical]

Wasm runtime test failure is #62303 .

Others are unrelated failures in runtime-staging.