@Kirk, I share your concern. If the builds are RED then we should
address them. Ideally there should be no flaky tests, but given the
hyper-threaded nature of the beast, things can go wrong that are really
hard to reproduce. Arguably, even those scenarios should be addressed,
but if we wait for
This is topic is very relevant given that we are working towards a 1.2.0
release. In order to release we need—at the very minimum--a clean pass through
distributedTest.
Recently we’ve had some instability that has contributed to failing tests.
Anthony
> On May 24, 2017, at 4:54 PM, Kirk Lun
If other people are ignoring the results of the flakyTest target and that's
the reason that people do not want to add FlakyTest category to tests that
aren't currently marked with FlakyTest then here's my proposal... we delete
FlakyTest category (well actually just rename it) and replace it with
Te
