Permalink
Commits on Nov 4, 2018
  1. Moved `types::Second` and `types::Unit` to new `unit` module

    jasonpeacock authored and sharkdp committed Nov 2, 2018
    Also review feedback.
  2. Add option to set time units for CLI & Markdown, closes #80

    jasonpeacock authored and sharkdp committed Oct 30, 2018
    Add option to set the time units to either `MilliSecond` or `Second`
    for both CLI output and Markdown export, overriding the default logic.
Commits on Oct 31, 2018
  1. Add option to set the shell, closes #61

    jasonpeacock authored and sharkdp committed Oct 31, 2018
    Allow the user to set the shell used for executing benchmark commands.
    
    The option (-S/--shell) can be overridden, when there are duplicate
    options the last option's value will be used.
Commits on Oct 28, 2018
  1. Addressed review feedback

    jasonpeacock authored and sharkdp committed Oct 27, 2018
  2. Change markdown export to use seconds, closes #71

    jasonpeacock authored and sharkdp committed Sep 9, 2018
    The markdown results exporter was using milliseconds, but the other
    results exporters are using the default seconds unit.
    
    Apply some refactoring so the same logic used to select units for the
    CLI output can be used to select the units for the markdown exporter.
    
    Now the units of the markdown exporter match that of the CLI.
    
    When there are multiple benchmarks, the CLI will choose the
    appropriate unit for each benchmark separately. In this case, the
    markdown exporter will use the first benchmark to select the units for
    all the results.
    
    *This will change the markdown results for all users from milliseconds
    to seconds, a UX breaking change.*
    
    Add unit tests for the markdown exporter to verify the output.
    
    Issue #80 proposes a new option to choose the units used for both the
    CLI report and results export.
Commits on Sep 28, 2018
  1. Compact output, add `-s color` option, closes #70

    jasonpeacock authored and sharkdp committed Sep 15, 2018
    Strip the empty lines within the results for each benchmark, but keep
    the empty line between each benchmark, and before the summary.
    
    Add `color` style option to show color but not be interactive (no
    progress bar).