could not compile `minify-html-common` (lib) #1

New issue

Closed

opened 2024-02-14 08:23:58 +00:00 by Tealk · 4 comments

Tealk commented

2024-02-14 08:23:58 +00:00

With the latest version v0.3.109 I get the following error when updating from v0.3.108 to v0.3.109. I update with cargo install-update -a

error: could not compile `minify-html-common` (lib)

Caused by:
  process didn't exit successfully: `/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc --crate-name minify_html_common --edition=2018 /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/minify-html-common-0.0.2/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --diagnostic-width=120 --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C metadata=5095d2e39b7edd23 -C extra-filename=-5095d2e39b7edd23 --out-dir /tmp/cargo-installQp0qC2/release/deps -L dependency=/tmp/cargo-installQp0qC2/release/deps --extern aho_corasick=/tmp/cargo-installQp0qC2/release/deps/libaho_corasick-f7a038e16c9c3a33.rmeta --extern lazy_static=/tmp/cargo-installQp0qC2/release/deps/liblazy_static-34117be0656d202f.rmeta --extern memchr=/tmp/cargo-installQp0qC2/release/deps/libmemchr-be5b85c1382ece6e.rmeta --extern rustc_hash=/tmp/cargo-installQp0qC2/release/deps/librustc_hash-e62c5ae08358c271.rmeta --cap-lints allow` (signal: 9, SIGKILL: kill)
warning: build failed, waiting for other jobs to finish...
error: failed to compile `ap-relay v0.3.109`, intermediate artifacts can be found at `/tmp/cargo-installQp0qC2`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

With the latest version `v0.3.109` I get the following error when updating from `v0.3.108` to `v0.3.109`. I update with `cargo install-update -a` ``` error: could not compile `minify-html-common` (lib) Caused by: process didn't exit successfully: `/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc --crate-name minify_html_common --edition=2018 /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/minify-html-common-0.0.2/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --diagnostic-width=120 --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C metadata=5095d2e39b7edd23 -C extra-filename=-5095d2e39b7edd23 --out-dir /tmp/cargo-installQp0qC2/release/deps -L dependency=/tmp/cargo-installQp0qC2/release/deps --extern aho_corasick=/tmp/cargo-installQp0qC2/release/deps/libaho_corasick-f7a038e16c9c3a33.rmeta --extern lazy_static=/tmp/cargo-installQp0qC2/release/deps/liblazy_static-34117be0656d202f.rmeta --extern memchr=/tmp/cargo-installQp0qC2/release/deps/libmemchr-be5b85c1382ece6e.rmeta --extern rustc_hash=/tmp/cargo-installQp0qC2/release/deps/librustc_hash-e62c5ae08358c271.rmeta --cap-lints allow` (signal: 9, SIGKILL: kill) warning: build failed, waiting for other jobs to finish... error: failed to compile `ap-relay v0.3.109`, intermediate artifacts can be found at `/tmp/cargo-installQp0qC2`. To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path. ```

asonix commented

2024-02-14 16:34:41 +00:00

Owner

what version of rust do you have installed?

Tealk commented

2024-03-18 15:39:10 +00:00

Author

Sorry for the late reply, rustc 1.76.0 (07dca489a 2024-02-04)

asonix commented

2024-03-24 00:03:16 +00:00

Owner

looking at that error again, it looks like rustc is getting killed. I wonder if this is a OOM issue on your box

looking at that error again, it looks like `rustc` is getting killed. I wonder if this is a OOM issue on your box

Tealk commented

2024-03-24 09:24:25 +00:00

Author

nothing is different on the vm than the relay, somehow it consumes an extreme amount of ram?
Also updating seems to need more ram now than the last time.

here is the graph from the vm:

i increased the ram by 1gb and restarted the server, hence the ram drop.

apparently i have to restart the server before the update works?

nothing is different on the vm than the relay, somehow it consumes an extreme amount of ram? Also updating seems to need more ram now than the last time. here is the graph from the vm: ![image](/attachments/5296fdec-d660-4af3-a48c-986891ab618b) i increased the ram by 1gb and restarted the server, hence the ram drop. apparently i have to restart the server before the update works?

image.png

40 KiB

image.png

108 KiB