[
https://issues.apache.org/jira/browse/FLINK-15318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17128915#comment-17128915
]
Robert Metzger commented on FLINK-15318:
----------------------------------------
I don't really have an opinion here, because I'm not very familiar with the
RocksDB code. Let's wait for Stephan's response.
Another case in {{[ERROR]
RocksDBPerformanceTest.testRocksDbRangeGetPerformance:146 ยป TestTimedOut test
...}}:
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=2973&view=logs&j=3b6ec2fd-a816-5e75-c775-06fb87cb6670&t=2aff8966-346f-518f-e6ce-de64002a5034
> RocksDBWriteBatchPerformanceTest.benchMark fails on ppc64le
> -----------------------------------------------------------
>
> Key: FLINK-15318
> URL: https://issues.apache.org/jira/browse/FLINK-15318
> Project: Flink
> Issue Type: Bug
> Components: Benchmarks, Runtime / State Backends
> Environment: arch: ppc64le
> os: rhel7.6, ubuntu 18.04
> jdk: 8, 11
> mvn: 3.3.9, 3.6.2
> Reporter: Siddhesh Ghadi
> Priority: Major
> Attachments: surefire-report.txt
>
>
> RocksDBWriteBatchPerformanceTest.benchMark fails due to TestTimedOut, however
> when test-timeout is increased from 2s to 5s in
> org/apache/flink/contrib/streaming/state/benchmark/RocksDBWriteBatchPerformanceTest.java:75,
> it passes. Is this acceptable solution?
> Note: Tests are ran inside a container.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
