255033 2023-04-05 08:20:29 -0700 Web Inspector: Console: timestamps are always wrong 2023-04-21 13:20:46 -0700 1 1 1 Unclassified WebKit Web Inspector WebKit Nightly Build All All RESOLVED FIXED InRadar P2 Normal --- 248240 1 hi hi hi inspector-bugzilla-changes jasmine.mok webkit-bug-importer oldest_to_newest 1946737 0 hi 2023-04-05 08:20:29 -0700 1. log any message 2. compare to time on your computer 1946738 1 webkit-bug-importer 2023-04-05 08:20:45 -0700 <rdar://problem/107660054> 1948829 2 jasmine.mok 2023-04-14 11:01:01 -0700 I was able to reproduce this bug on macOS. It does not reproduce on Windows. It looks like there's an issue with how MonotonicTime::now() is implemented for OS(DARWIN): https://github.com/WebKit/WebKit/blob/main/Source/WTF/wtf/CurrentTime.cpp#L265-L266 At 6:41 PM I output the following: mach_absolute_time(): 2410267093664 fromMachAbsoluteTime(mach_absolute_time()): Monotonic(100427.795617 sec) MonotonicTime::now(): Monotonic(100427.795629 sec) Seconds(MonotonicTime::now().secondsSinceEpoch()): 100427.795569 sec Converting 100427.795617 seconds to a timestamp yielded 19:53:47.795 When I commented out the OS(DARWIN) implementation of MonotonicTime::now() and tested again at 6:46 PM I got the correct timestamp of 18:46:54.921 1948888 3 hi 2023-04-14 14:58:35 -0700 very odd. id expect more things to be broken if this is that off 🤔 im pretty sure JS `Date` uses `WallTime`. perhaps we should be using that here too? 1949074 4 hi 2023-04-16 19:54:23 -0700 Pull request: https://github.com/WebKit/WebKit/pull/12782 1950463 5 ews-feeder 2023-04-21 13:20:44 -0700 Committed 263261@main (1eb0aa379232): <https://commits.webkit.org/263261@main> Reviewed commits have been landed. Closing PR #12782 and removing active labels.