On Thu, Mar 19, 2020 at 01:01:05PM +0100, Sumit Bose wrote: > On Thu, Mar 19, 2020 at 08:37:31AM +0000, Richard W.M. Jones wrote: > > On Wed, Mar 18, 2020 at 11:39:37AM +0100, Dan Horák wrote: > > > On Wed, 18 Mar 2020 09:50:24 +0000 > > > "Richard W.M. Jones" <rjones@xxxxxxxxxx> wrote: > > > > > > > On Wed, Mar 18, 2020 at 10:46:19AM +0100, Dan Horák wrote: > > > > > On Wed, 18 Mar 2020 09:34:45 +0000 > > > > > "Richard W.M. Jones" <rjones@xxxxxxxxxx> wrote: > > > > > > > > > > > > > > > > > This might be a bug in the package itself, but has anyone seen > > > > > > builds hanging in weird places, in Rawhide, especially on armv7 > > > > > > and s390x? > > > > > > > > > > > > This packge build has hung 3 times in the same place, once on > > > > > > armv7 and twice on s390x: > > > > > > > > > > > > https://koji.fedoraproject.org/koji/taskinfo?taskID=42570766 > > > > > > > > > > > > It's hard to explain how it could hang at that place in the build > > > > > > unless something fundamental is broken like make. > > > > > > > > > > let me try the rebuild locally on s390x ... > > > > > > > > Note that the build did succeed once on s390x (that was when it hung > > > > on armv7 instead). So it's not 100% reproducible. Also if our theory > > > > about tooling is correct then you would need all Rawhide packages. > > > > > > it's a deadlock in the tests, not in make. Reproduced with > > > "fedpkg local" in a cycle. > > > > > > sharkcz 1649225 0.0 0.0 222288 3904 pts/5 S+ 06:24 0:00 /bin/sh -e /var/tmp/rpm-tmp.RXcMRr > > > sharkcz 1649230 0.0 0.0 10372 3248 pts/5 S+ 06:24 0:00 make -j4 check > > > sharkcz 1658088 0.0 0.0 251236 3400 pts/5 Sl+ 06:25 0:00 /home/sharkcz/nbdkit/nbdkit-1.19.3/server/nbdkit -v -P test-nbd-tls-psk.pid1 -U /tmp/tmp.7e7Gv5MPmZ --tls=require --tls-psk=keys.psk -- /home/sharkcz/nbdkit/nbdkit-1.19.3/plugins/example1/.libs/nbdkit-example1-plugin.so > > > sharkcz 1658091 0.0 0.1 192944 4464 pts/5 Sl+ 06:25 0:00 /home/sharkcz/nbdkit/nbdkit-1.19.3/server/nbdkit -v -P test-nbd-tls-psk.pid2 -U /tmp/tmp.yp61yXx09y --tls=off -- /home/sharkcz/nbdkit/nbdkit-1.19.3/plugins/nbd/.libs/nbdkit-nbd-plugin.so tls=require tls-psk=keys.psk tls-username=qemu socket=/tmp/tmp.7e7Gv5MPmZ > > > > > > the 2 nbdkit processes are stuck in the futex() syscall > > > > > > Some years ago there was a kernel bug with the same symptoms. All > > > arches were affected, but mostly visible on s390x and armv7. > > > > In fact this happens on x86-64. I was able to reproduce it > > locally. Investigating now. > > Hi, > > jfiy, I have two builds with similar behavior as well: > > - https://koji.fedoraproject.org/koji/taskinfo?taskID=42581593 f33 i686 > - https://koji.fedoraproject.org/koji/taskinfo?taskID=42600523 f32 aarch64 > > both are stuck in tests. Trying to reproduce locally. It seems like if your test leaves any subprocesses around after the test it will now hang, whereas before it would have continued (albeit leaving orphaned processes which is bad behaviour). Not sure exactly what changed here, maybe make or rpmbuild? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
