Resurrect broken benchmark programs

[erikd]

Description

I thought benchmark programs were being built in CI but obviously they are not or these issues would have been found before they were merged to develop.

This may actually be due to a bug in stack.

Linked issue

N/A

Type of change

• 🐞 Bug fix (non-breaking change which fixes an issue)
• 🛠 New feature (non-breaking change which adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)
• 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
• 🔨 New or improved tests for existing code
• ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

• I have read the style guide document, and my code follows the code style of this project.
• If my code deals with exceptions, it follows the guidelines.
• I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.

Testing checklist

• I have added tests to cover my changes.
• All new and existing tests passed.

QA Steps

Ran:

stack test && stack bench --no-run-benchmarks

[KtorZ]

Benchmarks are still not built by the CI right?
Do we have a ticket tracking this?

[erikd]

Yes, there is a devops ticket tracking this.