Skip to content

Downstream CI for libc #5209

Open
Open

Description

@tgross35

libc is tested a handful of places downstream for targets that aren't Tier 2+, or have less common configurations. This issue is intended to aggregate a list of any such public CI.

Targets CI Maintainer Link Status Badge
armv7-rtems-eabihf https://github.com/physwkim/libc-downstream-ci CI

If you are interested in testing a target that can be run in Docker or natively on GitHub Actions (e.g. with a self-hosted runner), see https://github.com/tgross35/libc-downstream-ci for a simple template to get a daily job going.

If you are already running CI downstream anywhere with public results, comment a link and I'll update the table.

Activity

  1. added
    A-CIArea: CI-related items
    C-discussionCategory: Discussion or questions that doesn't represent issues with `libc`.
    on Jun 24, 2026
  2. tgross35 commented on Jun 24, 2026

    @tgross35
    MemberAuthor

    Cc @Gelbpunkt @asomers @semarie @maurer @skrap @neuschaefer @sunshowers @erickt @Nashenas88 @ivmarkov @MabezDev @SergioGasquez because I believe all of you have either expressed interest in running downstream CI, or are already doing so.

  3. pinned this issue on Jun 24, 2026
  4. maurer commented on Jul 20, 2026

    @maurer

    Android's downstream CI is currently only operating on released copies of libc (when we update the compiler or the version of the crate available to platform developers). The team recently shrunk, so it's unlikely that a CI integrating ToT libc with Android is going to happen. (Compiler would be first on the list, and that's also not likely to happen.)

  5. physwkim commented on Oct 23, 2026

    @physwkim
    Contributor

    armv7-rtems-eabihf is now tested daily at https://github.com/physwkim/libc-downstream-ci, on the RTEMS 6 xilinx_zynq_a9_qemu BSP under QEMU (badge: https://github.com/physwkim/libc-downstream-ci/actions/workflows/ci.yaml/badge.svg). It stays red until #5663 is fixed, and it uses nightly-2026-10-19 until rust-lang/rust#164719 and #5655 are fixed. I can maintain it. cc @thesummer

  6. thesummer commented on Oct 24, 2026

    @thesummer
    Contributor

    Thanks @physwkim I was a bit preoccupied with other things. Will have a look at #5663

  7. vignesh-chaturvedi commented on Oct 30, 2026

    @vignesh-chaturvedi
    Contributor

    x86_64-unknown-openbsd is now tested daily on both currently supported OpenBSD releases: 8.0 (Rust 1.98.1) and 7.9 (Rust 1.94.1), using each release's own rust package. The CI boots an OpenBSD VM with vmactions/openbsd-vm and runs libc's ci/run.sh... Both jobs are green, and it has already caught the getexecpath issue on 7.9 (#5670). I can maintain it. cc @semarie

    Targets CI Maintainer Link Status Badge
    x86_64-unknown-openbsd @vignesh-chaturvedi https://github.com/vignesh-chaturvedi/libc-downstream-ci CI
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-CIArea: CI-related itemsC-discussionCategory: Discussion or questions that doesn't represent issues with `libc`.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions