* [bench-hist] save messages to log file
And fix the commitid rule to always rerun the git query
* Do not build benchHist by default
Hopefully avoiding the additional dependencies for charts
* Simplify with FileStdout
* Add a flag for bench-hist
Could benchHist be a benchmark instead of an executable, removing the need
for this flag?
Almost. `stack bench` fails because `benchHist` cannot find `ghcide-bench`
in the path. It seems like a bad idea to have a benchmark that fails out of
the box
* Turn benchHist into a benchmark and ghcide-bench into an exe
This works out nicely because:
1. benchHist already runs ghcide-bench,
2. benchHist has additional deps, but ghcide-bench does not.
(benchmark deps don't get built by default)
3. This is the only way I've found to get ghcide-bench in the PATH for benchHist
* Remove redundant dep on applicative-combinators
* Bump versions in stack-ghc-lib.yaml
* update lower bounds for extra in benchHist executable
* Update README guideline on benchmarks
* [benchHist] Fix the commitid rule to always rerun the git query
* fix caps
* benchmark history script
* if HEAD no need to rebuild worktree
* add bench/README.md
* Enable all experiments
* Fix dependency tracking for git branches
* hlints
* Add stack84 extra-deps
* Identify failed experiments in graphs
* Filter our failed benchmarks from aggregate graphs
Otherwise they tend to distort the axis
* Improve graphs (more and easier to see colors)
* update cradles
* customizable output folder
* Cache the config for the duration of the script
Otherwise the script is vulnerable to config edits
* Allow omitting the git: field
* Ignore bench-hist intermediate artifacts
Handy for including bench-hist results in a branch while avoiding the
intermediate artifacts
