It seems that the rawhide s390x builders hang in various different places, randomly:
https://koji.fedoraproject.org/koji/getfile?taskID=20584916&volume=DEFAU... (stuck at wcsmbs)
https://koji.fedoraproject.org/koji/getfile?taskID=20592419&volume=DEFAU... (stuck at symlink.list)
https://koji.fedoraproject.org/koji/getfile?taskID=20592419&volume=DEFAU... (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.
Thanks, Florian
On Tue, 18 Jul 2017 10:08:06 +0200 Florian Weimer fweimer@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=DEFAU... (stuck at wcsmbs)
https://koji.fedoraproject.org/koji/getfile?taskID=20592419&volume=DEFAU... (stuck at symlink.list)
https://koji.fedoraproject.org/koji/getfile?taskID=20592419&volume=DEFAU... (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
Dan
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 fweimer@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=DEFAU... (stuck at wcsmbs)
https://koji.fedoraproject.org/koji/getfile?taskID=20592419&volume=DEFAU... (stuck at symlink.list)
https://koji.fedoraproject.org/koji/getfile?taskID=20592419&volume=DEFAU... (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.
Zbyszek
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 fweimer@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=DEFAU... (stuck at wcsmbs)
https://koji.fedoraproject.org/koji/getfile?taskID=20592419&volume=DEFAU... (stuck at symlink.list)
https://koji.fedoraproject.org/koji/getfile?taskID=20592419&volume=DEFAU... (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)
On Tue, Jul 18, 2017 at 08:57:23AM -0700, Adam Williamson wrote:
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 fweimer@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=DEFAU... (stuck at wcsmbs)
https://koji.fedoraproject.org/koji/getfile?taskID=20592419&volume=DEFAU... (stuck at symlink.list)
https://koji.fedoraproject.org/koji/getfile?taskID=20592419&volume=DEFAU... (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)
From #fedora-admin:
15:50 < puiterwijk> nirik: so, on the s390x stuff: I feel like there's something wrong with the mainframe. Even pings within VMs on that same vhost I'm seeing RTT's of +3 seconds
:[
Zbyszek