-
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
Microsoft.Extensions.Hosting.Tests.ConsoleLifetimeExitTests failing in Windows mono with PlatformNotSupportedException #57184
Comments
Tagging subscribers to this area: @eerhardt, @maryamariyan Issue DetailsEnsureEnvironmentExitDoesntHang and EnsureEnvironmentExitCode tests failing in CI: Stack trace (similar call stack for EnsureEnvironmentExitDoesntHang):
|
Why isn’t this always failing if it is a PNSE? I see the error is coming from the FileSystemWatcher. Is there something about the watcher that is non-deterministic? |
Do we run mono tests on windows or are the wrong assets getting copied |
We run mono tests on windows. There are numerous hosting tests already disabled for this issue: runtime/src/libraries/Microsoft.Extensions.Hosting/tests/UnitTests/HostTests.cs Lines 37 to 39 in 4ea7dc4
runtime/src/libraries/Microsoft.Extensions.Hosting/tests/UnitTests/HostTests.cs Lines 50 to 52 in 4ea7dc4
But I would have thought if a test was going to fail for this error, it would always fail. I can easily add the |
@eerhardt I saw these today and marked them for skipping in #57114 As for why it's flaky, I'm not sure and that is weird. @lateralusX would probably know best when he comes back from vacation. |
Hit again in #57235 |
@steveisok, just doing a quick look at the code it looks like it should be deterministic, given that the things being watched are always present on file system. Should we spend time to investigate this (Mono on Windows is not an official supported platform) or do a bigger pass once/if we decide to move ahead with Mono Windows support and decide to use an implementation of ThreadPoolBoundHandle not raising PNSE? |
…ew other tests (dotnet/runtime#57114) Since the library is PNSE by default, make sure the tests do not run on mobile. Also skips a few other tests. Closes dotnet/runtime#57184 Commit migrated from dotnet/runtime@defa26b
EnsureEnvironmentExitDoesntHang and EnsureEnvironmentExitCode tests failing in CI:
Stack trace (similar call stack for EnsureEnvironmentExitDoesntHang):
helix log:
https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-57136-merge-bab87ae1deee44e781/Microsoft.Extensions.Hosting.Unit.Tests/1/console.5019bb6b.log?sv=2019-07-07&se=2021-08-30T17%3A49%3A01Z&sr=c&sp=rl&sig=7qWWC35E1bcjEZiPSz9pB%2FQgg9TclDqq4GitesFZtpI%3D
The text was updated successfully, but these errors were encountered: