[ 
https://issues.apache.org/jira/browse/CASSANDRA-18131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Semb Wever updated CASSANDRA-18131:
-------------------------------------------
          Fix Version/s: 4.0.9
                         5.0
                         4.1.2
                             (was: 5.x)
                             (was: 4.0.x)
                             (was: 4.1.x)
          Since Version: 4.0.5
    Source Control Link: 
https://github.com/apache/cassandra/commit/b3256f5bf22c99a8f5410634dd41ca1643a34c1c
             Resolution: Fixed
                 Status: Resolved  (was: Ready to Commit)

Committed as 
[b3256f5bf22c99a8f5410634dd41ca1643a34c1c|https://github.com/apache/cassandra/commit/b3256f5bf22c99a8f5410634dd41ca1643a34c1c]

> LongBTreeTest times out after btree improvements from CASSANDRA-15510
> ---------------------------------------------------------------------
>
>                 Key: CASSANDRA-18131
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18131
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local/Memtable
>            Reporter: Michael Semb Wever
>            Assignee: Maxim Muzafarov
>            Priority: Normal
>             Fix For: 4.0.9, 5.0, 4.1.2
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Happening in both ci-cassandra.a.o and circleci.
> LongBTreeTest is timing out on 4.0, 4.1, trunk branches.
> Started back in mid April 
> (https://github.com/apache/cassandra/commit/018c8e0d5e and 
> https://github.com/apache/cassandra/commit/596daeb7f08). 
> Nightlies shows when the failures started, evident by the 
> 'jdk=jdk_1.8_latest,label=cassandra,split=7/' subfolder missing in the 
> following… 
> - 
> https://nightlies.apache.org/cassandra/trunk/Cassandra-trunk-test-burn/1254/Cassandra-trunk-test-burn/
> - 
> https://nightlies.apache.org/cassandra/cassandra-4.0/Cassandra-4.0-test-burn/343/



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to