You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new multi-benchmark-per-process framework introduced in 0abf242 will form the basis for both a passive upload mode (#75), and better integration of Criterion benchmark suites (which typically also run multiple benchmarks per criterion run).
But for this START_BENCHMARK/END_BENCHMARK protocol to be useful, the lines of output in between those delimiters had better be able to set/override all relevant fields of BenchmarkResult. For example PROGNAME:, VARIANT: and so on.
This will probably take the form of a whole pile of LineHarvesters that correspond to the builtin fields. It would be nice to derive that but not too painful to just write it out either.
The text was updated successfully, but these errors were encountered:
This is related to #75 and #73.
The new multi-benchmark-per-process framework introduced in 0abf242 will form the basis for both a passive upload mode (#75), and better integration of Criterion benchmark suites (which typically also run multiple benchmarks per criterion run).
But for this
START_BENCHMARK
/END_BENCHMARK
protocol to be useful, the lines of output in between those delimiters had better be able to set/override all relevant fields ofBenchmarkResult
. For examplePROGNAME:
,VARIANT:
and so on.This will probably take the form of a whole pile of
LineHarvesters
that correspond to the builtin fields. It would be nice to derive that but not too painful to just write it out either.The text was updated successfully, but these errors were encountered: