See https://builds.apache.org/job/Cassandra-quick/535/
--
[...truncated 389 lines...]
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 7.699 sec
[junit]
[junit] Testsuite: org.apache.cassandra.io.LazilyCompactedRowTest
[junit]
See https://builds.apache.org/job/Cassandra/1472/
--
[...truncated 1095 lines...]
[junit] Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 0.875 sec
[junit]
[junit] Testsuite: org.apache.cassandra.gms.ArrivalWindowTest
[junit] Tests
See https://builds.apache.org/job/Cassandra-quick/536/changes
Changes:
[sylvain] Avoid deadlock in migration stage
--
[...truncated 389 lines...]
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 7.169 sec
[junit]
[junit] Testsuite:
See https://builds.apache.org/job/Cassandra/1473/changes
Changes:
[sylvain] Avoid deadlock in migration stage
--
[...truncated 1136 lines...]
[junit]
[junit] Testsuite: org.apache.cassandra.io.sstable.SSTableReaderTest
[junit] Tests run: 7,
See https://builds.apache.org/job/Cassandra-quick/537/
--
[...truncated 457 lines...]
[junit]
[junit] Testsuite: org.apache.cassandra.dht.RangeTest
[junit] Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 0.646 sec
[junit]
[junit]
Hello cassandra-dev,
This is an update on the previous discussion on virtual nodes - for
anyone who missed that, an archive is here:
http://www.mail-archive.com/dev@cassandra.apache.org/msg03837.html
Work on our proposed design is being tracked on JIRA:
Hi Sam, Cassandra,
What interactions with Partitioning Strategies are there for this work? Will
the Random
Partitioner / Order Preserving Partitioner dichotomy remain largely unaffected
through this
change? Is there any potential unlocked or closed off by this move?
Pardon if this is totally
See https://builds.apache.org/job/Cassandra-quick/539/
--
[...truncated 379 lines...]
[junit]
[junit] Testsuite: org.apache.cassandra.io.LazilyCompactedRowTest
[junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 8.431 sec
[junit]
+1
On Fri, Jun 1, 2012 at 1:21 PM, Sylvain Lebresne sylv...@datastax.com wrote:
We've have fixed tons of bugs since 1.1.0 and have nothing critical
outstanding
so I propose the following artifacts for release as 1.1.1.
sha1: a788a23ca6fbb03f991a0c54325c371b4b1dd7cf
Git:
See https://builds.apache.org/job/Cassandra/1476/changes
Changes:
[sylvain] Take supercolumn names and deletion info into account in memtable
throughput
[sylvain] Add back backward compatibility for old style replication factor
[sylvain] Preserve compatibility with pre-1.1 index queries
+1
On Saturday 2 June 2012 at 01:22, Brandon Williams wrote:
+1
On Fri, Jun 1, 2012 at 1:21 PM, Sylvain Lebresne sylv...@datastax.com
(mailto:sylv...@datastax.com) wrote:
We've have fixed tons of bugs since 1.1.0 and have nothing critical
outstanding
so I propose the following
See https://builds.apache.org/job/Cassandra-Coverage/229/
--
Started by an SCM change
Building remotely on ubuntu4 in workspace
https://builds.apache.org/job/Cassandra-Coverage/ws/
Checkout:Cassandra-Coverage /
See https://builds.apache.org/job/Cassandra-quick/541/
--
[...truncated 379 lines...]
[junit]
[junit] Testsuite: org.apache.cassandra.io.LazilyCompactedRowTest
[junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 8.361 sec
[junit]
See https://builds.apache.org/job/Cassandra-quick/542/
--
[...truncated 360 lines...]
[junit] Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 0.638 sec
[junit]
[junit] Testsuite: org.apache.cassandra.gms.ArrivalWindowTest
[junit] Tests
14 matches
Mail list logo