-
Notifications
You must be signed in to change notification settings - Fork 436
Upgrade test #4397
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
base: main
Are you sure you want to change the base?
Upgrade test #4397
Conversation
|
👋 I see @valentinewallace was un-assigned. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4397 +/- ##
==========================================
+ Coverage 86.03% 86.04% +0.01%
==========================================
Files 156 156
Lines 103092 103178 +86
Branches 103092 103178 +86
==========================================
+ Hits 88694 88779 +85
- Misses 11885 11888 +3
+ Partials 2513 2511 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
TheBlueMatt
left a comment
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.
Because review bandwidth is rather limited, please don't open a flood of PRs at once - give each new PR some time to get review cycles before you open up new ones. If you're looking for ways to contribute, try reviewing existing open PRs! Learning the codebase through review is likely to be way more fruitful than just writing code.
| .is_err()); | ||
| } | ||
|
|
||
| // Test that a monitor with a legacy u64::MAX update_id (from pre-0.1 LDK) can still be read |
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.
By "upgrade test", the issue meant adding a test in the lightning-tests crate which actually uses an old version of LDK to get us into a state where we have to handle u64::MAX updates.
legacy_closed_channel_update_id_upgradethat verifies the upgrade path for nodes carrying legacyu64::MAXupdate IDs from pre-0.1 LDK.Closes: #4104