Skip to content

Migrate coverage CI from cargo-tarpaulin to cargo-llvm-cov #1

Description

@RAprogramm

Problem

The tarpaulin workflow is the only permanently red check in the repository, and it carries a stack of obsolete machinery:

Item State
actions-rs/tarpaulin@v0.1 unmaintained, runs on Node 20, which GitHub force-migrated to Node 24 on 2026-06-16
version: '0.22.0' cargo-tarpaulin pinned to a 2022 release; current is 0.34.x
OpenSSL 1.1 step downloads libssl1.1_1.1.1f-1ubuntu2_amd64.deb from the Ubuntu Bionic archive and installs it with dpkg on ubuntu-24.04
edition support tarpaulin 0.22.0 rejects edition 2024 (unknown variant '2024', expected one of '2015', '2018', '2021')

The pinned tarpaulin is also what blocks the edition bump needed by the Rust atoms work.

Proposal

Replace the workflow with cargo-llvm-cov, installed through taiki-e/install-action:

  • source-based LLVM coverage, no OpenSSL hack, no third-party wrapper action
  • --lcov output consumed directly by codecov/codecov-action
  • no edition restrictions

Housekeeping that comes with it:

  • git mv .github/workflows/tarpaulin.yml .github/workflows/coverage.yml
  • drop [lints.rust] unexpected_cfgs = { check-cfg = ['cfg(tarpaulin)'] } from Cargo.toml (no cfg(tarpaulin) is used anywhere in src)
  • replace tarpaulin-report.html with lcov.info in .gitignore

Out of scope

Upstream also fails the upload step with Token required because branch is protected, which needs a CODECOV_TOKEN repository secret. That is a repository setting, not a code change; the workflow passes the secret through so it starts working as soon as the secret exists.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions