From: Philip Li <philip.li@intel.com>
To: lkp@lists.01.org
Subject: Re: LKP with bluetooth-next
Date: Fri, 04 Dec 2020 07:30:20 +0800 [thread overview]
Message-ID: <20201203233020.GA31431@intel.com> (raw)
In-Reply-To: <0430DD4D-97F3-42BA-898E-9FF20FD23A9F@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1996 bytes --]
On Thu, Dec 03, 2020 at 09:09:27PM +0000, An, Tedd wrote:
> Hi
>
> I am working on Linux Bluetooth and I have a question about the service.
> For your background, the tree we are working is
> https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git
> And the mailing list is linux-bluetooth(a)vger.kernel.org
>
> We had received the test result with the patches in our mailing list once in a while, but we don't receive the test result for all the relevant patches.
> I just wonder if the 0-Day test runs all the patches in the mailing list and send out the email regardless of the result or it only sends the failed patches.
Hi Tedd, currently we will try to test every patch as we can, but it depends
on whether we can successfully find a base for the patch series so
we can form a branch. We recommend to use --base as documented in
https://git-scm.com/docs/git-format-patch.
Thus it's possible some patches are not covered.
>
> We prefer to receive the result for all patches even if it success so we can confirm it.
For repo side, it is now configured to notify overall build status.
For mailing list's patch, we will take a look for notifying success info.
>
> If it is only run per request without monitoring the patches from the mailing list, I would like to trigger the 0-Day test manually.
> How can I do that and is there any specific format?
We currently doesn't support manual testing from users, mostly
due to limited computing resource we have. We run standard set
of build testing for all repos. For runtime testing, we may not
cover your code as we test on server platforms and doesn't have
corresponding suite for bluetooth.
>
> Thanks for your support in advance.
you are welcome, you can drop mail to lkp(a)intel.com to reach us.
>
> Regards,
> Tedd
>
> _______________________________________________
> LKP mailing list -- lkp(a)lists.01.org
> To unsubscribe send an email to lkp-leave(a)lists.01.org
prev parent reply other threads:[~2020-12-03 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 21:09 LKP with bluetooth-next An, Tedd
2020-12-03 23:30 ` Philip Li [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=20201203233020.GA31431@intel.com \
--to=philip.li@intel.com \
--cc=lkp@lists.01.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 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.