[libcxx-commits] [PATCH] D139147: [libc++][Android] Enable libc++ testing on Android

[Mark de Wever via Phabricator via libcxx-commits]

Mordante added a comment.

In D139147#4412669 <https://reviews.llvm.org/D139147#4412669>, @rprichard wrote:

> In D139147#4412013 <https://reviews.llvm.org/D139147#4412013>, @Mordante wrote:
>
>> [...]
>>
>> I'm not discouraged reviewing this, especially since it adds CI support. But several of us work as volunteer which means we have limited time to work on libc++.
>>
>> For the way forward, I've a question. What is the intention regarding running the CI?
>>
>> Are you going to host it yourself like AIX/FreeBSD do or is it the intention the run on our existing Linux runners?
>
> My current plan is to use a different Docker image (libcxx-builder-android vs libcxx-builder) and run Android-specific buildkite agents. We could use the same Docker image and Linux runners for both, but the existing Docker image has gigabytes of GCC and Clang, whereas the Android Docker image has gigabytes of emulator OS images. (libcxx-builder is ~6GB while my current libcxx-builder-android is ~12GB with two OS images and only one NDK Clang.) My tentative plan is to host the Android-specific VMs in the same GCE project that hosts the current Linux runners. For the moment, I've also had to switch from using Container-Optimized OS (COS) to Ubuntu GCE images, because COS doesn't currently support KVM.

Thanks for the information. Then having two different Docker images indeed makes sense.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D139147/new/

https://reviews.llvm.org/D139147