This repository has been archived by the owner on Jan 2, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 97
Make BenchHist non buildable by default and save logs #666
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
And fix the commitid rule to always rerun the git query
Hopefully avoiding the additional dependencies for charts
ndmitchell
reviewed
Jun 24, 2020
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
I think I've figured out a nicer way to turn benchHist into a benchmark. EDIT: Tested with both stack and cabal and ready to merge |
pepeiborra
force-pushed
the
benchmark-tweaks
branch
2 times, most recently
from
June 24, 2020 14:08
080a22f
to
6c9de89
Compare
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
pepeiborra
force-pushed
the
benchmark-tweaks
branch
from
June 24, 2020 14:21
6c9de89
to
d16e0dc
Compare
pepeiborra
force-pushed
the
benchmark-tweaks
branch
2 times, most recently
from
June 27, 2020 12:00
29cf225
to
bf9f465
Compare
pepeiborra
force-pushed
the
benchmark-tweaks
branch
from
June 27, 2020 21:18
c4ea16d
to
3c5ac8b
Compare
cocreature
approved these changes
Jun 29, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, thank you!
pepeiborra
added a commit
to pepeiborra/ide
that referenced
this pull request
Dec 29, 2020
…#666) * [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
pepeiborra
added a commit
to pepeiborra/ide
that referenced
this pull request
Dec 29, 2020
…#666) * [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
pepeiborra
added a commit
to pepeiborra/ide
that referenced
this pull request
Dec 29, 2020
…#666) * [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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As the title says