geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kirk Lund <>
Subject Precheckin flakiness
Date Thu, 14 Feb 2019 00:10:59 GMT
Despite our attempts to make precheckin free of flaky failures, I'm still
seeing at least one flaky failure (that does not reproduce and does not
correlate to my PR changes) in every single precheckin launched for my PRs.

For example, the latest one ( is:

*org.apache.geode.internal.cache.ha.HAGIIDUnitTest > testGIIRegionQueue
*    java.lang.AssertionError: Suspicious strings were written to the log
during this run.*
*    Fix the strings or use IgnoredException.addIgnoredException to ignore.*
*    Found suspect string in log4j at line 2703*

* Connection refused (Connection refused)*

I've searched Jira and there is no open ticket for this test. Are we
expected to file new Jira tickets for every single failure I see in
precheckin? And if so, are other developers filing tickets like I am? Or do
we go back to ignoring all of these flaky failures (I don't really consider
this a good option)?

I'm worried that I'm wasting a lot of time filing all of these Jira tickets
if no one is ever going to work on them and then they get bulk closed by
someone 12 months from now...

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message