Belatedly...
During our investigation into the application of the FlakyTest category,
we ran the FlakyTest precheckin target approximately 1,500 times over this
past weekend. An abundance of these tests passed without failure. In my
opinion, this provides the base confidence in these tests, an
FYI, most of the intermittent failures I've reviewed and fixed were caused
by a Java GC during a small window in which the test assumes something
asynchronous will complete without using Awaitility. So these tests are
still inherently flaky if you don't change them. Unless you can find the
async ra
Here are two good resources about Flaky tests:
How to Deal With and Eliminate Flaky Tests [1]
An Empirical Analysis of Flaky Tests [2]
[1]
https://semaphoreci.com/community/tutorials/how-to-deal-with-and-eliminate-flaky-tests
[2] http://mir.cs.illinois.edu/~qluo2/fse14LuoHEM.pdf
Pipeline results can be found at:
Concourse:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/144
---
Spring Data GemFire > Nightly-ApacheGeode > #974 failed.
---
Scheduled
No failed tests found, a possible compilation error.
https://build.spring.io/browse/SG
---
Spring Data GemFire > Nightly-ApacheGeode > #974 failed (rerun once).
---
This build was rerun by John Blum.
No failed tests found, a possible compilation err
---
Spring Data GemFire > Nightly-ApacheGeode > #974 was successful (rerun 2 times).
---
This build was rerun by John Blum.
2425 tests in total.
https://build.sp
