Please don't forget that we are NOT supposed to ignore failures in
FlakyTest. That was never the intention of FlakyTest. The intention was
this:
1) run the test under a testing target that ALWAYS forks (or forks every 30
distributed test cases) -- this was enough to stabilize many of these
flicker
These problems stem from a dirty testing environment occupying the default
port, which this test wants to use. I have a pull request open to ignore
the test when the default port is not available.
On the one hand, an ignored test is essentially dead code. If the test is
consistently skipped and
