-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[R-package] warning on R-devel with clang 15: 'format string is not a string literal' #6212
Comments
This is now being reported as a WARNING on the project's CRAN page as well. https://cran.r-project.org/web/checks/check_results_lightgbm.html I will try to put up a PR this week. @shiyu1994 if you get any emails from CRAN about this, please post them here. |
Running
That helped to narrow down where the issue was. It appears to be what's discussed over in llvm/llvm-project#56583. As described in llvm/llvm-project#56583 (comment) specifically, something like
LightGBM/R-package/src/lightgbm_R.cpp Line 31 in 2ee3ec8
LightGBM/R-package/src/lightgbm_R.cpp Line 43 in 2ee3ec8
I put up #6216 with changes that'll hopefully fix that. I'll move it out of draft if CI passes. |
Description
With latest R-devel (
R Under development (unstable) (2023-11-24 r85626)
) +clang
15.0.7,R CMD check
raises the following WARNING.full logs (click me)
Reproducible example
See the latest
r-package (debian, R-devel, clang)
CI job run onmaster
(build link).That can be reproduced using this configuration:
LightGBM/.github/workflows/r_package.yml
Lines 260 to 265 in 2ee3ec8
Environment info
LightGBM version or commit hash: 2ee3ec8
Additional Comments
This would likely lead to a rejection of a new submission on CRAN.
It will also cause CI failures in this repo until it's either fixed or until we temporarily allow that WARNING in CI.
All of the lines noted in warnings are uses of the
R_API_END()
preprocessor macroLightGBM/R-package/src/lightgbm_R.cpp
Line 159 in 2ee3ec8
which looks like this:
LightGBM/R-package/src/lightgbm_R.cpp
Lines 38 to 44 in 2ee3ec8
The text was updated successfully, but these errors were encountered: