bug(Coverage): forge coverage --report lcov is failing after the latest release

[jalextowle]

Component

Forge

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

• Foundry
• Foundryup

What version of Foundry are you on?

Run forge --version forge 0.2.0 (3fec8c1 2023-08-11T00:15:50.024503184Z)

What command(s) is the bug in?

forge coverage

Operating System

Linux

Describe the bug

forge coverage --report lcov runs for 6 hours before our CI actions are timing out. I'm posting screenshots from before and after the new release dropped. Prior to the new release, we never had issues with our code coverage action, but since the release, every coverage job has run for 6 hours and failed due to a timeout.

Here's a screenshot showing our recent job statuses:

I looked at the release history, and the latest release coincides with this.

I downgraded to version forge 0.2.0 (1044042 2023-08-10T13:04:25.942019017Z), and sure enough, the coverage job succeeds:

Downgrading is an easy fix for us in the meantime, but let me know if there's any other information that would be helpful when investigating this. Unfortunately, our repo is private at the moment, so I don't have an example to point to.

[matbour]

I can confirm this bug on my company's smart contract repository. See relevant action run.

[arr00]

Actions broke on my repo as well. Reran past actions that succeeded and they fail now.

[Evalir]

Hey all! this is a result of revm upgrades we recently did—we're rolling out a fix soon: #5610

[matbour]

Issue seems to be solved in my CI

[0xTimepunk]

@Evalir the issue has returned today on our CI, can you please verify?

[Evalir]

Closed with #5695 and #5698