[
https://issues.apache.org/jira/browse/KUDU-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17874970#comment-17874970
]
ASF subversion and git services commented on KUDU-3462:
-------------------------------------------------------
Commit 145d34b11bc6d0d91401d237bf021d37c3e51632 in kudu's branch
refs/heads/master from Yingchun Lai
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=145d34b11 ]
KUDU-3462 [UT] Fix a flaky test in log_block_manager-test
This patch improves the determinacy of test
TestContainerBlockLimitingByMetadataSizeWithCompaction,
also adds some comments to explain the reason.
Change-Id: I913d99a6bbbfb16df1d1730701cab09222fc5c8c
Reviewed-on: http://gerrit.cloudera.org:8080/21686
Tested-by: Yingchun Lai <[email protected]>
Reviewed-by: Alexey Serbin <[email protected]>
> LogBlockManagerTest.TestContainerBlockLimitingByMetadataSizeWithCompaction
> sometimes fails
> ------------------------------------------------------------------------------------------
>
> Key: KUDU-3462
> URL: https://issues.apache.org/jira/browse/KUDU-3462
> Project: Kudu
> Issue Type: Bug
> Components: test
> Affects Versions: 1.17.0
> Reporter: Alexey Serbin
> Priority: Minor
> Attachments: log_block_manager-test.txt.xz
>
>
> The TestContainerBlockLimitingByMetadataSizeWithCompaction scenario of the
> LogBlockManagerTest sometimes fails with messages like the following:
> {noformat}
> src/kudu/fs/log_block_manager-test.cc:1343: Failure
> Expected: (FLAGS_log_container_metadata_max_size *
> FLAGS_log_container_metadata_size_before_compact_ratio) >= (file_size),
> actual: 26214.4 vs 31565
> {noformat}
> I'm attaching the full log generated by one of the pre-commit test runs
> (ASAN).
> To reproduce the flakiness, build the test in ASAN configuration and run the
> scenario with the {{\-\-stress_cpu_threads=16}} extra flag.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
