You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the overclock labs team would be OK with it, I configure a pretty nice CI server and would be happy to donate a powerful one to the cosmos-omnibus project. This could be used to automatically confirm weather or not chains can state sync, and probably a lot more.
Or you could.
Basically the constraint would be the 7gb of storage that github provides.
The text was updated successfully, but these errors were encountered:
I'd love to explore this further @faddat - agree Statesync is a great test as it won't require nearly as much disk, but not sure if it's reliable enough right now for every single chain?
Even just checking the node starts would be useful but not quite sure how to write that off the top of my head. Maybe just checking the initial output so we can confirm node boots, and the ENV namespace is correct by confirming the RPC address is configured correctly. Love to hear any thoughts when you get a moment.
If the overclock labs team would be OK with it, I configure a pretty nice CI server and would be happy to donate a powerful one to the cosmos-omnibus project. This could be used to automatically confirm weather or not chains can state sync, and probably a lot more.
Or you could.
Basically the constraint would be the 7gb of storage that github provides.
The text was updated successfully, but these errors were encountered: