Repository navigation
Test failure: System.Security.Cryptography.Xml.Tests.XmlDsigExcC14NTransformTest.ExcC14NSpecExample5 #113049
Description
Failed in: runtime-coreclr libraries-jitstress-random 20250301.1
Failed tests:
net10.0-linux-Release-arm64-jitstress_random_1-(Ubuntu.2404.Arm64.Open)Ubuntu.2204.Armarch.Open@mcr.microsoft.com/dotnet-buildtools/prereqs:ubuntu-24.04-helix-arm64v8
- System.Security.Cryptography.Xml.Tests.XmlDsigExcC14NTransformTest.ExcC14NSpecExample5
- System.Security.Cryptography.Xml.Tests.XmlDsigExcC14NTransformTest.ExcC14NSpecExample1
- System.Security.Cryptography.Xml.Tests.XmlDsigC14NTransformTest.C14NSpecExample1
- System.Security.Cryptography.Xml.Tests.XmlDsigC14NTransformTest.C14NSpecExample5
- System.Security.Cryptography.Xml.Tests.XmlDsigC14NWithCommentsTransformTest.C14NSpecExample1
- System.Security.Cryptography.Xml.Tests.XmlDsigC14NWithCommentsTransformTest.C14NSpecExample5
Error message:
System.ArgumentOutOfRangeException : Specified argument was out of the range of valid values. (Parameter 'start')
Stack trace:
at System.Uri.ParseSchemeCheckImplicitFile(String uriString, ParsingError& err, Flags& flags, UriParser& syntax) in /_/src/libraries/System.Private.Uri/src/System/Uri.cs:line 3706
at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind, UriCreationOptions& creationOptions) in /_/src/libraries/System.Private.Uri/src/System/UriExt.cs:line 39
at System.Xml.Resolvers.XmlPreloadedResolver..ctor(XmlResolver fallbackResolver, XmlKnownDtds preloadedDtds, IEqualityComparer`1 uriComparer) in /_/src/libraries/System.Private.Xml/src/System/Xml/Resolvers/XmlPreloadedResolver.cs:line 182
at System.Security.Cryptography.Xml.Tests.XmlDsigExcC14NTransformTest.ExcC14NSpecExample5() in /_/src/libraries/System.Security.Cryptography.Xml/tests/XmlDsigExcC14NTransformTest.cs:line 328
at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) in /_/src/coreclr/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.CoreCLR.cs:line 36
at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr) in /_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.cs:line 57
Activity
dotnet-policy-service commentedon Mar 3, 2025
Tagging subscribers to this area: @dotnet/area-system-security, @bartonjs, @vcsjones
See info in area-owners.md if you want to be subscribed.
vcsjones commentedon Mar 3, 2025
This test passes locally for me, even with
DOTNET_TieredCompilation=0 DOTNET_JitStress=5e. As another observation, this failure looks deeper insideSystem.Uri.Either the underlying problem is due to JIT stress, or an issue in
System.Uri, so I don't think there is much do be done for System.Security.dotnet-policy-service commentedon Mar 3, 2025
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.
JulieLeeMSFT commentedon Mar 6, 2025
@kunalspathak, please check the JIT stress failure on Arm64.
kunalspathak commentedon Mar 6, 2025
The repro is not consistent but I can see the failure once in every 3-4 runs. The reason of inconsistency is timing of tiering of methods that may get inlined in the problematic method that has bad code gen.
When there is no repro, I see the method
System.Uri:ParseSchemeCheckImplicitFileis jitted with this information:But when it repros, I see it is jitted with:
When I see the difference between repro and non-repro, it seems that we are missing
tbnzinstruction. Left is no-repro case, right is repro case. The hightlighted labels in each of them goes tothrow ArgumentOutOfRangeException()kunalspathak commentedon Mar 6, 2025
Most likely coming from #112411
kunalspathak commentedon Mar 7, 2025
git bisectis pointing to #112766, and I can see it repros starting 12bf864 (after you reapplied your proper fix), this might be a different issue related to bounds check. Here are the superpmi collections (based on 12bf864 ). You should see inbadcase,[000098]is eliminated.good_linux.arm64.Checked.3.mch.zip
bad_linux.arm64.Checked.4.mch.zip
Method name of interest:
ParseSchemeCheckImplicitFilecc: @EgorBo
kunalspathak commentedon Mar 7, 2025
Yep, just double confirmed on
mainthat the patch added in #112766 aroundoptAssertionProp_RangePropertiesmakes it add constant assertion and eliminate the branch. @EgorBo , since you have touched this lately, i will let you investigate further.amanasifkhalid commentedon Mar 17, 2025
#113052 looks like the same issue