All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Matthew Wilcox <willy@infradead.org>,
	Pavel Begunkov <asml.silence@gmail.com>
Cc: Veronika Kabatova <vkabatov@redhat.com>,
	CKI Project <cki-project@redhat.com>,
	linux-block@vger.kernel.org
Subject: Re: ❌ FAIL: Test report for kernel 5.13.0-rc6 (block, b0740de3)
Date: Mon, 21 Jun 2021 17:42:15 -0600	[thread overview]
Message-ID: <5cf4b5ae-c6aa-d64d-53ec-3e073a77baef@kernel.dk> (raw)
In-Reply-To: <YNEhq/C5/T4J8r2/@casper.infradead.org>

On 6/21/21 5:32 PM, Matthew Wilcox wrote:
> On Mon, Jun 21, 2021 at 11:57:06PM +0100, Pavel Begunkov wrote:
>> On 6/21/21 10:58 PM, Matthew Wilcox wrote:
>>> On Mon, Jun 21, 2021 at 11:07:16PM +0200, Veronika Kabatova wrote:
>>>> On Mon, Jun 21, 2021 at 11:00 PM Jens Axboe <axboe@kernel.dk> wrote:
>>>>>
>>>>> On 6/21/21 2:57 PM, Veronika Kabatova wrote:
>>>>>> On Mon, Jun 21, 2021 at 9:20 PM Veronika Kabatova <vkabatov@redhat.com> wrote:
>>>>>>>
>>>>>>> On Mon, Jun 21, 2021 at 9:17 PM CKI Project <cki-project@redhat.com> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> We ran automated tests on a recent commit from this kernel tree:
>>>>>>>>
>>>>>>>>        Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
>>>>>>>>             Commit: b0740de3330a - Merge branch 'for-5.14/drivers-late' into for-next
>>>>>>>>
>>>>>>>> The results of these automated tests are provided below.
>>>>>>>>
>>>>>>>>     Overall result: FAILED (see details below)
>>>>>>>>              Merge: OK
>>>>>>>>            Compile: FAILED
>>>>>>>>
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> the failure is introduced between this commit and d142f908ebab64955eb48e.
>>>>>>> Currently seeing if I can bisect it closer but maybe someone already has an
>>>>>>> idea what went wrong.
>>>>>>>
>>>>>>
>>>>>> First commit failing the compilation is 7a2b0ef2a3b83733d7.
>>>>>
>>>>> Where's the log? Adding Willy...
>>>>>
>>>>
>>>> Logs and kernel configs for each arch are linked in the original email at
>>>> https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/06/21/324657779
>>>
>>> Which aren't there by the time they get to the original commit author.
>>> You need to do better than this; the Intel build-bot bisects to the
>>> commit which actually causes the error.
>>
>> Matthew, I've just followed the link out of curiosity:
> 
> the link _which isn't in the first email i got_.  the redhat cki system
> is not very useful _because it doesn't do an automatic bisect and cc the
> author of the commit_.

Kinks are still being worked out on that, nobody has claimed it's
perfect yet. Some manual input/labor is still required.

But it's useful, as this report has indicated. So maybe try and be a bit
nicer and appreciative, instead of grumpy and dismissive. It did find a
problem with YOUR patch, fwiw.

-- 
Jens Axboe


  reply	other threads:[~2021-06-21 23:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cki.3F4F097E3B.299V5OKJ7M@redhat.com>
2021-06-21 19:20 ` ❌ FAIL: Test report for kernel 5.13.0-rc6 (block, b0740de3) Veronika Kabatova
2021-06-21 20:57   ` Veronika Kabatova
2021-06-21 21:00     ` Jens Axboe
2021-06-21 21:07       ` Veronika Kabatova
2021-06-21 21:58         ` Matthew Wilcox
2021-06-21 22:57           ` Pavel Begunkov
2021-06-21 23:32             ` Matthew Wilcox
2021-06-21 23:42               ` Jens Axboe [this message]
2021-06-21 23:49                 ` Matthew Wilcox
2021-06-22  0:48                   ` Jens Axboe
2021-06-21 23:36           ` Jens Axboe
2021-06-21 21:10       ` Keith Busch
2021-06-21 21:13         ` Jens Axboe

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=5cf4b5ae-c6aa-d64d-53ec-3e073a77baef@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=asml.silence@gmail.com \
    --cc=cki-project@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=vkabatov@redhat.com \
    --cc=willy@infradead.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.