Comment 2 for bug 2029926

Zixing, I belive you are misreading the logs and focusing on a failure that is actually ignored.

The actual failure seems to be

1273s process didn't exit successfully: `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=uom CARGO_MANIFEST_DIR=/usr/share/cargo/registry/uom-0.35.0 CARGO_PKG_AUTHORS='Mike Boutin <email address hidden>' CARGO_PKG_DESCRIPTION='Units of measurement' CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE=Apache-2.0/MIT CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=uom CARGO_PKG_README=README.md CARGO_PKG_REPOSITORY='https://github.com/iliekturtles/uom' CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.35.0 CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=35 CARGO_PKG_VERSION_PATCH=0 CARGO_PKG_VERSION_PRE='' CARGO_PRIMARY_PACKAGE=1 LD_LIBRARY_PATH='/tmp/tmp.AsoU5BAoAf/target/debug/deps:/usr/lib' rustc --crate-name uom --edition=2018 src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 --test --cfg 'feature="autoconvert"' --cfg 'feature="default"' --cfg 'feature="f32"' --cfg 'feature="f64"' --cfg 'feature="si"' --cfg 'feature="std"' -C metadata=e75d77c4414a8738 -C extra-filename=-e75d77c4414a8738 --out-dir /tmp/tmp.AsoU5BAoAf/target/powerpc64le-unknown-linux-gnu/debug/deps --target powerpc64le-unknown-linux-gnu -C incremental=/tmp/tmp.AsoU5BAoAf/target/powerpc64le-unknown-linux-gnu/debug/incremental -L dependency=/tmp/tmp.AsoU5BAoAf/target/powerpc64le-unknown-linux-gnu/debug/deps -L dependency=/tmp/tmp.AsoU5BAoAf/target/debug/deps --extern approx=/tmp/tmp.AsoU5BAoAf/target/powerpc64le-unknown-linux-gnu/debug/deps/libapprox-b74a64137042766a.rlib --extern num_traits=/tmp/tmp.AsoU5BAoAf/target/powerpc64le-unknown-linux-gnu/debug/deps/libnum_traits-072042e68199a6c6.rlib --extern quickcheck=/tmp/tmp.AsoU5BAoAf/target/powerpc64le-unknown-linux-gnu/debug/deps/libquickcheck-f211bc3c722912b1.rlib --extern serde_json=/tmp/tmp.AsoU5BAoAf/target/powerpc64le-unknown-linux-gnu/debug/deps/libserde_json-0391cf3843694cc1.rlib --extern static_assertions=/tmp/tmp.AsoU5BAoAf/target/powerpc64le-unknown-linux-gnu/debug/deps/libstatic_assertions-1319c5b4b478b1fe.rlib --extern typenum=/tmp/tmp.AsoU5BAoAf/target/powerpc64le-unknown-linux-gnu/debug/deps/libtypenum-849f673c1b973491.rlib -C debuginfo=2 --cap-lints warn -C linker=powerpc64le-linux-gnu-gcc -C link-arg=-Wl,-Bsymbolic-functions -C link-arg=-flto=auto -C link-arg=-ffat-lto-objects -C link-arg=-Wl,-z,relro --remap-path-prefix /usr/share/cargo/registry/uom-0.35.0=/usr/share/cargo/registry/uom-0.35.0 --remap-path-prefix /tmp/tmp.AsoU5BAoAf/registry=/usr/share/cargo/registry` (signal: 9, SIGKILL: kill)
1273s autopkgtest [10:01:00]: test librust-uom-dev:default: -----------------------]
1274s autopkgtest [10:01:01]: test librust-uom-dev:default: - - - - - - - - - - results - - - - - - - - - -
1274s librust-uom-dev:default FAIL non-zero exit status 101

and i'm seeing the same thing happen on arm64 as well.

My experiance is that when you see a SIGKILL in a build log it usually means the system ran out of memory and the OOM killer was triggered.