-
Notifications
You must be signed in to change notification settings - Fork 17
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
feat: dedockerize nodes #319
Conversation
…at/dedockerize-node
…at/dedockerize-node
Terraform Feature Environment (dev-319)Terraform Initialization ⚙️
|
Nice! Any reason to invoke the binary instead of just spawning a thread that use mpc code directly? |
@itegulov mainly because we can then control the profile of the binary. Like, if we were to run integration tests as-is, it would use a singular performance profile depending on what we invoked the integration tests with |
a14ea70
to
8ca535a
Compare
I have pushed a commit into your branch that makes this setup work on my Linux machine. For some reason spawned processes treat |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just two nitpicks
Also, this takes <60 seconds to run all of the integration tests on my machine which is awesome |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work @ChaoticTempest ! This change should make our development iterations faster and allow FE Integration tests to be built easily.
…covery into phuong/feat/dedockerize-node
Terraform Feature Environment Destroy (dev-319)Terraform Initialization ⚙️
|
Dedockerizes leader and signer nodes for local testing. Allows for incremental compilation without having to wait on docker builds.
New steps to run tests:
cargo build --release RUST_LOG=info cargo test -p mpc-recovery-integration-tests
Setup all nodes:
output: