Skip to content
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

[Bug]: Some runs of run.sh fail on ARM64 #278

Closed
geoff-vball opened this issue Feb 7, 2024 · 4 comments
Closed

[Bug]: Some runs of run.sh fail on ARM64 #278

geoff-vball opened this issue Feb 7, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@geoff-vball
Copy link
Contributor

geoff-vball commented Feb 7, 2024

logs.txt

Describe the bug
./scripts/local/run.sh fails intermittently when running on ARM64. This may be an issue with one of our dependencies.

To Reproduce
Run ./scripts/local/run.sh. run_setup.sh will sometimes fail when calling one of the instances of avalanche subnet deploy.

Expected behavior
The script should run normally without exiting.

Logs
Attached

Operating System
Mac ARM64

@geoff-vball geoff-vball added the bug Something isn't working label Feb 7, 2024
@geoff-vball geoff-vball self-assigned this Feb 7, 2024
@geoff-vball geoff-vball changed the title [Bug]: Subsequent runs of run.sh fail on ARM64git [Bug]: Subsequent runs of run.sh fail on ARM64 Feb 8, 2024
@geoff-vball geoff-vball changed the title [Bug]: Subsequent runs of run.sh fail on ARM64 [Bug]: Some runs of run.sh fail on ARM64 Feb 14, 2024
@geoff-vball
Copy link
Contributor Author

After some investigation, it seems that run.sh does not succeed on every clean run, and the failures seem to be fairly random. I've updated the bug description to reflect this.

@geoff-vball geoff-vball removed their assignment Feb 14, 2024
@cam-schultz
Copy link
Contributor

It sounds like this is an avalanche-cli bug. Do you mind opening an issue in that repo and closing this one out?

@geoff-vball
Copy link
Contributor Author

@cam-schultz I'm actually getting Error: no RPC version found now on both systems when trying to import genesis. I'm pretty sure this is because avalanche-cli hasn't been updated to be compatible with subnet-evm v0.6.0-fuji. I'll wait until they update for Durango compatibility, and then reassess if this is still an issue.

@michaelkaplan13
Copy link
Collaborator

Closing this issue out since the local setup scripts are being removed in https://github.com/ava-labs/teleporter/pull/393/files in favor of the Avalanche CLI support

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done ✅
Development

No branches or pull requests

3 participants