On Sat, Aug 4, 2018 at 7:35 AM Anthony Fok <f...@debian.org> wrote: > For some reasons, however, I have been unable to reproduce this test > FAIL on my own machine. >
It always fails on my cpu-busy server(same in upstream issue report) > So, yes, skipping TestExecutableDelete is the entirely pragmatic thing > to do, but there is this little voice in my gut urging me to learn to > diagnose what exactly triggers this intermittent test failure, and if > it is indeed a race condition, how to fix it? :-) The race is when os.Remove and os.Executable are called. I don't see there's a fix instead of rewriting the logic... -- Best regards, Shengjing Zhu
