You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2025/07/15 02:54:00 UTC

[jira] [Commented] (NIFI-14747) Consume Kinesis Record Tests can timeout and fail intermittently

    [ https://issues.apache.org/jira/browse/NIFI-14747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18005280#comment-18005280 ] 

ASF subversion and git services commented on NIFI-14747:
--------------------------------------------------------

Commit b77991b6162d873b6e98e913854c9d1fc17aa1a6 in nifi's branch refs/heads/main from Dariusz Seweryn
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b77991b616 ]

NIFI-14747 Set Test Kinesis Record Processor Timeout to 5 seconds (#10088)

Signed-off-by: David Handermann <ex...@apache.org>

> Consume Kinesis Record Tests can timeout and fail intermittently
> ----------------------------------------------------------------
>
>                 Key: NIFI-14747
>                 URL: https://issues.apache.org/jira/browse/NIFI-14747
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 2.4.0
>            Reporter: Dariusz Seweryn
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Concurrency tests can timeout in the wild:
> TestStandardRecordProcessorBlocker$TimeoutBlock.testBlockAndUnblock -- Time elapsed: 1.004 s <<< ERROR!
>  
> Example failure: [https://github.com/apache/nifi/actions/runs/16235438475/job/45858126249?pr=10053]
>  
> Apparently 1 second is not enough as seen in the above case. Lets bump the timeout period from 1 to 5 seconds — this should significantly reduce the probability of flakiness. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)