I'm working on a project with some quite complex test code and I'd like to
be able to understand what parts of it are executing for certain tests. I
generated coverage using the go test -coverprofile=coverage.out
command but the coverage file only seems to contain information for non
test
gt; It can sometimes be useful in such situations to look at the pprof "tree"
> output style (as opposed to graph).
>
> Than
>
>
> On Sat, Oct 19, 2019 at 4:14 AM Piers Powlesland <
> pierspowlesl...@gmail.com> wrote:
>
>> Kind of, but due to the sheer numb
from the tree output above.
On Mon, Oct 21, 2019 at 8:10 AM Than McIntosh wrote:
> It can sometimes be useful in such situations to look at the pprof "tree"
> output style (as opposed to graph).
>
> Than
>
>
> On Sat, Oct 19, 2019 at 4:14 AM Piers Powlesland <
> p
in the graph and see the callers?
>
> On Oct 18, 2019, at 8:54 PM, Robert Engels wrote:
>
>
> Yes. When using the command pprof viewer there is a way to show the
> hotspots with the callers. Again I don’t have access to dev at the moment.
>
> On Oct 18, 2019, at 8:44 PM
s than X %,
> and some of that filtering is on by default - so you may want to turn that
> off (can't say for sure since not at dev machine right now).
>
>
>
>
>
> -Original Message-
> >From: Ian Lance Taylor
> >Sent: Oct 18, 2019 2:43 PM
> >T
Hi Ian,
I was on go1.13.2 linux/amd64 so i upgraded to go1.13.3 linux/amd64.
I'm still seeing the same problem.
On Fri, Oct 18, 2019 at 8:43 PM Ian Lance Taylor wrote:
> On Fri, Oct 18, 2019 at 12:37 PM wrote:
> >
> > I used pprof to get an overview of where time is being spent in my
> latest
Hi
I have been looking at go's implementation YCbCr to RGB conversion and
there are a few details that are not clear to me.
The implementation follows the JFIF spec
// The JFIF specification says:
// R = Y' + 1.40200*(Cr-128)
// G = Y' - 0.34414*(Cb-128) - 0.71414*(Cr-128)
// B = Y' + 1.77200
