[lldb-dev] [Openmp-dev] RFC: Using GitHub Actions for CI testing on the release/* branches

Tom Stellard via lldb-dev lldb-dev at lists.llvm.org
Tue Nov 19 22:26:01 PST 2019

> Hi Tom,
> This sounds very interesting! +1 from me.
> What does this imply for the release testers?
> Would it be possible / desirable for us to add self-hosted runners for
> other architectures? I'm assuming GitHub only provides x86, right? I
> totally missed any details about that in their docs, but it seems to
> be implied here [1]. I'm not saying we should go all-possible-arches
> from the start, we can definitely try it out only for x86 this time
> around if you think that would be the best approach.

Nothing changes for release testers at this point.  The main goal here is
to get some post-commit testing so we can catch issues in the branch early.

Longer term I think have self-hosted runners would be great, because it would
allow us to fully automate the testing and uploading we do when a release gets

You are correct that GitHub only provides x86 machines, however, they don't
have enough disk space (14GB) to be able to run the test-release.sh script, so
adding x86 self-hosted builders with more disk space would still be very useful.

> [1] https://github.blog/2019-11-05-self-hosted-runners-for-github-actions-is-now-in-beta/
> Thanks,
> Diana

More information about the lldb-dev mailing list