Details
-
Task
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
None
Description
Not having the dtests reporting that they pass make it non-obvious when a new one breaks.
Either fix the tests so that they pass or exclude the known failures from success criteria.
For excluded tests, make sure there is a JIRA covering them so we can make sure someone is following up shortly.
Looking at http://cassci.datastax.com/job/CTOOL_trunk_utest/ it isn't clear if the issue is flapping tests or things being broken and then fixed. Without test history from
Attachments
Issue Links
- blocks
-
CASSANDRA-9042 Make trunk always releasable
- Open
- depends upon
-
CASSANDRA-9356 SSTableRewriterTest fails infrequently
- Resolved
-
CASSANDRA-9512 CqlTableTest.testCqlNativeStorageCollectionColumnTable failed in trunk
- Resolved
-
CASSANDRA-9514 TrackerTest.testAddSSTables fails in 2.2 and trunk
- Resolved
-
CASSANDRA-9516 ViewTest.testSSTablesInBounds fails in trunk
- Resolved
-
CASSANDRA-9271 IndexSummaryManagerTest.testCompactionRace times out periodically
- Resolved
-
CASSANDRA-9001 Triage failing utests
- Resolved
-
CASSANDRA-9002 Bootstrap utests so they pass on trunk
- Resolved
- is blocked by
-
CASSANDRA-9072 MessagePayloadTest.resetCqlQueryHandlerField fails on Java 7
- Resolved
-
CASSANDRA-9073 o.a.c.schema.LegacySchemaTablesTest.dropCf may be flapping
- Resolved
- is duplicated by
-
CASSANDRA-8539 Tests Errors: Latest Cassandra trunk
- Resolved
-
CASSANDRA-9001 Triage failing utests
- Resolved
-
CASSANDRA-9002 Bootstrap utests so they pass on trunk
- Resolved