An update: the flakiness in raft_consensus_nonvoter-itest has been fixed.
On 11/27/17 6:55 PM, Alexey Serbin wrote:
Yep, that CatalogManagerAddsNonVoter is the new one which was
committed just yesterday.
On 11/27/17 6:53 PM, Alexey Serbin wrote:
The raft_consensus_nonvoter-itest is the set of
Yep, that CatalogManagerAddsNonVoter is the new one which was committed
just yesterday.
On 11/27/17 6:53 PM, Alexey Serbin wrote:
The raft_consensus_nonvoter-itest is the set of tests added for 3-4-3
re-replication improvements. I'm adding more scenarios there right
now, and I'll take care
The raft_consensus_nonvoter-itest is the set of tests added for 3-4-3
re-replication improvements. I'm adding more scenarios there right now,
and I'll take care of the current flaky ones from there as well.
Thanks,
Alexey
On 11/27/17 6:38 PM, Andrew Wong wrote:
N/w! I should have checked
I just realized after re-reading this message that Andrew was about to
look at the flake in delete_table-itest as well. I'm sorry for the
double-effort here, if any. I read this message after posting the patch.
On 11/27/17 12:09 PM, Andrew Wong wrote:
I'm taking a look at tablet_copy-itest
I'll take a look at delete_table-itest (at least I have had a patch in
review for one flake there for a long time).
BTW, it would be much better if it were possible to see the type of
failed build in the dashboard (as it was prior to quasar). Is the type
of a build something inherently
Hey folks,
Looks like our flaky tests have gotten pretty out of hand again, with 6 or
7 of the suites >4% flaky.
Can we get some volunteers to diagnose and fix up these worst offenders?
I'll volunteer for log_rolling-itest and alter_table-test.
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
