Andrey Akinshin

@bradwilson, @andyczerwonka, @gorohoroh Sorry for late reply. We have own runner which directly use managed API. I guess, the best option will be extending of the `IFailureInformation` interface, it should...

It would be very good.

@martinothamar thanks for the PR! Indeed, it makes sense to unify dotTrace/dotMemory diagnosers and eliminate code duplication. However, the presented approach inherits the disadvantages of the poor design of the...

@FlatlinerDOA thanks!

@EgorBo should be fixed now. Could you please try `0.14.1-nightly.20240826.175` and check if it correctly detects `Neoverse-N1`?

Today I learned that the lscpu output repsects the system language[^1][^2]. Thus, the current parsing logic will fail to detect `Model name` on systems with non-English locale. One more fix...

@EgorBo, `0.14.1-nightly.20240826.177` contains the language-invariant fix.

@alastairlundy could you please run the below command in PowerShell and share if it prints the processor model? ```powershell Get-CimInstance Win32_Processor ```

BenchmarkDotNet has two strategies for detecting the CPU model on Windows (see [WindowsCpuDetector](https://github.com/dotnet/BenchmarkDotNet/blob/v0.15.0/src/BenchmarkDotNet/Detectors/Cpu/Windows/WindowsCpuDetector.cs)): [MosCpuDetector](https://github.com/dotnet/BenchmarkDotNet/blob/v0.15.0/src/BenchmarkDotNet/Detectors/Cpu/Windows/MosCpuDetector.cs) and [WmicCpuDetector](https://github.com/dotnet/BenchmarkDotNet/blob/v0.15.0/src/BenchmarkDotNet/Detectors/Cpu/Windows/WmicCpuDetector.cs). If Wmic is not installed, `MosCpuDetector` is the only available detector. However, it is...

Estimating the CPU's maximum frequency is not always straightforward. One of the main challenges is that some modern CPUs consist of heterogeneous cores — that is, cores with different nominal...