cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-10492) Fix failing upgrade tests on 2.1->2.2 path
Date Tue, 03 Nov 2015 20:24:27 GMT


Ariel Weisberg updated CASSANDRA-10492:
    Attachment: test_stdout.txt

I was able to run all the upgrade tests without failures using

{code}UPGRADE_TO="2.2.2" JDK_VERSION=1.8_60 NUM_TOKENS=32 SKIP=FALSE PRINT_DEBUG=true nosetests
upgrade_tests -x -s -v --with-flaky --verbosity=3 --with-xunit --nocapture 2>&1 | tee
-a test_stdout.txt{code}

The output is attached.

Environment variables were

I'll hit the tests that are failing in cassci a little harder to see if I can get them to

> Fix failing upgrade tests on 2.1->2.2 path
> ------------------------------------------
>                 Key: CASSANDRA-10492
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jim Witschey
>            Assignee: Ariel Weisberg
>              Labels: triage
>             Fix For: 2.1.x, 2.2.x
>         Attachments: test_stdout.txt
> 2 dtests for the storage engine upgrade on the 2.1->2.2 path fail:
> (If there are 3 failures at that link, don't worry; one was a dtest bug that's been fixed.)
> {{upgrade_tests/}} flaps when a TRUNCATE operation
times out:
> {{upgrade_tests/}}
also fails on this upgrade path:
> These are in the same ticket for the moment, but if one becomes a longer project, it
should be broken out into a separate ticket.

This message was sent by Atlassian JIRA

View raw message