-
Notifications
You must be signed in to change notification settings - Fork 21
FIX: Fixed an issue with the test_write_epoch_state
unit test.
#118
Conversation
… test runs before warming up the storage dirs. The fix is temporary. I'm currently working on improving the unit test organization. I will create a PR with a more elegant permanent fix. I did not detect this locally because the storage dirs existed. I will account for this in the future.
… local build and a failed build on the CI
…hereum-types` broke some things in our code.
The CI tests were failing after commit: 45facac.
After investigation, I determined that this was the culprit: tomusdrw/rust-web3@91639ff. Specifically, the problem is related to the For now, I resolved the issue by specifying the last good revision of |
Yeah in general it was a bad idea that we kept using his git master as a dependency. |
And I'm not sure what "warming up" means. |
I'm not sure of the reason why we kept using the master. I assume that some of our PRs were merged but never published. I'll trying using a publish version. By warming up, I refer to the setup of test prerequisites. |
Still don't really understand what setup is this. |
The setup required for this particular test is to create the |
@fredfortier I tested and #120 pass all the tests. what am I missing? |
So If I understood correctly, the "warm up" problem is just that your test assumes |
# Conflicts: # enigma-core/app/Cargo.lock # enigma-principal/app/Cargo.lock # enigma-principal/app/Cargo.toml # enigma-tools-u/Cargo.toml
Please do this in a new PR without the changes to web3 and rustc-demangle |
I'll just included in in PR #121 |
This test runs before warming up the storage dirs. The fix is temporary. I'm currently working on improving the unit test organization. I will submit a PR that fixes this permanently and handles setup more gracefully. In the meantime, this will fix the test. I did not detect this locally because the test setup did not delete the local storage, which I will remediate in the next PR. I do not know why the CI behaved differently on this branch and develop.