-
Notifications
You must be signed in to change notification settings - Fork 9
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
invalid trace timings #2147
Labels
Comments
nmm0
added a commit
that referenced
this issue
May 15, 2023
This was referenced May 15, 2023
nmm0
added a commit
that referenced
this issue
May 16, 2023
nmm0
added a commit
that referenced
this issue
May 16, 2023
nmm0
added a commit
that referenced
this issue
May 16, 2023
nmm0
added a commit
that referenced
this issue
May 16, 2023
…alls to start() and finish() trace runnable components
nmm0
added a commit
that referenced
this issue
May 16, 2023
nmm0
added a commit
that referenced
this issue
May 18, 2023
nmm0
added a commit
that referenced
this issue
May 18, 2023
nmm0
added a commit
that referenced
this issue
May 18, 2023
nmm0
added a commit
that referenced
this issue
May 18, 2023
nmm0
added a commit
that referenced
this issue
May 18, 2023
…alls to start() and finish() trace runnable components
nmm0
added a commit
that referenced
this issue
May 18, 2023
nlslatt
added a commit
that referenced
this issue
May 23, 2023
#2147: fix incorrect order of parameters for call to beginProcessing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Projections will complain about corrupted or invalid trace files, or that the time of a handler cannot fit into an integer. Occasionally, I see large negative numbers in the latency of a handler in the trace.
This makes me think that there may be some uninitialized values in the trace.
This bug seems to be introduced by #1998 as I have bisected and versions of VT from before that was merged work correctly.
The text was updated successfully, but these errors were encountered: