From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: Mark Wielaard <mark@klomp.org>
Cc: buildbot@sourceware.org
Subject: Re: [builder@sourceware.org: Buildbot Sourceware worker debian-ppc64 missing]
Date: Sat, 04 Feb 2023 20:00:41 -0500 [thread overview]
Message-ID: <m3v8khylhi.fsf@fitzsim.org> (raw)
In-Reply-To: <20230131203819.GI11361@gnu.wildebeest.org> (Mark Wielaard's message of "Tue, 31 Jan 2023 21:38:19 +0100")
Hi Mark,
Thanks for the message; it is back online now.
On Tuesday, January 31st, at approximately 2PM EST, a road work crew cut
through all my neighbourhood's fibre links. This resulted in a four day
Internet outage, with service finally being restored sometime this
afternoon.
I'll keep an eye on builder.sourceware.org while the debian-ppc64 worker
tries to catch up.
Thomas
Mark Wielaard <mark@klomp.org> writes:
> Hi Tom,
>
> We had a network and host upgrade today that made
> builder.sourceware.org unreachable for a couple of hour. Afterwards
> all buildbot workers did come back, except for the debian-ppc64
> one. Could you see if it is stuck on something?
>
> Thanks,
>
> Mark
>
> From: builder@sourceware.org
> Subject: Buildbot Sourceware worker debian-ppc64 missing
> Date: Tue, 31 Jan 2023 19:58:00 +0000 (4 days, 4 hours, 54 minutes ago)
>
> The Buildbot worker named debian-ppc64 went away.
>
> It last disconnected at Tue Jan 31 18:58:00 2023.
>
> The admin on record (as reported by WORKER:info/admin) was Mark Wielaard .
>
> ----------
parent reply other threads:[~2023-02-05 13:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230131203819.GI11361@gnu.wildebeest.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3v8khylhi.fsf@fitzsim.org \
--to=fitzsim@fitzsim.org \
--cc=buildbot@sourceware.org \
--cc=mark@klomp.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).