On Tue, 2017-07-18 at 14:47 +0000, Zbigniew Jędrzejewski-Szmek wrote: > On Tue, Jul 18, 2017 at 10:29:05AM +0200, Dan Horák wrote: > > On Tue, 18 Jul 2017 10:08:06 +0200 > > Florian Weimer <fwei...@redhat.com> wrote: > > > > > It seems that the rawhide s390x builders hang in various different > > > places, randomly: > > > > > > https://koji.fedoraproject.org/koji/getfile?taskID=20584916&volume=DEFAULT&name=build.log&offset=-4000 > > > (stuck at wcsmbs) > > > > > > https://koji.fedoraproject.org/koji/getfile?taskID=20592419&volume=DEFAULT&name=build.log&offset=-4000 > > > (stuck at symlink.list) > > > > > > https://koji.fedoraproject.org/koji/getfile?taskID=20592419&volume=DEFAULT&name=build.log&offset=-4000 > > > (stuck at PluginFrame_test) > > > > > > https://koji.fedoraproject.org/koji/taskinfo?taskID=20583725 > > > (stuck who knows where) > > > > > > I don't know if this is an issue with the mainframe, its storage, or > > > the Fedora kernel running on those builders (4.10.8-200.fc25.s390x > > > according to the glibc build log). Considering the wide variety of > > > affected packages and the randomness of the failure, I don't think > > > it's a packaging problem. > > > > yes, it's an infrastructure problem, > > buildvm-s390x-0{1,2,9,13}.s390.fedoraproject.org last reported to the > > hub at 23:14 UTC yesterday, I guess they carry the builds mentioned > > above > > I've had seemingly-random failures on > buildvm-s390x-0{10,11}.s390.fedoraproject.org > yesterday.
I also had a failure that didn't seem to be caused by anything wrong with the software or the package: https://koji.fedoraproject.org/koji/taskinfo?taskID=20586839 (a mariadb rebuild) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
