All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rong Chen <rong.a.chen@intel.com>
To: Philip Li <philip.li@intel.com>, Kalle Valo <kvalo@codeaurora.org>
Cc: Christoph Hellwig <hch@lst.de>,
	Zhengjun Xing <zhengjun.xing@linux.intel.com>,
	Liu Yiding <yidingx.liu@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: buildbot status?
Date: Tue, 2 Jul 2019 18:00:06 +0800	[thread overview]
Message-ID: <f5f5409b-eaca-d38c-bd31-c54ef69b3833@intel.com> (raw)
In-Reply-To: <20190630134944.GA22324@intel.com>

On 6/30/19 9:49 PM, Philip Li wrote:
> On Sun, Jun 30, 2019 at 12:51:54PM +0300, Kalle Valo wrote:
>> 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.
> hi Kalle and Christoph, sorry for inconvenience. We will check this as
> early as possible which may be due to certain issue in our side. +Rong
> to help check the exact problem.

Hi all,

There's a problem with the network in our side, we're trying to solve it.
Sorry for the inconvenience that may have caused to you.

Best Regards,
Rong Chen


>
>> -- 
>> Kalle Valo

      reply	other threads:[~2019-07-02 10:53 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
2019-06-30 13:49   ` Philip Li
2019-07-02 10:00     ` Rong Chen [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=f5f5409b-eaca-d38c-bd31-c54ef69b3833@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=hch@lst.de \
    --cc=kvalo@codeaurora.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.