-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dev env]: Running tests locally on Mac OS #224
Comments
It seems that the hash for Osmosis differs from one Mac VM to another since I still get the hash mismatch if using this fork https://github.com/Farhad-Shabani/cosmos.nix/tree/update-osmosis-vendorhash but @Farhad-Shabani doesn't get the hash mismatch with the fork |
Tests which do not require Osmosis can be run on MacOS using a Linux VM with ARM by running: |
@soareschen, do you have any idea what's causing this? |
Hmm one possibility might be that one of the git tag on Osmosis or its dependencies had been force pushed, and the local git cache for Nix becomes stale. But Nix should have caught any inconsistency somewhere, unless you have a locally updated flake.lock file. In any case, you could try running |
Tried running Let's wait for the Osmosis release with the Wasm fix and then update Cosmos.Nix to see if this fixes the issue then |
It seems like different Nix versions might also produce different hashes from |
The CI seems to be running Nix 2.22.1, https://github.com/informalsystems/ibc-starknet/actions/runs/12948587943/job/36117548337#step:3:321 On Linux VM with
On Linux VM with
So same hash for both versions. But if I run it on MacOS directly with |
Ok, tried out building Osmosis from Cosmos Nix and had the option to configure the 'trusted-public-key': If I don't I get the same hash mismatch, but if I do I end up being able to build Osmosis. And afterwards I can correctly build Osmosis on ibc-starknet. @Farhad-Shabani Could you try these steps? |
Ah, then maybe there are some inconsistencies on the artifacts from different Cachix stores. Probably you should also run |
I tried with allowing the After that, I got curious and wondered if it might be something with the Nix version. So, I uninstalled Nix, deleted all the related files, and reinstalled the latest version (2.26.1) on my Orbstack Linux. Then, I ran the relayer's integration tests locally, and everything worked fine with no hash mismatches. I’m starting to think, like Soares, that this might actually be a bug in Nix. |
Summary
Currently dependencies for running
starknet-integration-tests
is done by usingnix develop ..#rust
from therelayer/
crate. But the behaviour varies depending on the machine used.This makes running tests locally more tedious than needed.
Status
MacOS Darwin (M1 ARM)
Running
nix develop ..#rust
will result in the error:MacOS Darwin running Debian ARM VM
Running
nix develop ..#rust
will result in the error:MacOS Darwin running Debian AMD VM
Linux (Arch) AMD
No issues
The text was updated successfully, but these errors were encountered: