Skip to content
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

Don't build (Haskell) benchmarks by default, use cabal bench #119

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

hacklschorsch
Copy link
Member

@hacklschorsch hacklschorsch commented Mar 6, 2025

Building the benchmark suite by default broke the tahoe-lafs-mobile build since its criterion can't be built with the android version of GHC.

Also, building the benchmark takes ages.

Use cabal build --enable-benchmark to build the benchmark from now on, and cabal bench to run the benchmark (like specified in the Cabal documentation).

This broke the tahoe-lafs-mobile build since its criterion
can't be built with the android version of GHC.

Use `cabal build --enable-benchmark` to build the
benchmark from now on.
@hacklschorsch hacklschorsch changed the title Don't build benchmarks by default Don't build (Haskell) benchmarks by default, use cabal bench Mar 6, 2025
@hacklschorsch
Copy link
Member Author

Hey @meejah can we merge this?

@hacklschorsch
Copy link
Member Author

Or who could be interested in this - @sajith?

Copy link
Member

@sajith sajith left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the deal with the CI failures here? Is upload-artifact@v3 too old?

@hacklschorsch
Copy link
Member Author

What is the deal with the CI failures here? Is upload-artifact@v3 too old?

Yes, that's what #121 is for - happy if you can take a look there as well!

@sajith
Copy link
Member

sajith commented Mar 17, 2025

Yes, that's what #121 is for - happy if you can take a look there as well!

I approved #121. Are you able to merge it, or should I do that?

@hacklschorsch
Copy link
Member Author

hacklschorsch commented Mar 17, 2025 via email

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