forked from apache/cassandra
-
Notifications
You must be signed in to change notification settings - Fork 22
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Enable DEFAULT_IS_NODE_AWARE for testing
- Loading branch information
1 parent
6f6d711
commit 8c4b186
Showing
1 changed file
with
2 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
8c4b186
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Build rejected: 2389 NEW test failure(s) in 4 builds., Build 4: ran 17001 tests with 2417 failures and 111 skipped.
Butler analysis done on ds-cassandra-pr-gate/node-aware-shard-manager vs last 16 runs of ds-cassandra-build-nightly/main.
Showing only first 13 NEW test failures
org.apache.cassandra.db.commitlog.BatchCommitLogTest.testHeaderOnlyFileFiltering[5]: test failed in the recent build. No failures on upstream;
branch story: [F+++] vs upstream: [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]; [NEW]
org.apache.cassandra.distributed.test.FullRepairCoordinatorNeighbourDownTest.validationParticipentCrashesAndComesBack[SEQUENTIAL/true]: test failed in the recent build. No failures on upstream;
branch story: [F+++] vs upstream: [++++++++++++++++]; [NEW]
org.apache.cassandra.distributed.test.FullRepairCoordinatorFastTest.simple[SEQUENTIAL/true]: test failed in the recent build. No failures on upstream;
branch story: [F+++] vs upstream: [++++++++++++++++]; [NEW]
org.apache.cassandra.io.sstable.LegacySSTableTest.testAutomaticUpgrade: test failed in the recent build. No failures on upstream;
branch story: [F+++] vs upstream: [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]; [NEW]
org.apache.cassandra.db.RecoveryManagerFlushedTest.testWithFlush[1]: test failed in the recent build. No failures on upstream;
branch story: [F+++] vs upstream: [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]; [NEW]
org.apache.cassandra.db.RecoveryManagerTest.testRecoverPIT[2]: test failed in the recent build. No failures on upstream;
branch story: [F+++] vs upstream: [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]; [NEW]
org.apache.cassandra.db.commitlog.BatchCommitLogTest.testEqualRecordLimit[4]: test failed in the recent build. No failures on upstream;
branch story: [F+++] vs upstream: [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]; [NEW]
org.apache.cassandra.distributed.test.PreviewRepairCoordinatorNeighbourDownTest.validationParticipentCrashesAndComesBack[SEQUENTIAL/false]: test failed in the recent build. No failures on upstream;
branch story: [F+++] vs upstream: [++++++++++++++++]; [NEW]
org.apache.cassandra.db.VerifyTest.testVerifyPartitionIndex: test failed in the recent build. No failures on upstream;
branch story: [F+++] vs upstream: [+S+++S+++S+++S+++S+++S+++S+++S+++S+++S+++S+++S+++S+++S+++S++]; [NEW]
org.apache.cassandra.cql3.validation.operations.SelectTest.testListContainsWithIndex: test failed in the recent build. No failures on upstream;
branch story: [F+++] vs upstream: [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]; [NEW]
org.apache.cassandra.db.commitlog.GroupCommitLogTest.testHeaderOnlyFileFiltering[2]: test failed in the recent build. No failures on upstream;
branch story: [F+++] vs upstream: [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]; [NEW]
org.apache.cassandra.db.VerifyTest.testVerifyRowIndex: test failed in the recent build. No failures on upstream;
branch story: [F+++] vs upstream: [+S+++S+++S+++S+++S+++S+++S+++S+++S+++S+++S+++S+++S+++S+++S++]; [NEW]
org.apache.cassandra.db.NameSortTest.testNameSort100: test failed in the recent build. No failures on upstream;
branch story: [F+++] vs upstream: [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]; [NEW]
butler comparison
8c4b186
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@blambov - here are the test results from enabling node awareness by default. I'll review today
8c4b186
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There were a lot of failures. I think it was due to a faulty
rangeSpanned
implementation. That's fixed in the next commit.