You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running ./magic-trace run -working-directory workdir -full-execution -multi-thread ./dotnet/dotnet -- benchmark/Abc.TradingPerfTests.dll
magic-trace end up throwing when writing the trace with the error: "duration_complete event must have start tick (166428285) greater than end tick (166428276)"
Thanks for helping us make magic-trace better!
Please consider answering any subset of the following questions, based on what you think
is most relevant to your report:
How can we, magic-trace developers, reproduce the issue you're seeing?
If needed I can provide a zip that contains everything to reproduce the issue.
What version of perf userspace tools are you running? perf --version
perf version 6.8.12
What CPU do you have? cat /proc/cpuinfo
Intel(R) Xeon(R) Gold 6146 CPU
The text was updated successfully, but these errors were encountered:
Kuinox
changed the title
"duration_complete event must have start tick (166428285) greater than end tick (166428276)"
Bug when decoding: "duration_complete event must have start tick (166428285) greater than end tick (166428276)"
Dec 5, 2024
When running
./magic-trace run -working-directory workdir -full-execution -multi-thread ./dotnet/dotnet -- benchmark/Abc.TradingPerfTests.dll
magic-trace end up throwing when writing the trace with the error:
"duration_complete event must have start tick (166428285) greater than end tick (166428276)"
Thanks for helping us make magic-trace better!
Please consider answering any subset of the following questions, based on what you think
is most relevant to your report:
If needed I can provide a zip that contains everything to reproduce the issue.
perf version 6.8.12
cat /proc/cpuinfo
Intel(R) Xeon(R) Gold 6146 CPU
The text was updated successfully, but these errors were encountered: