-
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
CopyToNanosecondsPresent_LowTempRes #48717
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue Details
Runfo Tracking Issue: copytonanosecondspresent_lowtempres
Build Result Summary
|
A Kusto query is returning, for the last 60 days, 1 result in master CI and 5 in PR CIs:
Although this is marked for System.IO, I'll defer this to the WASM team to decide if they want to address this or not. |
This appears to be resolved, please reopen if no. |
I just hit this on #54253 |
@radekdoulik I think we can ActiveIssue this for now and skip it on wasm |
Any reason we shouldn't resolve this by adding a little more tolerance in the test? Seems the browser timer has more slop than expected, but there's no real consequences? |
@radekdoulik, what is the plan for this failure? |
on |
Failing 5 times a month, always on WASM, always the same digit is one off, eg
|
log https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-master-680cda3803df473ebe/System.IO.FileSystem.Tests/console.1c1154a3.log?sv=2019-07-07&se=2021-03-15T11%3A39%3A01Z&sr=c&sp=rl&sig=X87s3NAfVydw24wA36GljHufqJYUgs7qOK%2B2i3NKmAM%3D
build https://dev.azure.com/dnceng/public/_build/results?buildId=1007570&view=logs&j=108d2c4a-8a62-5a58-8dad-8e1042acc93c&t=568f884b-cc12-5fd3-e7fe-790b5ac403f4
cc @carlossanlop
Runfo Tracking Issue: copytonanosecondspresent_lowtempres
Build Result Summary
The text was updated successfully, but these errors were encountered: