-
Notifications
You must be signed in to change notification settings - Fork 648
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 for node connectivity #1715
base: develop
Are you sure you want to change the base?
Conversation
In what way does this relate to the |
This PR is about creating a market and building some market history. #887 (and now #1764) add some access to the node to watch messages go through for address requests. Both contort node to get the information they need. They will no doubt cause conflicts, but I am unsure when (or if) they will get merged. |
I think you're confusing this with #1661. Otherwise you should rethink your commit messages. :-) |
Is it obvious that I do not multitask well? That is the personal task list for improvement. Who knows what I was thinking when I wrote the above. This ticket breaks things out into an "application_runner" for easier testing of 2 nodes. It has a lot in common with #1764 . I will examine the two in order to see if anything in this ticket is worth salvaging. |
#1764 is believed to be near complete. Once that rolls, only a small piece of this branch is salvageable. I will close this ticket, but keep the branch around until I can redo it to only keep the good parts (big block and big transaction tests). |
This test was built to test the p2p portion of node connectivity. I hope it to be of use for some tests.
This breaks out some of the graphene::app functionality to more easily get a test going that needs 2 nodes talking to each other.