You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge #6921: test: wait for new trigger for up to 1s while mining in maturity window
6a13041 test: generate block by batches when it's not important to go one-by-one (Konstantin Akimov)
f56ce76 test: wait for new trigger for up to 1s while mining in maturity window (UdjinM6)
Pull request description:
## Issue being fixed or feature implemented
Mining too fast can result in creation of multiple triggers none of which is going to win - too many "no" votes from competing mns for `AbsoluteYesCount` to go above 0.
## What was done?
Wait for new trigger for up to 1s while mining in maturity window. If no winning trigger was found in 1s we move to the next block. When there is a winning trigger `wait_until` is basically instant.
## How Has This Been Tested?
Run multiple `feature_governance.py` jobs in parallel.
develop: some jobs fail on `wait_until(lambda: have_trigger_for_height(...))`
this PR: should be no to little difference in test duration times comparing to develop with no failures on `wait_until(lambda: have_trigger_for_height(...))`
## Breaking Changes
## Checklist:
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have added or updated relevant unit/integration/functional/e2e tests
- [ ] I have made corresponding changes to the documentation
- [ ] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
ACKs for top commit:
knst:
re-ACK 6a13041
Tree-SHA512: 22317d5097a2836febfddcffa45eb2ebe284ec34dc3b9541e796fb2f99afac4990c2381b28a59c71c90a5fbd386a70f23d4a0cd9d34b55717a4a30538daf6895
0 commit comments