-
Notifications
You must be signed in to change notification settings - Fork 269
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
[perf pipeline] Perf_BigInteger.ModPow
failing with System.ArgumentException: Destination is too short. (Parameter 'destination')
#2575
Comments
It's also reproducible with CLR. Repro: py .\scripts\benchmarks_ci.py -f net7.0 --filter System.Numerics.Tests.Perf_BigInteger.ModPow
@dakersnar @tannergooding Has a recent change in dotnet/runtime introduced a product bug or exposed a benchmark bug? |
Looks like a product bug, investigating. Most likely caused by dotnet/runtime#74112 |
Closed by #2578 |
* Adding a regression test for dotnet/performance#2575 * Ensure that the result span is fully initialized.
…74672) * Adding a regression test for dotnet/performance#2575 * Ensure that the result span is fully initialized. Co-authored-by: Tanner Gooding <tagoo@outlook.com>
This doesn't seem to have been fixed by dotnet/runtime#74585. #2590 re-enables the benchmark, but gets the same error. |
Looking into this right now. |
I'd expect we're just not on the right build. A regression test for the exact value the perf test fails on was added. |
It looks like dotnet/installer is still pointing to https://github.com/dotnet/runtime/tree/ef077d0b58ffddcf54fa73bd85dace6b999b8992, which is 3 days before the ModPow fix was merged into main. This should be resolved once dotnet/installer points to an updated dotnet/runtime. |
fixed by dotnet/runtime#74585 and #2590 |
Log from runtime-wasm-perf run on dotnet/runtime#74097:
...
This is reproducible on main, with interpreter.
cc @adamsitnik @LoopedBard3 @lewing
The text was updated successfully, but these errors were encountered: