echidna 2.0.5

[elopez]

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

[elopez]

As a sidenote, I noticed the 13-arm64 builders do not appear to have Rosetta set up, so they end up skipping bottle production (one of the dependencies on the chain, solc-select, requires it when running on ARM)

[SMillerDev]

None of the runners should be using rosetta to build anything.

[elopez]

It's not used in the build process, but part of the test involves invoking an intel-only program (solc). Normally this works fine because Rosetta is there to help.

I don't know what the right way to proceed here would be, maybe we should skip testing on ARM? This appears to affect only macOS 13 runners FWIW (see the warning about "brew test --verbose echidna failed on macOS Ventura (13) on Apple Silicon!")

[BrewTestBot]

🤖 A scheduled task has triggered a merge.