{"push_id":863276955,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"b5a0c67fcc2f87b5e2fd04e023f9a0b2f3d759da","before":"d54c35675c1f4d4ca9b5a6de568e977c513f364a","commits":[{"sha":"b5a0c67fcc2f87b5e2fd04e023f9a0b2f3d759da","author":{"email":"7ea35d812706d9213868749011af1ed4fa2f6aa0@google.com","name":"Austin Clements"},"message":"test: force heap profile update in heapsampling.go test\n\nThe heapsampling.go test occasionally fails on some architectures\nbecause it finds zero heap samples in main.alloc. This happens because\nthe byte and object counts are only updated at a GC. Hence, if a GC\nhappens part way through allocInterleaved, but then doesn't happen\nafter we start calling main.alloc, checkAllocations will see buckets\nfor the lines in main.alloc (which are created eagerly), but the\nobject and byte counts will be zero.\n\nFix this by forcing a GC to update the profile before we collect it.\n\nFixes #13098.\n\nChange-Id: Ia7a9918eea6399307f10499dd7abefd4f6d13cf6\nReviewed-on: https://go-review.googlesource.com/16846\nRun-TryBot: Austin Clements <austin@google.com>\nTryBot-Result: Gobot Gobot <gobot@golang.org>\nReviewed-by: Dmitry Vyukov <dvyukov@google.com>","distinct":true,"url":"https://api.github.com/repos/mk0x9/go/commits/b5a0c67fcc2f87b5e2fd04e023f9a0b2f3d759da"}]}