build single crate success, but build as whole workspace always failed caused by (signal: 9, SIGKILL: kill) #2425
-
For example, when I go into the directory of nautilus_trader/crates/adapters/tardis, and execute "cargo build" or "cargo test", the results are both successful.cargo test running 71 tests test result: ok. 71 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 173.64sBut when I execute "poetry install" on the parent path nautils_trader, it always fails by (signal: 9, SIGKILL: kill). I googled, and found there were similar problems that happened when some bugs would cause Rust compiler or something use all of the system memory and finally linux kernel kill the process. What should I do? I want to develop an adaptor that services in Japan stock market, but firstly I need to build it success in source code level. $cd nautilus_trader No dependencies to install or update Installing the current project: nautilus_trader (1.212.0)Preparing build environment with build-system requirements setuptools>=75, poetry-core>=2.0.1, numpy>=1.26.4, cython==3.1.0a1 =====================================================================
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Some additional info: When build crate persistence, "cargo build" is success, but "cargo test" is failed. cargo build nautilus_trader/crates/persistence$ cargo test Compiling nautilus-common v0.42.0 (/home/london/Develop/nautilus_trader/crates/common) error: could not compile error: could not compile |
Beta Was this translation helpful? Give feedback.
-
Did you manage to resolve this issue yet? |
Beta Was this translation helpful? Give feedback.
I figured it out.
My Linux runs on an 8-core Intel i5 CPU with 8G of memory. Rust uses all of them by default setting, which causes the issue.
To solve it, only add the below setting on .cargo/config.toml to limit resources.
[build]
jobs = 1