You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "Amichai Rothman (Jira)" <ji...@apache.org> on 2021/02/08 16:00:00 UTC
[jira] [Commented] (ZOOKEEPER-4204) Flaky test -
RequestPathMetricsCollectorTest.testMultiThreadPerf
[ https://issues.apache.org/jira/browse/ZOOKEEPER-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17281162#comment-17281162 ]
Amichai Rothman commented on ZOOKEEPER-4204:
--------------------------------------------
Just noticed it happened also e.g. here [https://ci-hadoop.apache.org/blue/organizations/jenkins/zookeeper-precommit-github-pr/detail/PR-1594/1/pipeline]
So it's not just me :)
> Flaky test - RequestPathMetricsCollectorTest.testMultiThreadPerf
> ----------------------------------------------------------------
>
> Key: ZOOKEEPER-4204
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4204
> Project: ZooKeeper
> Issue Type: Bug
> Components: tests
> Affects Versions: 3.8.0
> Reporter: Amichai Rothman
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This test sometimes fails on a laptop. Timed performance tests in unit tests can be problematic in general due to the variety of hardware it might run on, but I have a little fix that reduces the test overhead and tightens the timing, so it's a good first step (and works for me).
>
> org.opentest4j.AssertionFailedError: expected: <true> but was: <false>
> at org.apache.zookeeper.server.util.RequestPathMetricsCollectorTest.testMultiThreadPerf(RequestPathMetricsCollectorTest.java:448)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)