Hi Gabriel,

On 2015-09-09 23:29, Gabriel Scherer <gabriel.scherer@gmail.com> writes:

> - A way to collect coverage checking information (which parts of the
> compiler codebase are exercized by the tests?). I started working on
> it once by just adding Bisect somewhere in the compiler build system,
> but lost motivation before getting into a a work-out-of-the-box state
> (it generated many independent coverage files, one for each test, that
> would have to be aggregated). I think that should not be too hard.

We use bisect to test coverage of the JavaScript test suite on our
interpreter, and aggregating the results is simply a matter of doing
  bisect-report -html report bisect*.out
(assuming you want to put the generated report in the report directory).

Best,

Alan

-- 
OpenPGP Key ID : 040D0A3B4ED2E5C7
Last week athmospheric CO₂ average (Updated September 6, 2015, Mauna Loa Obs.):
377.86 ppm