• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

tarantool / tarantool / 36718850818
88%

Build:
DEFAULT BRANCH: master
Ran 30 Sep 2026 01:16PM UTC
Jobs 1
Files 528
Run time 3min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

30 Sep 2026 01:02PM UTC coverage: 87.946% (+0.002%) from 87.944%
36718850818

push

github

Totktonada
ci: run aarch64 jobs on GitHub-hosted runners

The main idea behind this switch is to have less of our own
infrastructure to support.

We added our own aarch64 runners before GitHub started to provide them
natively [1] and, in fact, never wanted to spend time on them.

A big advantage of GitHub-hosted runners is that they're created per
job. Ours are long-lived machines, and a bad job may break the jobs
after it. This is a constant source of problems we have to work around:
the CodeQL workflow has to clean up the CodeQL bundles it downloads so
as not to fill the whole disk; the environment action kills test
processes left by earlier jobs and cleans up the git repository. We even
have the special `prepare-checkout` action that does some black magic,
so that `actions/checkout` works on a git repository left by a previous
job.

In fact, the runner-per-job approach can be implemented for self-hosted
runners too, see [2] and [3]. But that's the infrastructure work we want
to avoid.

I'd also note that there are providers of GitHub Actions runners besides
GitHub itself, including ones that offer aarch64 runners. So if we find
ourselves in need of more resources, we have options that don't require
managing our own Kubernetes cluster.

All of the above applies to the x86_64 runners too, and I hope we will
move them as well, just later.

Besides `debug_aarch64` and `packaging_build_test_deploy`, which run in
tarantool CI, this commit adjusts `luajit-integration`, which is called
from tarantool/luajit CI (as is `debug_aarch64`). This way we move part
of LuaJIT's CI to GitHub-hosted runners.

[1]: https://github.blog/changelog/2025-01-16-linux-arm64-hosted-runners-now-available-for-free-in-public-repositories-public-preview/
[2]: https://github.blog/changelog/2021-09-20-github-actions-ephemeral-self-hosted-runners-new-webhooks-for-auto-scaling/
[3]: https://github.com/actions/actions-runner-controller/discussions/2174

Drafted by an LLM, conducted and corrected ... (continued)

72368 of 121184 branches covered (59.72%)

108739 of 123643 relevant lines covered (87.95%)

1418987.42 hits per line

Coverage Regressions

Lines Coverage ∆ File
4
94.15
-2.13% src/box/vy_range.c
4
93.62
-0.61% src/box/xrow_update_field.c
3
98.03
-0.19% src/box/memtx_tx.c
3
96.17
-0.52% src/box/relay.cc
3
22.66
-0.06% src/lib/uri/uri_parser.c
2
91.2
0.0% src/box/box.cc
2
88.84
-0.3% src/box/vy_lsm.c
1
90.31
0.15% src/box/applier.cc
1
95.22
-0.1% src/box/replication.cc
1
92.8
0.09% src/box/vinyl.c
1
92.75
0.2% src/box/vy_scheduler.c
1
85.9
-0.09% src/box/xlog.c
1
94.11
-0.1% src/lib/core/fiber.c
1
96.55
-1.15% src/lib/core/histogram.c
1
97.09
0.3% src/lib/msgpuck/msgpuck.h
1
79.44
-0.25% src/main.cc
Jobs
ID Job ID Ran Files Coverage
1 36718850818.1 30 Sep 2026 01:16PM UTC 528
87.95
GitHub Action Run
Source Files on build 36718850818
  • Tree
  • List 528
  • Changed 27
  • Source Changed 0
  • Coverage Changed 27
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • 5efb60c3 on github
  • Prev Build on master (#36700119812)
  • Next Build on master (#36722345524)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc