I guess the title should be updated too

Thanks. Updated.

Removing the experiment didn't make the 1.21 release, there are still some bugfix CLs not yet submitted (e.g. 495446, 495447, and 495452). Once those go in I should be in a better position to get rid of the experiment.

@thanm Is this likely to be removed in 1.22, or bumped to 1.23? (I tried to find links to the issues you included, 495446, 495447, and 495452, but was unsuccessful)

Hi @tombrown52,

Thanks for the note. That last comment I posted was a bit cryptic, sorry about that. "495446, 495447, and 495452" are Gerrit CLs, not issues. These CLs have now been merged, and bugs they were intended to address have been closed. More details with links:

CLs 495446 and 495447 are for issues #18909 and #24570.

CL 495452 is for issue #58770.

My intent was to have these fixed early in this cycle, but for a variety of reasons this didn't happen. As a result we're going to bump the deletion of GOEXPERIMENT=coverageredesign until the next release; with less than a month to go before the freeze, it is better to wait until early in the next cycle.

@thanm Thanks for the update!

Bumping milestone to 1.23

I have generated packages in my monorepo that I don't want to include in the coverage report. With GOEXPERIMENT=nocoverageredesign they are not included.

If this is removed, how can I remove specific packages from the coverage? For example, I would like to ignore all packages within the paths:

• sdk/generated/**
• **/mocks/*

Is it possible to do that configuration in the go test command?

Hi, I'm not able to tell if this issue has been resolved or is tracked elsewhere, but if we don't set GOEXPERIMENT=nocoverageredesign, we get the following errors for two packages in our repository:

github.com/rilldata/rill/proto/gen/rill/admin/v1: open /tmp/go-build1717652986/b205/covmeta.efd544d54abd57024320e5b09e7fbb7333ec3c9e2c058a3d351094eaca3dd4d6: no such file or directory
github.com/rilldata/rill/proto/gen/rill/runtime/v1: open /tmp/go-build1717652986/b324/covmeta.067b3bf4a6ecbbbcd442d5d3dfcb816dbf6bc1aee18591e902bf98c6b115f2e7: no such file or directory

I believe the error originates from here:

It seems there is some edge case in the coverage redesign where BuildActionCoverMetaFile looks for a cover meta file that doesn't exist.

@begelundmuller thanks for the report. The problem you posted about is being tracked in #65653.