Re: [PATCH 0/4] Add a CI for unsigned char system

From: Jeff King <peff@peff.net>
Date: Mar 9, 2023, 09:53 UTC
Message-ID: <ZAmsikbYncUbNjD2@coredump.intra.peff.net>
In-Reply-To: <cover.1677850517.git.congdanhqx@gmail.com>

On Fri, Mar 03, 2023 at 08:46:02PM +0700, Đoàn Trần Công Danh wrote:

Show 5 quoted lines

> Recently, we have a brokeness on system with unsigned char because most of
> people are working with x86_64 which has signed char.
> 
> This series tries to add a CI system for a widely used system with signed
> char, which is arm64 via circle-ci.

I like the overall goal, but I'm not wild about having another CI provider. That requires people logging in there, and then dealing with possible credit overages, etc.

I wonder what the timeline is for GitHub Actions getting arm64 support. It looks like there are images for linux/arm64, but no runners yet, according to:

  https://github.com/actions/runner-images/issues/5631

You can point it at your own runners, and some people in that thread mentioned a third-party service which provides arm machines. That doesn't get out of the "oops, credits" handling, but it would at least keep the CI results all together.

I dunno. Another option I saw suggested is using qemu within a regular GitHub runner. I have no idea if that would be painfully slow or what, but it looks like people have even written actions to handle it:

  https://github.com/docker/setup-qemu-action

-Peff