use batching for checkstyle command #55
Comments
dougxc
pushed a commit
that referenced
this issue
May 12, 2016
…x:topic/benchdoc to master * commit '6ade893df8a98f9e3571fd4d6491b41ec5c36bbf': Re-enable numeric extra fields in commit info for non-main suites. Fix inconsistencies with `JavaVm` classes. Temporarily disable benchmark timestamp info in extra suites. Fix example in design doc. Bump up mx version. Embed all the commit-related information of all suites into datapoint. Fix GR-272: store commit revision for all mx suites. Add `mxsuite` argument when registering a `bm_suite`. Introduce `DynamicVar` class for dynamically scoped global variables. Implement `mx benchmark` functionality from `benchmark` design doc. Fix typo. Complete mx benchmark design doc. Add design doc for mx benchmark.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As suggested in https://github.com/graalvm/graal-core/issues/72, the checkstyle command should use batch processing for all projects that share the same checkstyle configuration. We can probably re-use some of the batching logic from the
mx eclipseformatcommand to do this.The text was updated successfully, but these errors were encountered: