search

dotnet / runtime

.NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
https://docs.microsoft.com/dotnet/core/
MIT License
15.35k stars 4.74k forks source link

Microsoft.Extensions.Caching.Memory.Tests hanging in Mono after test execution finishes #35970

Open jaredpar opened 4 years ago

jaredpar commented 4 years ago

Builds

Build Pull Request Test Failure Count
#629156 Rolling 1
#629314 Rolling 1
#629997 Rolling 1
#631423 Rolling 1
#632868 Rolling 1
#632967 Rolling 1
#633095 Rolling 1
#634699 Rolling 1

Configurations

ghost commented 4 years ago

Tagging subscribers to this area: @directhex Notify danmosemsft if you want to be subscribed.

jaredpar commented 4 years ago

@steveisok @akoeplinger FYI

akoeplinger commented 4 years ago

@jaredpar all of the libicui18n.so.50: cannot open shared object file: No such file or directory errors are happening on a single PR, which is working on integrating the ICU shim so those failures are "expected" with the current state of the PR: https://github.com/dotnet/runtime/pull/35790

The remaining two errors look like hangs since test execution seems to finish: https://helix.dot.net/api/2019-06-17/jobs/cfe744d2-90d6-4002-9304-aa45ea40efd0/workitems/Microsoft.Extensions.Caching.Memory.Tests/files/console.85791f98.log

We should remove the icu failures from this issue.

safern commented 4 years ago

Yeah, the icu failures are related to the changes of that PR, I confirmed it with @thaystg. We should definitely remove it from here.

The other 2 failures seem like a weird issue as the tests did finish, maybe loop in @MattGal here see if he has any insight there as xunit did finish.

MattGal commented 4 years ago

Taking a look.

MattGal commented 4 years ago

It's a timeout - from the log and where it stops, it looks like the xunit call never actually returns, otherwise it'd have various other things logged.

safern commented 4 years ago

So it seems like the test is barely finishing before the timeout but there is no timeout for the reporting steps, right?

safern commented 4 years ago

But XUnit reports that the test finished in 20s which is very weird.

MattGal commented 4 years ago

All that means here is that you made it to the point of writing that to the console. Something ... whether it be an infinite loop in a finalizer, a dialog that pops up that DHandler doesn't know how to click, or otherwise... is preventing that Xunit invocation from finishing.

safern commented 4 years ago

Updated the issue description, it seems like from 50 builds it has happened a lot more times than just 2.

All that means here is that you made it to the point of writing that to the console. Something ... whether it be an infinite loop in a finalizer, a dialog that pops up that DHandler doesn't know how to click, or otherwise... is preventing that Xunit invocation from finishing.

Yeah I just thought about that, @akoeplinger seems like a runtime hang? Seems like it only happens on Windows.

safern commented 4 years ago

Seeing this too often. So disabling this on: https://github.com/dotnet/runtime/pull/36083

akoeplinger commented 4 years ago

@lateralusX seems to be a Windows only issue, would you mind trying to repro?