{"push_id":1295031372,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"d00a3cead8423c8af6c5781aa2a3efe0a9a442ae","before":"6ca7c2055bd114c08426d3dbdee444b280b569b6","commits":[{"sha":"d00a3cead8423c8af6c5781aa2a3efe0a9a442ae","author":{"name":"Keith Randall","email":"ae06bff050675a0e7c0005beb983046badc26cda@golang.org"},"message":"runtime: make gdb test resilient to line numbering\n\nDon't break on line number, instead break on the actual call.\nThis makes the test more robust to line numbering changes in the backend.\n\nA CL (28950) changed the generated code line numbering slightly.  A MOVW\n$0, R0 instruction at the start of the function changed to line\n10 (because several constant zero instructions got CSEd, and one gets\npicked arbitrarily).  That's too fragile for a test.\n\nChange-Id: I5d6a8ef0603de7d727585004142780a527e70496\nReviewed-on: https://go-review.googlesource.com/29085\nRun-TryBot: Keith Randall <khr@golang.org>\nReviewed-by: Brad Fitzpatrick <bradfitz@golang.org>\nTryBot-Result: Gobot Gobot <gobot@golang.org>","distinct":true,"url":"https://api.github.com/repos/golang/go/commits/d00a3cead8423c8af6c5781aa2a3efe0a9a442ae"}]}
{"actor":{"display_login":"gopherbot"}}