Comment 9 for bug 1626381

Thanks Kyle.
I will change the revision.
But this issue is not totally fixed, it is still reproduced at about once per 3000 tests.
I have written to some golang experts for help, no response till now.