-
Notifications
You must be signed in to change notification settings - Fork 7
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
Test sway at commit and converge for unseen candidates #617
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #617 +/- ##
==========================================
- Coverage 79.76% 79.50% -0.27%
==========================================
Files 52 52
Lines 4676 4689 +13
==========================================
- Hits 3730 3728 -2
- Misses 593 604 +11
- Partials 353 357 +4
|
The codecov claims that CONVERGE sway is not hit. |
c60226a
to
0c1cc1e
Compare
0c1cc1e
to
d3ba304
Compare
OK this is ready for another look; please let me know if you can think of a simpler way to test sway at CONVERGE. thanks |
What is the source of non-determinism? I think it should be only the chain seed, which leads to beacons. |
Order of chainsupport map for committed state, and consequently candidate inclusion in |
That seems counter to the comment there, as the comment states that there should be only one. |
Right. If i have not missed anything I think that would only hold if this is fixed. |
d3ba304
to
f185974
Compare
d84abb1
to
e727697
Compare
Test that a participant sways for unseen candidates at `COMMIT` and `CONVERGE`. Part of #237
e727697
to
cb6794a
Compare
Test that a participant sways for unseen candidates at
COMMIT
andCONVERGE
.Part of #237