diff options
| author | Mission Liao <mission.liao@dexon.org> | 2019-03-18 17:06:38 +0800 |
|---|---|---|
| committer | Jimmy Hu <jimmy.hu@dexon.org> | 2019-03-18 17:06:38 +0800 |
| commit | 9e97ddc00c67ee13ceb8fc597f4f55cfd6df6101 (patch) | |
| tree | a9c3c3c9520fca2205c5eef9b1355a5db0fca539 /core/crypto/utils.go | |
| parent | 89dddf787c9360f0fed76738fb515be30c7d73bc (diff) | |
| download | tangerine-consensus-9e97ddc00c67ee13ceb8fc597f4f55cfd6df6101.tar tangerine-consensus-9e97ddc00c67ee13ceb8fc597f4f55cfd6df6101.tar.gz tangerine-consensus-9e97ddc00c67ee13ceb8fc597f4f55cfd6df6101.tar.bz2 tangerine-consensus-9e97ddc00c67ee13ceb8fc597f4f55cfd6df6101.tar.lz tangerine-consensus-9e97ddc00c67ee13ceb8fc597f4f55cfd6df6101.tar.xz tangerine-consensus-9e97ddc00c67ee13ceb8fc597f4f55cfd6df6101.tar.zst tangerine-consensus-9e97ddc00c67ee13ceb8fc597f4f55cfd6df6101.zip | |
test: try to mitigate flaky tests (#498)
* Add assertion to make sure all nodes are synced.
* Retry round event with BA's interval
We are about to modify lambdaDKG with block height, instead of timing.
Therefore, the last interval we could use is BA's interval.
* Check ctx in inifite loop
* Disable this panic temporary
If a fast sync triggered by receiving types.AgreementResult from later
position, this panic would be triggered 100%, ex.
current-round: 1,
change-notary-height: 120,
agreeemnt-result from round:2 height:121
However, I don't have easy way to fix it temporary.
* Lower down the test size for TCP
* Fix typo
* Fixup: revert the removed panic
Diffstat (limited to 'core/crypto/utils.go')
0 files changed, 0 insertions, 0 deletions