Sorry for jumping in so boldly before.
TL;DR:
- I didn't mean to delete every flaky test just like that
- To improve quality, each failing test has to be analyzed individually
for release
More thoughts on that:
I had a closer look on some of the tests tagged as flaky and realized that
Thanks for your thoughts on testing Apache Cassandra, I share them.
I just wanted to note that the known_failure() annotations were recently
removed from cassandra-dtest [0], due to lack of annotation removal when
bugs fixed, and the internal webapp that we were using to parse has been
broken for
Hi Michael,
Thanks for this update. As a newbie it helped me to understand the
organization and processes a little bit better.
I don't know how many CS-devs know this but I love this rule (actually the
whole book):
http://programmer.97things.oreilly.com/wiki/index.php/The_Boy_Scout_Rule
I person
