Bump evmone to v0.12.0 and add ubuntu2404 image

[nikola-matic]

No description provided.

[ekpyron]

What's the exact reason for the specific version meddling here, i.e. what exactly breaks without that? The very purpose of these images is to test something close to a default configuration, so messing with that too much is kinda against the point of these - and also strange that 20.04 gcc seems fine with whatever triggers this, while default 22.04 clang isn't :-).

[ekpyron]

Before we install non-default versions in this one, we can also consider switching to 24.04 for the clang image.

We also need to add a gcc 24.04 image anyways by the way.

[nikola-matic]

clang-15 is now the minimum required version to build evmone.

[nikola-matic]

Before we install non-default versions in this one, we can also consider switching to 24.04 for the clang image.

We also need to add a gcc 24.04 image anyways by the way.

ossfuzz is still gonna be a problem since the Google team that maintains it doesn't really wanna upgrade their base images, which are still on focal (20.04) - google/oss-fuzz#11835

All in all, kinda annoying :)

[ekpyron]

Any problem with just pulling in the binaries for evmone (that's done for the 20.04 gcc images already anyways)? There's little point in us testing the builds for them - and changing our compiler setup for building a testing-only dependency is rather weird :-).

[github-actions]

solbuildpackpusher/solidity-buildpack-deps:ubuntu2204-10 [solbuildpackpusher/solidity-buildpack-deps@sha256:ba2d878c26d681a7d6c1922258b47c2e5dd61d0e46ab4c6a4862b473e61997b6].

[github-actions]

solbuildpackpusher/solidity-buildpack-deps:ubuntu2204.clang-9 [solbuildpackpusher/solidity-buildpack-deps@sha256:703cdad5fa5c8686a3080ebb1aea1485ded2446561bf56e2945a87f2fa20a446].

[github-actions]

solbuildpackpusher/solidity-buildpack-deps:ubuntu2404-1 [solbuildpackpusher/solidity-buildpack-deps@sha256:5d6d27551104321a30326d6024bd4e96d9d899a97a78eb9feea364996f1d18b5].

[github-actions]

solbuildpackpusher/solidity-buildpack-deps:ubuntu2004-25 [solbuildpackpusher/solidity-buildpack-deps@sha256:b3f321fb2d8e7a41ca9328672061c1840e5cd3fb5be503aa158d1c508deacf0a].

[r0qs]

LGTM. But will we run tests using the ubuntu2404 image in the CI? If so, we need another PR adding it to the CircleCi config.

[nikola-matic]

LGTM. But will we run tests using the ubuntu2404 image in the CI? If so, we need another PR adding it to the CircleCi config.

I'd prefer to do that in another PR so as not to trigger yet another buildpack-deps build. By the way, if I merge this now, I assume a new buildpack-deps build will be triggered on develop (do we stop these manually, or just let them run)?

[r0qs]

LGTM. But will we run tests using the ubuntu2404 image in the CI? If so, we need another PR adding it to the CircleCi config.

I'd prefer to do that in another PR so as not to trigger yet another buildpack-deps build. By the way, if I merge this now, I assume a new buildpack-deps build will be triggered on develop (do we stop these manually, or just let them run)?

If I'm not mistaken, the action is only triggered on PRs targeting the develop branch, so merging will not run it.