You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@arrow.apache.org by "kou (via GitHub)" <gi...@apache.org> on 2023/06/17 20:54:47 UTC

[GitHub] [arrow] kou opened a new issue, #36148: [CI][C++] Should we run IWYU check as CI

kou opened a new issue, #36148:
URL: https://github.com/apache/arrow/issues/36148

   ### Describe the enhancement requested
   
   Our lint CI job disables IWYU check explicitly: https://github.com/apache/arrow/blob/10e2090cec66a90a2a5a12b53983adaae6ce99dc/docker-compose.yml#L1769
   
   If we run IWYU check manually by `ninja iwyu`, we get a very long report.
   
   Should we run IWYU check periodically and maintain our `#include`? Or should we abandon maintain our `#include` with IWYU?
   
   Note that `ninja iwyu` is slow. So we may want to use nightly CI or push to main only CI instead of PR CI.
   
   ### Component(s)
   
   C++, Continuous Integration


-- 
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: issues-unsubscribe@arrow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org