-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
report: use consistent format for dumpEventTime #25751
Conversation
Use the same JS-compatible format on both POSIX and Windows.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Any idea why it was done like this originally?
No idea. The equivalent code in the standalone module is consistent (both Windows and non-Windows use |
@cjihrig - no specific reason I can recollect; so may be a slip when I changed many things in succession. |
Landed in 23d51a1 |
Use the same JS-compatible format on both POSIX and Windows. PR-URL: #25751 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Use the same JS-compatible format on both POSIX and Windows. PR-URL: #25751 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Use the same JS-compatible format on both POSIX and Windows.
Side note: It might be nice to wrap up all the different date-handling pieces of code in a single place, with a single mechanism and using some standardized format(s).
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes