Skip to content
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

Bug when decoding: "duration_complete event must have start tick (166428285) greater than end tick (166428276)" #319

Open
Kuinox opened this issue Dec 5, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Kuinox
Copy link

Kuinox commented 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:

  • 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

@Kuinox Kuinox added the bug Something isn't working label Dec 5, 2024
@Kuinox 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant