cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10669) Scrub dtests are failing
Date Wed, 11 Nov 2015 03:48:10 GMT


Stefania commented on CASSANDRA-10669:

It's +1 but I think {{reader.descriptor.filenameFor(Component.DATA)}} should perhaps be {{reader.getFilename()}}
at line 159 of A bit more direct although both work.

Incidentally, the warning on a bad file descriptor has always been there, well at least for
a while. It was only when CASSANDRA-9937 redirected the warnings of standalone tools to {{stderr}}
that the tests started failing. However, at the time the tests were already failing for yet
another reason and so it did not get noticed.

CI is here:

It looks OK but we cannot verify the scrub dtests pass on Jenkins until the dtest pull request
is merged. However I've checked locally and they pass.

> Scrub dtests are failing
> ------------------------
>                 Key: CASSANDRA-10669
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Sylvain Lebresne
>            Assignee: Marcus Eriksson
>             Fix For: 3.1
> A [bunch of scrub dtest|] have
been failing for a while. Looking at the history of one of those test, it used to pass reliably
but stopped working a while ago, and the changes when that happened doesn't seem related from
a quick glance. So maybe that's due to a change in the dtest framework (maybe a ccm change

This message was sent by Atlassian JIRA

View raw message