-
Notifications
You must be signed in to change notification settings - Fork 248
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
Run Cargo test failed in location #337
Comments
In order to run the tests, you need to have a suitable substrate binary available on your PATH. It looks like that isn't the case here :) |
I want to know if it is possible to use polkadot directly? |
I believe (as I've been experimenting with this today) that the latest polkadot binary you can grab is not quite as uptodate as the latest substrate binary we use for CI, and so at the moment you'd need to have a recent substrate binary (we use https://releases.parity.io/substrate/x86_64-debian:stretch/latest/substrate/substrate at the mo) to run the integration tests locally :) |
sandly, my local use is an Apple computer |
Likewise; that shouldn't prevent you from installing Substrate :) this guide (paying special attention to the macOS specific bits as needed) should get you going: https://docs.substrate.io/v3/getting-started/installation/ |
This I know, you can't use the substrate binary provided by btw, I encountered this problem and I wonder if you know exactly where the problem is ? |
I'm sorry, I don't quite follow! The error reported in this issue is hit specifically in the To summarize; you must have a working (recent) |
I see what you mean, it has to be a substrate executable binary file. I have one more such mistake(https://github.com/DaviRain-Su/example-subxt) here I don't know, are you clear? |
Yup, you got it! I'll close this now, and we can comment on your other issue separately :) |
The text was updated successfully, but these errors were encountered: