-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
LinqBenchmarks.Where00ForX has regressed on x86 #67968
Comments
Tagging subscribers to this area: @dotnet/area-system-linq Issue Details
Looking at the commit diff, there is nothing suspicious. @AndyAyersMS is there any chance it could be caused by #66618? Repro: git clone https://github.com/dotnet/performance.git
py .\performance\scripts\benchmarks_monthly.py net7.0-preview2 net7.0-preview3 --filter LinqBenchmarks.Where00ForX --architecture x86 LinqBenchmarks.Where00ForX
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue Details
Looking at the commit diff, there is nothing suspicious. @AndyAyersMS is there any chance it could be caused by #66618? Repro: git clone https://github.com/dotnet/performance.git
py .\performance\scripts\benchmarks_monthly.py net7.0-preview2 net7.0-preview3 --filter LinqBenchmarks.Where00ForX --architecture x86 LinqBenchmarks.Where00ForX
|
LinqBenchmarks.Where00ForX
has regressed on x86:Reporting System:
Looking at the commit diff, there is nothing suspicious. @AndyAyersMS is there any chance it could be caused by #66618?
Repro:
LinqBenchmarks.Where00ForX
The text was updated successfully, but these errors were encountered: