lordgamez opened a new pull request #1078: URL: https://github.com/apache/nifi-minifi-cpp/pull/1078
The clcache object invalidation caused failures in the Github Actions Windows-VS2019 job previously which reappeared in run https://github.com/apache/nifi-minifi-cpp/runs/2628922164?check_suite_focus=true with the restore key: windows-vs2019-clcache-refs/heads/main-63f6e716f74f0936fc38b755eea23f83b481044c Amending the PR by adding the CLCACHE_NODIRECT option to the job made the next run succeed with the same restore key: https://github.com/apache/nifi-minifi-cpp/runs/2630706634?check_suite_focus=true Description of the option: > **CLCACHE_NODIRECT** > Disable direct mode. If this variable is set, clcache will always run preprocessor on source file and will hash preprocessor output to get cache key. Use this if you experience problems with direct mode or if you need built-in macroses like _TIME_ to work correctly. -------------------------------------------------- Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [ ] Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [ ] Has your PR been rebased against the latest commit within the target branch (typically main)? - [ ] Is your initial contribution a single, squashed commit? ### For code changes: - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the LICENSE file? - [ ] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible. -- 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. For queries about this service, please contact Infrastructure at: [email protected]
