dwz build for fedora-ppc64 failed with 'worker not pinged'

public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed

* dwz build for fedora-ppc64 failed with 'worker not pinged'
@ 2019-01-01  0:00 Tom de Vries
  2019-01-01  0:00 ` Mark Wielaard
  0 siblings, 1 reply; 2+ messages in thread
From: Tom de Vries @ 2019-01-01  0:00 UTC (permalink / raw)
  To: Mark Wielaard; +Cc: dwz

Hi Mark,

dwz build
https://builder.wildebeest.org/buildbot/#/builders/22/builds/132 failed
with:
...
worker not pinged
...

Could you retry?

Thanks,
- Tom

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: dwz build for fedora-ppc64 failed with 'worker not pinged'
  2019-01-01  0:00 dwz build for fedora-ppc64 failed with 'worker not pinged' Tom de Vries
@ 2019-01-01  0:00 ` Mark Wielaard
  0 siblings, 0 replies; 2+ messages in thread
From: Mark Wielaard @ 2019-01-01  0:00 UTC (permalink / raw)
  To: Tom de Vries; +Cc: dwz

Hi Tom,

On Mon, 2019-11-25 at 07:19 +0100, Tom de Vries wrote:
> dwz build
> https://builder.wildebeest.org/buildbot/#/builders/22/builds/132
> failed
> with:
> ...
> worker not pinged
> ...
> 
> Could you retry?

It is already in the queue to be retried together with some other
builds: https://builder.wildebeest.org/buildbot/#/pendingbuildrequests
The worker lost ipv4 connectivity. As soon as it is restored it should
process the pending builds. I don't know how long that will take
though. I'll ping the administrator again.

Cheers,

Mark

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-11-25  9:49 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-01  0:00 dwz build for fedora-ppc64 failed with 'worker not pinged' Tom de Vries
2019-01-01  0:00 ` Mark Wielaard

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).