-
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
Test failure: Loader/binding/tracing/BinderTracingTest.Basic/BinderTracingTest.Basic.sh #45088
Comments
Tagging subscribers to this area: @vitek-karas, @agocke, @CoffeeFlux Issue Detailsfailed in job: runtime-coreclr jitstress2-jitstressregs 20201122.1 CoreCLR OSX x64 Checked jitstress2_jitstressregs0x1000 @ OSX.1013.Amd64.Open Error message
|
Looks like a NullReferenceException in the bind event listener |
Looking through the code I don't see a way to make this value Personally I would wait a bit if it gets another hit... @elinor-fung - maybe you will see some other way... |
I'm not seeing how it would be |
@sywhang Could you please explain why this test used to fail with an |
A task is used to monitor/pump events into listeners. When the last listener waiting was getting disposed (the one used in the test) it tried to remove itself from the interested EventSources. Part of it is to stop said task while the event dispatch configurations get updated. That set of operations triggered a TPL event, which the listener getting disposed was listening to. At that point, the string array had already been disposed of hence the nullref. |
@hoyosjs is correct. Thanks for jumping in and explaining - I should've done that when I submitted the PR :-) |
failed in job: runtime-coreclr jitstress2-jitstressregs 20201122.1
CoreCLR OSX x64 Checked jitstress2_jitstressregs0x1000 @ OSX.1013.Amd64.Open
Error message
Runfo Tracking Issue: loader/binding/tracing/bindertracingtest.resolutionflow/bindertracingtest.basic.sh
Build Result Summary
The text was updated successfully, but these errors were encountered: