-
Notifications
You must be signed in to change notification settings - Fork 619
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: rework connect tests to daily tests, add cargo hack. #1433
Conversation
Example run where I modified the trigger to run for |
514d497
to
da5bf4a
Compare
Codecov Report
@@ Coverage Diff @@
## main #1433 +/- ##
=======================================
Coverage 96.49% 96.49%
=======================================
Files 71 71
Lines 15169 15169
=======================================
Hits 14637 14637
Misses 532 532 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
We are gradually adding other CI task here that aren't appropriate for the main CI runs. Since it's no longer dedicated to just running the connection tests we need a more representative name.
This ensures the example binary continues to build, similar to how we handle the other examples.
This better separates the connection tests from the example binary smoke tests. In a subsequent commit we will add another job for running `cargo hack`.
Test the feature powerset of the crate using `cargo hack`. The runtime of this is too large to use as part of the regular CI flow but it is helpful for catching feature interaction breakages.
da5bf4a
to
d75935f
Compare
Test run for the updated branch. |
This branch reworks the existing "connect tests" CI job that runs once a day to be "daily tests". This better matches how we've been using it for things beyond the connect test suite (e.g. smoke test builds of example binaries).
Additionally it:
name
fields to each workflowstep
for better readability.cargo test
for all feature combinations #1427 earlier than we would otherwise, without compromising PR dev velocity.