-
-
Notifications
You must be signed in to change notification settings - Fork 689
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
run coverage only after merge #2212
Conversation
coverage is a quite slow step in CI. It can be run only after merging
run: cargo +nightly build --all-features | ||
|
||
- name: Check Bench Compilation | ||
run: cargo +nightly bench --no-run --profile=dev --all-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.
Will we look at the result? It won't give a diff of the last run will it?
It seems too much for a PR especially.
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.
Note the --no-run
argument. This will not execute the benchmarks, just check that they compile (and even use the dev
profile to get fast build time instead of fast builds).
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.
We broke the benchmarks compilation previously, since they are not covered in the CI. This did break as a consequence https://pseitz.github.io/tantivy_bench_graph/index.html
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.
ah got it!
Co-authored-by: Paul Masurel <[email protected]>
coverage is a quite slow step in CI. It can be run only after merging
Add compile benchmarks to regular CI test