You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Alexey Serbin (JIRA)" <ji...@apache.org> on 2017/06/19 21:07:00 UTC
[jira] [Assigned] (KUDU-2042) Flakiness in raft_consensus-itest due
to no process to resume
[ https://issues.apache.org/jira/browse/KUDU-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Serbin reassigned KUDU-2042:
-----------------------------------
Assignee: Alexey Serbin
> Flakiness in raft_consensus-itest due to no process to resume
> --------------------------------------------------------------
>
> Key: KUDU-2042
> URL: https://issues.apache.org/jira/browse/KUDU-2042
> Project: Kudu
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Alexey Serbin
> Assignee: Alexey Serbin
>
> Commit 86116e4 has surfaced a source of flakiness in {{raft_consensus-itest}} where there's no process to resume.
> [~adar] reported 3 failures in 1000 run with messages like:
> {noformat}
> Check failed: _s.ok() Bad status: Illegal state: Request to resume '/tmp/run_tha_testp3dlYu/build/debug/bin/kudu-tserver' but the process is not there
> {noformat}
> The link for the flakiness stats of the {{raft_consensus-itest}}:
> http://dist-test.cloudera.org:8080/test_drilldown?test_name=raft_consensus-itest
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)