Failing tests 2016-09-12

[Joel Knighton]

cassandra-3.9
===
testall: 1 failure
  org.apache.cassandra.db.lifecycle.LogTransactionTest
  .testUnparsableFirstRecord-compression
CASSANDRA-12632. New failure, needs triage. I've never seen this
fail on any branch.

===
dtest && novnode:
  Failed to fetch test results due to environmental issues.

===
upgrade: 3 failures
  upgrade_tests.storage_engine_upgrade_test
  .TestBootstrapAfterUpgrade
  .upgrade_with_range_tombstone_eoc_0_test
  New failure, yet to be triaged.

  upgrade_tests.storage_engine_upgrade_test
  .TestStorageEngineUpgrade
  .upgrade_with_range_tombstone_eoc_0_test
  New failure, yet to be triaged. Looks very similar to the failure
above.

  upgrade_tests.paging_test
  .TestPagingWithDeletionsNodes2RF1_Upgrade_current_2_1_x_To_indev_3_x
  .test_failure_threshold_deletions
  New failure, yet to be triaged. Looks like it is due to a mistake
  in recent revisions to the test.


trunk
===
testall: 10 failures
  All timeouts in a string of tests that most frequently timeout when the
  system has degraded I/O performance.

===
dtest: All passed!

===
novnode: 2 failures
  repair_tests.repair_test.TestRepairDataSystemTable
  .repair_parent_table_test
New failure. It looks like stress failed to create a keyspace.

  user_types_test.TestUserTypes.test_type_as_part_of_pkey
New failure. It looks like it was broken by CASSANDRA-11031 and
a PR fixing the test is in progress.

===
upgrade: 1 failure
  upgrade_tests.paging_test
  .TestPagingDataNodes2RF1_Upgrade_current_2_2_x_To_indev_3_x
  .static_columns_paging_test
  CASSANDRA-11195. The fix has been committed since this run.


ASF Infra
  No significant updates. I think there's been discussion of somehow
  contributing Cassandra specific resources to the ASF CI pool, but
  I don't know much about this. If anyone does, feel free to reply!

Re: Proposal: create a mailing list for just the newly created Jira ticket notifications

[Jeremy Hanna]

It sounds like people generally prefer subscribing to Jira filters.  I’ll just 
keep my message rules then from the commits@ mailing list.

Thanks all.

Jeremy

> On Aug 29, 2016, at 12:32 PM, Patrick McFadin  wrote:
> 
> I have one setup for new AND updated. Very handy to seeing activity
> progression.
> 
> Jira has some really nice query + notification settings if you want to get
> more granular.
> 
> On Mon, Aug 29, 2016 at 10:12 AM, Jonathan Haddad  wrote:
> 
>> Wow, I am embarrassed to say that I had no idea that existed.  Thanks Russ!
>> 
>> On Mon, Aug 29, 2016 at 9:58 AM Russell Hatch  wrote:
>> 
>>> This is currently possible using jira saved search + subscription.
>> Create a
>>> new saved search with a query like:
>>> 
>>> project = CASSANDRA AND created >= -24h ORDER BY createdDate DESC
>>> 
>>> When viewing your filter, go to Details > New Subscription and set it up
>> to
>>> run once a day and you're set!
>>> 
>>> Hope it helps,
>>> 
>>> Russ
>>> 
>>> On Mon, Aug 29, 2016 at 10:45 AM, Jonathan Haddad 
>>> wrote:
>>> 
 A daily digest of new issues would be incredible.  A non-binding +1
>> from
 this guy.
 
 
 On Mon, Aug 29, 2016 at 8:58 AM Jeremy Hanna <
>> jeremy.hanna1...@gmail.com
 
 wrote:
 
> Currently we have a mailing list (commits@) that includes commit
 messages
> as well as all updates to Jira tickets.  However for the purpose of
 staying
> up to date with new tickets, it’s something of a firehose with the
>>> rapid
> rate of change.
> 
> Some people (like me) filter out just the new ticket creation emails
>>> and
> watch/vote for those that seem interesting.  Others create Jira
>> filters
 and
> subscribe to them.  Personally I prefer an email per Jira creation.
>>> For
> those that prefer that route, would anyone mind if I created an infra
> ticket to create a mailing list to just publish those emails?  Are
>>> there
> others like me out there that prefer that to doing a daily digest or
> something similar?
> 
> Thanks,
> 
> Jeremy
 
>>> 
>>