-
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
System.Net test suites asserts in CI on ArrayBuffer.Discard #43686
Comments
Tagging subscribers to this area: @dotnet/ncl |
cc @dotnet/ncl |
@danmosemsft @maryamariyan see the bot's message above. The |
cc: @wfurt |
Did we get core file @ViktorHofer ? |
Unfortunately no. |
how so? OSX core files are pain to deal with, but I thought we had that in place. I have some suspicions but that would be hard to verify without core or repro. I can do loop test run to see if I can make it happen locally. From the trace, it looks like the offending test was Task clientJob = Task.Run(() => {
client.AuthenticateAsClient(hostName);
Assert.True(false, "RemoteCertificateValidationCallback called when AuthenticateAsServerAsync was expected to fail.");
}); inside of |
This test is poorly written. I'm not sure what that's trying to validate, but the Task returned from the Task.Run is never joined with, so any exceptions thrown from AuthenticateAsClient or from a failing assert are just going to be eaten. And as you say, assuming the server call can fail before or part-way through the client authenticating, the client can be disposed of during this synchronous AuthenticateAsClient call. |
Crash and hang dump support across the entire supported OS matrix (except mobile) will be enabled with #39923. |
This is just a github rendering bug |
I could not reproduce it so far. This may need to waiter core or reocuerence. |
Triage: We need core dump to investigate more ... |
Does not seem to be actionable - unable to reproduce, no core dump for investigation ... closing for now. |
Failed in #51826, looks like there is a dump available |
Note: I copied the dump locally in case it disappears before we get to it ... |
Triage: punting. |
it seems like |
The linked failure is different as it does not live in macOS PAL. It is tracked by #66818. |
Failures 7/30-8/19 (incl. PRs)
Configuration:
net6.0-OSX-Debug-x64-CoreCLR_release-OSX.1015.Amd64.Open
Build:
https://dev.azure.com/dnceng/public/_build/results?buildId=861070&view=ms.vss-test-web.build-test-results-tab&runId=27582874&paneView=debug
console.df11c71b.log:
https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-43583-merge-76feeba0b9b24d0cac/System.Net.Security.Tests/console.df11c71b.log?sv=2019-07-07&se=2020-11-10T12%3A04%3A15Z&sr=c&sp=rl&sig=ollbotIg4oFm3EfLfaPrGBm4k92qWZ%2BrhXS7ydWvQ0I%3D
The text was updated successfully, but these errors were encountered: