-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[libraries][MacCatalyst] System.IO.FileSystem.Watcher NonZeroTimeout_NoActivity_TimesOut failure #58418
Comments
Tagging subscribers to this area: @dotnet/area-system-io Issue Details
|
cc @jozkee |
Looks like this only fails on MacCatalyst arm64, but not x64. |
@akoeplinger does it mean that we would need macbook M1 to repro it? |
Yes. |
…t and test fixes for Android (#58841) Manual backport of #57208, #58519, #58562, #58210, #57732, #58428, #58586, #58745, #57687 to release/6.0 Numerous test suites have been failing for iOS/tvOS/MacCatalyst consistently on CI without useful logs as to why. Moreover, some of these suites pass locally. This PR looks to reduce the failures on CI by skipping the problematic suites Skips test suites logged in #53624 ActiveIssues #58440 #58418 #58367 #58584 Co-authored-by: Mitchell Hwang <[email protected]> Co-authored-by: Alexander Köplinger <[email protected]> Co-authored-by: Jo Shields <[email protected]>
Again in #66992 System.IO.Tests.WaitForChangedTests.NonZeroTimeout_NoActivity_TimesOut [Details] [History] [Artifacts] |
It's odd as it seems just a getter/setter validation. runtime/src/libraries/System.IO.FileSystem.Watcher/tests/FileSystemWatcher.WaitForChanged.cs Lines 121 to 123 in baffb71
|
Build: https://dev.azure.com/dnceng/public/_build/results?buildId=1329092&view=logs&j=3a31f037-b056-5f1b-7dc0-d7edb248100e&t=6f68142f-0a7c-54ea-feaf-6db573804c2c
The text was updated successfully, but these errors were encountered: