[
https://issues.apache.org/jira/browse/NIFI-11591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726428#comment-17726428
]
ASF subversion and git services commented on NIFI-11591:
--------------------------------------------------------
Commit 9f61b5f957e0389d4929fd7f4e9fd83521bcd4c5 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=9f61b5f957 ]
NIFI-11591 Improved stability of DynamicallyClassPath and AsyncCommitCallback
tests
After terminating Processor in DynamicallyModifiedClasspathIT system test, keep
trying to empty queue until successful instead of assuming success after the
first iteration.
When writing to a replacement file in AsyncCommitCallbackIT, write to a temp
file and then rename. This prevents the processor from picking up the file
while it's still being written.
This closes #7302
Signed-off-by: David Handermann <[email protected]>
> Address failing system tests
> ----------------------------
>
> Key: NIFI-11591
> URL: https://issues.apache.org/jira/browse/NIFI-11591
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework, Tools and Build
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 2.0.0, 1.22.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We've been seeing intermittent failures in the following system tests:
> - DynamicClasspathModificationIT
> - RegistryClientIT#testControllerServiceUpdateWhileRunning
> - ClusteredRegistryClientIT#testControllerServiceUpdateWhileRunning
> Additionally, NIFI-11557 introduced a surefire-report step in the system
> tests to attempt to capture more logs from failures, but that step is not
> working as expected and additionally it appears that the log output from the
> tests themselves is already captured into the diagnostic dump that is
> included.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
