[
https://issues.apache.org/jira/browse/CASSANDRA-16526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-16526:
-----------------------------------------
Test and Documentation Plan: run the test a lot
Status: Patch Available (was: In Progress)
What I've determined is that any of these tests can run together in the suite
with no problem, as long as testPut and/or testOffer are not mixed with the
truncation test, and even then most of time nothing fails.
But every once in a while, through no fault of their own, these tests seem to
confuse Chronicle when it goes to read logs in testTrucationReleasesLogSpace,
where it sometimes expects to see a file _that it deleted itself_. Since these
work fine in isolation and the failure is quite rare, I've taken the route of
running it twice under the flakyTest handler so that a failure one time is
tolerated. The patch also modernizes the temporary directory creation and
fixes the 'trucation' typo in the test name.
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/530/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/530/pipeline]
> BinLogTest is flaky
> -------------------
>
> Key: CASSANDRA-16526
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16526
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 4.0-rc
>
>
> Probably due to increasing the runners:
> {noformat}
> java.lang.RuntimeException: java.lang.IllegalStateException: Expected file to
> exist for cycle: 1616021848, file:
> /home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test-compression/jdk/jdk_11_latest/label/cassandra/tmp/foo17bar/20210317-225728T.cq4.
> minCycle: 1616021850, maxCycle: 1616021852
> Available files: [20210317-225730T.cq4, 20210317-225732T.cq4]
> at
> org.apache.cassandra.utils.binlog.BinLogTest.readBinLogRecords(BinLogTest.java:492)
> at
> org.apache.cassandra.utils.binlog.BinLogTest.lambda$testTrucationReleasesLogSpace$8(BinLogTest.java:444)
> at org.apache.cassandra.Util.spinAssertEquals(Util.java:605)
> at org.apache.cassandra.Util.spinAssertEquals(Util.java:595)
> at
> org.apache.cassandra.utils.binlog.BinLogTest.testTrucationReleasesLogSpace(BinLogTest.java:444)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Caused by: java.lang.IllegalStateException: Expected file to exist for cycle:
> 1616021848, file:
> /home/jenkins/jenkins-slave/workspace/Cassandra-devbranch-test-compression/jdk/jdk_11_latest/label/cassandra/tmp/foo17bar/20210317-225728T.cq4.
> minCycle: 1616021850, maxCycle: 1616021852
> Available files: [20210317-225730T.cq4, 20210317-225732T.cq4]
> at
> net.openhft.chronicle.queue.impl.single.SingleChronicleQueue$StoreSupplier.nextCycle(SingleChronicleQueue.java:1157)
> at
> net.openhft.chronicle.queue.impl.WireStorePool.nextCycle(WireStorePool.java:66)
> at
> net.openhft.chronicle.queue.impl.single.SingleChronicleQueue.nextCycle(SingleChronicleQueue.java:507)
> at
> net.openhft.chronicle.queue.impl.single.StoreTailer.nextIndexWithNextAvailableCycle(StoreTailer.java:507)
> at
> net.openhft.chronicle.queue.impl.single.StoreTailer.endOfCycle(StoreTailer.java:323)
> at
> net.openhft.chronicle.queue.impl.single.StoreTailer.next0(StoreTailer.java:295)
> at
> net.openhft.chronicle.queue.impl.single.StoreTailer.readingDocument(StoreTailer.java:202)
> at
> net.openhft.chronicle.queue.impl.single.StoreTailer.readDocument(StoreTailer.java:108)
> at
> org.apache.cassandra.utils.binlog.BinLogTest.readBinLogRecords(BinLogTest.java:481)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
