-
Notifications
You must be signed in to change notification settings - Fork 15
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
fix: restart node on compatible upgrade #4886
Conversation
if (isCompatible) { | ||
console.log('The versions are compatible.'); | ||
await simpleRuntimeUpgrade(nextVersionWorkspacePath, true); | ||
|
||
// TODO: Add restart nodes support, as in the prebuilt case. |
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.
leaving this as a TODO because I'm considering deleting the git-based upgrade test, feels a bit unnecessary now
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4886 +/- ##
======================================
- Coverage 72% 72% -0%
======================================
Files 428 428
Lines 73171 73026 -145
Branches 73171 73026 -145
======================================
- Hits 52685 52483 -202
- Misses 17933 17988 +55
- Partials 2553 2555 +2 ☔ View full report in Codecov by Sentry. |
Pull Request
Checklist
Please conduct a thorough self-review before opening the PR.
Summary
When the versions are "compatible" it doesn't mean the RPCs will be unbroken. So we have to start the node with the new version to ensure the RPC updates are reflected on the node.
e.g. see this failure: https://github.com/chainflip-io/chainflip-backend/actions/runs/9191091275/job/25277048379
Upgrade tests should pass now: https://github.com/chainflip-io/chainflip-backend/actions/runs/9208000827