On Mon, Nov 29, 2021 at 07:36:30AM -0500, Kaleb Keithley wrote:
This seems to be happening on a semi-regular basis now. I run
scratch
builds and they invariably work, but I have seen at least one of my scratch
builds fail with the same error on f36/rawhide.
This makes no sense that gcc gets an internal error on random occastions.
Is it the machine (or vm) that it's running on?
---------- Forwarded message ---------
From: <notifications(a)fedoraproject.org>
Date: Fri, Nov 26, 2021 at 1:07 AM
Subject: ceph's builds started to fail in Fedora 35
To: <kkeithle(a)redhat.com>
Notification time stamped 2021-11-26 06:06:34 UTC
ceph's builds started to fail in Fedora 35
https://apps.fedoraproject.org/koschei/package/ceph?collection=f35
THe most recent failure here is
https://kojipkgs.fedoraproject.org/work/tasks/9266/79389266/build.log
with an error
[quote]
*** WARNING *** there are active plugins, do not report this as a bug unless you can
reproduce it without enabling any plugins.
Event | Plugins
PLUGIN_FINISH_UNIT | annobin: Generate final annotations
PLUGIN_START_UNIT | annobin: Generate global annotations
PLUGIN_ALL_PASSES_START | annobin: Generate per-function annotations
PLUGIN_ALL_PASSES_END | annobin: Register per-function end symbols
during RTL pass: reload
/builddir/build/BUILD/ceph-16.2.6/src/os/bluestore/BlueStore.cc: In member function
'void BlueStore::_kv_sync_thread()':
/builddir/build/BUILD/ceph-16.2.6/src/os/bluestore/BlueStore.cc:12280:1: internal compiler
error: maximum number of generated reload insns per insn achieved (90)
12280 | }
| ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <
http://bugzilla.redhat.com/bugzilla> for instructions.
Preprocessed source stored into /tmp/ccyafRbB.out file, please attach this to your
bugreport.
[/quote]
I'd suggest filing a bug against GCC IN Fedora. The GCC maintainers are
typically quick to respond and help diagnose such issues.
I note that where it started failing saw a systemtap rebase. This is a
bit of a flag for me, because last week we saw glusterfs builds start
failing with internal compiler errors due this systemtap rebase. That
was in arm7, while your failures are x86, but still makes me wonder
if your build problems go away if you test with disabled systemtap
Regards,
Daniel
--
|:
https://berrange.com -o-
https://www.flickr.com/photos/dberrange :|
|:
https://libvirt.org -o-
https://fstop138.berrange.com :|
|:
https://entangle-photo.org -o-
https://www.instagram.com/dberrange :|