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

Ferenc Gerlits commented on MINIFICPP-2305:
-------------------------------------------

Another failure of the same kind on macos: 
https://github.com/apache/nifi-minifi-cpp/actions/runs/8894224658/job/24422028589?pr=1771

{noformat}
Error: 4-30 12:37:34.731] 
[org::apache::nifi::minifi::core::flow::AdaptiveConfiguration] [error] Error 
while processing configuration file: Unable to parse configuration file as none 
of the possible required fields [Flow Controller] is available [in '' section 
of configuration file]
libc++abi: terminating due to uncaught exception of type std::invalid_argument: 
Unable to parse configuration file as none of the possible required fields 
[Flow Controller] is available [in '' section of configuration file]
{noformat}


> C2VerifyHeartbeatAndStopSecure test transiently fails in CI
> -----------------------------------------------------------
>
>                 Key: MINIFICPP-2305
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-2305
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: Improvement
>            Reporter: Gábor Gyimesi
>            Priority: Major
>         Attachments: C2VerifyHeartbeatAndStopSecure_failure.log
>
>
> C2VerifyHeartbeatAndStopSecure sometimes fails in CI:
> {code:java}
> Error: 2-23 14:39:39.239] 
> [org::apache::nifi::minifi::core::flow::AdaptiveConfiguration] [error] Error 
> while processing configuration file: Unable to parse configuration file as 
> none of the possible required fields [Flow Controller] is available [in '' 
> section of configuration file]
> terminate called after throwing an instance of 'std::invalid_argument'
>   what():  Unable to parse configuration file as none of the possible 
> required fields [Flow Controller] is available [in '' section of 
> configuration file] {code}
> More info in the attached logs.



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

Reply via email to