grandizzy

closing in favour of #8367

unfortunately this approach doubles time of building, as there's a single runner building for both platforms, we'd need something like https://docs.docker.com/build/ci/github-actions/multi-platform/#distribute-build-across-multiple-runners to parallelize them this can be tested locally by...

> > unfortunately this approach doubles time of building > > Is that an issue in practice? I think so, pretty sure this will kick in https://github.com/foundry-rs/foundry/blob/617931240f77e4751f04ae53e61ca855c78a5bbf/.github/workflows/docker-publish.yml#L26 (at least on...

> But really, this begs the question: why even compile for docker? Why not just use the built artifacts and just package it after the fact vs. compiling for docker...

no longer the case with latest version, please reopen if you hit same behavior 

@pcaversaccio can this one be closed now?

> Do we really need a docker container to run the deploy scripts? All dependencies should already be handled by Nix. I found it easier to sharing keystore and start...

> @dizzy I think doing this without Docker would be nicer, unless Docker really adds something unique. > > It would mean starting parity in Travis, and then running `scripts/setup-env.sh`....

@cruzdanilo most probably this happens because we also populate fuzz dict from push bytes (motivated by #1168 )

@cruzdanilo I meant probably the order of values we collect here is not ordered either and affected by such changes as well, will investigate more why this happens