You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/04/05 13:58:00 UTC

[jira] [Updated] (ZOOKEEPER-4511) Flaky test: FileTxnSnapLogMetricsTest.testFileTxnSnapLogMetrics

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

ASF GitHub Bot updated ZOOKEEPER-4511:
--------------------------------------
    Labels: pull-request-available  (was: )

> Flaky test: FileTxnSnapLogMetricsTest.testFileTxnSnapLogMetrics
> ---------------------------------------------------------------
>
>                 Key: ZOOKEEPER-4511
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4511
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: tests
>            Reporter: Kezhu Wang
>            Assignee: Kezhu Wang
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> * https://github.com/kezhuw/zookeeper/runs/5830250287?check_suite_focus=true
> * https://github.com/apache/zookeeper/runs/5759834147?check_suite_focus=true
> {code:none}
> org.opentest4j.AssertionFailedError: expected: <1> but was: <0>
> 	at org.apache.zookeeper.server.persistence.FileTxnSnapLogMetricsTest.testFileTxnSnapLogMetrics(FileTxnSnapLogMetricsTest.java:86)
> {code}
> This test tries to write some txns to trigger snapshot with remaning txns in txn log. But snapshot taking is asynchronous, thus all txns could be written to snapshot. So in restarting, it is possible that no txns to load after snapshot restored. This will fail assertion.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)