Fix firedancer-dev backtest requiring keys (pt. 2) #6643
Conversation
| } | ||
|
|
||
| static ulong | ||
| next_leader_slot( fd_replay_tile_t const * ctx, |
There was a problem hiding this comment.
What exactly is this "fixing"? You're just removing functionality from backtest that we actually need to simulate real production performance.
@mmcgee-jump I can't run backtest without random unrelated file system accesses to ~/.firedancer/fd1/identity_key.json. This file usually doesn't exist, so I just get a non-descriptive exit code 1 error. Backtest does asynchronous single ledger replay without fork choice or block production We should make a new subcommand if we want a topology that exercises block production and fork choice on historical data. |
|
Oh I see, didn't realize backtest is already doing block production. Rewriting this PR |
|
Well, this is still valid. firedancer-dev backtest is never going to get a leader slot unless we also have functionality to forcibly inject ourselves into a leader schedule (and break consensus rules) |
No description provided.