Re: [go-nuts] Question about go test and -cpuprofile

I thought that hitting CTRL+C(i.e. sending SIGINT) is a relatively common way to abort tests that run for too long. суббота, 4 марта 2017 г., 10:32:47 UTC+5 пользователь Ian Lance Taylor написал: > > On Fri, Mar 3, 2017 at 9:18 PM, > > wrote: > >> I would not expect to get a CPU profile if yo

Re: [go-nuts] Question about go test and -cpuprofile

> > I would not expect to get a CPU profile if you hit ^C. > Just curious as of why? I mean we could use *signal.Notify* for that, no? пятница, 3 марта 2017 г., 23:04:30 UTC+5 пользователь Ian Lance Taylor написал: > > On Fri, Mar 3, 2017 at 9:41 AM,

[go-nuts] Question about go test and -cpuprofile

Say you have a package with a test suite that completes in 30 seconds on average. You run: go test -cpuprofile cpu.pprof -timeout 10s > Then whether you abort tests by hitting CTRL+C or they end with a panic due to a low timeout value, in both cases, *cpu.pprof* will be empty. Is this intended b

[go-nuts] bombardier - Fast cross-platform HTTP benchmarking tool written in Go

https://github.com/codesenberg/bombardier I just released a v1.0 of my benchmarking tool. If you have been looking for a *wrk*/*weighttp *replacement for Windows or want something more performant than, say, *ab*/*siege*/*hey*/*vegeta*