[
https://issues.apache.org/jira/browse/NIFI-16339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18116969#comment-18116969
]
ASF subversion and git services commented on NIFI-16339:
--------------------------------------------------------
Commit 49628d70c03dcc096d2f807e2791e363b674fb5e in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=49628d70c03 ]
NIFI-16339 Improved stability of PythonNarDeletionDuringInitIT (#11697)
> Make Processor Type Discovery Test Deterministic
> ------------------------------------------------
>
> Key: NIFI-16339
> URL: https://issues.apache.org/jira/browse/NIFI-16339
> Project: Apache NiFi
> Issue Type: Test
> Components: Core Framework
> Affects Versions: 2.11.0
> Reporter: Alexander Bij
> Assignee: David Handermann
> Priority: Minor
> Labels: test-flaky
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> I'm seeing build failures caused by timing-sensitive race conditions in
> tests. They
> intermittently fail CI on unrelated pull requests, forcing maintainers to
> re-run jobs.
> h3. Affected tests
> *PythonNarDeletionDuringInitIT.testNarReuploadAfterForceDeleteDuringInit*
> After a NAR is re-uploaded and reaches INSTALLED, the processor type may not
> be immediately
> visible. The test can fail if it asserts the type is available too early.
> h3. Expected behavior
> - Processor type discovery should be allowed a short time to catch up after
> NAR re-upload.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
