-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
System.Diagnostics.Tests.StopwatchTests.GetTimestamp test fails in the CI #62021
Comments
Tagging subscribers to this area: @tommcdon Issue DetailsDescription
Reproduction StepsCI run Expected behaviorNo failures Actual behaviorThe test fails Regression?No response Known WorkaroundsNo response ConfigurationNo response Other informationNo response
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsDescription
Reproduction StepsCI run Expected behaviorNo failures Actual behaviorThe test fails Regression?No response Known WorkaroundsNo response ConfigurationNo response Other informationNo response
|
same in #61768
|
This means that this is getting called twice in approx 1ms and returning the same result. @lewing does Wasm have a larger quantum, or jitter? If so we should make the test sleep longer.
|
Also saw it in #62244, I wonder though why this started failing recently since the test is untouched since 2020. |
The test is untouched, my assumption is that clock_gettime (or clock_gettime_nsec_np) changed on Blazor (?) |
@lewing may know. |
The browser definitely has lower resolution than desktop but I'm also a bit unsure why it started failing recently. @pavelsavara any thoughts? |
We have new chrome, it may be the cause. |
@radical could we close this one ? |
If we are good with the workaround, and won't be fixing it, then feel free to close the issue. |
There is also CLOCK_MONOTONIC feature in emscripten. I don't know much about it yet. Should we explore this topic further @lewing ? |
Another failure due to the same reason, IIUC:
|
…he (#62411) .. desktop. Earlier we did this for one test, but others are hitting this issue randomly too. New one: ``` [00:32:41] fail: [FAIL] System.Diagnostics.Tests.StopwatchTests.StartNewAndReset [00:32:41] info: Assert.True() Failure [00:32:41] info: Expected: True [00:32:41] info: Actual: False [00:32:41] info: at System.Diagnostics.Tests.StopwatchTests.StartNewAndReset() [00:32:41] info: at System.Reflection.RuntimeMethodInfo.InvokeWorker(Object obj, BindingFlags invokeAttr, Span`1 parameters) ``` Issue: #62021
Description
https://dev.azure.com/dnceng/public/_build/results?buildId=1483932&view=logs&jobId=108d2c4a-8a62-5a58-8dad-8e1042acc93c&j=108d2c4a-8a62-5a58-8dad-8e1042acc93c&t=568f884b-cc12-5fd3-e7fe-790b5ac403f4
https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-61992-merge-7fb43d6a883f4488b6/System.Runtime.Extensions.Tests/1/console.767e6c7f.log?sv=2019-07-07&se=2021-12-14T02%3A29%3A30Z&sr=c&sp=rl&sig=z6v3ggZBbFYzzSs7RnkjjXGrSz8%2Fu01LaKM7xQ8zMAw%3D
Reproduction Steps
CI run
Expected behavior
No failures
Actual behavior
The test fails
Regression?
No response
Known Workarounds
No response
Configuration
No response
Other information
No response
The text was updated successfully, but these errors were encountered: