-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Change regtest port to 18344. Closes #2269. #2270
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.
utACK. I confirmed that 18444 does not appear as a port number anywhere else in the source and docs. There should be no compatibility obstacles to changing this for regtest.
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.
utACK
Tested, works fine. ACK. @zkbot try |
Change regtest port to 18344. Closes #2269.
Hmm, why is this still pending after 11 hours? @ageis? |
💥 Test timed out |
@zkbot retry |
Change regtest port to 18344. Closes #2269.
☀️ Test successful - zcash |
@zkbot r+ |
📌 Commit 05844ba has been approved by |
⌛ Testing commit 05844ba with merge 6142843... |
💔 Test failed - zcash |
Known-nondeterministic test failure unrelated to this PR. @zkbot retry |
Change regtest port to 18344. Closes #2269.
☀️ Test successful - zcash |
Are we merging this soon? And oh ugh, I think I fixed the nondeterministic test failure in the latest commit to #2200, should merge that to prevent this from happening |
@arcalinea yes, it had already merged. |
No description provided.