I don't have any objection to this, really. I know I rely on a handful of
nose plugins, and possibly others do, but those should be easy enough to
re-write. I am curious though, what's the impetus for this? Is there some
pytest feature we want that nose lacks? Is there some nosetest bug or
trunk:
===
testall: 2 failures
org.apache.cassandra.service.RemoveTest
.testLocalHostId
CASSANDRA-9541.
org.apache.cassandra.db.KeyspaceTest
.testLimitSSTables
New failure. Needs a jira ticket.
trunk:
===
testall: 2 failures
org.apache.cassandra.service.RemoveTest
.testLocalHostId
CASSANDRA-9541.
org.apache.cassandra.dht.tokenallocator.ReplicationAwareTokenAllocatorTest
.testNewClusterWithMurmur3Partitioner
This times out every
Hi All,
3.9 was released, so I've dropped it from this email.
trunk:
===
testall: 4 failures
org.apache.cassandra.config.DatabaseDescriptorRefTest
.testDatabaseDescriptorRef
org.apache.cassandra.config.DatabaseDescriptorRefTest
sandra-dtest/pull/1214
>
> I've rebased and currently re-running tests.
>
> On Wed, Sep 28, 2016 at 6:23 PM Philip Thompson <
> philip.thomp...@datastax.com> wrote:
>
> > Hi All,
> >
> > cassandra-3.9:
> > ===
Hi All,
cassandra-3.9:
===
testall: All passed!
===
dtest: All passed!
===
upgrade: All passed!
===
Hi All,
cassandra-3.9:
===
testall: 5 failures
org.apache.cassandra.cql3.ViewFilteringTest
.testMVCreationSelectRestrictions
org.apache.cassandra.cql3.ViewFilteringTest
.testClusteringKeyFilteringRestrictions
org.apache.cassandra.cql3.ViewTest
re releasing 3.6.
>
> On Thu, May 12, 2016 at 12:44 PM, Philip Thompson <
> philip.thomp...@datastax.com> wrote:
>
> > I've updated the TE report with the results of the upgrade testing we
> did.
> > We experienced a higher than expected number of test failures, wh
I've updated the TE report with the results of the upgrade testing we did.
We experienced a higher than expected number of test failures, which
prompted the filing of:
CASSANDRA-11760
CASSANDRA-11763
CASSANDRA-11765
CASSANDRA-11767
Two errors were related to handling the legacy hint format after
/jira/browse/CASSANDRA-9007 which is the root
for a new kitchen sink style test that validates the entire feature set
together in a black box fashion. Philip Thompson has a basic job running so
we are close to (or at) the tipping point where the doneness criteria for
every ticket needs to include
for
a particular slice of C* versions, e.g. 2.0.X x 2.1.3.
On Fri, Jan 9, 2015 at 12:01 PM, Tyler Hobbs ty...@datastax.com wrote:
On Thu, Jan 8, 2015 at 2:23 PM, Philip Thompson
philip.thomp...@datastax.com wrote:
I expect the benefits to grow as we make more radical changes
to cassandra
to Cassandra that use or
contribute to cassandra-dtest. Are you in favor of this change?
Thanks,
Philip Thompson
https://github.com/riptano/cassandra-dtest/compare/cassandra-2.0
https://github.com/riptano/cassandra-dtest/compare/cassandra-2.1
https://github.com/riptano/cassandra-dtest/compare/trunk
://cassci.datastax.com/job/cassandra-2.1_dtest_pydriver/
Thanks,
Philip Thompson
13 matches
Mail list logo