llvm dev - Oct 2021 - Upcoming change with how libc++, libc++abi and libunwind are being built

On Mon, Oct 18, 2021 at 2:49 PM Michael Kruse <llvmdev at meinersbur.de>
wrote:
> Am Mo., 18. Okt. 2021 um 13:06 Uhr schrieb Louis Dionne <
> ldionne.2 at gmail.com>:
> > On Mon, Oct 18, 2021 at 12:23 PM Michael Kruse <llvmdev at
meinersbur.de>
> wrote:
> > The build bots that wish to build libc++ with a supported
> non-clang-trunk compiler
> > can switch to the "default build", which is basically the
equivalent of
> the Project
> > build we had before.
>
> Which buildbots will test the "default build" for
gcc/AppleClang/Clang
> 11/Clang 12? Individual buildbot maintainers may be interested in
> keeping their buildbot green, not necessarily to ensure coverage.
>
Nowadays, we handle all libc++'s own build bots through BuildKite at
https://buildkite.com/llvm-project/libcxx-ci.

That pipeline contains all the configurations that we support officially.
If someone has a build bot and
they think they are adding coverage, we'd like to know it so we can look
into migrating it to BuildKite
and owning it ourselves.

Otherwise, they should just make whatever change is needed to keep their
bot green. In most cases I
would expect the easiest thing to do here would be to use the Bootstrapping
build so as to always build
against the latest Clang, however they can also use the "Default
build"
with a suitably-recent system
compiler if they want to avoid building all of Clang on their bot.

Cheers,
Louis


>
> Michael
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20211018/084050f0/attachment.html>

Am Mo., 18. Okt. 2021 um 15:19 Uhr schrieb Louis Dionne <ldionne.2 at
gmail.com>:
> Nowadays, we handle all libc++'s own build bots through BuildKite at
https://buildkite.com/llvm-project/libcxx-ci.
I didn't know. Good that there is systematic testing, but I am a bit
concerned about the fracturing of the CI infrastructure (Buildbot,
Green dragon, GitHub actions, Buildkite, ...)

Michael

Louis,

Do libcxx/abi, clang code reviews on phabricator trigger these buildkite builds
similar to some of the other monorepo content?

-Brian

From: libcxx-dev <libcxx-dev-bounces at lists.llvm.org> On Behalf Of Louis
Dionne via libcxx-dev
Sent: Monday, October 18, 2021 3:19 PM
To: Michael Kruse <llvmdev at meinersbur.de>
Cc: llvm-dev <llvm-dev at lists.llvm.org>; clang developer list
<cfe-dev at lists.llvm.org>; Libc++ Dev <libcxx-dev at
lists.llvm.org>
Subject: Re: [libcxx-dev] [llvm-dev] Upcoming change with how libc++, libc++abi
and libunwind are being built


WARNING: This email originated from outside of Qualcomm. Please be wary of any
links or attachments, and do not enable macros.


On Mon, Oct 18, 2021 at 2:49 PM Michael Kruse <llvmdev at
meinersbur.de<mailto:llvmdev at meinersbur.de>> wrote:
Am Mo., 18. Okt. 2021 um 13:06 Uhr schrieb Louis Dionne <ldionne.2 at
gmail.com<mailto:ldionne.2 at gmail.com>>:
> On Mon, Oct 18, 2021 at 12:23 PM Michael Kruse <llvmdev at
meinersbur.de<mailto:llvmdev at meinersbur.de>> wrote:
> The build bots that wish to build libc++ with a supported non-clang-trunk
compiler
> can switch to the "default build", which is basically the
equivalent of the Project
> build we had before.
Which buildbots will test the "default build" for gcc/AppleClang/Clang
11/Clang 12? Individual buildbot maintainers may be interested in
keeping their buildbot green, not necessarily to ensure coverage.

Nowadays, we handle all libc++'s own build bots through BuildKite at
https://buildkite.com/llvm-project/libcxx-ci.

That pipeline contains all the configurations that we support officially. If
someone has a build bot and
they think they are adding coverage, we'd like to know it so we can look
into migrating it to BuildKite
and owning it ourselves.

Otherwise, they should just make whatever change is needed to keep their bot
green. In most cases I
would expect the easiest thing to do here would be to use the Bootstrapping
build so as to always build
against the latest Clang, however they can also use the "Default
build" with a suitably-recent system
compiler if they want to avoid building all of Clang on their bot.

Cheers,
Louis



Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20211019/45004c76/attachment-0001.html>