This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Check all cargo features of Substrate on CI #12711
Labels
I5-tests
Tests need fixing, improving or augmenting.
Comments
|
I suggest trying cargo-hack we are using it in jsonrpsee for instance but I reckon that it's quite slow and not sure if that is "acceptable" in substrate. https://github.com/paritytech/jsonrpsee/blob/master/.github/workflows/ci.yml#L68-#L92 |
Thanks for the hint. I also found a similar one at https://github.com/frewsxcv/cargo-all-features#usage.
I think we could use something that just prints the crates and their features, then process that output to generate the commands for a given execution strategy. Perhaps contributing a I've played a bit with a script for that idea cargo metadata --quiet --format-version=1 | jq -r '
. as $in |
paths | select(
.[0]=="packages" and
.[-1]=="source" and
(. | length == 3) and
. as $p | $in | getpath($p)==null # .source == null for workspace crates
) as $crate_path |
del($crate_path[-1]) as $crate_path |
$in | getpath($crate_path) |
.features | if type == "array" then
$in | getpath($crate_path) | .name, [$in | getpath($crate_path + ["features"]) | .[]]
else
$in | getpath($crate_path) | .name, [$in | getpath($crate_path + ["features"]) | keys | .[]]
end
'OutputI don't know if that is enough (looks like there's some special handling in https://github.com/taiki-e/cargo-hack/blob/4ccbb89b4f91e8d79a999280d3b0c22c3d30df24/src/features.rs#L46-L60) or if it's correct, but it could be a starting point. |
oh didn't know that then it makes sense not to use it for substrate where not all crates are published on crates.io |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem: feature checks are hardcoded at the moment
substrate/scripts/ci/gitlab/pipeline/test.yml
Line 159 in eb1a2a8
substrate/scripts/ci/gitlab/pipeline/test.yml
Line 173 in eb1a2a8
The current approach has at least two problems
Solution: come up with a way of automatically testing all the features provided by Substrate.
The general idea of #12709 could be used for reference.
The text was updated successfully, but these errors were encountered: