Ensure that benchmarks continue to compile #2674
Labels
A-Build-System
Related to build systems or continuous integration
C-Code-Quality
A section of code that is hard to understand or change
As noticed in #2673, our benchmark code can silently go stale and fail to compile. Obviously, this is bad and we should fix it.
Running the benchmarks for each PR is too expensive and noisy (in terms of time, compute and developer attention), but verifying that they compile is much cheaper.
@cart's opinion is that this should be a separate step in the CI, rather than handled by integrating the CI into the main Bevy cargo workspace.
The text was updated successfully, but these errors were encountered: