From: Veronika Kabatova <vkabatov@redhat.com>
To: axboe@kernel.dk
Cc: linux-block@vger.kernel.org
Subject: Re: ❌ FAIL: Test report for kernel 5.10.0-rc5 (block)
Date: Mon, 30 Nov 2020 14:29:52 -0500 (EST) [thread overview]
Message-ID: <1212579999.19835613.1606764592454.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <cki.DBF986CEF7.1DN2XEHOVP@redhat.com>
----- Original Message -----
> From: "CKI Project" <cki-project@redhat.com>
> To: linux-block@vger.kernel.org, axboe@kernel.dk
> Sent: Monday, November 30, 2020 8:27:49 PM
> Subject: ❌ FAIL: Test report for kernel 5.10.0-rc5 (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: cd8ae268840e - Merge branch 'for-5.11/block' 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/30/618887
>
> We attempted to compile the kernel for multiple architectures, but the
> compile
> failed on one or more architectures:
>
> aarch64: FAILED (see build-aarch64.log.xz attachment)
> ppc64le: FAILED (see build-ppc64le.log.xz attachment)
> s390x: FAILED (see build-s390x.log.xz attachment)
> x86_64: FAILED (see build-x86_64.log.xz attachment)
>
Hi,
looks to be introduced by
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?h=for-next&id=1076736138841d8516555f352ae0426a99ae9f92
Veronika
> We hope that these logs can help you find the problem quickly. For the full
> detail on our testing procedures, please scroll to the bottom of this
> message.
>
> Please reply to this email if you have any questions about the tests that we
> ran or if you have any suggestions on how to make future tests more
> effective.
>
> ,-. ,-.
> ( C ) ( K ) Continuous
> `-',-.`-' Kernel
> ( I ) Integration
> `-'
> ______________________________________________________________________________
>
> Compile testing
> ---------------
>
> We compiled the kernel for 4 architectures:
>
> aarch64:
> make options: make -j30 INSTALL_MOD_STRIP=1 targz-pkg
>
> ppc64le:
> make options: make -j30 INSTALL_MOD_STRIP=1 targz-pkg
>
> s390x:
> make options: make -j30 INSTALL_MOD_STRIP=1 targz-pkg
>
> x86_64:
> make options: make -j30 INSTALL_MOD_STRIP=1 targz-pkg
>
>
>
next parent reply other threads:[~2020-11-30 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cki.DBF986CEF7.1DN2XEHOVP@redhat.com>
2020-11-30 19:29 ` Veronika Kabatova [this message]
2020-11-30 21:43 ` ❌ FAIL: Test report for kernel 5.10.0-rc5 (block) 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=1212579999.19835613.1606764592454.JavaMail.zimbra@redhat.com \
--to=vkabatov@redhat.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox