Skip to content
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

Replayer test in CI: User artificial blockchain instead of recorded one #15576

Open
dkijania opened this issue Apr 29, 2024 · 0 comments
Open

Comments

@dkijania
Copy link
Member

After we enabled Replayer test in Ci we found out another problem which is related to data. Currently we are using recorded data as we are unable to produce artificially generated. Recorded data generation is problematic as it requires a lot of time (> 6h ) or some hacks (like manually converting pending blocks to canonical). There are some ideas like:

Does the proof need to be valid? If not, you can generate the block contents and stick in the dummy blockchain proof
This is the job of the Block_producer.generate_next_state  function, which shouldn't be too bad to setup. (that didn't do quite as much as I hoped)

I can setup an alternative mode for the daemon where it sources its transaction and other data from JSON, but it's still going to be a daemon.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant