From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: Mark Brown <broonie@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>
Cc: kernelci@lists.linux.dev, clang-built-linux <llvm@lists.linux.dev>
Subject: Re: kernelci: please upgrade clang-17
Date: Tue, 13 Jun 2023 12:37:05 +0200 [thread overview]
Message-ID: <dfa85ccc-693b-00cb-a4d9-af32e0dfbed8@collabora.com> (raw)
In-Reply-To: <262df5fd-d8c4-47aa-a65d-dd79a303a9ca@sirena.org.uk>
On 12/06/2023 17:11, Mark Brown wrote:
> On Fri, Jun 09, 2023 at 01:50:13PM -0700, Nick Desaulniers wrote:
>> Starting a new thread because gmail cannot handle replying to an email
>> w/ >45k warnings.
>> https://lore.kernel.org/llvm/6482b7dd.170a0220.a93c3.9102@mx.google.com/
>>
>> instances of -Wbuiltin-macro-redefined have been fixed in ToT llvm.
>> Updating clang-17 should resolve most of the error spew.
>>
>> Does kernel CI update ToT clang builds on a fixed cadence?
>
> The containers with the tools should be being rebuilt during the
> production update which normally happens every Monday. There's some
> disruption at the minute due to some infrastructure rebuilding that's
> going on so today's update of the containers might be delayed.
Yes the LLVM-17 update has now trickled down into production and
warnings are all gone:
https://storage.kernelci.org/next/master/next-20230613/arm/multi_v7_defconfig/clang-17/logs/kernel.log
compared with the previous linux-next build which had all the warnings:
https://storage.kernelci.org/next/master/next-20230609/arm/multi_v7_defconfig/clang-17/logs/kernel.log
We skipped the regular production update last Monday to focus on
migrating VMs to the new Azure subscription, sorry for the
inconvenience. We're back on the regular schedule now.
Thanks,
Guillaume
next prev parent reply other threads:[~2023-06-13 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 20:50 kernelci: please upgrade clang-17 Nick Desaulniers
2023-06-12 15:11 ` Mark Brown
2023-06-13 10:37 ` Guillaume Tucker [this message]
2023-06-14 16:43 ` Nick Desaulniers
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=dfa85ccc-693b-00cb-a4d9-af32e0dfbed8@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=broonie@kernel.org \
--cc=kernelci@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox