Description of problem: I'm not sure if that's the correct component co please move if I did that wrong. Firefox fails to build on Rawhide/s390x bacuse cargo crashes during build: https://koji.fedoraproject.org/koji/taskinfo?taskID=55048351 Failing line: process didn't exit successfully: `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=gkrust CARGO_MANIFEST_DIR=/builddir/build/BUILD/firefox-82.0.2/toolkit/library/rust CARGO_PKG_AUTHORS='nobody' CARGO_PKG_DESCRIPTION='Rust code for libxul' CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE=MPL-2.0 CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=gkrust CARGO_PKG_REPOSITORY='' CARGO_PKG_VERSION=0.1.0 CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=1 CARGO_PKG_VERSION_PATCH=0 CARGO_PKG_VERSION_PRE='' LD_LIBRARY_PATH='/builddir/build/BUILD/firefox-82.0.2/objdir/release/deps:/usr/lib' /usr/bin/rustc --crate-name gkrust toolkit/library/rust/lib.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type staticlib --emit=dep-info,link -C opt-level=2 -C panic=abort -C embed-bitcode=no -Clto --cfg 'feature="cubeb-remoting"' --cfg 'feature="cubeb_pulse_rust"' --cfg 'feature="moz_places"' --cfg 'feature="new_cert_storage"' --cfg 'feature="quantum_render"' --cfg 'feature="webgpu"' --cfg 'feature="with_dbus"' -C metadata=82c8699045b9adf1 -C extra-filename=-82c8699045b9adf1 --out-dir /builddir/build/BUILD/firefox-82.0.2/objdir/s390x-unknown-linux-gnu/release/deps --target s390x-unknown-linux-gnu -C linker=/builddir/build/BUILD/firefox-82.0.2/build/cargo-linker -L dependency=/builddir/build/BUILD/firefox-82.0.2/objdir/s390x-unknown-linux-gnu/release/deps -L dependency=/builddir/build/BUILD/firefox-82.0.2/objdir/release/deps --extern gkrust_shared=/builddir/build/BUILD/firefox-82.0.2/objdir/s390x-unknown-linux-gnu/release/deps/libgkrust_shared-6f65635a7eb0bdf8.rlib --extern mozglue_static=/builddir/build/BUILD/firefox-82.0.2/objdir/s390x-unknown-linux-gnu/release/deps/libmozglue_static-f4fdef0d5cf497ad.rlib --extern mozilla_central_workspace_hack=/builddir/build/BUILD/firefox-82.0.2/objdir/s390x-unknown-linux-gnu/release/deps/libmozilla_central_workspace_hack-95a2c516c70ae1b7.rlib --extern swgl=/builddir/build/BUILD/firefox-82.0.2/objdir/s390x-unknown-linux-gnu/release/deps/libswgl-f3d262d0a6f17004.rlib -C opt-level=2 -C debuginfo=2 --cap-lints warn -Cembed-bitcode=yes -C codegen-units=1 -L native=/usr/lib64 -L native=/builddir/build/BUILD/firefox-82.0.2/objdir/s390x-unknown-linux-gnu/release/build/lmdb-rkv-sys-cb7360ee56ba0ec9/out -L native=/builddir/build/BUILD/firefox-82.0.2/objdir/s390x-unknown-linux-gnu/release/build/mozglue-static-773c8acab37a8f80/out -L native=/builddir/build/BUILD/firefox-82.0.2/objdir/dist/bin -L native=/builddir/build/BUILD/firefox-82.0.2/objdir/security/nss/lib/nss/nss_nss3 -L native=/builddir/build/BUILD/firefox-82.0.2/objdir/security/nss/lib/ssl/ssl_ssl3 -L native=/builddir/build/BUILD/firefox-82.0.2/objdir/config/external/nspr/pr -L native=/builddir/build/BUILD/firefox-82.0.2/objdir/s390x-unknown-linux-gnu/release/build/swgl-f76defdb27e1004b/out` (signal: 9, SIGKILL: kill) Build details:
This looks like it could be an Out-Of-Memory failure. Can you retry with parallel builds disabled?
(In reply to Martin Stransky from comment #0) > I'm not sure if that's the correct component co please move if I did that wrong. The rust-cargo package is for cargo used as a crate/library within other programs. The binary cargo tool itself is part of the rust package, and anyway it was rustc that actually crashed here. Reassigned to rust, though it may be LLVM too. But I agree with Tom -- SIGKILL is almost always OOM. The builders for s390x are often poor in memory, although yours had 10GB which isn't so bad. I think the most likely culprit is LTO combined with debuginfo -- the entire gkrust with dependencies will be codegen'ed in one process.
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.
FEDORA-2022-74ff7f9e74 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-74ff7f9e74
FEDORA-2022-02d2625a01 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-02d2625a01
FEDORA-2022-ee0d54e824 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-ee0d54e824
FEDORA-2022-74ff7f9e74 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-74ff7f9e74` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-74ff7f9e74 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-02d2625a01 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-ee0d54e824 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-ee0d54e824` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ee0d54e824 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-ee0d54e824 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-74ff7f9e74 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.