Fix ledger_priority.sequential_blocks testcase (#4805) Different account chains are ot guaranteed to have the same priority timestamp. Openening could happen much later, independant of the sending. It can be euqal or greater Co-authored-by: gr0vity <gr0vity.dev@gmail.com>
__________
Type: commit
Hash: bdbefc601f4ecec4f807c431cd98adbec99bb2f7
Created: 42 day(s) ago
__________
gr0v1ty/nano-node:bdbefc601f4ecec4f807c431cd98adbec99bb2f7
Test Case | Status | Duration | Median Deviation | Log | Graph |
---|---|---|---|---|---|
5n4pr_conf_10k_bintree | PASS | 118 s | 7.0 s | - | Show |
5n4pr_conf_10k_change | PASS | 151 s | 12.0 s | - | Show |
5n4pr_conf_change_dependant | PASS | 154 s | 24.0 s | - | - |
5n4pr_conf_change_independant | PASS | 129 s | -1.0 s | - | - |
5n4pr_conf_send_dependant | PASS | 139 s | 12.5 s | - | - |
5n4pr_conf_send_independant | PASS | 122 s | 0.5 s | - | - |
5n4pr_rocks_10k_bintree | PASS | 117 s | 0.0 s | - | - |
5n4pr_rocks_10k_change | PASS | 165 s | -2.0 s | - | - |