[
https://issues.apache.org/jira/browse/ARROW-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552135#comment-17552135
]
Jacob Wujciak-Jens commented on ARROW-16794:
--------------------------------------------
Hm, the timeout seems to be set pretty tight as even if [ccache
hits|https://github.com/apache/arrow/runs/6782212921?check_suite_focus=true#step:7:57]
the mingw job needs 40-58 minutes to finish. Other than improving caching I am
not sure what we can do (for now) to improve this, as we are locked into the
runner hardware with only 2 cores. So I think it would make sense to increase
the timeout to prevent jobs from failing because of that.
I do think that the key for the ccache-cache is set to restrictive {{key:
cpp-ccache-mingw$\{\{ matrix.mingw-n-bits \}\}-$\{\{ hashFiles('cpp/**')\}\}}}
as it will miss on any change in the cpp dir. Maybe my understanding of ccache
is wrong but isn't invalidating the cached version of changed source files part
of ccache's function?
> [CI][C++] MinGW builds sometimes time out
> -----------------------------------------
>
> Key: ARROW-16794
> URL: https://issues.apache.org/jira/browse/ARROW-16794
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++, Continuous Integration
> Reporter: Antoine Pitrou
> Priority: Major
>
> When ccache is cold, the MinGW builds sometimes exceed the (large) 55 minutes
> timeout:
> https://github.com/apache/arrow/runs/6806190892?check_suite_focus=true
> C++ compile times have always been a concern on CI, but it may only grow as
> the codebase expands.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
