-
Notifications
You must be signed in to change notification settings - Fork 11
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
S5 fails state-hash when primed at 65436418 #902
Comments
The last known block where priming works correctly is 51359673. Error at when priming to block 65436417:
Command to reproduce the error.
|
Confirming that the database is correct. Because ithout priming it succeeds: https://jenkins.fantom.network/job/Aida/job/AidaDb/job/pre-release-mainnet/21/ |
Priming keeps failing after 55M with develop and most recent tosca and carmen. |
Found out that the block 54535894 has incorrect ressurection order generated in deletedDb generation has to be fixed. |
When priming S5 carmen up till 51M blocks the state-hash is correct. When priming last block of previous patch it fails.
xapi150 https://jenkins.fantom.network/job/Aida/job/CustomBuild/job/s5-priming-tests/10/
This issue also occured on xapi310:
https://jenkins.fantom.network/job/Aida/job/AidaDb/job/pre-release-mainnet/20/
On xapi310 I started zero-last block without priming to confirm the database is correct.
https://jenkins.fantom.network/job/Aida/job/AidaDb/job/pre-release-mainnet/21/
The text was updated successfully, but these errors were encountered: