On Tue, Feb 18, 2020 at 06:46:05PM -0500, Orcan Ogetbil wrote:
In an effort to update the fluidsynth library version, which comes
with a soname bump, in rawhide (F33) I created a side tag
f33-build-side-19396. All but one dependent packages are rebuilt. The
last dependent is the muse package.
I tried to rebuild muse in the side tag three times. In all of the
attempts the i686 target build gets stalled at the end of %build. Here
is the latest build, which still ongoing for 18 hours as I'm writing
this email:
https://koji.fedoraproject.org/koji/taskinfo?taskID=41579850
As a comparison, the slowest builder (s390x) finishes the build in
about 15 minutes.
How do I debug this? Where to file a ticket?
Well, if you just want info on what the builder is stuck on, an
infrastructure ticket.
Since I am already here:
It seems to be using 100% of 1 cpu running:
kojibui+ 3203495 99.3 2.4 388244 372724 ? R Feb18 1127:51
/usr/libexec/gcc/i686-redhat-linux/10/cc1plus -quiet -I
/builddir/build/BUILD/muse-3.0.2/i686-redhat-linux-gnu/synti/deicsonze....<lots
more snipped>
| `-rpmbuild,3201583 -bb --target i686 --nodeps
/builddir/build/SPECS/muse.spec
| `-sh,3201611 -e /var/tmp/rpm-tmp.cEJyaS
| `-make,3201975 -j6
| `-make,3201978 -f CMakeFiles/Makefile2 all
| `-make,3203442 -f
synti/deicsonze/CMakeFiles/deicsonze.dir/build.make ...
| `-c++,3203494 -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG
-DQT_SVG_LIB -DQT_UITOOLS_LIB ..
.
| |-cc1plus,3203495 -quiet -I ...
| `-as,3203496 -I
/builddir/build/BUILD/muse-3.0.2/i686-redhat-linux-gnu/synti/deicso
nze -I ...
strace of that process doesn't show anything happening.
Looking at open files:
...
lr-x------. 1 kojibuilder mock 64 Feb 19 00:37 11 ->
/var/lib/mock/f33-build-side-19396-19429711-1367041/root/usr/include
/c++/10/bits/std_function.h
lr-x------. 1 kojibuilder mock 64 Feb 19 00:37 12 ->
/var/lib/mock/f33-build-side-19396-19429711-1367041/root/usr/include
/qt5/QtCore/qmap.h
lr-x------. 1 kojibuilder mock 64 Feb 19 00:37 13 ->
/var/lib/mock/f33-build-side-19396-19429711-1367041/root/usr/include
/qt5/QtCore/qvariant.h
lr-x------. 1 kojibuilder mock 64 Feb 19 00:37 14 ->
/var/lib/mock/f33-build-side-19396-19429711-1367041/root/usr/include
/qt5/QtCore/qset.h
lr-x------. 1 kojibuilder mock 64 Feb 19 00:37 15 ->
/var/lib/mock/f33-build-side-19396-19429711-1367041/root/builddir/bu
ild/BUILD/muse-3.0.2/muse/memory.h
lr-x------. 1 kojibuilder mock 64 Feb 19 00:37 16 ->
/var/lib/mock/f33-build-side-19396-19429711-1367041/root/builddir/bu
ild/BUILD/muse-3.0.2/muse/evdata.h
lr-x------. 1 kojibuilder mock 64 Feb 19 00:37 17 ->
/var/lib/mock/f33-build-side-19396-19429711-1367041/root/builddir/bu
ild/BUILD/muse-3.0.2/muse/mpevent.h
lr-x------. 1 kojibuilder mock 64 Feb 19 00:37 18 ->
/var/lib/mock/f33-build-side-19396-19429711-1367041/root/builddir/bu
ild/BUILD/muse-3.0.2/synti/libsimpleplugin/simpler_plugin.h
lr-x------. 1 kojibuilder mock 64 Feb 19 00:37 19 ->
/var/lib/mock/f33-build-side-19396-19429711-1367041/root/usr/include
/qt5/QtWidgets/qstyleoption.h
lr-x------. 1 kojibuilder mock 64 Feb 19 00:37 20 ->
/var/lib/mock/f33-build-side-19396-19429711-1367041/root/usr/include
/qt5/QtGui/qtextformat.h
I wonder if it's some kind of loop in qt5 headers?
So, I'd say try and duplicate it in a i686 mock chroot on a x86_64
machine and see if you can gather enough info for a c++ or qt5 bug.
Hope that helps.
kevin