Skip to content

Use gauge to avoid dependency cycles in the benchmarks #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 2, 2018
Merged

Use gauge to avoid dependency cycles in the benchmarks #16

merged 1 commit into from
Nov 2, 2018

Conversation

RyanGlScott
Copy link
Contributor

In #15, we had to go through unfortunate contortions to modify the haskell-ci-generated .travis.yml script to disable running benchmarks, since vector-binary-instances' dependency on criterion lead to dependency cycles (which confuse cabal-install). To work around this, I employ a similar trick that I use in the reflection library: replace criterion with gauge, a lighter benchmarking library that doesn't depend on vector-binary-instances. With this, we can actually build the benchmarks on Travis, and best of all, we can completely automate the generation of the .travis.yml script.

Pinging @bgamari. See also here for a successful Travis run of this patch (since Travis support for this repo is disabled, I believe).

@RyanGlScott
Copy link
Contributor Author

Ping?

@bgamari
Copy link
Collaborator

bgamari commented Nov 2, 2018

Thanks Ryan!

@bgamari bgamari merged commit c412c66 into bos:master Nov 2, 2018
@bgamari
Copy link
Collaborator

bgamari commented Nov 2, 2018

Released as 0.2.5.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants