Indeed, this is what I just checked this morning and saw whil generating
coverage info on a "per package" basis
I'll check the issue status over the next weeks
Thanks for your help
Best regards
Le jeudi 28 février 2019 01:07:55 UTC+1, Krzysztof Kowalczyk a écrit :
>
> https://github.com/golang/g
Hello,
Just after the new release of go 1.12, I migrated my project to use the new
version.
Every thing went fine so far, all tests and code coverage reports were
generated accruately just like before.
Once done I activated GO111MODULE option to get rid of the dep dependency
manager we were us
Hello,
Just after the new release of go 1.12, I migrated my project to use the new
version.
Every thing went fine so far, all tests and code coverage reports were
generated accruately just like before.
Once done I activated GO111MODULE option to get rid of the dep dependency
manager we were us
The code used in the playground was unfortunately not the proper one here
is a link to the new code
https://play.golang.org/p/kbRsWxsQwE0
since current version of playground (as of 2018-09-03) is still 1.10.3 the
playground does not show the issue
I've logged an issue there to track the resolut