Skip to content

bug(forge coverage): forge coverage run gets killed #11789

@pcaversaccio

Description

@pcaversaccio

Component

Forge

Have you ensured that all of these are up to date?

  • Foundry
  • Foundryup

What version of Foundry are you on?

1.3.6-nightly

What version of Foundryup are you on?

1.3.0

What command(s) is the bug in?

forge coverage --report summary --report lcov --lcov-version 2.3.1

Operating System

None

Describe the bug

If I run the following command on my repo, the process will be killed:

forge coverage --report summary --report lcov --lcov-version 2.3.1

You can realise it's super slow as well. Use the following version to repro:

forge Version: 1.3.6-nightly
Commit SHA: ad1f9ab554301b1475dfef3189cb36c3fc73d3f3
Build Timestamp: 2025-09-24T06:02:53.198606567Z (1758693773)
Build Profile: maxperf

Everything works if I install latest stable version:

forge Version: 1.3.5-stable
Commit SHA: 9979a41b5daa5da1572d973d7ac5a3dd2afc0221
Build Timestamp: 2025-09-09T04:48:08.305566906Z (1757393288)
Build Profile: maxperf

You can also see this in my CI runs:

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    Done

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions