-
Notifications
You must be signed in to change notification settings - Fork 214
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
Manual test for syncProgress #977
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @piotr-iohk
bors r+ |
bors r- |
Canceled |
@Anviking I just noticed the file location. |
85c22fb
to
24e7531
Compare
Maybe. There is already an existing I just renamed the addition to What would feel off to me is that this test is really testing functionality in |
@Anviking that makes sense. Maybe it'd be better actually to have an additional file with an index/table of contents with links to all manual procedures for convenience. |
I agree. Then, it makes sense to have them all in a parent location, at the root of the project perhaps? Let's move them all in a |
bors r+ |
977: Manual test for syncProgress r=Anviking a=Anviking # Issue Number #921 # Overview - [x] I have added a manual test making sure 1. State is `Ready`, 2. syncProgress drops when node is killed, 3. syncProgress reaches `Ready` again when node is re-started. # Comments <!-- Additional comments or screenshots to attach if any --> <!-- Don't forget to: ✓ Self-review your changes to make sure nothing unexpected slipped through ✓ Assign yourself to the PR ✓ Assign one or several reviewer(s) ✓ Once created, link this PR to its corresponding ticket ✓ Acknowledge any changes required to the Wiki --> Co-authored-by: Johannes Lund <johannes.lund@iohk.io>
Build succeeded |
Issue Number
#921
Overview
Ready
, 2. syncProgress drops when node is killed, 3. syncProgress reachesReady
again when node is re-started.Comments