Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[tests] restoreSSL category#10495

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Draft
jonathanpeppers wants to merge3 commits intomain
base:main
Choose a base branch
Loading
fromdev/peppers/ssl-crypto-tests

Conversation

@jonathanpeppers
Copy link
Member

We think some of the recent changes in main, should fix .NET APIs related to crypto on both CoreCLR and NativeAOT.

We think some of the recent changes in main, should fix .NET APIs related to crypto on both CoreCLR and NativeAOT.
@jonathanpeppers
Copy link
MemberAuthor

It seems like in the middle ofAndroidMessageHandlerSendsClientCertificate(False), we crash:

09-17 17:29:12.466 21031 21056 I NUnit   : AndroidMessageHandlerSendsClientCertificate(False) ...09-17 17:29:12.756 21031 21056 E droid.NET_Test: JNI ERROR (app bug): attempt to use stale Global 0x36f6 (should be 0x36f2)09-17 17:29:12.756 21031 21056 F droid.NET_Test: java_vm_ext.cc:570] JNI DETECTED ERROR IN APPLICATION: use of deleted global reference 0x36f609-17 17:29:12.756 21031 21056 F droid.NET_Test: java_vm_ext.cc:570]     from void crc643df67da7b13bb6b1.TestInstrumentation_1.n_onStart()

@grendello
Copy link
Contributor

It seems like in the middle ofAndroidMessageHandlerSendsClientCertificate(False), we crash:

09-17 17:29:12.466 21031 21056 I NUnit   : AndroidMessageHandlerSendsClientCertificate(False) ...09-17 17:29:12.756 21031 21056 E droid.NET_Test: JNI ERROR (app bug): attempt to use stale Global 0x36f6 (should be 0x36f2)09-17 17:29:12.756 21031 21056 F droid.NET_Test: java_vm_ext.cc:570] JNI DETECTED ERROR IN APPLICATION: use of deleted global reference 0x36f609-17 17:29:12.756 21031 21056 F droid.NET_Test: java_vm_ext.cc:570]     from void crc643df67da7b13bb6b1.TestInstrumentation_1.n_onStart()

Might possibly be a GC bridge bug? /cc@simonrozsival

@simonrozsival
Copy link
Member

That might be a GC bridge bug or it could be a bug in runtime's Crypto PAL code which also uses JNI.

@jonathanpeppers can you repro it locally?

@jonathanpeppers
Copy link
MemberAuthor

After fixing merge conflict with main, it seems like these passed on CoreCLR and nothing crashed.

NativeAOT has some failures like:

Certificate validationExpected: No Exception to be thrownBut was:   (net_auth_SSPI)at System.Net.Security.SslStream.<ForceAuthenticationAsync>d__159`1.MoveNext() + 0xa9f--- End of stack trace from previous location ---at System.NetTests.SslTest.DoVerifyTrustedCertificates() + 0xb1at System.NetTests.SslTest.RunIgnoringWebException(Action test) + 0x34at NUnit.Framework.Constraints.VoidInvocationDescriptor.Invoke() + 0xcat NUnit.Framework.Constraints.ExceptionInterceptor.Intercept(Object) + 0x2a

So, let me change this to only add the category to CoreCLR and see if it is green.

simonrozsival reacted with thumbs up emoji

@jonathanpeppers
Copy link
MemberAuthor

Seems like CI gets the same error, but it's working for me locally:

# arm64 device.\dotnet-local.cmd build tests\Mono.Android-Tests\Mono.Android-Tests\Mono.Android.NET-Tests.csproj-t:Install,RunTestApks-r android-arm64-bl-p:IncludeCategories=SSL-p:UseMonoRuntime=false-c Release# API 29 emulator.\dotnet-local.cmd build tests\Mono.Android-Tests\Mono.Android-Tests\Mono.Android.NET-Tests.csproj-t:Install,RunTestApks-r android-x64-bl-p:IncludeCategories=SSL-p:UseMonoRuntime=false-c Release

@jonathanpeppers
Copy link
MemberAuthor

Ok, weird it seems to pass about 50% of the time. Let me just run it again to see.

@jonathanpeppers
Copy link
MemberAuthor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jonathanpeppers
Copy link
MemberAuthor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@grendellogrendellogrendello approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@jonathanpeppers@grendello@simonrozsival

[8]ページ先頭

©2009-2025 Movatter.jp