-
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
getRecentTime() should not be used when tracing is enabled #2390
Labels
Comments
cwschilly
added a commit
that referenced
this issue
Jan 10, 2025
cwschilly
added a commit
that referenced
this issue
Jan 10, 2025
cwschilly
added a commit
that referenced
this issue
Jan 13, 2025
cwschilly
added a commit
that referenced
this issue
Jan 14, 2025
cwschilly
added a commit
that referenced
this issue
Jan 14, 2025
cwschilly
added a commit
that referenced
this issue
Jan 14, 2025
lifflander
added a commit
that referenced
this issue
Jan 20, 2025
…-not-be-used-when-tracing-is-enabled #2390: getRecentTime() should not be used when tracing is enabled
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
In runnable.cc, using the "recent time" to avoid calling the timer which is expensive leads to highly inaccurate traces. We should get the current time when tracing is compile-time enabled and being used at runtime (i.e., the trace context is enabled for a runnable).
The text was updated successfully, but these errors were encountered: