In lieu of a weekly wrap-up, here's a pre-Thanksgiving call for help. If you haven't been paying attention to JIRA, you likely didn't notice that Josh went through and triage/categorized a bunch of issues by adding components, and Michael took the time to open a bunch of JIRAs for failing tests.
How many is a bunch? Something like 35 or so just for tests currently failing on trunk. If you're a regular contributor, you already know that dtests are flakey - it'd be great if a few of us can go through and fix a few. Even incremental improvements are improvements. Here's an easy search to find them: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+CASSANDRA+AND+component+%3D+Testing+ORDER+BY+updated+DESC%2C+priority+DESC%2C+created+ASC&mode=hide If you're a new contributor, fixing tests is often a good way to learn a new part of the codebase. Many of these are dtests, which live in a different repo ( https://github.com/apache/cassandra-dtest ) and are in python, but have no fear, the repo has instructions for setting up and running dtests( https://github.com/apache/cassandra-dtest/blob/master/INSTALL.md ) Normal contribution workflow applies: self-assign the ticket if you want to work on it, click on 'start progress' to indicate that you're working on it, mark it 'patch available' when you've uploaded code to be reviewed (in a github branch, or as a standalone patch file attached to the JIRA). If you have questions, feel free to email the dev list (that's what it's here for). Many thanks will be given, - Jeff
