-
-
Notifications
You must be signed in to change notification settings - Fork 34.1k
src: fix negative nodeTiming milestone values #46588
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
Conversation
|
#43781 didn't land on v14.x and v16.x, so this fix doesn't need to land on v14.x and v16.x too. |
b318df3 to
6760c9a
Compare
|
Fixed the test failure with |
PR-URL: #46588 Fixes: #45958 Refs: #43781 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Minwoo Jung <[email protected]>
|
Landed in a8c3d03 |
PR-URL: #46588 Fixes: #45958 Refs: #43781 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Minwoo Jung <[email protected]>
PR-URL: #46588 Fixes: #45958 Refs: #43781 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Minwoo Jung <[email protected]>
|
@legendecas this didn't land cleanly on v18.x - do you mind opening a backport PR? Thank you |
|
#43781 didn't land on v18.x. I'm tagging this as https://github.com/nodejs/node/labels/dont-land-on-v18.x. |
Although the
performance.timeOriginis a Web API, Node.js specific extensionperformance.nodeTimingexposes the process performance milestones in the main thread and the worker threads. In order to avoid exposing negative values inperformance.nodeTiming, set theperformance.timeOriginto the start time of the process both in the main thread and worker threads.Refs: #43781
Fixes #45958, with regression test cases.