Regarding Owen's comments, there has been discussion in past CIO Retros
about changing how stressNewTest runs things. From that, I believe that the
current behavior is that when the number of tests changed is above some
arbitrary number, it doesn't run any of them (please correct me if my
This PR changes 17 tests. At 50 repeats each, that’s 850 tests. I’m not sure
if StressNew does all 850 serially — if it does, they would have to complete in
under 10 seconds per test to duck the concourse timeout (currently set a little
over 2 hours).
Approximately how long do you expect
On the PR for https://github.com/apache/geode/pull/2938, the StressNewTest
and (in two different runs of the same code) other jobs fail occasionally.
I'm inclined to think that the Upgrade and Acceptance test failures were
caused by flaky tests, and I can keep rerunning the PR build.
The
