From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: [ANNOUNCE] xfs-linux: for-next *rebased* to 73d30d48749f
Date: Mon, 1 Jul 2019 01:49:45 -0700 [thread overview]
Message-ID: <20190701084945.GA1356@infradead.org> (raw)
In-Reply-To: <20190630163404.GG1404256@magnolia>
On Sun, Jun 30, 2019 at 09:34:04AM -0700, Darrick J. Wong wrote:
> **NOTE** I discovered while bisecting the previous for-next that I
> introduced a build failure in "xfs: move xfs_ino_geometry to xfs_shared.h"
> that I hadn't noticed because apparently 0day doesn't do commit by
> commit build tests anymore? (Frankly, it doesn't tell me /anything/
> unless it finds failures, so I think I'm not going to rely on cloud
> kernel build tests anymore.)
The buildbot doesn't seem to work at all basically. Once it a while
it reports occasional errors for week old trees, but otherwise it
stays entirely silent, even for completely b0rked trees. I've been
bitten by this more than once in the last weeks.
prev parent reply other threads:[~2019-07-01 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-30 16:34 [ANNOUNCE] xfs-linux: for-next *rebased* to 73d30d48749f Darrick J. Wong
2019-07-01 8:49 ` Christoph Hellwig [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=20190701084945.GA1356@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.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