You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Gabor Gyimesi (Jira)" <ji...@apache.org> on 2021/06/02 08:50:00 UTC
[jira] [Resolved] (MINIFICPP-1562) Failing CI due to corrupted
cache on Windows-2019
[ https://issues.apache.org/jira/browse/MINIFICPP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gabor Gyimesi resolved MINIFICPP-1562.
--------------------------------------
Resolution: Fixed
> Failing CI due to corrupted cache on Windows-2019
> -------------------------------------------------
>
> Key: MINIFICPP-1562
> URL: https://issues.apache.org/jira/browse/MINIFICPP-1562
> Project: Apache NiFi MiNiFi C++
> Issue Type: Bug
> Reporter: Martin Zink
> Assignee: Gabor Gyimesi
> Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> The windows-vs2019 CI is failing due to corrupted clcache.
> Unfortunetly github doesnt have clean way to clear the cache.
> {code:java}
> GitHub will remove any cache entries that have not been accessed in over 7 days. There is no limit on the number of caches you can store, but the total size of all caches in a repository is limited to 5 GB. If you exceed this limit, GitHub will save your cache but will begin evicting caches until the total size is less than 5 GB.
> {code}
> But since the cache is used I dont think github will clear it.
> A quick and dirty fix is: if we were to change the key in the .github/ci.yml file, it would fix the issue.
> [https://github.community/t/how-to-clear-cache-in-github-actions/129038/3]
> If this issue comes up again maybe we could implement a workflow that clears the caches, with [https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)