The nose.failure.Failure.runTest was a missing import in a dtest that was
quickly fixed. We'd ideally have a way to stage dtest changes to catch
these sort of things, but there seems to be a reasonable consensus that
this is a lower priority issue than environmental stability and other test
fixes.

On Tue, Aug 9, 2016 at 7:30 PM, Josh McKenzie <jmcken...@apache.org> wrote:

> Today's unpleasantry: upgrade tests failed to run. This makes
> failure to run to completion on 4 of the last 10 runs. We
> should probably look into stabilizing this test environment and/or
> the tests if tests are causing the full job to fail as a failed run
> is essentially the worst result we can get here.
>
> ===================================================
> testall: No failures!
>
> ===================================================
> dtest: Down to 1 failure
>    topology_test.TestTopology.crash_during_decommission_test
>       CASSANDRA-11611
>       Removed windows label
>       Needs triage
>       Slightly flaky - failed 2 of last 24
>
> ===================================================
> novnode: 5 failures
>    2x cdc_test.TestCDC.test_cdc_data_available_in_cdc_raw
>       Addressed by CASSANDRA-11811
>       Assigned to blambov
>       Removed windows label on that ticket
>       Regression on cdc test, first failure
>    nose.failure.Failure.runTest
>       Honestly, no clue what's up here.
>       Looks like it's failing to find the known_failure method in tools.py
>       ? Anyone have any ideas?
>    bootstrap_test.TestBootstrap.resumable_bootstrap_test
>       Linked to: CASSANDRA-11414 (closed as resolved)
>       Single regression
>       Likely needs triage and a new ticket to track different failure
>    repair_tests.repair_test.TestRepair.test_multiple_concurrent_repairs
>       Linked to: CASSANDRA-12395 (closed as resolved)
>       Different error than ticket
>       Likely needs triage and a new ticket to track different failure
>
> I'm going to be out for a few days so Joel will be taking over on the daily
> email again in my stead.
>
> ~Josh
>



-- 

<http://www.datastax.com/>

Joel Knighton
Cassandra Developer | joel.knigh...@datastax.com

<https://www.linkedin.com/company/datastax>
<https://www.facebook.com/datastax> <https://twitter.com/datastax>
<https://plus.google.com/+Datastax/about>
<http://feeds.feedburner.com/datastax> <https://github.com/datastax/>

<http://cassandrasummit.org/Email_Signature>

Reply via email to