Re: March 2015 QA retrospective

This does create a strange incentive structure, though: we currently (even with 1-3m patch cycles) don't fix every bug with every release. So if we cannot commit a bug fix without a corresponding sufficient test coverage, then we are potentially reducing the number of bug fixes we will incorporate

Re: March 2015 QA retrospective

CASSANDRA-8285 Aleksey Yeschenko Move all hints related tasks to hints private executor Pierre's reproducer represents something we weren't doing, but that users are. Is that now being tested? That particular issue will not happen again. That

Re: March 2015 QA retrospective

Hi Benedict, This only requires unit testing or dtests to be run this way. However for > the kitchen sink tests this is just another dimension in the configuration > state space, which IMO should be addressed as a whole methodically. Perhaps > we should file a central JIRA, or the Google doc you s

Re: March 2015 QA retrospective

On Fri, Apr 10, 2015 at 8:34 PM, Ariel Weisberg wrote: > Hi Marcus, > > CASSANDRA-8211 > Overlapping > sstables in L1+ > > So the question I would ask is would the workload that reproduces this > specific bug be interesting in the general sen

Re: March 2015 QA retrospective

> > CASSANDRA-8459 > "autocompaction" > on reads can prevent memtable space reclaimation > > Can you link a ticket to CASSANDRA-9012 and characterize in a way we can > try and implement how to make sufficiently large partitions, over > sufficie

Re: March 2015 QA retrospective

Hi, *CASSANDRA-8550 - Internal pagination in CQL3 index queries creating substantial overhead* Disabling things via flags would be a good safeguard like Java -XX flags to enable experimental things. It's just more work. I am talking about users. When you release monthly and discourage long runnin

Re: March 2015 QA retrospective

Hi, OK, can you file and link a ticket to CASSANDRA-9012 that we should test the commands that nodetool supports? Thanks, Ariel On Fri, Apr 10, 2015 at 2:09 PM, Carl Yeksigian wrote: > CASSANDRA-8028 > > Carl Yeksigian > > Unable > > to co

Re: March 2015 QA retrospective

Hi Sam, CASSANDRA-8280 Cassandra crashing on inserting data over 64K into indexed strings Added tests are good example, could focusing on testing all access paths and boundary conditions per access path have prevented Can you create a ticket

Re: March 2015 QA retrospective

CASSANDRA-8687 > Jeremiah Jordan > Keyspace > should also check Config.isClientMode Is there a way to test for missing > Config.isClientMode checks? We should probably redo the client mode type stuff. Code should assume we are in a tool unt

Re: March 2015 QA retrospective

CASSANDRA-8292 From Pig: org.apache.cassandra.exceptions.ConfigurationException: Expecting URI in variable: [cassandra.config]. Please prefix the file with file:/// for local files or file:/// for remote files. PIG not tested As advertised. I didn't run the pig tests before commit so that's 100% o

Re: March 2015 QA retrospective

Here is my response. T Jake Luciani Null pointer after droping keyspace Add/drop keyspace not tested under load, with server logs checked for errors To detect this we would need a test to write to a table, wait for compaction to start then d

Re: March 2015 QA retrospective

Here are my responses for my tickets: CASSANDRA-7910 - wildcard prepared statements are incorrect after a column is added to the table As part of the ticket, I added general dtests for prepared statement invalidation after ALTER TABLE statements: https://github.com/riptano/cassandra-dtest/blob/18

Re: March 2015 QA retrospective

Repeated with sort *Key* *Assignee* *Summary* *Revisit reason* CASSANDRA-8285 Aleksey Yeschenko Move all hints related tasks to hints private executor Pierre's reproducer represents something we weren't doing, but that users are. Is that no

Re: March 2015 QA retrospective

Could you sort the ticket list by assignee so people just have to look for their name once? On Thu, Apr 9, 2015 at 12:43 PM, Ariel Weisberg wrote: > Hi, > > Thanks Philip. > > For items in went poorly, is there anything we could change or should have > done differently to get contributor branche

Re: March 2015 QA retrospective

Hi, Thanks Philip. For items in went poorly, is there anything we could change or should have done differently to get contributor branches running in CI? I don’t recall us setting a fixed goal for when that had to be done. There are two angles to evaluate this from and decide if there is a probl

Re: March 2015 QA retrospective

To add to this: *Went well* Tyler Hobbs has reduced failing dtests on trunk by ~90%. By next month, test results should be at 100% pass. *Went poorly* We've failed to make progress on running the full test suite across all contributor branches. By the end of this month, I assume we will at least

March 2015 QA retrospective

Hi all, It’s time for the first retrospective. For those not familiar this is the part of the development process where we discuss what is and isn’t working when it comes to making reliable releases. We go over the things that worked, the things that didn’t work, and what changes we are going t