-
Notifications
You must be signed in to change notification settings - Fork 176
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
Network tests failing. #602
Comments
Yes/no. Network tests are not reliable as unit tests. |
Agreed, also required is a version4 community server. But I at least want to enable it to ensure the tests can complete in testing, so more a reminder. |
Changing this to a bug. Network tests are still failing. |
IIRC, many of the failing tests require payment indexing and a v4 server at this point. I agree it's a bug, but maybe temporarily we can allocate some additional domain pointers for v4 mainnet/testnet? Speaking of which, is there are a plan to deprecate v3 mainnet/testnet domains while transitioning over, or will they just be replaced at some specified point? |
Sorry, kind of rushing through triage and forgot what the deal was here. We’ll just replace the community servers on release - after an announcement to the lists. |
Ping on network tests being broken. We need v4 mainnet/testnet servers up for these to work (or identify if they're not working yet). I think we have some mainnet v4 servers coming online at some point in the future, can look into. |
Need to get v4 server out first, working on it. |
Just realized that network tests have been disabled for some time and should be re-enabled.
The text was updated successfully, but these errors were encountered: