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

[hacklschorsch]

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).

[hacklschorsch]

Hey @meejah can we merge this?

[hacklschorsch]

Or who could be interested in this - @sajith?

[sajith]

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

[hacklschorsch]

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]

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]

Please do it when you get to it, no hurries. (I don't have the necessary permission)

[hacklschorsch]

This is CI green apart from publishing on test PyPI - Maybe the CI needs a tiny bit of tweaking to actually not publish pull requests on test pypi @sajith?

https://github.com/tahoe-lafs/zfec/actions/runs/14239893166/job/39907563248?pr=119

The workflow context indicates that this action was called from a
pull request on a fork. GitHub doesn't give these workflows OIDC permissions,
even if id-token: write is explicitly configured.

To fix this, change your publishing workflow to use an event that
forks of your repository cannot trigger (such as tag or release
creation, or a manually triggered workflow dispatch).

[hacklschorsch]

Hey @sajith ! Please hit the merge button on this PR, I don't have the privilege. (The one red CI item is because of #133 I believe)

[sajith]

@hacklschorsch Done! Sorry about not being around much.

[hacklschorsch]

Thanks @sajith and no worries!