search

julienschmidt / go-http-routing-benchmark

Go HTTP request router and web framework benchmark
BSD 3-Clause "New" or "Revised" License
1.65k stars 237 forks source link

SIGQUIT when running with -bench=. #44

Closed jbuberel closed 9 years ago

jbuberel commented 9 years ago

Here's a problem I've now run into consistently running the benchmarks using go 1.4.2 and 1.5 (master):

http://pastebin.com/K1QweDns

The SIGQUIT occurs in different places each time, although the stack dumps often mention Beego.

Significantly, these problems were only seen using virtualized Linux instances (VMWare, VirtualBox). Have you seen similar stack dumps running the full suite?

julienschmidt commented 9 years ago

It is quite unusual for an program to send SIGQUIT. AFAIK this signal is usually manually triggered by the user.

If it always happens after roughly the same run time, my best guess would be that it is triggered by go tests timeout. You can set a higher timeout with e.g. go test -timeout=2h -bench=.. But you should see a more helpful explanation in that case.

jbuberel commented 9 years ago

Let me give that a try!

jbuberel commented 9 years ago

Yep - that was it. Just a overall timeout problem. Thanks for the tip.