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

Fix tests for multisig, staking-pool and staking-pool-factory #165

Open
3 tasks
telezhnaya opened this issue Jul 12, 2021 · 1 comment
Open
3 tasks

Fix tests for multisig, staking-pool and staking-pool-factory #165

telezhnaya opened this issue Jul 12, 2021 · 1 comment

Comments

@telezhnaya
Copy link
Contributor

telezhnaya commented Jul 12, 2021

cargo test is broken for:

  • multisig
  • staking-pool
  • staking-pool-factory

The CI is switched off for these contracts. It is switched on only for this list https://github.com/near/core-contracts/blob/master/scripts/contracts.json

@evgenykuzyakov could you please help with this?

@mikedotexe
Copy link
Contributor

Just FYI, I was looking into similar tests and found that a culprit was the rust-toolchain file.
I was updating a contract to a newer version and it would look "up" a directory and find the toolchain file and use that.
This is not a solution, but the way I got around it was to do cargo +stable test -- --nocapture

I think the better solution is to follow what we did with near-sdk-rs where we have Docker build them.
https://github.com/near/near-sdk-rs/blob/15c63cde9e08c242e9d26bb5e07991f51c13ff45/examples/build_all_docker.sh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants