-
Notifications
You must be signed in to change notification settings - Fork 155
Remove unstable
feature
#482
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
Conversation
Not sure what to make of this CI failure. It might be a bug in |
Could you also add a note to the README explaining how to run the benchmarks? |
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.
ACK 0c653bc
My memory is super vague on this but I kind of remember now that we can't do this PR until we stop using |
Sounds like it's about time we just wrote our own |
Shall we fork https://github.com/marshallpierce/rust-base64 at the version we depend on (0.13) and hack it to suit our project? Or do you think it is worth investing the time to write from scratch? |
Can you kick CI on this one to see if the failure has gone away? Re forking base64, I think no, I think we should instead try to find a version that works and |
The CI fail is because of |
It works now, IIRC it was because of edition 2018 and Rust 1.29 that it did not work. I'll put |
f2c25f3
to
d12eb70
Compare
This has uncovered a bug in feature gating in test/bench code in |
d12eb70
to
17ffc7b
Compare
Rebase on master. |
Back on ice till rust-bitcoin/rust-bitcoin#1936 merges and is released. EDIT: Fix is in rust-bitcoin v0.30.1 |
99ded54 release 0.30.1 (Andrew Poelstra) b46b61a Use hex_lit::hex in benches (Tobin C. Harding) Pull request description: Needed to unstick rust-bitcoin/rust-miniscript#482 ACKs for top commit: tcharding: ACK 99ded54 sanket1729: utACK 99ded54 Tree-SHA512: d8eeb3203be8d5823a600f4e8066061f27a2eef576f7e979271bf435c4610ed1861b4416254eb52ed2306df250bebca35cec12e8ecaa3779ca12a7b8ddae3a3c
fce9af3
to
8ccc4ae
Compare
Currently it is not possible to run the test suite with `cargo test --all-features`, this is because we use a feature called `unstable` to enable the unstable `test` crate that is used for benchmarking. There is another way to conditionally enable the test crate and guard the benchmark code. We can use a custom configuration option `bench` and then set it using `RUSTFLAGS='--cfg=bench`.
8ccc4ae
to
1a33e67
Compare
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.
ACK 1a33e67
Currently it is not possible to run the test suite with
cargo test --all-features
, this is because we use a feature calledunstable
to enable the unstabletest
crate that is used for benchmarking.There is another way to conditionally enable the test crate and guard the benchmark code. We can use a custom configuration option
bench
and then set it usingRUSTFLAGS='--cfg=bench
.