Linux block layer
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Veronika Kabatova <vkabatov@redhat.com>
Cc: linux-block@vger.kernel.org
Subject: Re: ❌ FAIL: Test report for kernel 5.10.0-rc3 (block)
Date: Mon, 9 Nov 2020 09:15:04 -0700	[thread overview]
Message-ID: <4795330a-cd9c-a5cb-a256-35281fde5142@kernel.dk> (raw)
In-Reply-To: <449460775.17920557.1604938423946.JavaMail.zimbra@redhat.com>

On 11/9/20 9:13 AM, Veronika Kabatova wrote:
> 
> 
> ----- Original Message -----
>> From: "CKI Project" <cki-project@redhat.com>
>> To: linux-block@vger.kernel.org, axboe@kernel.dk
>> Sent: Monday, November 9, 2020 5:11:45 PM
>> Subject: ❌ FAIL: Test report for kernel 5.10.0-rc3 (block)
>>
>>
>> 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: c91882ba0790 - Merge branch 'tif-task_work.arch' into
>>             for-next
>>
>> The results of these automated tests are provided below.
>>
>>     Overall result: FAILED (see details below)
>>              Merge: OK
>>            Compile: FAILED
>>
>> All kernel binaries, config files, and logs are available for download here:
>>
>>   https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2020/11/09/617345
>>
>> We attempted to compile the kernel for multiple architectures, but the
>> compile
>> failed on one or more architectures:
>>
>>             x86_64: FAILED (see build-x86_64.log.xz attachment)
>>
> 
> Hi, we're seeing the following errors with the last two git pushes
> (the other one being commit dd8da1a825a9ba9ad3c7d0e707db9441c9182349):
> 
> 00:00:10 In file included from ./arch/x86/include/asm/atomic.h:5,
> 00:00:10                  from ./include/linux/atomic.h:7,
> 00:00:10                  from ./include/linux/crypto.h:15,
> 00:00:10                  from arch/x86/kernel/asm-offsets.c:9:
> 00:00:10 ./include/linux/sched/signal.h: In function ‘signal_pending’:
> 00:00:10 ./include/linux/sched/signal.h:368:39: error: ‘TIF_NOTIFY_SIGNAL’ undeclared (first use in this function)
> 00:00:10   368 |  if (unlikely(test_tsk_thread_flag(p, TIF_NOTIFY_SIGNAL)))
> 00:00:10       |                                       ^~~~~~~~~~~~~~~~~
> 00:00:10 ./include/linux/compiler.h:78:42: note: in definition of macro ‘unlikely’
> 00:00:10    78 | # define unlikely(x) __builtin_expect(!!(x), 0)
> 00:00:10       |                                          ^
> 00:00:10 ./include/linux/sched/signal.h:368:39: note: each undeclared identifier is reported only once for each function it appears in
> 00:00:10   368 |  if (unlikely(test_tsk_thread_flag(p, TIF_NOTIFY_SIGNAL)))
> 00:00:10       |                                       ^~~~~~~~~~~~~~~~~
> 00:00:10 ./include/linux/compiler.h:78:42: note: in definition of macro ‘unlikely’
> 00:00:10    78 | # define unlikely(x) __builtin_expect(!!(x), 0)
> 00:00:10       |                                          ^
> 00:00:10   HDRINST usr/include/linux/thermal.h
> 00:00:10   HDRINST usr/include/linux/time.h
> 00:00:10 make[3]: *** [scripts/Makefile.build:117: arch/x86/kernel/asm-offsets.s] Error 1
> 00:00:10   HDRINST usr/include/linux/time_types.h
> 00:00:10   HDRINST usr/include/linux/timerfd.h
> 00:00:10 make[2]: *** [Makefile:1200: prepare0] Error 2

Missed branch on my part, it should be fine now.

-- 
Jens Axboe


      reply	other threads:[~2020-11-09 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-09 16:11 ❌ FAIL: Test report for kernel 5.10.0-rc3 (block) CKI Project
2020-11-09 16:13 ` Veronika Kabatova
2020-11-09 16:15   ` Jens Axboe [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=4795330a-cd9c-a5cb-a256-35281fde5142@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=vkabatov@redhat.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