Skip to content

Use LLVM instrumentation for accurate coverage reports #484

Description

@jolars

The coverage workflow uses Tarpaulin's default Linux tracing backend with opt-level = 3 in the test profile. Codecov can therefore report source lines as uncovered even when the existing tests execute them.

PR #480 shows the problem: the report marks parts of the lazy matrix products and estimator fits as uncovered, although the tests call those paths. A local run with LLVM instrumentation covers those lines with the same optimized test profile.

Switch the coverage job to cargo tarpaulin --engine llvm and install llvm-tools-preview with the nightly toolchain. Keep unit tests, integration tests, doctests, the LCOV output, and the existing 44% threshold.

Related coverage setup: #399 and #400.

Activity

  1. added a commit that references this issue on Oct 12, 2026
    20cc502
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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions