From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: Breakage on builder Fedora-s390x-m64, revision b392b304b92ddd81ecfb4902c3fc3501ff90e999
Date: Mon, 30 Oct 2017 15:34:00 -0000 [thread overview]
Message-ID: <87tvygejjh.fsf@redhat.com> (raw)
In-Reply-To: <1509003358.10879.13.camel@klomp.org> (Mark Wielaard's message of "Thu, 26 Oct 2017 09:35:58 +0200")
On Thursday, October 26 2017, Mark Wielaard wrote:
> On Wed, 2017-10-25 at 18:44 -0400, Sergio Durigan Junior wrote:
>> On Saturday, October 21 2017, Simon Marchi wrote:
>> > The s390 builder has no space left (see below). Can you reach to
>> > the owner of that machine?
>>
>> Thanks for the heads up, Simon.
>>
>> Mark, could you please take a look?
>
> Over the weekend /var/tmp filled up through some other process running
> on the machine. It has been cleaned up and we'll look at why the tmp
> cleaner didn't. /dev/mapper/Fedora-Root 64G 37G 25G 61% /
> Please let me know if you have seen failures after last weekend.
Thanks!
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
prev parent reply other threads:[~2017-10-30 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-21 14:36 Oh dear. I regret to inform you that commit b392b304b92ddd81ecfb4902c3fc3501ff90e999 might be unfortunate gdb-buildbot
2017-10-21 14:36 ` Breakage on builder Fedora-s390x-m64, revision b392b304b92ddd81ecfb4902c3fc3501ff90e999 gdb-buildbot
2017-10-21 14:46 ` Simon Marchi
2017-10-25 22:44 ` Sergio Durigan Junior
2017-10-26 7:36 ` Mark Wielaard
2017-10-30 15:34 ` Sergio Durigan Junior [this message]
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=87tvygejjh.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=mark@klomp.org \
--cc=simon.marchi@polymtl.ca \
/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