Skip to content

Fix new warnings causing CI build failures on rustc beta #2954

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

Merged
merged 9 commits into from
Apr 5, 2024

Conversation

TheBlueMatt
Copy link
Collaborator

No description provided.

@TheBlueMatt TheBlueMatt force-pushed the 2024-03-test-ci-beta-fail branch from 4f5ae10 to 9fac656 Compare March 20, 2024 19:16
@codecov-commenter
Copy link

codecov-commenter commented Mar 20, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.35%. Comparing base (1e54dd6) to head (2f734f9).

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2954      +/-   ##
==========================================
- Coverage   89.38%   89.35%   -0.03%     
==========================================
  Files         117      117              
  Lines       95623    95597      -26     
  Branches    95623    95597      -26     
==========================================
- Hits        85476    85425      -51     
- Misses       7918     7935      +17     
- Partials     2229     2237       +8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@TheBlueMatt
Copy link
Collaborator Author

Will try to fix the new regression in our lockorder testing on Windows rustc beta as well.

@tnull
Copy link
Contributor

tnull commented Mar 21, 2024

Unfortunately still failing, it seems. :(

@TheBlueMatt
Copy link
Collaborator Author

Sorry, was just adding logging so I could see what was up. Sadly it looks like a backtrace or rustc regression, so we'll have to ignore it for now. Opened rust-lang/rust#122857 upstream

@TheBlueMatt TheBlueMatt force-pushed the 2024-03-test-ci-beta-fail branch 5 times, most recently from 7381a1d to 88314d6 Compare March 21, 2024 15:54
@TheBlueMatt
Copy link
Collaborator Author

Also fixed all the new non-failing warnings....turns out there were a lot.

dunxen
dunxen previously approved these changes Mar 26, 2024
Copy link
Contributor

@dunxen dunxen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM (with understanding that we'll have to wait to fix windows beta later due to rustc regression). At least these were mostly single line fixes just in a bunch of files.

@TheBlueMatt
Copy link
Collaborator Author

Yea, apparently rustc may do a point release to fix backtraces on Windows (not actually sure why we aren't failing on stable and only failing on beta, but whatever).

@TheBlueMatt TheBlueMatt added this to the 0.0.122 milestone Mar 28, 2024
New rustc now warns on duplicate imports when one of the imports
is from a wildcard import or the default prelude. Thus, because we
often don't actually use the imports from our prelude (as they
exist to duplicate the `std` default prelude), we have to mark most
of our `crate::prelude` imports with `#[allow(unused_imports)]`,
which we do here.
New rustc beta now warns on duplicate imports when one of the
imports is from a wildcard import or the default prelude. Thus, for
simplicity, we need to make our `crate::prelude` mostly identical
to the `std` one, allowing us to always simply use the
`crate::prelude` and let it decide if we need to import anything.
New rustc beta now warns on duplicate imports when one of the
imports is from a wildcard import or the default prelude. Thus, to
avoid this here we prefer to always use `crate::prelude::*` and let
it decide if we actually need to import anything.
We no longer use `Time` during scoring, which makes several of its
methods now useless. We remove those here.
... that newer rustc now warns about.
@TheBlueMatt
Copy link
Collaborator Author

Rebased.

@tnull
Copy link
Contributor

tnull commented Apr 5, 2024

Given that these are ~trivial changes, will merge after CI passes.

@tnull tnull merged commit 3a9fe20 into lightningdevkit:main Apr 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants