[libcxx-commits] [libcxx] [libcxx][docs] Update "Exporting new symbols" for the move to GitHub CI (PR #222533)

Nikolas Klauser via libcxx-commits libcxx-commits at lists.llvm.org
Thu Sep 10 05:32:22 PDT 2026


================
@@ -163,15 +163,31 @@ Exporting new symbols from the library
 When exporting new symbols from libc++, you must update the ABI lists located in ``lib/abi``.
 To test whether the lists are up-to-date, please run the target ``check-cxx-abilist``.
 To regenerate the lists, use the target ``generate-cxx-abilist``.
-The ABI lists must be updated for all supported platforms; currently Linux and
-Apple.  If you don't have access to one of these platforms, you can download an
-updated list from the failed build at
-`Buildkite <https://buildkite.com/llvm-project/libcxx-ci>`__.
-Look for the failed build and select the ``artifacts`` tab. There, download the
-abilist for the platform, e.g.:
-
-* C++<version>.
-* macOS X86_64 and macOS arm64 for the Apple platform.
+The ABI lists must be updated for all supported platforms. If you don't have
+access to one of these platforms, you can download an updated list from the
+failed CI build: when the ABI list check fails, CI regenerates the list and
+uploads it together with the other build artifacts.
+
+For Linux (x86-64) and the Apple platforms, the checks run on GitHub as part of
+the ``[libc++] Conformance tests`` workflow. From your pull request, open the
+failed workflow run, select the failed job, and download its artifact from the
+``Artifacts`` section (you must be logged into GitHub to download artifacts).
----------------
philnik777 wrote:

Where do you have an "Artifacts" section on GH?

https://github.com/llvm/llvm-project/pull/222533


More information about the libcxx-commits mailing list