-
Notifications
You must be signed in to change notification settings - Fork 382
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
Remove the lightning-transaction-sync MSRV #2055
Remove the lightning-transaction-sync MSRV #2055
Conversation
Apparently it has dependencies that don't track an MSRV at all, so we can't practically enforce one in CI.
a4e0e22
to
2ba289a
Compare
Codecov ReportBase: 87.26% // Head: 87.25% // Decreases project coverage by
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more Additional details and impacted files@@ Coverage Diff @@
## main #2055 +/- ##
==========================================
- Coverage 87.26% 87.25% -0.02%
==========================================
Files 101 100 -1
Lines 44414 44480 +66
Branches 44414 44480 +66
==========================================
+ Hits 38759 38810 +51
- Misses 5655 5670 +15
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
@@ -144,7 +144,7 @@ jobs: | |||
run: | | |||
cd lightning && cargo test --verbose --color always --features backtrace | |||
- name: Test on Rust ${{ matrix.toolchain }} with net-tokio | |||
if: "matrix.build-net-tokio && !matrix.coverage && matrix.build-tx-sync" | |||
if: "matrix.build-net-tokio && !matrix.coverage" |
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.
In line 137, can we assume that if matrix.coverage
is not set then it is false? If so, we already have a build covering that in line 125.
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.
I'm not sure what you're asking? We have two builds, one for coverage and one for not-coverage, the coverage one sets link-dead-code.
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.
Right, and on line 136, there's another build for lightning-transaction-sync
where the condition doesn't check for matrix.coverage
at all. Just wondering if there's a difference here, because if there isn't, then that build could be removed.
Because `lightning-transaction-sync` does not have an MSRV (and because its dev-dependencies are huge), we can't build it by default when devs run `cargo test`, so it is moved out of the top-level workspace.
64a7567
to
c4f2e48
Compare
Fixed the bonus transaction-sync test run: $ git diff-tree -U1 64a75679 c4f2e487
diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index 9fb37f1b4..cebaa9a46 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -135,8 +135,2 @@ jobs:
RUSTFLAGS="-C link-dead-code" cargo build --verbose --color always --features esplora-async
- - name: Test transaction sync clients on Rust ${{ matrix.toolchain }} with features
- if: "matrix.build-tx-sync"
- run: |
- cd lightning-transaction-sync
- cargo test --verbose --color always --features esplora-blocking
- cargo test --verbose --color always --features esplora-async
- name: Test backtrace-debug builds on Rust ${{ matrix.toolchain }} |
I'm confused: why are these 'bonus' again? We now only have cases where the tx-sync crate is built, but none that run the tests? |
c4f2e48
to
64a7567
Compare
Grrrr, apparently @wpaulino and I both can't read - I missed that it was separate between test/build. |
Apparently it has dependencies that don't track an MSRV at all, so
we can't practically enforce one in CI.