Re: [go-nuts] Re: Getting new coverage output format from go test -cover

2025-01-21 Thread Paul Chesnais (papacharlie)
osts/go-combined-unit-integration-code-coverage/ > > 2025년 1월 13일 월요일 오전 10시 13분 15초 UTC+9에 Paul Chesnais (papacharlie)님이 작성: > >> The blog post doesn't provide a way to translate the output of `go test >> -coverprofile ...` (which is the so-called legacy text format) into

Re: [go-nuts] Re: Getting new coverage output format from go test -cover

2025-01-12 Thread Paul Chesnais (papacharlie)
at into the new format? On Saturday, January 11, 2025 at 9:26:40 PM UTC-5 Ian Lance Taylor wrote: > On Sat, Jan 11, 2025 at 10:07 AM Paul Chesnais (papacharlie) > wrote: > > > > Is there another forum I can ask about this? Should this be a feature > request against the go team

[go-nuts] Re: Getting new coverage output format from go test -cover

2025-01-11 Thread Paul Chesnais (papacharlie)
:04 PM UTC-5 Paul Chesnais (papacharlie) wrote: > Hello, > > I'd like to be able to merge the data from the output of `go test -cover` > with the output of a run using `go build -cover` but it seems that there's > no way to translate the "legacy" format fro

[go-nuts] Getting new coverage output format from go test -cover

2024-12-03 Thread Paul Chesnais (papacharlie)
Hello, I'd like to be able to merge the data from the output of `go test -cover` with the output of a run using `go build -cover` but it seems that there's no way to translate the "legacy" format from go test into the new binary format. This means it's not possible to use the built-in tooling l