From: "Guillaume Tucker" <guillaume.tucker@collabora.com>
To: Nick Desaulniers <ndesaulniers@google.com>, llvm@lists.linux.dev
Cc: "kernelci@groups.io" <kernelci@groups.io>
Subject: Re: next/master build: 205 builds: 8 failed, 197 passed, 21 errors, 52 warnings (next-20220706)
Date: Wed, 6 Jul 2022 17:48:14 +0100 [thread overview]
Message-ID: <2aaa6787-619a-7672-05b7-e3ae07c87cce@collabora.com> (raw)
In-Reply-To: <CAKwvOdnusz+AjYzkW4pyHraJ1_exhwAz9bscMkRiqjiXRj+66g@mail.gmail.com>
On 06/07/2022 17:40, Nick Desaulniers wrote:
> On Wed, Jul 6, 2022 at 9:16 AM kernelci.org bot <bot@kernelci.org> wrote:
>> next/master build: 205 builds: 8 failed, 197 passed, 21 errors, 52 warnings (next-20220706)
>>
>> Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20220706/
>>
>> Tree: next
>> Branch: master
>> Git Describe: next-20220706
>> Git Commit: 088b9c375534d905a4d337c78db3b3bfbb52c4a0
>> Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>> Built: 7 unique architectures
>>
>> Build Failures Detected:
>>
>> arm64:
>> allmodconfig: (clang-15) FAIL
>> allmodconfig: (gcc-10) FAIL
>>
>> arm:
>> cros://chromeos-5.10/armel/chromiumos-arm.flavour.config: (clang-13) FAIL
>> cros://chromeos-5.10/armel/chromiumos-rockchip.flavour.config: (clang-13) FAIL
>> allmodconfig: (clang-15) FAIL
>> allmodconfig: (gcc-10) FAIL
>>
>> i386:
>> allmodconfig: (clang-15) FAIL
>>
>> mips:
>> decstation_64_defconfig: (gcc-10) FAIL
>>
>> Errors and Warnings Detected:
>>
>> arc:
>>
>> arm64:
>> allmodconfig (gcc-10): 4 errors
>> allmodconfig (clang-15): 1 error
>>
>> arm:
>> allmodconfig (clang-15): 1 error, 13 warnings
>> allmodconfig (gcc-10): 8 errors
>> aspeed_g5_defconfig (clang-15): 10 warnings
>> cros://chromeos-5.10/armel/chromiumos-arm.flavour.config (clang-13): 1 error, 5 warnings
>> cros://chromeos-5.10/armel/chromiumos-rockchip.flavour.config (clang-13): 1 error, 5 warnings
>> multi_v5_defconfig (clang-15): 2 warnings
>> multi_v7_defconfig (clang-15): 12 warnings
>>
>> i386:
>> allmodconfig (clang-15): 1 error
>> allnoconfig (clang-15): 2 warnings
>>
>> mips:
>> 32r2el_defconfig (gcc-10): 1 warning
>> 32r2el_defconfig+kselftest (gcc-10): 1 warning
>> fuloong2e_defconfig (gcc-10): 1 error
>> lemote2f_defconfig (gcc-10): 1 error
>> loongson2k_defconfig (gcc-10): 1 error
>> loongson3_defconfig (gcc-10): 1 error
>> rb532_defconfig (gcc-10): 1 warning
>>
>> riscv:
>>
>> x86_64:
>>
>> Errors summary:
>>
>> 4 drivers/gpu/drm/amd/amdgpu/../display/dc/dc_dmub_srv.c:603:59: error: ‘-mgeneral-regs-only’ is incompatible with the use of floating-point types
>> 4 cc1: error: ‘-mloongson-mmi’ must be used with ‘-mhard-float’
>> 2 lib/maple_tree.c:4272:20: error: stack frame size (1096) exceeds limit (1024) in function 'mas_wr_modify' [-Werror,-Wframe-larger-than]
>> 1 sound/soc/intel/avs/path.c:815:18: error: stack frame size (2176) exceeds limit (2048) in 'avs_path_create' [-Werror,-Wframe-larger-than]
>> 1 lib/maple_tree.c:4272:20: error: stack frame size (1144) exceeds limit (1024) in 'mas_wr_modify' [-Werror,-Wframe-larger-than]
>> 1 lib/maple_tree.c:4272:20: error: stack frame size (1072) exceeds limit (1024) in 'mas_wr_modify' [-Werror,-Wframe-larger-than]
>> 1 ERROR: modpost: "__aeabi_ui2d" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!
>> 1 ERROR: modpost: "__aeabi_i2d" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!
>> 1 ERROR: modpost: "__aeabi_dsub" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!
>> 1 ERROR: modpost: "__aeabi_dmul" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!
>> 1 ERROR: modpost: "__aeabi_ddiv" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!
>> 1 ERROR: modpost: "__aeabi_dadd" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!
>> 1 ERROR: modpost: "__aeabi_d2uiz" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!
>> 1 ERROR: modpost: "__aeabi_d2iz" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!
> ^ interesting, these look new to me, must be from the new CrOS configs.
Except these were not meant to be part of this report as the CrOS
configs are built on a separate instance on
https://chromeos.kernelci.org
This is something we need to investigate, it looks like some
wires got crossed somehow. We may however start sending email
reports for the CrOS builds (only doing LTS 5.10 and 5.15 at the
moment) and we're starting to run tests with Chromium OS
user-space too. Please let us know if you're interested in any
of that.
Guillaume
next prev parent reply other threads:[~2022-07-06 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 16:16 next/master build: 205 builds: 8 failed, 197 passed, 21 errors, 52 warnings (next-20220706) kernelci.org bot
2022-07-06 16:40 ` Nick Desaulniers
2022-07-06 16:48 ` Guillaume Tucker [this message]
2022-07-06 16:51 ` Nathan Chancellor
2022-07-06 16:59 ` Guillaume Tucker
-- strict thread matches above, loose matches on Subject: below --
2022-07-06 16:16 kernelci.org bot
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=2aaa6787-619a-7672-05b7-e3ae07c87cce@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=kernelci@groups.io \
--cc=llvm@lists.linux.dev \
--cc=ndesaulniers@google.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.