You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While investigating #5571 and #5587, I found that my tools for transcript extraction/replay had bitrotted. The task is to update them.
transcript extraction needs to capture the whole syscall result, even for failed syscalls
gcEveryCrank must be true, else GC is entirely disabled
replay now uses the whole syscall result, even for failed syscalls
the fake kernelKeeper needs getEnableFakeDurable
the fake kernelSlog needs delivery() and syscall()
we should track deliveryNum and try to align it with the original slog
Security Considerations
None, this is for a diagnostic tool
Test Plan
None, although if I'd put more energy into writing these tools in a form that could be tested, they probably wouldn't have bitrotted. I'm currently ok with that.
The text was updated successfully, but these errors were encountered:
These had bitrotted:
* transcript now includes whole syscall result, even failures
* handle kerneldb bundleIDs
* new LMDB in swingstore
* gcEveryCrank=false else all GC is disabled (refs #5600)
* fake kernelKeeper/slogger needed new methods
The new code also attempts to track `deliveryNum`, to align it with
the original slog, but I'm not positive it is accurate.
closes#5602
These had bitrotted:
* transcript now includes whole syscall result, even failures
* handle kerneldb bundleIDs
* new LMDB in swingstore
* gcEveryCrank=false else all GC is disabled (refs #5600)
* fake kernelKeeper/slogger needed new methods
The new code also attempts to track `deliveryNum`, to align it with
the original slog, but I'm not positive it is accurate.
closes#5602
What is the Problem Being Solved?
While investigating #5571 and #5587, I found that my tools for transcript extraction/replay had bitrotted. The task is to update them.
gcEveryCrank
must betrue
, else GC is entirely disabledgetEnableFakeDurable
delivery()
andsyscall()
deliveryNum
and try to align it with the original slogSecurity Considerations
None, this is for a diagnostic tool
Test Plan
None, although if I'd put more energy into writing these tools in a form that could be tested, they probably wouldn't have bitrotted. I'm currently ok with that.
The text was updated successfully, but these errors were encountered: