Re: arm64/for-kernelci build: 2 builds: 1 failed, 1 passed, 2 errors, 1 warning (arm64-fixes)

[Guillaume Tucker <guillaume.tucker@collabora.com>]

On 20/07/2021 13:53, Will Deacon wrote:
> On Mon, Jul 19, 2021 at 08:05:20AM -0700, kernelci.org bot wrote:
>> arm64/for-kernelci build: 2 builds: 1 failed, 1 passed, 2 errors, 1 warning (arm64-fixes)
>>
>> Full Build Summary: https://kernelci.org/build/arm64/branch/for-kernelci/kernel/arm64-fixes/
>>
>> Tree: arm64
>> Branch: for-kernelci
>> Git Describe: arm64-fixes
>> Git Commit: e6f85cbeb23bd74b8966cf1f15bf7d01399ff625
>> Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
>> Built: 1 unique architecture
>>
>> Build Failure Detected:
>>
>> arm64:
>>     allmodconfig: (gcc-8) FAIL
>>
>> Errors and Warnings Detected:
>>
>> arm64:
>>     allmodconfig (gcc-8): 2 errors, 1 warning
>>
>> Errors summary:
>>
>>     1    ./../include/linux/compiler_types.h:328:38: error: call to ‘__compiletime_assert_1864’ declared with attribute error: FIELD_PREP: value too large for the field
>>     1    ./../include/linux/compiler_types.h:328:38: error: call to ‘__compiletime_assert_1857’ declared with attribute error: FIELD_PREP: value too large for the field
> 
> Hmm, is there a way to find out more information about which assertion is
> causing the problem here? I'm not able to reproduce this locally, the branch
> in question has now been merged upstream and I can't see anything in there
> which would trigger this.

It's true that each section about a particular build could have a
link to the page on the dashboard with all the details, that's
something to improve.

The way to find things out right now is to start with the main
link from the top of the email report, which shows all the builds
for this kernel revision:

  https://kernelci.org/build/arm64/branch/for-kernelci/kernel/arm64-fixes/

Then you can see the ones with errors, including the allmodconfig one:

  https://linux.kernelci.org/build/id/60f59321f76d8d0f141160be/

There's also a direct link to the logs, and then it takes a bit
of manual hunting.  The error mentioned here can be found in the
modules build log:

  https://storage.kernelci.org/arm64/for-kernelci/arm64-fixes/arm64/allmodconfig/gcc-8/logs/modules.log

In file included from ../include/linux/byteorder/little_endian.h:5,
                 from ../arch/arm64/include/uapi/asm/byteorder.h:23,
                 from ../include/asm-generic/bitops/le.h:7,
                 from ../arch/arm64/include/asm/bitops.h:29,
                 from ../include/linux/bitops.h:32,
                 from ../include/linux/of.h:15,
                 from ../include/linux/irqdomain.h:35,
                 from ../include/linux/acpi.h:13,
                 from ../drivers/infiniband/hw/hns/hns_roce_hw_v2.c:33:
In function ‘modify_qp_init_to_rtr’,
    inlined from ‘hns_roce_v2_set_abs_fields’ at ../drivers/infiniband/hw/hns/hns_roce_hw_v2.c:4798:9,
    inlined from ‘hns_roce_v2_modify_qp’ at ../drivers/infiniband/hw/hns/hns_roce_hw_v2.c:5001:8:
./../include/linux/compiler_types.h:328:38: error: call to ‘__compiletime_assert_1857’ declared with attribute error: FIELD_PREP: value too large for the field
  _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
                                      ^

I guess you could take a look at allmodconfig build logs from
linux-next now it's merged, to see if it's also there.

Hope that helps.

Best wishes,
Guillaume

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel