Upgrade tests are probably broken because we haven't been running them since the move to ASF jenkins (I believe). I'll start having a look at some MV test failures.
On 17 November 2017 at 14:34, Josh McKenzie <jmcken...@apache.org> wrote: > > > > Do we have any volunteers to fix the broken Materialized Views and CDC > > DTests? > > I'll try to take a look at the CDC tests next week; looks like one of the > base unit tests is failing as well. > > On Fri, Nov 17, 2017 at 12:09 AM, Michael Kjellman < > mkjell...@internalcircle.com> wrote: > > > Quick update re: dtests and off-heap memtables: > > > > I’ve filed CASSANDRA-14056 (Many dtests fail with ConfigurationException: > > offheap_objects are not available in 3.0 when OFFHEAP_MEMTABLES=“true”) > > > > Looks like we’re gonna need to do some work to test this configuration > and > > right now it’s pretty broken... > > > > Do we have any volunteers to fix the broken Materialized Views and CDC > > DTests? > > > > best, > > kjellman > > > > > > > On Nov 15, 2017, at 5:59 PM, Michael Kjellman < > > mkjell...@internalcircle.com> wrote: > > > > > > yes - true- some are flaky, but almost all of the ones i filed fail > 100% > > (💯) of the time. i look forward to triaging just the remaining flaky > ones > > (hopefully - without powers combined - by the end of this month!!) > > > > > > appreciate everyone’s help - no matter how small... i already > personally > > did a few “fun” random-python-class-is-missing-return-after-method > stuff. > > > > > > we’ve wanted this for a while and now is our time to actually execute > > and make good on our previous dev list promises. > > > > > > best, > > > kjellman > > > > > >> On Nov 15, 2017, at 5:45 PM, Jeff Jirsa <jji...@gmail.com> wrote: > > >> > > >> 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 > > > > >
