Skip to content
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

[CI] - Run tests and/or compilation separately for each workspace crate #1213

Closed
Dinonard opened this issue Mar 29, 2024 · 1 comment
Closed
Labels
project Issue is part of an ongoing project

Comments

@Dinonard
Copy link
Member

It's possible that even though our cargo check or cargo test work just fine, compiling or testing them separately will fail because they don't define correctly dependency features. This is easily hidden when testing everything since it's likely that all necessary features will be enabled.

To avoid this, introduce a new job which will check test each crate individually.

for package in $(cargo metadata --format-version=1 --no-deps | jq -r '.packages[].name'); do
    cargo test -p $package
done
@Dinonard Dinonard added the project Issue is part of an ongoing project label Mar 29, 2024
@Dinonard Dinonard changed the title CI - Run tests and/or compilation separately for each workspace crate [CI] - Run tests and/or compilation separately for each workspace crate Apr 5, 2024
@Dinonard
Copy link
Member Author

Dinonard commented Sep 6, 2024

Should be handled by the introduction of zepter into CI.

@Dinonard Dinonard closed this as completed Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
project Issue is part of an ongoing project
Projects
None yet
Development

No branches or pull requests

1 participant