rust-clap failed to build from source in Fedora rawhide/f35 https://koji.fedoraproject.org/koji/taskinfo?taskID=72496009 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild Please fix rust-clap at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, rust-clap will be orphaned. Before branching of Fedora 36, rust-clap will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
Created attachment 1808723 [details] build.log file build.log too big, will only attach last 32768 bytes
Created attachment 1808724 [details] root.log file root.log too big, will only attach last 32768 bytes
Created attachment 1808725 [details] state.log
This seems to be caused by either an LLVM or Rust bug that is encountered when compiling a massive number of doctests in parallel on i686: error: ran out of registers during register allocation LLVM ERROR: Cannot emit physreg copy instruction Couldn't compile the test.
I would call that an LLVM bug first, unless we find something specific that Rust is doing wrong.
Do you know if there's a way to limit parallelism for building doctests? It seems like rustdoc does not limit the number of compile tasks it launches in parallel at all, which might contribute to this issue.
The parallelism should default to the number of logical cpus, but you can set RUST_TEST_THREADS=1 (or any number).
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
Ok ... I ran a scratch build with RUST_TEST_THREADS=1, and the i686 issue is still the same: https://koji.fedoraproject.org/koji/taskinfo?taskID=73671680 ---- src/build/arg_group.rs - build::arg_group::ArgGroup::arg (line 119) stdout ---- error: ran out of registers during register allocation LLVM ERROR: Cannot emit physreg copy instruction Couldn't compile the test. Not sure how LLVM would ever run out of registers during code generation ...
FEDORA-2021-d30f9d81fe has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-1937205ae5 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-1937205ae5
FEDORA-2021-b9e6038b3b has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-b9e6038b3b
FEDORA-2021-1937205ae5 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 --advisory=FEDORA-2021-1937205ae5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-1937205ae5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-b9e6038b3b has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-b9e6038b3b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-b9e6038b3b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-1937205ae5 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-b9e6038b3b has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.