-
Notifications
You must be signed in to change notification settings - Fork 39
Integrate bitreq crate into CI tests
#400
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: master
Are you sure you want to change the base?
Conversation
1e58034 to
2936211
Compare
2b912a3 to
b49f999
Compare
bitreq badgesbitreq subdirectory and update badges
|
Oh I forgot to tie |
b49f999 to
70a9ef0
Compare
Added a blank one with no listed features. |
bitreq/contrib/test_vars.sh
Outdated
| FEATURES_WITH_STD="" | ||
|
|
||
| # Test all these features without "std" enabled. | ||
| FEATURES_WITHOUT_STD="" |
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.
These need filling in with all the crate's features.
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.
Done
NB. due to this the nature of this PR has changed significantly and I have updated the title and description.
cfcf50c to
d1ebd4c
Compare
bitreq subdirectory and update badgesbitreq crate into CI tests
|
I added the features and |
|
Looks like you've messed up the rebase a bit mate, a couple of the patches now have mixed up changes (i.e not described in the git log). |
d1ebd4c to
d6cb085
Compare
|
Tidied up the commits and commit log. |
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.
cACK d6cb085
|
Needs rebase because of the |
`proxy` only works with `std` and causes an error in `no-std`. Add `std` to the `proxy` feature.
LazyLock only stabilizes in rustc 1.80 and causes a CI test error. OnceLock is stable since 1.70 and has the required functionality. Use OnceLock instead of LazyLock.
The example `no-std.rs`, which is currently broken and commented out, fails to compile without `std` because it has a crate level attribute `#![cfg(feature = "std")]`. Remove the `std` attribute so that the (broken) example compiles with `no-std`.
Add all of the features to the lists. async, async-https and proxy require std and are therfore not listed in the no-std features.
Reorder the list alphabetically and add bitreq.
bitreq is now part of the corepc workspace and the github workflow files in its subdirectory are not run anymore. Remove these files.
These badges were linked to workflows that are no longer run on this crate individually.
d6cb085 to
3497da8
Compare
|
Rebased and removed |
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.
cACK 3497da8
bitreqwas developed as a standalone repo with its own.github/workflowdirectory that had workflows to test and lint it.It's now a leaf crate in
corepcand test and lint workflows in its own subdirectory are not run. It is not included in CI tests and contains some issues that cause CI tests to fail.Fix the CI errors, integrate into CI and remove redundant workflow files and badges:
stdto theproxyfeature since it only works withstd.LazyLockwhich is only in stable rustc from 1.80. UseOnceLockinstead which is stable from 1.70.no-stdexample.stdattribute fromno-std.rs. The example is broken and commented out, but still causes a compile failure inno-stdsince the attribute made the module empty. The example was left in so that it can be fixed and used later rather than just deleting it.test_vars.shto integratebitreqinto the CI tests.bitreqto the list of crates to test.bitreqsubdirectory, these are no longer run now it is part of thecorepcworkspace and not its own repo.README.mdbadges.Closes #397