From: Kalle Valo <kvalo@codeaurora.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Philip Li <philip.li@intel.com>,
Zhengjun Xing <zhengjun.xing@linux.intel.com>,
Liu Yiding <yidingx.liu@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: buildbot status?
Date: Sun, 30 Jun 2019 12:51:54 +0300 [thread overview]
Message-ID: <87h887qu2t.fsf@codeaurora.org> (raw)
In-Reply-To: <20190628142859.GA4844@lst.de> (Christoph Hellwig's message of "Fri, 28 Jun 2019 16:28:59 +0200")
Christoph Hellwig <hch@lst.de> writes:
> Hi buildbot maintainers,
>
> lately I usually get no, in some case a few very delayed build bot
> results for my repos. Is this as known issue?
I have the same problem, I did receive few reports on Wednesday but
nothing after that. I rely a lot for buildbot doing build checks on
wireless-drivers patches so I hope it comes back soon.
--
Kalle Valo
next prev parent reply other threads:[~2019-06-30 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 14:28 buildbot status? Christoph Hellwig
2019-06-30 9:51 ` Kalle Valo [this message]
2019-06-30 13:49 ` Philip Li
2019-07-02 10:00 ` Rong Chen
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=87h887qu2t.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=philip.li@intel.com \
--cc=yidingx.liu@intel.com \
--cc=zhengjun.xing@linux.intel.com \
/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