james94 commented on PR #1857:
URL: https://github.com/apache/nifi-minifi-cpp/pull/1857#issuecomment-2300298687

   @szaszm @lordgamez  For **MacOSX CI/CD**, out of 268, **one** of the **tests 
fail: C2VerifyHeartbeatAndStop.cpp** after this PR was merged into MiNiFi C++ 
main branch:
   
   ~~~bash
   Error: 8-20 03:35:36.872] 
[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]
   Randomness seeded to: 2401196312
   
   
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   C2VerifyHeartbeatAndStop is a Catch2 v3.4.0 host application.
   Run with -? for options
   
   
-------------------------------------------------------------------------------
   Verify C2 heartbeat and stop operation
   
-------------------------------------------------------------------------------
   
/Users/runner/work/nifi-minifi-cpp/nifi-minifi-cpp/libminifi/test/integration/C2VerifyHeartbeatAndStop.cpp:54
   
...............................................................................
   
   
/Users/runner/work/nifi-minifi-cpp/nifi-minifi-cpp/libminifi/test/integration/C2VerifyHeartbeatAndStop.cpp:61:
 FAILED:
   due to unexpected exception with message:
     Unable to parse configuration file as none of the possible required fields
     [Flow Controller] is available [in '' section of configuration file]
   
   
===============================================================================
   test cases:  1 |  0 passed | 1 failed
   assertions: 85 | 84 passed | 1 failed
   ~~~
   
   - MacOSX CI/CD Error: 
https://github.com/apache/nifi-minifi-cpp/actions/runs/10464498844/job/28978198432


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to