From: Mark Wielaard <mark@klomp.org>
To: Tom de Vries <tdevries@suse.de>, dwz@sourceware.org
Cc: "Dan Horák" <dhorak@redhat.com>
Subject: Re: buildbot exception on dwz-fedora-s390x
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <6399295bf29e98c300786af00ec591dd29d703cb.camel@klomp.org> (raw)
In-Reply-To: <ebdff36a-3ce7-bd78-dc5b-750149e87b1b@suse.de>
Hi,
CCed Dan, who maintains the machine where the dwz-fedora-s390x buildbot
worker runs.
On Tue, 2019-07-02 at 15:53 +0200, Tom de Vries wrote:
> I noticed a "purple" build:
> https://builder.wildebeest.org/buildbot/#/builders/25/builds/77 .
> Apparently some exception happened during git checkout.
I logged in the machine and it seems there is something wrong with the
file system. Various processes dealing with files just hang waiting on
simple things like creating or deleting a file.
Dan, this is on lfedora1.lf-dev.marist.edu. Could you take a look?
Thanks,
Mark
next prev parent reply other threads:[~2019-07-02 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Tom de Vries
2019-01-01 0:00 ` Mark Wielaard [this message]
2019-01-01 0:00 ` Dan Horák
2019-01-01 0:00 ` Dan Horák
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Tom de Vries
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=6399295bf29e98c300786af00ec591dd29d703cb.camel@klomp.org \
--to=mark@klomp.org \
--cc=dhorak@redhat.com \
--cc=dwz@sourceware.org \
--cc=tdevries@suse.de \
/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).