Write transactions to static files on insert_historical_block
#11524
Labels
C-enhancement
New feature or request
C-test
A change that impacts how or what we test
M-prevent-stale
Prevents old inactive issues/PRs from being closed due to inactivity
S-needs-investigation
This issue requires detective work to figure out what's going wrong
Describe the feature
Writing transactions to static files on
insert_historical_block
tried on #11523 (05cf701) triggered a bunch of errors in other tests.Many tests across the test-suite are assuming that transactions are on database instead of static files. This should change especially with the introduction of the new engine, given that transactions will start getting written directly to static files. (they already do during staged sync)
When done, remove the transaction writer from
provider_with_chain_spec_and_random_blocks
introduced on the above PR.We probably want to do this crate by crate if there are a lot of tests involved that need to be changed.
Additional context
No response
The text was updated successfully, but these errors were encountered: