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

process didn't exit successfully #13

Closed
Artim96 opened this issue Jun 6, 2024 · 5 comments
Closed

process didn't exit successfully #13

Artim96 opened this issue Jun 6, 2024 · 5 comments

Comments

@Artim96
Copy link

Artim96 commented Jun 6, 2024

I'm trying to compile the deb again in a Debian Stable VM, as I originally compiled it on Testing, but that won't be able to run on a Stable system. But the Stable systm doesn't have enough space for compiling. I've installed everything needed, including both the rust 1.78 toolchain via rustup and cargo (and with that the rust toolchain of Stable). For some reason toolchain 1.76 is being installed by the script (either by it or vaultwarden), but compilation fails with this message:
Screenshot from 2024-06-06 11-16-49

@dionysius
Copy link
Owner

dionysius commented Jun 6, 2024

I see SIGKILL in your message. Something is killing the build process from outside. Is that a container or VM? Have a look into the /var/log/kern.log on your host system. Probably OOM (out-of-memory)

@dionysius
Copy link
Owner

dionysius commented Jun 6, 2024

Oh, and 1.76 is used because https://github.com/dani-garcia/vaultwarden/blob/1.30.5/rust-toolchain.toml describes it. rustup handles this autonomously. But since the --locked fix from #12 this should not be an issue to build with 1.76, cargo will use the dependencies references by version as defined in the lock file https://github.com/dani-garcia/vaultwarden/blob/1.30.5/Cargo.lock

@dionysius
Copy link
Owner

dionysius commented Jun 6, 2024

Building this locally on my laptop (with other tools open and full desktop environment) the full system memory usage peaked at 19.2GB. There are several issues in cargo addressing memory issues, e.g.: rust-lang/cargo#12912

@Artim96
Copy link
Author

Artim96 commented Jun 6, 2024

Right, compiling diesel_migrations and building the packages takes up loads of memory. In a VirtualBox VM on a very basic install from Debian Netinstall, it used 14.7 GB of memory (measured by GNU time). Was confused that compiling on an 8 GB machine on the other hand wasn't a problem. But loads of swap space does that for you.

@Artim96
Copy link
Author

Artim96 commented Jun 6, 2024

Do this is done now

@Artim96 Artim96 closed this as completed Jun 6, 2024
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