Re: distributed test harness

Yes, it's at: test/distributed/README.txt The repo is basically a branch of 0.7. We're more than happy to assist anyone w/ setting up and bootstrapping the test harness -Kelvin On Tue, Dec 14, 2010 at 5:51 PM, Jonathan Ellis wrote: > Great! > > Is there a README for the test harness? (github

Re: distributed test harness

Great! Is there a README for the test harness? (github is picking up the cassandra one) On Tue, Dec 14, 2010 at 7:45 PM, Kelvin Kakugawa wrote: > Hi devs, > > A number of us have been doing our own ad-hoc distributed testing. i.e. > manually putting up a cluster and then running a script to p

distributed test harness

Hi devs, A number of us have been doing our own ad-hoc distributed testing. i.e. manually putting up a cluster and then running a script to perform a series of tests against it. [e.g., see: CASSANDRA-1072's increment_test.py] However, this approach does not scale and we'd like to formalize a di

Build failed in Hudson: Cassandra #630

See Changes: [gdusbabek] merge from 0.7 -- [...truncated 1448 lines...] [junit] Testsuite: org.apache.cassandra.db.MultitableTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapse

Re: AssertionError: attempted to delete non-existing file CommitLog-1292324828581.log

https://issues.apache.org/jira/browse/CASSANDRA-1790, fixed in rc2 On Tue, Dec 14, 2010 at 6:31 PM, Rishi Bhardwaj wrote: > Has anyone seen this assert failure below? Seems like a race to delete a > commit > log file. I am running 0.7-beta1, I was wondering if this has already been > fixed, in wh

Re: AssertionError: attempted to delete non-existing file CommitLog-1292324828581.log

On Tue, Dec 14, 2010 at 6:31 PM, Rishi Bhardwaj wrote: > Has anyone seen this assert failure below? Seems like a race to delete a > commit > log file. I am running 0.7-beta1, I was wondering if this has already been > fixed, in which case I can merge that fix in my current tree. > I seem to remem

AssertionError: attempted to delete non-existing file CommitLog-1292324828581.log

Has anyone seen this assert failure below? Seems like a race to delete a commit log file. I am running 0.7-beta1, I was wondering if this has already been fixed, in which case I can merge that fix in my current tree. INFO [FLUSH-WRITER-POOL:1] 2010-12-14 03:12:38,364 Memtable.java (line 157) C

Re: Any chance of getting cassandra releases published to repo1.maven.org?

On Tue, 2010-12-14 at 19:39 +, Stephen Connolly wrote: > Well one piece of evidence is that the ivy.xml does not look to have > been kept in sync with the binaries in the lib directory... That is my > argument for not keeping binaries in lib folders... No, the contents of lib/ are runtime dep

Re: Any chance of getting cassandra releases published to repo1.maven.org?

On Tue, 2010-12-14 at 17:02 +0100, Bjorn Borud wrote: > Eric Evans writes: > > > I have little faith at this point that maintaining a pom.xml is > going to > > work for us. > > why? (if you have answered this question before I apologize) This has come up a lot, the list archives tell the stor

Hudson build is back to normal : Cassandra-0.7 #81

See

Build failed in Hudson: Cassandra #629

See Changes: [brandonwilliams] Always put schema state in local gossip. Patch by gdusbabek, reviewed by brandonwilliams for CASSANDRA-1824 -- [...truncated 1470 lines...] [junit] Testsuite:

Build failed in Hudson: Cassandra-0.7 #80

See Changes: [brandonwilliams] Always put schema state in local gossip. Patch by gdusbabek, reviewed by brandonwilliams for CASSANDRA-1824 -- [...truncated 1436 lines...] [junit] Testsui

Re: Internal error processing batch_mutate

Looks like https://issues.apache.org/jira/browse/CASSANDRA-1860, which we think is fixed in latest 0.7 branch (as of yesterday). On Sat, Dec 11, 2010 at 6:40 AM, Timo Nentwig wrote: > I assume this is not supposed to happen (?) 0.7rc2 (think I also > experienced this a few times on rc1). Just FYI

Re: Any chance of getting cassandra releases published to repo1.maven.org?

> I will say this once and only once, if you want to migrate to a maven based > build, I could help... However I do not want to mix issues, I'm quite > prepared to work with the current build system, there is a community of > developers here that seem happy with the existing build system, they are

Re: Any chance of getting cassandra releases published to repo1.maven.org?

Well one piece of evidence is that the ivy.xml does not look to have been kept in sync with the binaries in the lib directory... That is my argument for not keeping binaries in lib folders... You don't know exactly where they came from, or that they actually are the version they claim to be... Of c

Hudson build is back to normal : Cassandra-0.7 #79

See

Build failed in Hudson: Cassandra-0.7 #78

See Changes: [jbellis] make inner classes static where possible patch by Dave Brosius; reviewed by jbellis for CASSANDRA-1845 -- [...truncated 1409 lines...] [junit] at org.apache.cas

Re: Any chance of getting cassandra releases published to repo1.maven.org?

Eric Evans writes: > I have little faith at this point that maintaining a pom.xml is going to > work for us. why? (if you have answered this question before I apologize) -Bjørn